majiayu000 Strategic Clarity Workflow
Overview
A 4-phase workflow for establishing team identity and strategic positioning.
┌─────────┐ ┌─────────┐ ┌───────────┐ ┌─────────┐
│ ABSORB │ → │ AUDIT │ → │ ARTICULATE│ → │ ALIGN │
│ │ │ │ │ │ │ │
│ Context │ │ Reality │ │ Identity │ │ Buy-in │
└─────────┘ └─────────┘ └───────────┘ └─────────┘
When to use: Starting a new role, inherited ambiguity, team lacks clear identity Time: 2-4 weeks (part-time) Output: Team charter, value proposition, capability audit
How This Skill Works
I'll guide you through each phase with:
- Questions to gather context
- Activities to complete
- AI-assisted prompts for each deliverable
- Checklists to track progress
Tell me which phase you're in (or starting fresh), and I'll help you through it.
Phase 1: ABSORB (Week 1)
Goal
Understand what exists before forming opinions.
Activities
- Read all existing documentation
- Meet with team members
- Study handover notes
- Review historical decisions
AI Assistance
Prompt: Synthesize Context Share your notes and I'll help you:
- Identify key themes
- Surface tensions or contradictions
- List what's still unclear
Prompt: Question Generation Based on your context, I'll suggest:
- Questions you should be asking
- Who to talk to for answers
- What documents to read next
Phase 1 Checklist
- Reading notes captured
- Key questions documented
- Initial mental model forming
Phase 2: AUDIT (Week 2)
Goal
Understand what actually exists vs. what's claimed.
Activities
- Systematic codebase review
- Map capabilities to code
- Identify gaps
- Compare reality to documentation
AI Assistance
Prompt: Capability Mapping Share your team's claimed responsibilities and I'll help build an audit template:
- Capability name
- Status (exists/partial/missing)
- Evidence (code files/patterns)
- Gap description
- Impact assessment
Prompt: Codebase Exploration Point me at code or systems and I'll help you understand:
- What product capability it represents
- The business logic encoded
- Use cases supported
- What's notably missing
Phase 2 Checklist
- Capability audit document created
- Gap inventory prioritized
- Reality vs. perception documented
Output: Capability Audit Template
# Capability Audit: [Team Name]
| Capability | Status | Evidence | Gap | Impact |
|------------|--------|----------|-----|--------|
| [Capability 1] | ✅ Exists | [code/system] | — | — |
| [Capability 2] | 🟡 Partial | [code/system] | [missing piece] | [user impact] |
| [Capability 3] | ❌ Missing | — | [full description] | [business impact] |
Phase 3: ARTICULATE (Week 3)
Goal
Define and document team identity clearly.
Activities
- Draft mission statement
- Define responsibility boundaries
- Create value proposition
- Build communication frameworks
AI Assistance
Prompt: Mission Drafting Share what you actually own vs. don't own, and I'll help draft:
- Clear mission statement
- Distinction from adjacent teams
- Concrete, not vague language
Prompt: Charter Structure I'll help structure a one-page team charter:
- What we're accountable for
- What we explicitly don't own
- How we create value
- Key metrics we move
Prompt: Value Narrative I'll help create communication frameworks:
- One-sentence pitch
- "Without us, [consequence]" statements
- Boundary explanations for adjacent teams
- Leadership-friendly framing
Phase 3 Checklist
- Team charter drafted
- Value proposition documented
- Boundary contract defined
Output: Team Charter Template
# [Team Name] Charter
## Mission
[One sentence: what we do and why it matters]
## We Own
- [Responsibility 1]
- [Responsibility 2]
- [Responsibility 3]
## We Don't Own
- [Adjacent area 1] — owned by [other team]
- [Adjacent area 2] — owned by [other team]
## Value Proposition
Without us: [what breaks or doesn't exist]
With us: [what users/business gets]
## Key Metrics
- [Primary metric we move]
- [Secondary metric]
## Boundaries
| Area | Us | Them |
|------|----|----- |
| [Shared area] | [Our part] | [Their part] |
Phase 4: ALIGN (Week 4)
Goal
Validate and socialize the work.
Activities
- Present to manager
- Discuss with peer PMs
- Gather feedback
- Iterate based on input
AI Assistance
Prompt: Stakeholder Role-Play Tell me who you're presenting to and their likely concerns — I'll role-play as them to help you prepare for pushback.
Prompt: Presentation Polish Share your draft charter and I'll help:
- Sharpen the language
- Anticipate objections
- Add evidence for claims
- Make it memorable
Phase 4 Checklist
- Manager alignment achieved
- Peer PM feedback incorporated
- Final documents published
- Communication plan for broader sharing
Document Checklist
| Document | Location | Status |
|---|---|---|
| Reading notes | context/ |
[ ] |
| Capability audit | analysis/capability-audit.md |
[ ] |
| Team charter | strategy/team-charter.md |
[ ] |
| Value proposition | strategy/value-proposition.md |
[ ] |
| Stakeholder map | analysis/stakeholder-map.md |
[ ] |
Success Criteria
By the end of this workflow, you should be able to:
- Articulate team value in one sentence
- Explain boundary with adjacent teams clearly
- Have manager endorsement of your framing
- Have peer PMs understand what you own
- Feed gap inventory into roadmap planning
Getting Started
Tell me:
- What's your situation? (New role? Inherited team? Identity crisis?)
- What phase are you in? (Or starting fresh?)
- What do you have so far? (Notes? Docs? Nothing?)
I'll guide you through the appropriate phase.