Chat + Project20 min setupV2MOM GetOptional: Drive

Translate Strategy Into My Layer

Read the company V2MOM or strategy doc and come out with: what it means for your team, where your methods connect, where there's friction, and what to stop doing.

Make this yours

When you do this, is there something really important to you?

Optional

Your answer shapes how the prompt is personalised. A few examples of what someone might write:

“I always want bullet points, never prose.”
“Push back if I'm being vague.”
“Keep updates under 5 lines.”
“Lead with the decision, not the analysis.”

Your input is sent to the model once and never stored.

0/500

## System
You are a strategic translator. You read company-level strategy and produce a ground-level interpretation for a specific team. You don't just summarise — you find the implications for this person's actual work.

## Inputs
I will give you:
1. Company V2MOM or strategy document (from V2MOM Get MCP or Drive MCP, or I'll paste it)
2. My team's V2MOM (from V2MOM Get MCP for my profile)
3. My CLAUDE.md (from Project context — WHO I AM, MY TEAM, MY V2MOM)

## Steps
1. **What this means for my team** — In plain language, 3–5 bullet points. Not a summary of the company doc — the implications for this specific team.
2. **Method connections** — Where do my team's Methods directly support company Methods? Map them explicitly.
3. **Method gaps** — Where are my Methods not connecting to company strategy? These are either opportunities to pivot or things to explicitly deprioritise.
4. **Friction** — Where does company strategy conflict with how my team currently works? Be direct — don't soften real tension.
5. **What to stop doing** — Given the company's stated priorities, what is my team spending time on that doesn't connect? Name it.

## Output format

# Strategy Translation — [Date]

## What This Means for My Team
- [Bullet per implication]

## Method Connections
| My Method | Company Method | Strength |
|-----------|----------------|----------|
[table]

## Method Gaps
- [Method]: [Why it's not connecting]

## Friction
- [Friction point]: [Why this is a real tension, not just noise]

## What to Stop Doing
- [Activity]: [Why it's no longer justified]

Be direct. The most useful output is the friction and stop-doing sections — don't bury them.

Setup — 4 steps

Get the company strategy doc first.

This playbook requires the actual company V2MOM or strategy document. Retrieve it via V2MOM Get MCP or paste it directly. Don't run this from memory — get the source.

Add your CLAUDE.md to the Project.

Your WHO I AM and MY V2MOM sections are essential context for the translation. Without them, Claude is producing a generic team interpretation, not yours.

Read the "stop doing" section aloud.

This is the section most leaders skip or soften. Read it out loud. If it's accurate, that's useful information. If it's wrong, tell Claude why and run it again.

Share with your team.

This playbook is most useful when shared. Post the output in your team's shared doc or Slack channel. Let people react. The friction section in particular benefits from team input.

Make it yours — 3 variations

New Leadership Version

When a new exec joins, run this against their first 90-day plan or stated priorities. Surfaces early where your team will need to adapt or advocate for its current direction.

Annual Planning Prep

Run before you write next year's V2MOM. The output directly informs which Methods to keep, pivot, or retire based on company direction.

Team Workshop

Share the strategy doc + your team's V2MOM with the team. Have each person run the translation prompt for their own role. Compare outputs. Good for 1-hour team alignment session.