Identify an opportunity

✅ Let’s define the challenge ahead

You’ve got a spark — maybe a frustration, a “wouldn’t it be cool if…”, or a pattern you’ve noticed in your industry. This first stage is where you turn that spark into something worth exploring. Before diving into ideas, it's vital to step back and ask: is this the right problem to solve?

Think of this like choosing which hill to climb before you start hiking. Get this choice wrong, and even the best solution will lead you to the wrong summit.


📘 What you’ll learn

  • How to spot a real-world problem worth solving
  • Why unmet needs are better starting points than ready-made ideas
  • Ways to define an opportunity without jumping to solutions
  • How to scope your innovation energy wisely

🛠️ Tools and methods

  • Observation log – jot down problems or patterns you encounter
  • Pain point mapping – sketch out frustrations customers or teams face
  • Opportunity checklist – check for urgency, relevance, and value alignment
  • Reverse brainstorming – flip assumptions to uncover fresh directions
  • Jobs-to-be-Done thinking – focus on what people are trying to achieve

⚠️ Watch-outs

(and how to overcome them)

  • Don’t confuse ideas with opportunities

    A product idea isn’t an opportunity until you know who it helps and why it matters.

  • Avoid jumping to solutions

    Pause before solving. Great ideas often emerge when you sit longer with the problem.

  • Don’t assume your problem is unique

    Check if others are already tackling it — and how well they’re doing.

Examples of weak vs strong opportunity framing.

❌ Weak opportunity framing

  • “Build an app that tracks when people water their plants.”

    → Jumps to solution, no clear problem or user.

  • “Create a smart fridge with voice control.”

    → Tech-first idea with no real user need explored.

  • “Make a new type of ergonomic office chair.”

    → Assumes a solution without defining whose problem it's solving.


✅ Strong opportunity framing

  • “People in small flats struggle to keep indoor plants alive due to inconsistent lighting and unpredictable schedules.”

    → Defines a real, recurring user problem.

  • “Busy professionals often forget food expiry dates, leading to waste and cost.”

    → Clear pain point with potential value in solving it.

  • “Remote workers report back pain after long workdays, especially without access to high-end seating.”

    → Specific group, defined need, room for creative responses.


💡 Tips from the field

“We used to chase every idea that felt exciting. Once we started pausing to frame the opportunity, our hit rate skyrocketed.”

– Hardware Product Lead, IEN Community

  • Seen it before: Many teams leap into development too early. Pausing to validate the problem leads to stronger products later.
  • Early signals help: If three customers mention the same friction point, it’s worth a closer look.

🔗 Helpful links & resources


✍️ Quick self-check

Have you written your opportunity in plain, problem-first language?
Can you explain who this affects and why it matters?
Have you avoided jumping to “solution mode” too soon?
Is there evidence (even anecdotal) that this is a recurring issue?

✅ Score 3 or more = ready to move forward.