The Strategy Stack: Vision → Strategy → Tactics → Metrics

A strategy stack is the simplest way to align your entire organization—from boardroom goals to Tuesday’s to-do list. When leaders anchor work to a clear stack—Vision → Strategy → Tactics → Metrics—teams stop chasing shiny objects, bandwidth returns, and progress becomes measurable.

This article gives you a complete, practical playbook for using the strategy stack at a nonprofit (or any mission-driven org). You’ll get definitions, an operating rhythm, a one-page template, decision filters, and real examples you can copy-paste into your next planning session.

What is a strategy stack?

A strategy stack is a layered framework that connects the “why” to the “what now,” with each layer answering a different leadership question:

Vision — Why do we exist? What long-term change are we here to create?
Strategy — How will we win? What path—complete with trade-offs—will we follow over the next 12–24 months?
Tactics — What will we do? What projects, sprints, and weekly commitments move the strategy forward right now?
Metrics — How will we know? What leading and lagging indicators tell us we’re on track?

Think of the strategy stack as an operating system. Vision is the device’s purpose; strategy is the OS; tactics are the apps; metrics are the system diagnostics that keep everything healthy.

Why the strategy stack solves nonprofit pain points

Nonprofits drown in well-meaning requests. The strategy stack:

Restores focus by giving you a shared filter for saying yes (in scope) and no (out of scope).
Protects bandwidth (people × time × focus) by preventing random work from hijacking calendars.
Turns plans into action via a weekly execution cadence.
Builds trust with boards, volunteers, and donors because outcomes become visible and repeatable.

When every project traces to the stack, you avoid the two traps that kill execution: a big vision with no path, or busywork with no outcome.

The four layers (and how to make each one real)

1) Vision: durable and directional (10+ years)

Purpose: Define the world you’re trying to create. This should withstand staff turnover, funding cycles, and news cycles.
Make it real: One plain-English sentence, testable by the “5th-grader rule.” Example: Every student in our city has clothing, food, and hygiene items so they can learn with dignity.

Anti-patterns:

Laundry-list vision statements (“and… and… and…”)
Jargon that sounds strategic but isn’t (“empower synergistic community uplift…”)

Leadership move: Read the vision at the start of high-stakes meetings. It’s the north star, not a poster.

2) Strategy: a path with trade-offs (12–24 months)

Purpose: Choose how you will win—and what you will not do. Strategy exists to make trade-offs explicit.

Make it real: One page, renewed annually. Answer four questions:

Arena: Where will we play? (geography, partners, demographics)
Advantage: Why do we win there? (capabilities, model, network)
Approach: What methods? (e.g., weekly delivery, standardized kits, partner training)
Abstain: What good things will we not do this year to keep focus?

Anti-patterns:

Calling everything “priority 1.”
Confusing values (“be excellent”) with strategy (the path and trade-offs).

Leadership move: Convert the strategy into a decision filter (you’ll see how below) so saying “no” isn’t personal—it’s principled.

3) Tactics: projects, sprints, and weekly commitments

Purpose: Turn strategy into action. Tactics are what you’ll complete in the next quarter and week.

Make it real:

Quarterly outcomes (90-day sprints): 3–5 outcomes (not tasks) that are unambiguously done or not done.
Weekly commitments: The small number of promises each team makes to move a sprint outcome.
Owner: One accountable person per outcome.

Anti-patterns:

Rolling “to-do soup.”
Work with no owner.
Meetings that produce no commitments.

Leadership move: Ten-minute Friday wrap: what shipped, what rolls, what we learned.

4) Metrics: leading & lagging indicators that matter

Purpose: Prove progress and improve decisions.

Make it real:

Leading indicators (activity/quality): order cycle time, volunteer show rate, partner onboarding time, error rate.
Lagging indicators (outcomes/impact): people served, prevention rate (crises avoided), donor retention, Return on Donation (ROD) framed as community impact enabled.
Cadence: Check weekly for leading indicators, monthly for lagging indicators; adjust sprints accordingly.

Anti-patterns:

Vanity metrics (website visits without conversion).
Overhead-only storytelling (it’s incomplete).
Measuring everything (noise) or nothing (blindness).

Leadership move: Make one metric the North Star for the quarter; color-code the dashboard; celebrate green, diagnose red.

The operating rhythm that keeps the stack alive

Monday (15 minutes): Each team states the single outcome that must move this week and the one risk in the way.
Mid-week (async): Green/Yellow/Red check on sprint outcomes; unblock yellows.
Friday (10 minutes): What shipped? What rolls? What did we learn? Close the loop and reset.

This cadence turns the strategy stack from a document into a habit.

The one-page strategy stack (template)

