A Three-Step Framework For Solving Problems 👌
Jun 2019
Everyone on your team has a unique version of the problem in their heads. The larger and more complex the project, the more likely they are different. Your job is to eradicate this misalignment early by making the implicit explicit—opening up the wrapper so everyone agrees on what's inside.
Related
Ideas from across Lenny's archive that connect to this one
What Seven Years at Airbnb Taught Me About Building a Business
Jun 2019Simple projects with vague problem statements circle for weeks; complex projects with strong problem statements sail smoothly. Crystallizing the problem you're solving is the single most important step before solving anything. Misalignment on the problem is invisible waste.
A Three-Step Framework For Solving Problems 👌
Jun 2019Resist the urge to jump to a solution early. A strong problem statement references an unfulfilled need, includes both what and why, is focused enough for one team to own, and can be expressed in a single sentence. The more you need to explain it, the less clear the problem actually is.
A Three-Step Framework For Solving Problems 👌
Jun 2019Nothing helps reduce scope creep more than repeatedly coming back to the problem statement and success metrics. As projects grow in complexity, teams naturally drift from the original intent. The antidote is a simple habit: review the problem statement in every design review, every stakeholder update, and before finalizing any work.
This Week #0: Advice on growth, product, and leadership
Sep 2019If you ask anyone on your team what your strategy is, would they be able to explain it? If not, your strategy isn't clear enough. A strategy that only lives in the PM's head isn't a strategy—it's a secret.
Gokul Rajaram on designing your product development process, when and how to hire your first PM, a playbook for hiring leaders, getting ahead in you career, how to get started angel investing, more
Jun 2022The biggest pitfall is founders becoming too tactical and dictating features instead of presenting problems. Present the goal—'increase weekly usage from 2x to 5x'—and let the team brainstorm solutions. This creates ownership and prevents the feature factory trap.
Import your highlights, and we'll find the connections you've been missing.