Strategy Alignment Check
You validate how your planning aligns with business strategy
What It Does
AI checks how your planning maps to your business strategy.
Requires context about:
• Your business plan
• Strategic objectives
• Company priorities
The AI analyzes the connections between your technical decisions and business goals, identifying alignment gaps and suggesting improvements.
StrategyRadar Notes
High risk of hallucination causing you to make wrong decisions. Be very critical and contrast results against your actual business strategy and goals. AI can miss nuances in your organization's context and may suggest alignments that look good on paper but don't fit your reality. Always validate with stakeholders.
Prompts
Validate Strategy Alignment
You are a strategic planning expert. Given the following business strategy and technical plan, analyze if they are properly aligned.
Business Strategy:
{business_strategy}
Technical Plan:
{technical_plan}
Please identify:
1. Alignment points where technical decisions support business goals
2. Misalignments or gaps
3. Recommendations for improvement Check Technical Decision Impact
Analyze how this technical decision aligns with our business objectives:
Business Objective:
{business_objective}
Technical Decision:
{technical_decision}
Evaluate:
1. Does this technical decision directly support the business objective?
2. What business value does it provide?
3. Are there risks or trade-offs?
4. Alternative approaches that might align better?Resources
Premium Packs
Get comprehensive guides, templates, and advanced prompts to implement this capability effectively in your organization.
Blog Posts
Related AI Capabilities
Conventional Planning
Project planning as the baseline approach, completely human-driven. This encompasses defining **project scope** (goals, deliverables, success criteria), **resource planning** (team structure, timelines, budgets), and **work organization** (epics, milestones, roadmaps). You can plan using different approaches depending on your context: traditional waterfall (detailed upfront planning), iterative/agile methods (continuous adaptation), or hybrid approaches. Each has its place depending on project constraints, industry regulations, and team dynamics. ## Common Approach Today: Iterative Planning The most common practice in software development today emphasizes **short-term cycles** and **continuous adaptation**. Teams plan in sprints or iterations (typically 1-6 weeks), allowing them to incorporate real feedback and adjust course quickly. The key is creating _just enough plan to start_, then evolving it based on what you learn. This approach includes: - **Short-term planning cycles** - Sprint planning (1-4 weeks) - Iteration planning (2-6 weeks) - Release planning with flexible scope - **Feedback loops from other phases** - **Analysis:** Validate requirements through stakeholder discovery - **Design:** Test feasibility with architecture spikes - **Coding:** Learn from MVPs, prototypes, and proof-of-concepts - **Continuous adaptation** - Adjust priorities based on user feedback - Refine scope as you discover new information - Embrace uncertainty instead of fighting it - **Validation and alignment** - Regular planning reviews with stakeholders - Feasibility and capacity checks - Team alignment meetings _See the Resources section below for recommended books and guides on planning practices._
OKR Planning Document Assistant
AI acts as an **OKR planning specialist** that helps you create well-structured Objectives and Key Results following industry best practices. ## What is OKR Planning? **OKRs** (Objectives and Key Results) are a goal-setting framework used by organizations to define measurable goals and track their outcomes: - **Objective**: Qualitative, inspiring, time-bound goal (e.g., "Become the fastest checkout experience in e-commerce") - **Key Results**: 3-5 quantitative, measurable outcomes that prove the Objective was achieved (e.g., "Reduce checkout time from 4 minutes to 90 seconds") ## What AI helps with: - **Writing OKRs**: Generate well-structured OKRs from project context - **Reviewing OKRs**: Check if Objectives are qualitative and Key Results are measurable - **Improving clarity**: Ensure KRs have specific metrics (numbers, percentages, completion status) - **Alignment validation**: Verify Key Results actually measure progress toward the Objective - **Format compliance**: Follow OKR best practices (ambitious yet achievable, SMART criteria) ## Common OKR Mistakes AI Catches: - ❌ **Objective is too vague**: "Improve the product" → ✅ "Deliver the most intuitive user onboarding experience" - ❌ **Key Result has no metric**: "Better performance" → ✅ "Reduce API response time from 500ms to 100ms" - ❌ **KR doesn't measure the Objective**: Objective about "user satisfaction" with KRs about "lines of code written" ## What AI does NOT do: - Set your business goals (you define what matters) - Decide your priorities or strategy - Replace stakeholder alignment discussions Think of it as an **OKR coach** that ensures your goals follow the framework correctly.
Project Planning Assistance
AI assists in project planning and scope definition at the project level. Works between projects and requires: • Organizational context • Team structure • Current assignments • Resource availability
Manual Requirement Gathering
Traditional requirement gathering as the baseline approach, completely human-driven: Discovery & Research: • Market analysis and competitive research • Business plan review and strategic alignment • Stakeholder interviews and user research Requirements Gathering: • Face-to-face meetings with stakeholders • Workshop sessions (design thinking, event storming, etc.) • User story mapping and backlog creation • User journey mapping • Business requirements documentation Validation: • Requirement review sessions • Stakeholder sign-offs • Manual consistency checks This is your baseline - the foundation that all AI-assisted capabilities build upon.