From Problem to Product: My Go-To Framework for Building the Right Thing

Over the years, I've developed and refined a process to help me zero in on the right product and scope before building anything. Whether I'm leading product at a startup or spinning up a side project, I rely on this framework to stay grounded in real problems, avoid unnecessary complexity, and build something people actually want. Here's a high-level walkthrough of how I approach new product development—plus the tools I rely on to bring ideas to life.

1. Start with the problem

Before thinking about features or roadmaps, I start with the pain point. What's the actual problem we're trying to solve? How does it show up in someone's daily experience? Who is most affected by it, and why would they care about a solution?

This early stage is about curiosity and empathy. I talk to users, gather anecdotes, and immerse myself in the problem space. The better you can articulate the problem in plain language, the easier it will be to design a solution that sticks.

2. Use "how might we" questions to explore solutions

Once the problem is clear, I shift into a solution space using "How might we…" statements. This opens up creative thinking without locking us into one path too early. From there, I try to validate solution ideas through multiple lenses: user research, market trends, competitor audits, and usage data (when available).

One common pitfall is defaulting to the first idea that sounds good or seems technically feasible. Fight that urge. Push yourself to explore a range of options—including non-technical or operational ones—before committing to a build. Even if you're excited about an AI-based solution (which is fair!), it's worth pressure-testing your assumptions before you go deep.

3. Prototype early and often

I'm a big believer in designing early prototypes—wireframes, clickable flows, low-fidelity mockups, whatever helps bring the experience to life. Tools like Figma make this incredibly fast and accessible, even if you're not a designer by trade.

This step helps me visualize how a solution might work in the real world. It's also way easier for users and teammates to give useful feedback on something they can see and interact with rather than react to a verbal concept. You'll catch confusing flows, unclear copy, or even misaligned assumptions much faster this way.

4. Define success metrics (and know the difference between input vs. output)

It's critical to establish clear, measurable success metrics before you launch anything. I always define both:

• Input metrics — things you can more directly influence (e.g., click-through rates, % of users who complete a step, number of visits)
• Output metrics — outcomes that matter, but are harder to move directly (e.g., increased retention, revenue lift, conversion rates)

Input metrics are especially important in early development when you're still learning what works. Output metrics will follow, but they take longer to materialize. Set ambitious but focused goals, and make sure you're checking progress against them consistently.

5. Build scrappy MVPs and ship fast

I've learned (the hard way) that spending months building a polished product before getting feedback is almost always a mistake. Instead, I focus on delivering incremental value fast. A functional prototype or lightweight version of your idea—plus basic analytics via a tool like Mixpanel—can tell you:

• Are people using it?
• How are they using it?
• Where are they getting stuck?
• What's resonating?

Pair that usage data with qualitative feedback from user interviews or surveys, and you'll be in a much better position to iterate quickly and build something that actually delivers on the original problem.

6. Build relationships with super users

If you notice a few people engaging with your product more deeply or more frequently than others, reach out. These early adopters are gold. They'll give you honest feedback, share what's working (and what's not), and help guide product decisions as you evolve.

Make it a two-way relationship: offer sneak peeks, ask for feedback, and make sure they feel heard. These users often become your strongest advocates down the line.

7. My favorite tools right now

• Figma – I've been evangelizing Figma for nearly a decade. It's free to start, packed with community templates/components, and perfect for everything from wireframes to prototypes.
• v0 by Vercel – An AI-assisted coding tool I use for personal projects. Great for fast iteration and basic integrations.
• usertesting.com – A go-to for structured user testing, especially when you have clickable prototypes and want targeted feedback at scale.

Final thoughts

Every product journey is unique, but this framework helps me stay focused on what matters: solving real problems for real people. It forces me to stay scrappy, stay curious, and continuously learn from the people I'm building for.

If you're feeling stuck or unsure about what to build next, start with the problem. Everything good grows from there.