For most of my career, I’ve prided myself on being a problem-solver. See a challenge, throw a solution at it. Move fast. Build things. Iterate. Ship. But this module stopped me in my tracks. It made me realize that the real work of innovation starts not with a clever idea or a shiny solution, but with the discipline to sit with a challenge and understand it deeply.

Here are my key takeaways, along with some personal reflections:

Don’t Jump to the Solution

As technologists, we’re often wired to solve problems fast. I’ve definitely been guilty of hearing someone mention a business pain point and immediately saying, “Oh, we can fix that with X!”

One of the tools we used was a simple but powerful framing:

How might we [do something] for [someone] so that [outcome happens]? For example:
How might we improve customer onboarding for small businesses so that support tickets drop by 30%?

That one line forces clarity. It makes sure you’re not just building something cool, but something truly valuable, for the right people, with the right result in mind.

Use a Canvas, Not a Crystal Ball

We used something called a business canvas, a structured framework to help capture everything about the innovation journey. Think of it like a digital whiteboard or a living playbook.

This wasn’t about filling boxes for the sake of it. It actually gave me a way to map out stakeholders, benefits, personas, financial impact, and strategic alignment, all in one place.

The best part? It’s alive. The canvas isn’t a one-off exercise; it’s a tool I can update as the project evolves. I realized this is something I can start using on real projects immediately, not just theoretical ones.

Passion + Strategy = The Right Challenge

One thing that really stood out for me was how much emphasis was put on picking the right challenge. Not just any problem, but one that:

• Aligns with business strategy
• Delivers real value
• Has support from leadership
• Gets me fired up to work on it

That last point surprised me. I always thought of innovation as purely a corporate responsibility, but I now see how important personal motivation is. If I don’t care deeply about the problem, I’m unlikely to push through the messy parts of innovation.

Be a Detective, Not a Genius

Once I picked my challenge, the next step was investigation.

This is where the real magic happens. I learned to ask:

• Why does this problem even exist?
• Why hasn’t it been solved before?
• Who is impacted, and how?
• What workarounds are currently in place?
• What’s the real cost of doing nothing?

I started having conversations, real ones, with users, colleagues, and stakeholders. And guess what? I learned things that completely changed how I originally saw the problem.

The course instructor called it “being a detective,” and I love that metaphor. Great innovation doesn’t come from being a genius with groundbreaking ideas, it comes from being a curious listener who follows the evidence.

Personas Aren’t Fluff. They’re Your Reality Check.

I’ve used personas before in design thinking sessions, but I usually treated them like just another box to tick. This time, I did it properly.

I built a full persona, outlining:

• Who they are
• What frustrates them
• What motivates them
• How they think and behave
• Even what their hobbies are

I added a real photo and gave them a name. Suddenly, the challenge wasn’t abstract anymore. It was about helping Priya, a product manager drowning in manual reports every Monday morning.

From then on, everything I thought about, every feature, every process, had to make sense to Priya. And if it didn’t, it had to go.

Get Your Sponsor, or You’ll Be Stuck

Here’s something that really hit home: the #1 reason innovation projects fail is the lack of the right sponsor.

Not budget. Not time. Not tech. But not having someone senior who cares whether you succeed and has the influence to clear roadblocks.

I mapped out all my stakeholders, categorized them as supporters or detractors, and rated their influence. That visual map alone was worth the exercise. I now know exactly who to engage, who to win over, and who could potentially block me if I’m not careful.

Learning from Failure (Someone Else’s)

We also heard the inspiring story of Dr. Millicent Stone, a doctor turned health-tech entrepreneur. She shared how her first product failed to resonate because they never talked to the right users, nurses, in her case.

It was a powerful reminder that discovery doesn’t stop after week one. It’s ongoing. And if you only build for people like you, you’ll probably miss what really matters.

Define the Challenge Like a Pro

At the end of this process, I pulled together everything I’d learned and refined my original challenge. And guess what? It wasn’t quite the same as what I started with.

That’s the whole point. By taking the time to investigate, build empathy, and understand the system, I was able to define a much better problem statement, and feel way more confident in the path forward.

Final Thoughts

This module truly reminded me that innovation isn’t about flashy ideas, it’s about focus, empathy, and influence.

If you’re leading a product, a team, or a company, here’s my advice:

Slow down. Define the challenge. Investigate it deeply. Listen to your users. Build internal allies. And only then start thinking about your solution.

I wish I’d learned this years ago.