aiwg/agentic/code/addons/writing-quality/context/executive-voice.md

Deployment tool and support utility for AI context. Copies agents, skills, commands, rules, and behaviors into the paths each AI platform reads (Claude Code, Codex, Copilot, Cursor, Warp, OpenClaw, and 6 more) so one source of truth works across 10 platfo

# Executive Voice Guide

## When to Use This Guide

Only include this for:

- Board presentations
- C-level communications
- Strategic documents
- Investor updates
- Executive summaries

## The Executive Voice Balance

### What Executives Expect

- **Strategic thinking** - not tactical details
- **Business impact** - not technical implementation
- **Clear outcomes** - not process descriptions
- **Confident decisions** - not hedged possibilities
- **Time efficiency** - not comprehensive coverage

### Maintaining Sophistication

Executive communication requires high sophistication without technical jargon:

- Complex business concepts
- Strategic vocabulary
- Financial terminology
- Market dynamics language

## Appropriate Patterns for Executive Context

### Strategic Framing

✅ **Acceptable**: "This initiative aligns with our digital transformation strategy" ✅ **Acceptable**: "The investment
demonstrates our commitment to innovation"

These are appropriate in executive context even though they might be "banned" in technical writing.

### Business Language

✅ **Use freely**:

- ROI, TCO, EBITDA
- Market penetration
- Competitive advantage
- Strategic initiatives
- Value creation
- Stakeholder alignment

### Executive-Appropriate Complexity

> "The platform consolidation reduces operational expenditure by 30% while improving time-to-market for new products,
> directly supporting our strategic objective of operational excellence and market responsiveness."

This complexity is justified by the audience's expectation of strategic thinking.

## What to Avoid

### Technical Deep Dives

❌ "The system uses Kubernetes with Istio service mesh" ✅ "The cloud infrastructure provides scalability and resilience"

### Implementation Details

❌ "We refactored the codebase using SOLID principles" ✅ "We improved system maintainability and reduced technical debt"

### Uncertain Language

❌ "This might possibly help us perhaps achieve" ✅ "This positions us to capture market opportunity"

## Executive Communication Patterns

### Lead with Impact

Start with business value, not technical achievement:
> "This quarter we reduced customer acquisition cost by 40% through automated onboarding, directly improving unit
> economics."

### Quantify Strategic Value

- Market share percentage
- Revenue impact
- Cost reduction
- Time to market
- Competitive positioning

### Address Risk Professionally

> "While the migration carries execution risk, our phased approach and fallback provisions mitigate potential service
> disruption."

## Sophistication Without Jargon

### Complex Ideas, Clear Language

> "The acquisition provides vertical integration opportunities that reduce our dependency on third-party suppliers while
> improving margin structure through elimination of intermediary costs."

### Strategic Vocabulary

- Synergies (yes, it's okay here)
- Transformation (appropriate for executives)
- Leverage (as business term, not technical)
- Optimize (in business context)
- Enable (for strategic capabilities)

## Executive Formatting Preferences

### Structured Thinking

- Clear hierarchies of information
- Bullet points for scanning
- Bold key metrics
- Executive summary upfront

### Conclusion-First Writing

Unlike technical writing, executives prefer:

1. Recommendation/conclusion first
2. Supporting rationale second
3. Details in appendix if needed

## The Executive Test

Before sending, verify:

1. Can this be understood without technical knowledge?
2. Is the business impact clear in the first paragraph?
3. Are strategic implications addressed?
4. Would a board member find this valuable?
5. Is the reading level appropriate (graduate level but not technical)?

## Remember

For executives, some "banned" AI patterns are actually industry-standard business language. The key is using them
authentically with specific business context, not as empty filler.