Creative Thinking Prompts for Product Managers

The fact that your team keeps landing on the same obvious solutions usually isn’t a creativity problem—it’s a framing problem. When a roadmap discussion starts with "How do we improve X?" or "What should we build for Y?", the brain naturally defaults to the most available memory: the competitor’s feature or the last feature you built. Here are five practical, PM-specific techniques to force divergent thinking before you converge on a roadmap. ### 1. Reframe the problem as a "Job to be Done" or a "Progress-Making" statement Obvious solutions happen when the problem is too broad or too solution-oriented. - **Instead of:** "How do we improve our dashboard?" - **Try:** "When does a user currently feel the need to check our dashboard, and what are they actually trying to accomplish in their physical world at that moment?" **The Exercise:** Write the problem as a "How Might We" (HMW) statement, but ban any features from the sentence. - *Bad HMW:* "HMW build a better notification system?" - *Good HMW:* "HMW ensure users feel confident they haven’t missed a critical update without having to log in daily?" ### 2. The "Opposite Day" / Assumption Reversal This is a lateral thinking technique that forces the brain out of its ruts. List all the assumptions you have about the problem, then reverse them. - **Assumption:** The user must create an account to save their work. - **Reversal:** The user can save their work without ever creating an account. - **Assumption:** The dashboard needs to be highly detailed and data-rich. - **Reversal:** The dashboard shows *zero* data unless there is an anomaly. **The Exercise:** Have the team brainstorm ways to accomplish the goal by specifically *breaking* your current constraints. Even if the ideas are unshippable, they usually reveal a hidden desire (e.g., users don’t want accounts, they just want their data synced). ### 3. Analogous Inspiration (Steal from a different industry) If you are building B2B SaaS, stop looking at B2B SaaS. The best way to avoid the obvious is to look at a completely different domain that solves a similar emotional or functional need. - **If you are solving:** "How do we onboard users quickly?" - **Look at:** How does a video game teach you controls in the first 60 seconds without a manual? - **If you are solving:** "How do we surface complex data?" - **Look at:** How does a car dashboard communicate "check engine" without showing you the engine’s code? **The Exercise:** Bring a "Show and Tell" segment to your roadmap meeting. Every team member brings one example of a great solution from a non-software domain and explains how the mechanism could map to your product. ### 4. The "Kill Your Darlings" / Subtraction Method If you keep landing on the same solution (e.g., "We need an AI chatbot"), remove the most valuable part of that solution and force the team to compensate. **The Exercise:** "Okay, we all agree the obvious answer is an AI chatbot that answers questions. For the next 15 minutes, we are not allowed to use chat, text, or natural language. How do we solve the user’s problem?" - *Result:* You might land on "proactive highlighting" (we highlight the answer before they ask), or "community curation" (we pin the best answer to the top). ### 5. Work Backwards from a Press Release (Amazon’s Method) Obvious solutions happen when we think in "features." A feature is incremental. A narrative is transformative. **The Exercise:** Before looking at the backlog, write a mock press release for the product release 12 months from now. - **The Prompt:** "Write a headline and a quote from a happy customer. What is the customer doing now that they couldn't do before? Why do they love us?" - **The Logic:** This forces the team to think about *value* and *impact*. When you read the press release out loud, ask: "Would our current 'obvious' feature set make this user quote possible?" Usually, the answer is no. Then you work backward to find the features that *would* ⚠️ [内容较长，已达到本次长度上限被截断]