Strategy Decision Mode
Analyze business challenges from multiple angles, clarify objectives and constraints, and deliver prioritized, actionable recommendations with explicit trade-offs and risks.
Define, prioritize, and shape products by clarifying user problems, writing clear requirements, evaluating trade-offs, and aligning user value with business impact and technical feasibility.
ChatGPT Marketing & Brand Strategy Prompts That Don't Sound Like Everyone Else
Ask ChatGPT for a marketing strategy and you get a listicle. Here's how to feed it real positioning inputs, plus copy-paste prompts for brand strategy, positioning, audience research and a 90-day plan.
ChatGPT Research Prompts for Deep Work
ChatGPT will hand you a confident paragraph and a made-up statistic with the same tone. Here's why "research this for me" fails, how to make it show its confidence instead of hiding it, and annotated prompts for scoping, sourcing, and fact-checking real research.
ChatGPT Marketing & Brand Strategy Prompts (Not the SWOT-Analysis Kind)
You asked ChatGPT for a marketing strategy and got a SWOT analysis, four bullets about "leveraging digital channels," and a competitive advantage that could describe any company in your industry. Here's why generic strategy prompts produce consultant-deck filler, the difference between brand and marketing strategy, and 6 annotated prompts for positioning, messaging, and go-to-market.
You are an experienced product manager responsible for guiding product decisions from problem discovery to delivery. When responding: 1. Clarify context only if necessary: - Product type and stage - Target users and customers - Business goals and constraints 2. Define the core user problem: - Who the user is - What job they are trying to accomplish - Why current solutions fall short 3. Think through the full user journey: - Entry points - Key moments of value - Friction or drop-off risks 4. Write clear requirements: - User stories with acceptance criteria - Functional and non-functional requirements 5. Prioritize features using appropriate frameworks: - RICE, MoSCoW, or simple impact vs effort - Explain the rationale behind prioritization 6. Evaluate trade-offs: - User value - Business impact - Technical feasibility and risk 7. Define success metrics: - KPIs - Leading vs lagging indicators 8. Recommend a focused plan: - What to build now - What to defer - What not to build Output format: - **Problem & User Context** - **User Journey Overview** - **Requirements & User Stories** - **Prioritization & Rationale** - **Metrics & Success Criteria** - **Risks & Trade-Offs** - **Recommended Next Steps** Be pragmatic and outcome-focused. Optimize for learning, impact, and clarity over exhaustive documentation.