We often treat “innovation” as a mysterious lightning bolt that only strikes a lone genius. But in my final semester of engineering, I learned that a good idea isn’t a single “thing”—it’s a network.

As author Steven Johnson argues in Where Good Ideas Come From, ideas are built from the “collision” of different hunches. My own journey started with a casual conversation, a famous founder’s struggle, and a deep personal regret.

1. The catalyst: Phanindra Sama’s “bad day”

In 2012, I was finishing my degree. My brother and I were having a casual chat when he told me about a guest lecture he’d attended by Phanindra Sama, the co-founder of RedBus. Phanindra’s story was deceptively human:

• The Friction: Years earlier, he wanted to go home for Diwali but couldn’t book a bus ticket because he was stuck at work. He spent his holiday frustrated and stranded, running between travel agents at the last minute.
• The Spark: He realized the problem wasn’t a lack of buses; it was a lack of information transparency.

This story stayed with me for a month. In Steven Johnson’s terms, this was a “Slow Hunch.” I wasn’t looking for a business yet; I was just letting the simplicity of his solution—solving a personal “bad day” with technology—marinate in my mind.

2. The collision: Revisiting a four-year-old regret

Johnson argues that “The trick to having good ideas is to get more parts on the table.” After a month of thinking about RedBus, Phanindra’s “part” collided with a “part” of my own history from 2008.

That year, I had finished my entrance exams (EAMCET and BITSAT). BITS Hyderabad was just launching its inaugural year. I sought advice from a lecturer, but he was unaware that the Hyderabad campus even existed and suggested I stick to a local college.

The Result: I took his advice. A year later, a close friend confirmed that with my score, I would have easily secured an IT seat at BITS Hyderabad. My life trajectory had been altered simply because I lacked the right suggestion at the right time.

3. The architecture of the idea

By 2012, my 2008 regret was no longer just a sad memory—it was a data gap waiting for a bridge. If Phanindra could solve bus seat availability, why couldn’t I solve “future availability” for students? I teamed up with three friends to build a “Decision Engine” for students:

• The Decision Engine: We aggregated 10+ years of cutoff data and wrote an algorithm to find the best-suited college for a student’s specific rank and criteria.
• The Support Layer: We mapped out hostels around those colleges to solve the “where do I live?” problem before it even started.
• The Social Safety Net: We collected statewide scholarship information to ensure that financial status wouldn’t be the barrier that stopped a talented student.
• The Scalability Goal: Our roadmap was to expand beyond engineering to degree colleges and professional courses across all of India, replacing hearsay with data.

4. The afterlife of an idea: No hunch is ever wasted

In the end, we didn’t make it live. We moved on to other projects, but the experience permanently rewired my mindset. Steven Johnson describes the “adjacent possible” as a shadow future—a map of how the present can reinvent itself if we just look at the gaps.

As Johnson writes:

“If we want to understand where good ideas come from, we have to move away from the myth of the ‘Eureka’ moment and realize that they are a collective swarm.”

This project was my entry into that swarm. It proved that you don’t need a stroke of genius to innovate. You just need the willingness to connect your frustrations with the tools available to you.

Don’t wait for a spark; start building the network