| Component | Definition | FlowScale Example |
|---|---|---|
| Vision | Long-term future state | "The platform where operations teams build and run all their workflows" |
| Target market | Who you serve | Mid-market ops teams (50โ500 employees) |
| Value proposition | Why customers choose you | Faster workflow setup, less technical overhead |
| Differentiation | What makes you unique | Template-first onboarding, no-code automation |
| Strategic focus | What you prioritize | Activation and retention over new features |
Reversible vs Irreversible Decisions (Two-Way vs One-Way Doors)
| Type | Approach | FlowScale Example |
|---|---|---|
| Two-way door (reversible) | Decide quickly, iterate | A/B testing onboarding copy, adding a template category |
| One-way door (irreversible) | Deliberate slowly, gather data | Rebranding, entering new market, major pricing change |
Rule: If you can reverse the decision in <1 quarter with acceptable cost, it's a two-way door. Decide fast. If reversal costs >1 quarter or significant revenue/customer trust, decide carefully.
Optionality Framework โ When facing multiple strategic directions, evaluate which path preserves the most future options:
| Strategic Choice | Options Opened | Options Closed | Score |
|---|---|---|---|
| Build onboarding wizard first | Activation data, unlocks enterprise if onboarding is smooth | Defers enterprise features, may lose some enterprise deals now | High |
| Build RBAC first | Enables enterprise expansion immediately | Consumes eng capacity, defers activation improvements | Medium |
| Build AI features first | Differentiation, marketing narrative | High technical risk, defers proven needs | Low |
Premortem Analysis
Before committing to a strategy, ask: "It is 6 months from now and this strategy has failed. What went wrong?"
Common failure modes: Premature optimization ยท Competitive overreaction ยท Sunk cost escalation ยท Analysis paralysis ยท Vision drift
AI is excellent at generating failure scenarios because it isn't emotionally invested in your strategy.
AI is excellent at synthesizing competitive intelligence but has known failure modes:
| Failure Mode | What It Looks Like | Mitigation |
|---|---|---|
| Recency bias | Overweights recent information | Provide your own time-bounded data |
| Confirmation bias | Agrees with your framing rather than challenging it | Ask the AI to challenge your assumptions specifically |
| Hallucination | Invents competitive claims that aren't real | Cross-reference every claim with primary sources |
| Surface analysis | Lists features without analyzing strategic implications | Explicitly ask for strategic implications, not feature lists |
WorkForge โ "Enterprise workflow automation"
Strengths: Advanced RBAC, SSO/SAML, SOC2/HIPAA compliance, API-first
Weaknesses: Complex 3-month onboarding, expensive, mid-market unfriendly
FlowEasy โ "Workflows for everyone"
Strengths: Easy onboarding (avg 12 min), 100+ templates, free tier, affordable
Weaknesses: No enterprise features, basic reporting, no custom integrations
AutomatePro โ "AI-powered process automation"
Strengths: AI workflow generation, wow-factor demos, modern UI
Weaknesses: Young product (18 months), limited integrations, occasional AI errors
Create prompts/competitive-analysis.md. The prompt must ask for: feature comparison matrix (Superior/Parity/Inferior/Missing), positioning map description, strategic threats per competitor, and strategic opportunities across all three. Include a critical rule: only use provided data; mark any claim not in the source as [UNVERIFIED].
Run the competitive analysis. Then verify every claim: Verified (in source data) / Inferred (reasonable deduction) / Unverifiable (no source support) / Suspect (contradicts source). Count each category.
Write a strategic tradeoff memo at deliverables/W04-strategy-memo.md. Analyze three directions: (A) double down on onboarding/activation, (B) build enterprise permissions, (C) invest in AI capabilities. Recommend one, justify it, and state what evidence would change your mind.