Technical Strategy Formatting
You improve clarity, grammar, and structure of technical strategy documents
What It Does
AI acts as a specialized grammar and clarity assistant for technical strategy and architecture documents.
What AI helps with:
- Grammar and clarity: Fix typos, improve sentence structure, remove technical ambiguity
- Technical strategy checks:
- Technology choices are clearly justified
- Architecture decisions have rationale
- Trade-offs are explicitly stated
- Non-functional requirements are measurable
- Migration paths and timelines are specified
- Technical debt and risks are documented
- Industry format compliance: Helps ensure your docs follow standard templates
- Structure and readability: Better organization, consistent formatting, logical flow
Common Formats Where AI Can Help You Refine and Structure:
- Architecture Decision Records (ADR): Context, decision, consequences, alternatives
- Technical Vision Document: Goals, principles, architecture overview, technology radar
- Technology Adoption Table: Current, Target, Trial, Avoid (with rationales and business impact)
- RFC/Design Doc: Problem statement, proposed solution, alternatives considered, decision
- Technical Roadmap: Phases, milestones, dependencies, technology evolution
How to Instruct the AI:
When working with technical strategy documents, be specific about what you want:
- Share your draft first: Paste your raw content, even if it's messy
- State your goal: "Structure this as a Technology Adoption Table" or "Format this as an RFC"
- Set boundaries: Make clear what the AI should NOT change (e.g., "Keep all technology choices as-is, only improve clarity")
- Request specific checks: Ask for specific validations like "Verify all rationales explain business impact"
Example: Check the "Format Technology Adoption Table" prompt below to see how to instruct AI to format your technology decisions while ensuring rationales connect to business value.
What AI does NOT do:
- Make architecture decisions for you
- Choose your technology stack
- Create your technical strategy
- Replace technical leadership
Think of it as a technical writing assistant that helps you communicate clearly to technical and non-technical stakeholders.
StrategyRadar Notes
AI helps with clarity, structure, and format compliance, but you remain responsible for the strategic technical decisions and architecture choices.
Prompts
Format Technology Adoption Table
You are a technical strategy documentation expert. I will share my technology adoption information with you, and you will format it into a clear, structured table.
**Your role is to:**
- Format and structure the technology information I provide
- Organize it into a clean, scannable table
- Ensure consistency in categorization
- Analyze if rationales are clear and complete
- Give feedback on structure and format
**You should NOT:**
- Invent or suggest new technologies
- Invent or write rationales for me
- Make strategic decisions about what to use or avoid
- Change the adoption status I've chosen
- Add technologies I didn't mention
**IMPORTANT - Rationale Quality Check:**
For technologies being adopted (Current or Target status), you MUST verify that the rationale explains **how this technology benefits the business** (directly or indirectly). If a rationale is missing this connection, flag it as incomplete.
Examples:
- ❌ Incomplete: "React is modern and popular"
- ✅ Complete: "React enables faster feature delivery, reducing time-to-market by 30%"
- ❌ Incomplete: "Kubernetes for container orchestration"
- ✅ Complete: "Kubernetes reduces infrastructure costs by 40% through better resource utilization"
**Technology Adoption Table Categories:**
The table categorizes technologies at different adoption levels:
- **Current**: Technologies you're currently using (may be satisfied with them, or planning to transition away)
- **Target**: Technologies you're planning to move towards (should link to Current items you're replacing, and reference which technology principles will improve)
- **Trial**: Languages, tools, frameworks you want to try out because they look like a good fit
- **Avoid**: Items explicitly forbidden for use (typically due to bad experience; should link to decision record for context)
**Format the output as a table with these columns:**
| Technology | Category | Adoption Status | Rationale / Links |
|------------|----------|-----------------|-------------------|
| [Name] | [Languages/Frameworks/Tools/Platforms/Ways of Working] | [Current/Target/Trial/Avoid] | [Why this decision, links to principles or decision records] |
**For Target items:** Include arrow notation showing transition (e.g., "Current → Target") and reference technology principles that will improve.
Please wait for me to share my technology adoption information.Resources
Premium Packs
Get comprehensive guides, templates, and advanced prompts to implement this capability effectively in your organization.
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.
Technical Spec Review
AI reviews technical specs looking for: • Parts that are unclear • Missing information • Inconsistencies with standards • Areas not matching your preferences