Vision (10+ years)

One sentence; durable; human.

Strategy (12–24 months)

Arena • Advantage • Approach • Abstain (the four A’s).
3–5 annual priorities.

Quarterly Outcomes (90 days)

3–5 outcomes; owner per outcome; success criteria in one line.

Weekly Commitments (this week)

What ships by Friday; who owns it; dependencies.

Metrics

3–5 leading, 3–5 lagging; review cadence.

Copy this to your planning doc and fill it in with your team.

Example cascade (so staff see “today”)

Vision: Families get help at the first signs of struggle so crises are prevented.
Strategy (12–24 months): Equip schools and civic partners with standardized, size-specific resources on a predictable weekly schedule; certify partners; measure prevention.
Annual priorities:

Sustain inventory accuracy at 97%+
Cut partner order cycle time to 5 business days
Launch partner onboarding playbook (training + SLAs)

Q1 outcomes:

Inventory accuracy ≥95% for 8 consecutive weeks (Owner: Ops)
Median cycle time ≤6 days; 85% on-time (Owner: Logistics)
10 partners certified (Owner: Programs)

This week:

Clear order backlog; run 3 QA spot checks; pilot new intake form with two partners.

That’s the strategy stack in action—vision through to Friday.

The decision filter: how to say “no” without drama

A written strategy stack lets you turn “no” into a neutral, repeatable process. Use this five-question filter for incoming requests:

Does it advance the current strategy? If not, it’s a no (or “later”).
Which quarterly outcome does it move? If none, it’s misaligned.
What will it displace this week? Name the trade-off in the same breath.
What metric will improve? If we can’t measure benefit, we won’t do it.
Who owns it? No owner, no go.

Reply template: “This is a good idea, but it doesn’t advance Outcome 2 this quarter. Let’s park it for roadmap review on the 1st.” You’ve said no; you’ve honored the idea; you’ve protected bandwidth.

Building your first 90 days on the stack (quick start)

Weeks 1–2: Align on vision & strategy.

Draft in one hour; refine in one day. Name the abstains.

Weeks 3–4: Choose quarterly outcomes.

Limit to 3–5; assign owners; write success in one sentence.

Weeks 5–6: Instrument leading metrics.

Build a simple sheet or dashboard; define green/yellow/red.

Weeks 7–8: Train the operating rhythm.

Monday, mid-week, Friday. Calendar it; time-box it.

Weeks 9–12: Run the play and review.

Celebrate what shipped; adjust and roll. Publish a one-page update to board and staff.

Common failure modes (and how to avoid them)

Vision masquerading as strategy: “We value dignity” isn’t a path. Write trade-offs.
Everything is priority 1: If everything matters, nothing moves. Force ranking is a kindness.
Tactics without metrics: Work that can’t be measured can’t be managed.
Annual plans that never change: Give the plan a shelf life; review quarterly.
Data overload: Track a short list that leadership actually reads.
Person-dependent execution: If a key person vanishes, the work shouldn’t.

Tooling that helps (start simple)

You can run a strategy stack on a shared doc and a dashboard:

Docs: One-page plan + sprint board + weekly commitments.
Dashboards: A lightweight sheet or BI tool (Power BI/Tableau/Grafana) for metrics.
Cadence: Calendar holds for Monday/Mid-week/Friday with standing agendas.

Invest only when the habit is sticky. Tools don’t fix planning; habits do.

FAQs

Isn’t this just OKRs?
OKRs are one way to express outcomes and measures. The strategy stack is broader—it ensures the vision and trade-offs are explicit, then ties OKR-like outcomes to a weekly rhythm.

How many metrics should we track?
Start with 6–10 (split evenly between leading and lagging). If leaders aren’t reading them, you have too many.

How do we handle good ideas that don’t fit?
Keep a parking lot with review dates. Great ideas often become next quarter’s outcomes—without derailing this quarter.

What if our board wants everything?
Show the stack, the outcomes, and the resource limits. Ask, “Which outcome should we drop to add this?” Trade-offs build trust.

Put it to work this week (checklist)

Write a one-sentence Vision.
Choose a one-page Strategy with clear abstains.
Pick 3–5 Quarterly Outcomes with owners.
Set a Monday/Mid-week/Friday Operating Rhythm.
Choose 3–5 Leading and 3–5 Lagging Metrics; publish a dashboard.
Use the five-question Decision Filter for all new requests.
Report weekly: what shipped, what rolls, what we learned.

When you run this strategy stack, your team always knows why we exist, how we’ll win, what we’re doing next, and how we’ll measure success. That clarity compounds—projects finish faster, stakeholders trust your process, and your mission moves from aspiration to execution.