← All solutions
Product Managers
AI Brainstorming Tool
AI Brainstorming Tool for Product Managers
A real question from product managers, the standard AI answer, and cross-domain brainstorming ideas from Limenbell side by side.
🔍 The question
A real question from product managers
I'm a product manager trying to brainstorm new feature ideas, but everything we come up with feels like something a competitor already shipped. Help me brainstorm something different.
🔹 The standard AI answer
What a typical AI tool says
The "everything feels like a competitor already shipped it" trap usually means you are competing on **features** instead of competing on **a shift in perspective or business model.**
Competitors have optimized for the current way the user works. To beat them, you have to change the *rules* of the workflow.
Here is a structured brainstorming framework designed to force divergence, along with 10 specific prompts you can steal for your next whiteboard session.
### Step 1: Run a "Forced Divergence" Audit
Before brainstorming, look at your product and map it against these 5 axes. Competitors usually sit in the center. You want to find the extreme edge.
1. **Time:** Competitors serve the user *during* the task. Can you serve them *before* (pre-mortem) or *after* (post-mortem)?
2. **Actor:** Competitors serve the *user*. Can you serve the user’s *manager*, *client*, or *future self*?
3. **Mode:** Competitors use *click/type* interfaces. Can you win with *ambient*, *voice*, or *invisible* UI?
4. **Incentive:** Competitors sell *software*. Can you sell *outcomes*, *insurance*, or *access*?
5. **Data:** Competitors store data in a *walled garden*. Can you win by being the *open* or *portable* layer?
---
### Step 2: 10 "Anti-Competitor" Brainstorming Prompts
Run a session where you force the team to answer these questions. If the answer sounds like a competitor, throw it out and go one level deeper.
#### 1. "What feature are we building that we *hope* the user never has to use?"
Most software is built to be engaged with. Build the feature that solves the problem so fast the user leaves.
- *Example:* Instead of "Project Management Software," build "The Automated Status Report." The user doesn't manage tasks; the software just asks them every morning, "Did you finish X?" and writes the report for their boss.
#### 2. "What would our product look like if we charged for *not* using it?"
Look at usage-based pricing vs. outcome-based pricing.
- *Example:* A competitor sells a "Social Media Scheduler." You sell "Content Insurance." You connect the account. If a post goes viral and crashes their site, you pay them. (You are betting on uptime, not scheduling).
#### 3. "What is the most annoying thing about our competitor’s *settings page*?"
Look for "Configuration Fatigue." Competitors brag about being "flexible" and "customizable." That usually means the user has to do the work.
- *Idea:* Launch a product with **zero settings**. It uses AI to infer the user's workflow. Market it as "The tool that configures itself."
#### 4. "What if we stopped selling to the user and started selling to their *vendor*?"
Flip the value chain. If the workflow is B2B, the user is usually trying to please a client or a buyer.
- *Example:* Design tools are saturated (Figma, Canva). Instead of a new design tool, build a tool for *clients* to give feedback to designers. The client uses your tool, and it forces the designer to export files in your format. You own the relationship from the top down.
#### 5. "Where is the user’s data trapped?"
Find the "Roach Motel" problem. Competitors lock data in to retain users. You can disrupt by being the liberator.
- *Idea:* Build the "Universal Exporter." One-click migration tools that move data from Competitor A to Competitor B. You monetize the migration anxiety, not the storage.
#### 6. "What manual task happens between two different competitor tools?"
The gap between tools is the goldmine. The user copies a number from App A and pastes it into App B.
- *Idea:* Don't build a new App. Build a "Middleware Agent." An invisible Chrome extension that watches App A and automatically fills out App B. You aren't competing with either; you are the glue.
#### 7. "What if we make the
⚠️ [内容较长,已达到本次长度上限被截断]
✨ Cross-domain ideas from Limenbell
air traffic control
Air traffic control succeeds only by assuming separation minima, radio contact, and predictable handoffs—remove one assumption, and controllers must redesign coordination from scratch.
Assume your competitors’ products assume users always know what they want next. Build “Holding Pattern Mode”: instead of pushing users to the next feature or goal, let them deliberately park a task in a visible, bounded limbo with a stated re-entry condition (“resume when X happens”). Unlike a backlog or snooze, it shows live dependencies and only surfaces the task when the condition is met, not on a timer. This solves the problem of users losing context or feeling forced into premature action, creating a calmer, trust-based flow no competitor currently owns.
Moroccan souk marketplaces
Souks are not just shops; they are curated, negotiable, sensory discovery spaces where the value is in the detour, not the destination.
Build a feature that lets users deliberately abandon their product’s “ideal path.” In a Moroccan souk, getting lost in side alleys is how you find the best non-commodity goods; the failure is forcing every feature to be linear and optimizable. So ship “The Back-Alley Button”—one click, no search, that drops users into a random, low-priority, or abandoned menu corner your analytics say is underused. It solves the “competitor parity” trap because no rival has a reason to ship intentional inefficiency, yet it creates discovery value and surfaces hidden user needs you’d never roadmap into a sprint.
kaleidoscopes
Just as a kaleidoscope creates novelty from the same fixed fragments by rotating the viewing angle, your feature set can feel fresh by recombining existing capabilities through an unexpected constraint or customer lens.
Stop asking “what’s new?” and start asking “what’s deliberately broken?” Launch a “Wrong Tool Mode” where your app disables its core efficiency feature and forces users to complete the task with a slower, collaborative, or analog-style interface for one week. This feels counter to your roadmap’s optimization bias, and competitors won’t clone it because it looks like anti-productivity. The value: it uncovers hidden workflows, emotional attachment, and edge cases that focus groups never surface.
Try your own question →