Category Archives: Operations

Operations

Time Horizon Discipline

Leave a comment

Leaders often say:

  • “We don’t have enough time.”
  • “We’re far from our goals.”
  • “Everything feels urgent.”

Most of the time, the issue is not time.

It is a mismatch between the decision and the planning horizon.

Manage to Lead is built on clarity and disciplined change. Time horizon discipline is part of that clarity.

Different Decisions Require Different Clocks

Not every decision should run on the same timeline.

When leaders use one clock for everything, they either:

  • Overreact in the short term, or
  • Drift in the long term.

High-performing organizations operate with multiple time horizons.

Each clock answers a different question:

  • Where are we going?
  • How will we win over this bounded period?
  • What must change next?
  • Are we doing what we said we would do?

If those questions collapse into one timeframe, confusion follows.

If they contradict one another, stress follows.

If they are coherent and nested, focus follows.

The Mandate Horizon Is Contextual

The Mandate answers:

What are we trying to accomplish, by when?

There is no universal duration.

A Mandate horizon should be:

  • Long enough to require real capability building.
  • Short enough that the current leadership team owns the outcome.
  • Explicitly bounded so capital allocation decisions can be evaluated against it.

For many organizations, that is about three years.

For some, it is shorter.
For others, longer.

Three years is common because it is often long enough to require meaningful change and short enough to sustain accountability. But it is not doctrine.

The discipline is not in picking “three.”

The discipline is in making the horizon explicit and holding it steady long enough for strategy and investment decisions to compound.

Multiple Clocks Must Be Coherent 

One common architecture looks like this:

  • Mandate horizon → Defines destination
  • Strategy horizon → Defines directional choices
  • Initiative horizon → Defines staged change
  • Management horizon → Ensures execution discipline

For many organizations, that might roughly translate into:

  • Multi-year Mandate
  • Annual strategy framing
  • Quarterly initiatives
  • Monthly management cadence

But this is an example, not a rule.

  • Different organizations legitimately design different clock speeds.
  • What matters is not the exact durations.
  • What matters is coherence across them.

Match Capital Commitment with Time Horizon

The longer capital is tied up, the longer the planning lens must be.

Examples:

  • Hiring a senior executive → Mandate lens
  • Entering a new vertical → Mandate lens
  • Building a new sales discipline → Initiative lens
  • Running a marketing experiment → Management lens

Short-horizon thinking applied to long-horizon commitments produces fear and underinvestment.

Long-horizon thinking applied to short-cycle execution produces drift and lack of accountability.

Match the clock to the decision.

NOW and NEXT Must Be Far Enough Apart

In the Change Framework:

NOW → WHY → NEXT → WHAT MUST BE DONE → BARRIERS

NEXT must relieve the constraints of NOW.

If NEXT is too close:

  • You get incremental improvement.
  • The system remains fundamentally unchanged.

If NEXT is too far:

  • It becomes aspirational.
  • The team cannot see the path.

A disciplined principle:

Choose a future state far enough out that you can think beyond current constraints, but close enough that the current leadership team is accountable for reaching it.

That balance creates energy without fantasy.

Why Leaders Feel “Short on Time”

When leaders say they are short on time, often one of three things is happening:

  • The Mandate horizon is unclear.
  • Too many initiatives are competing at once.
  • The management clock is crowding out strategic thinking.

Clarity of horizon reduces emotional noise.

When the Mandate is explicit and bounded, urgency becomes focus rather than pressure.

Bottom Line

  • Time is not the problem.
  • Unbounded thinking is the problem.
  • Use multiple clocks.
  • Make each explicit.
  • Ensure they are coherent.

Let the longer horizon guide capital allocation.
Let staged initiatives translate direction into change.
Let disciplined review reinforce commitments rather than override them.

Get Clear. Align. Grow.

Operations

From Tool to Teammate: Six Practices That Make AI Work for Us

Leave a comment

At IntelliVen, we work from a defined body of leadership and management practice: the Manage to Lead (MtL) System. It is documented in our text, taught in our classes, and organized into more than sixty tools and templates and 70 insights and tutorials. We use these tools every day with clients and trainees and we are gradually giving each one AI support.

Key points

  • We turned a defined body of work (Manage to Lead) into an AI teammate, IVOA.
  • What you load into AI and how you use it matters most: a focused core pack, clear logic, simple ground rules.
  • The same six practices can turn your content, tools, and methods into an AI teammate.
  • The payoff is on-demand access for many more people with higher quality and consistency.

AI, in the form of our custom GPT, IntelliVen Operations Advisor (IVOA), has become a working teammate we did not know we needed or could afford. Grounded in our MtL text and tool tutorials, IVOA extends our thinking and lifts the quality and consistency of our work. Hours become minutes, and the output is sharper and more thorough.

Serious content is moving this way. Professors and authors will pair their books, courses, and toolkits with AI teammates that know their material, use their language, and sit beside the users of their work (leaders for us; scientists for a science professor) as they think, decide, and act.

This makes the originator’s best thinking available on demand to anyone, anywhere, at any time, with no enrollment required. Much of the IP is free to access. Revenue comes from deeper engagement: subscriptions for full access and community features, and paid classes and consulting to apply the knowledge and logic to real cases. That is the shift from tool to teammate.

What follows is what we have done with MtL so far and six practices that make AI work for us: three to set up a teammate like IVOA and three to use it well. IVOA is something we use extensively in our own work, and it is equally open and available for anyone to use or adapt.

SET UP

These three steps prepared IVOA to perform as part of our team and are the same steps you can use to turn your own body of work into an AI teammate. In the configuration window that opened when we set up the GPT, we:

  • Loaded a small Core Pack as its working knowledge base
  • Uploaded logic tutorials so it thinks the way we do
  • Set default behaviors so tone and structure fit our brand

The Core Pack is our MtL textbook plus about a dozen of our curated tutorials, templates, and e-books, each under 10 pages. These materials and the ground rules persist in IVOA’s configuration, so we don’t need to upload or restate them each time we use it.

1. Loaded a knowledge base

On advice from participants in our Manage to Lead (MtL) Executive Alignment System for Operations and Governance training program, we loaded the Core Pack, our MtL text, e-book, tutorials, and prompt logic into IVOA. The impact was immediate.

Consider the contrast when we ask IVOA versus a generic AI: “What’s the purpose of a business?”

IVOA (MtL-aligned):
The purpose of a business is to solve a specific problem for a specific customer set.

  • Purpose is external: it’s about the customer’s problem, not your internal motivations.
  • Teams that stay clear on WHAT they deliver, to WHOm, and WHY the buyer chooses them execute better and grow faster.

Generic AI:
Provide goods or services to customers, generate profit, create jobs, and contribute to the economy.

Same question. Both answers are reasonable English. Only one is tight enough, and specific enough, to guide how leaders think, talk, and act.

2. Uploaded logic

We configured IVOA with the guts of Manage to Lead: detailed tool logic, what “good” looks like, common failure modes, and the assess-and-suggest moves we use across the tools. When it works on a task, it runs the same checks and upgrades we use with clients, not generic internet advice.

It also runs those checks more consistently and exhaustively than we do; where a human often stops once something is “good enough,” IVOA keeps applying the full set of tests and upgrades without getting tired or impressed with itself. That logic base changes how it sees and improves work.

Here is what that looks like on a simple WHAT–WHO–WHY.

Example: IVOA sharpening a WHAT–WHO–WHY

We asked IVOA to assess an early draft W-W-W for a “leadership training” offer.

Draft:

  • WHAT: Leadership training for managers who need to be more strategic
  • WHO: Mid-level managers in growing organizations
  • WHY: They are too focused on tasks and need to operate more strategically

IVOA’s assessment surfaced several issues and concrete upgrades.

Feedback on clarity and specificity

WHAT

  • “Leadership training” is a service, which is good, but it is broad. Name the deliverables a buyer can point to (for example, program format, length, and core components).
  • The phrase “for managers who need to be more strategic” mixes in WHO and WHY. Keep WHAT focused on the offer itself, not on audience or motivation.

WHO

  • “Mid-level managers” describes participants, not the buying decision-maker. Specify the role that approves budget (for example, Head of L&D, CHRO, BU leader) and add simple qualifiers such as organization size and context.
  • Tighten targeting by using traits like pain, urgency, economics, authority, and advocacy.

WHY

  • The draft states the problem (“too focused on tasks”) but not why buyers choose this offer over alternatives. Frame WHY in the buyer’s words, with evidence where possible.
  • A crisp, customer-voiced WHY anchors growth and alignment; teams that describe WHAT, WHO, and WHY the same way perform better.

Suggested upgraded WHAT–WHO–WHY

  • WHAT: A 12-week strategic leadership program that combines cohort workshops, on-the-job applied projects, and 1:1 coaching, with toolkits and manager-sponsor check-ins.
  • WHO: Head of Learning & Development or Business Unit leader responsible for developing mid-level managers in organizations of ~500–5,000 employees.
  • WHY: They choose us to reliably shift managers from task execution to strategic operating behaviors through applied work tied to their business, with measurable improvements in planning, delegation, and cross-functional outcomes; strong internal references and repeat sponsorship reduce adoption risk.

Notes to strengthen further

  • Add simple qualifiers to WHO (industry focus, region, typical team size) and score best buyers on pain, urgency, economics, authority, and advocacy to tighten the ideal customer profile.
  • Bolster WHY with proof points buyers trust (for example, internal references, completion-to-application rates), keeping the focus on the buyer’s reasons, not your beliefs.

Why this matters

  • A specific, shared W-W-W keeps teams aligned on purpose and choices.
  • Clarity on WHAT, WHO, and WHY is foundational to better execution and growth.

Without uploaded logic

We also ran the same draft W-W-W through a general-purpose AI assistant.

It told us, in effect: “This is a very clear and concise statement of purpose. It covers the three W’s and only needs minor refinement.” It praised the draft, offered some marketing polish, and suggested using it as-is as a mission or elevator pitch.

IVOA did something very different. It:

  • Flagged that WHAT mixed service, audience, and motivation and pushed us to name concrete deliverables
  • Pointed out that WHO described participants, not the buying decision-maker, and asked us to specify the role and simple qualifiers like size and context
  • Reframed WHY from “the problem” to “why buyers choose us over alternatives,” and nudged us toward buyer-voiced language and proof points
  • Produced a sharper, more specific W-W-W that we could actually use to target, sell, and deliver

Both AIs wrote in fluent, confident English. The difference is that IVOA is tuned to our Manage to Lead logic and tools. It does not just sound right. It pushes our thinking to be right for the way we run and grow organizations.

If you want to see this in your own context, try this sequence:

  • Write your current WHAT–WHO–WHY.
  • Paste it into your favorite general AI assistant and ask for feedback.
  • Paste the same W-W-W into IntelliVen Operations Advisor (IVOA) and ask it to assess and upgrade it.
  • Then ask IVOA to compare its assessment with the other AI’s response and explain the differences.

The value is not that it writes nicely. It is that it knows the logic, tools, and standards behind the work and helps you apply them. The same AI teammate we use in our work is available for anyone to use or adapt.

3. Configured ground rules

When we configured IVOA, we set clear ground rules for tone, structure, length, and emphasis. We gave these instructions once. We override them only when a task needs a different style.

With guidance

“Use a direct, executive tone. Short paragraphs. Bullets by default. No filler. Focus on operational impact and next actions.”
→ Output fits our brand.

Without guidance

The AI invents its own style (which can be annoying!).

Example default ground rules to paste into GPT config:

  • Tone: direct and executive; warm when appropriate.
  • Length: be concise; short paragraphs.
  • Altitude: start with a high-level summary; add detail on request.
  • Format: bullets by default; numbers only when sequence matters.
  • Structure for substantial replies: Context and aim; What we see; What to do next; Risks and tradeoffs; Optional variants or examples.
  • Emphasis: actions, owners, timing, concrete examples.
  • Avoid: em dashes, tropes, filler, sycophancy, purple prose. Use plain language.

USAGE

With setup complete, day-to-day work is straightforward. The next three steps set context for the task, share our best current draft, and iterate line by line until the result is crisp and on target.

4. Set context

Before asking IVOA for help, we share everything relevant about the situation. It doesn’t need to be organized or polished. Completeness beats polish:

  • Role
  • Audience
  • Stakes
  • Constraints
  • What’s working
  • What’s not
  • Why it matters
  • Who cares
  • Etc.

With context

“I’ll be addressing a cross-functional leadership team that’s behind on customer onboarding. They’re feeling pressure on service levels. I want to open by acknowledging that pressure and the opportunity ahead if we align on the few priorities that matter. Tone should be direct, not rah-rah.”
→ It sounds like us.

Without context

“Draft an intro for my conference talk on building a team.”
→ Generic, motivational filler.

Power comes from knowing your world: role, audience, situation, goals, style, what matters most. We use our Core language when it fits and skip the frameworks when they don’t help.

5. Draft best effort

We use AI as a performance multiplier, not a blank-page generator. A rough outline, memo, bullet list, or old deck is enough to start. Give it something to sharpen and it will. Tell it what’s working, and what isn’t, in your draft.

With a starting point

“Uploaded is the current job description and here is where the CEO is frustrated […]. Rewrite to highlight expected leadership behavior and desired outcomes.”
→ We get an on-target draft.

Without a starting point

“Write a job description for our COO.”
→ Might be fine, but generic.

6. Iterate

Iteration turns a good draft into a ready asset. Lead with focused passes, then keep what works and tune what doesn’t.

With iteration

  • We read and refine with specific notes: “Tighten the second paragraph.” “Swap these two points.” “Raise the stakes in the opening.” “Cut jargon.” “Add a concrete example here.”
  • We work paragraph by paragraph. We avoid whole-document rewrites. We lock improved sections and move on.
  • We ask for one or two alternatives when a paragraph is close but not quite there.
  • We run a zoom-out pass after paragraph edits. We check sequence and placement, merge overlaps, trim repeats, and fix transitions. We rebalance if one paragraph got over-developed in isolation.
  • We use the right tools. A canvas editor for inline comments. Side-by-side views to compare versions and keep the best parts.
  • We run a quality check. We confirm every word says what we mean, remove filler, and fix lines that sound good but are not accurate or relevant.

Example prompts:

  • “Revise paragraph 3 for clarity; keep the ideas; cut 20%; offer 2 alternatives.”
  • “Tighten paragraph 2 to three short sentences; keep key terms; offer 2 tone variants (direct, warmer).”
  • “Zoom out: propose a better section order for flow to decision; list what you moved and why.”
  • “Find and merge redundancies; flag any paragraphs with overlapping content; keep the stronger phrasing.”

Without iteration

We accept the first draft and leave quality on the table.

Summary points

  • Short, focused passes beat one big rewrite.
  • Lock improvements as you go.
  • Always zoom out after tightening parts.
  • Read every word before you ship.
  • When what you do becomes guidance or a template, add it to the Core Pack.

Try IVOA

IVOA is live and available for everyone to use.

Start by asking: “What can you help me with?”

Ways to work with and learn IVOA

We welcome questions, suggestions, and feedback.

Get Clear. Align. Grow.

 

Get Aligned, Operations

When there’s no right answer: get input, get commitment, then decide

Leave a comment

Calls about who the team counts on for what are hard. Leaders worry about making valued people feel overlooked or diminished. Direct reports mostly want clarity, fair reasoning, and as much scope and recognition as they can reasonably earn. This post offers a way to handle those tensions: get input one-on-one, secure commitment to support the outcome, then decide and lead alignment.

Before you decide on a consequential call about who the team counts on for what, check in one-on-one with those who will be most impacted. Use these 1x1s to get their best thinking and secure an explicit commitment to support the outcome, whichever way you go. Then decide, own it, and lead everyone to align and execute. Remember: there is no single “right” organization. What works is what your team commits to make work. Don’t chase the perfect answer; make a sound call and then make the call right.

Start each 1×1 by setting context. Explain the decision you have to make and why it matters now. Ask them to set aside self‑interest and give you their best view of what to do and why. Probe for what you may be missing, the main risks, and how they would mitigate them. Listen hard. You are not asking them to decide for you; you are gathering the input you need to make the decision you are accountable to make.

Close every 1×1 with a clear ask for commitment to support whatever you decide. Say plainly that it is your job to decide and that, when you do, you expect full support either way. Make sure they know that support means words and deeds, in the room and outside the room. If they hesitate, stay with it. Surface concerns now, while you can still use them. If after a real conversation they cannot commit, that is useful data about whether they are on this team for this next phase.

After you decide, announce the decision and the reasoning at a level that lets reasonable people understand how you got there. Remind the team of the commitments made in 1x1s. Set the expectation that leaders will be visibly and consistently supportive, especially when they share the decision with their teams. Organizations change best slowly because change is hard on people, so favor steady, incremental moves and keep everyone clear on what is happening, why, and what you need from them. Sometimes it is better to roll out a major change as a series of smaller changes over a longer period.

If support slips, use a three‑step response that matches the moment:

  • First slip: private reset. Meet one-on-one to reaffirm the decision and what support looks like—words and deeds, in the room and outside the room. Ask for explicit recommitment. If they hesitate, stay with it. Surface concerns now, while you can still use them. Leave with a clear “yes.”
  • Second slip: public correction. In the moment and in front of others, restate the decision and the expectation to align. Keep it short, neutral, and firm. Move the conversation back on track.
  • Third slip: in or out. Meet privately, with your inner circle if helpful, and make the choice explicit: be fully in and support the path we chose, or step out. This is about whether they are part of the team that moves forward in a specific way. If not, help them out.

Two mindsets make this work. First, own the call. Do not attribute the decision to advisors, the board, or the market. Once you know, own it. Second, get help without becoming dependent on it. Invite strong input and dissent, and then decide. Disagreement before the decision is input. After the decision, alignment is the standard.

How organizations evolve

Organizations are not fixed. Treat structure and roles as means to an end, and expect them to change as you grow.A short script you can adapt

  • “I need to make this decision. Before I do, give me your best thinking—what do you recommend and why? What am I missing? When I decide, can I count on your full support either way?“
  • “If you can’t commit, tell me now and we’ll address it. After I decide, we speak with one voice and execute.“

Why this works is straightforward. Everyone is heard and treated with respect. Commitment is explicit, not assumed. You show up as decisive and fair. And if misalignment appears, you handle it quickly and cleanly.

Next steps

  • Run the 1x1s. Use the script above. Capture each leader’s recommendation and explicit commitment in writing.
  • Book an IntelliVen workshop for your ELT. A focused 60–90-minute session to practice the Input → Commitment → Decide method on a real decision. Includes prep and a follow‑up plan.
  • Enroll in Manage to Lead (MtL) training. Apply the seven truths and the W‑W‑W framework to your strategy and org design.
  • Share the “How organizations evolve” section with your ELT. Ask each leader to name one risk and one action to support the change.
  • Set a cadence checkpoint. For the next four ELT meetings, include a 10‑minute alignment check on this decision.
  • Want help? Invite IntelliVen to facilitate your first round of 1x1s or the in‑or‑out conversation.

Get Clear. Align. Grow.

Operations

Say the Same Words. Mean the Same Things.

Leave a comment

Walk into almost any leadership meeting and you will hear the same words:

  • Vision.
  • Strategy.
  • Mandate.
  • Values.
  • Culture.

Everyone nods. Everyone is confident they understand.

Then you listen a little longer and realize something important:

People are using the same words to mean different things …
and different words to mean the same things.

That small problem with language quietly becomes a big problem with performance.

Teams are smart and committed, yet they talk past each other because their mental maps are not the same.

This post introduces a simple fix: agree, explicitly, on what key words mean and commit that one word will not do the job of two, and two words will not mean the same thing.

Shared language is the first step to:
Get Clear. Align. Grow.

Language as a leadership tool

Words matter. Great leaders start by making sure everyone uses the same words in the same way.

When a leadership team shares precise meanings for core terms:

  • Decisions are faster because people are not debating definitions.
  • Priorities are clearer because everyone knows where each topic “lives.”
  • New leaders and staff get up to speed faster because there is one map, not many.

When meanings are fuzzy, the opposite happens:

  • “Vision” and “strategy” get blurred.
  • “Operations” and “management” are used interchangeably.
  • “Values” and “culture” are treated as the same thing.

The result is good people working hard on different versions of the job.

 

The Executive Alignment Map: one word, one meaning

At IntelliVen, we use the Executive Alignment Map below, where each of seven core words has an unambiguous meaning. The definitions are ours and offered for convenience. You don’t have to adopt them. What matters is that your team agrees on what each term means. Alignment begins with a shared vocabulary.

  • Vision: Where we are headed and why, about 10 or more years out.
  • Strategy: How we plan to win in the marketplace over the next 5 years or so.
  • Mandate: The milestone by when. The 3–5 year target that turns strategy into concrete ambitions.
  • Management: How we plan, build, and assign work so that the Mandate and Strategy get done.
  • Operations: How we do, sell, and grow every day to serve customers and deliver results.
  • Values: The beliefs that shape behavior and guide decisions, especially when tradeoffs are hard.
  • Culture: Values in action. How it actually feels to work here and with us.

Every organization has these elements. The key is to make them explicit, consistent, and shared by those who lead.

  • Vision is not a slogan.
  • Strategy is not an initiative.
  • Mandate is not a task list.
  • Values are not posters.
  • Culture is not a slide in the onboarding deck.

Once the top team adopts this shared map, everyone knows what conversation they are in and where it fits in the bigger picture.

Why this matters so much

Here is what tends to happen before there is a shared language:

  • A CEO says, “We need to revisit our strategy,” but what they really mean is the Mandate (the 3–5 year numbers and milestones). The team hears “new product bets” and “market moves” and they start working on something different.
  • HR talks about “culture work” but is really redesigning processes and management practices. Operations leaders hear this as “soft stuff” and disengage, even though the changes will affect them directly.
  • A board member asks for “more visibility into operations” and the team responds with detailed project plans (management) instead of how the business actually does, sells, and grows.

The words are familiar, so no one notices the disconnect right away. Yet misfires accumulate. Time and energy are lost. Frustration grows.

When a team decides, together, what each word means, three things change:

  • Conversations become shorter and more focused.
  • Disagreements become about real choices, not vocabulary.
  • People at every level gain confidence that they understand “how things work around here.”

One simple practice to try with your team

If you want to experience the power of shared language, try this:

Ask each member of your leadership team, privately, to write down their definition of:

    • Vision

    • Strategy

    • Mandate

    • Management

    • Operations

    • Values

    • Culture

Bring the definitions to your next offsite or leadership meeting.

Compare them side by side, either by hand or by feeding everyone’s entries into IntelliVen Operations Advisor (IVOA), and circle or highlight where they differ.

You will likely find that:

  • Some people skip a word completely and fold its meaning into another.
  • Some use the same word for very different ideas.
  • A few are surprisingly aligned, which gives you a head start.

From there, work as a group to settle on one short, shared definition for each word, using the Executive Alignment Map as a guide.

Document your final list. Use it in meetings, in onboarding, and in your MtL work. Refer back to it when discussions drift. Over time it becomes part of how you manage and lead.

Do not assume your words are their words

Not assuming that others use key words the same way you do is especially important when you work with people from a different organization, whether you have joined a new company, are serving a client, or are partnering with another team.

It is natural to assume that words like “strategy,” “plan,” “mandate,” or “operating model” mean what they meant in your last organization. Often they do not. Teams may use familiar terms in very local and specific ways.

In a new setting, it helps to:

  • Ask early how people use a few key words.
  • Listen for how those words show up in real conversations, not just in formal definitions.
  • Notice where your own definitions are different from theirs.
  • Decide whether to adopt their language, or to work together to reset a few key terms.

What matters most is that you do not assume. You surface differences in meaning early and work toward shared definitions instead of talking past each other for months.

Connecting to your MtL work

In the Manage to Lead system, “Get Clear” always comes first. Tools like:

  • WHAT–WHO–WHY (W-W-W)
  • Mandate
  • Change Framework

all work better when the team shares the same language.

Sorting out the terms covered in this post is just a start. Throughout MtL we unpack important words in a similar way. Each module highlights at least one key term that is easy to gloss over but matters a lot in practice. For example, in Module 4 we sort out the difference between a budget, a forecast, and a working view so leaders stop talking past each other when they talk about “the numbers.”

You can think of shared vocabulary as the foundation.
MtL tools are how you build on it to think, decide, and act.

If you are using MtL on Maven or working with IntelliVen advisors, consider making the Executive Alignment Map your first stop. Agree on the words. Agree on the meanings. Then build everything else on top.

Say the same words.
Mean the same things.
That is how you Get Clear. Align. Grow.

Next Step

If you want help putting this into practice with your leadership team, you can schedule a workshop with IntelliVen or enroll in a Manage to Lead (MtL) training program.

To explore what’s right for you, get in touch with us and we’ll follow up to discuss next steps.

Glossary of MtL Terms

Get Clear, Manage to Lead, Operations

Purpose and Goals: Why You Need Both W-W-W and Mandate

Leave a comment

W-W-W and Mandate: Two Distinct Tools, Both Essential

When working on their business, leaders sometimes ask: Which sequence is right?

W-W-W → Mandate

Mandate → W-W-W

Both sequences work. You need to work on both.

W-W-W is about purpose. It clarifies identity by answering three simple but interconnected questions:

  • WHAT do we provide?
  • WHO do we serve?
  • WHY do they choose us?

This is the cornerstone of clarity, rooted in Drucker’s insight that the purpose of a business is to solve a problem for a customer.

The Mandate is about goals. It defines what must be achieved, financially and non-financially, in a time frame. It sets targets, aspirations, and milestones. Where W-W-W establishes identity, Mandate locks in success conditions.

Though related, they require distinct lines of thinking:

  • W-W-W = identity and purpose
  • Mandate = success conditions and commitments

Which comes first? Both sequences work:

  • Mandate first: If you like Covey’s “Begin with the end in mind,” Mandate lays out the outcomes that guide everything else.
  • W-W-W first: Ensures that goals tie back to a clearly expressed purpose.

What matters more is that teams use both. W-W-W brings clarity of purpose. Mandate brings clarity of outcomes. Together, they create a foundation for alignment, prioritization, and growth.

W-W-W and Mandate aren’t one-and-done — they evolve together and become the backbone of the story you tell, tailored to what you need to say and to whom.

So, whether you start with W-W-W or Mandate, don’t stop until you’ve done both. And remember, they aren’t “one and done.” As your organization grows, work on one will often lead you to refine the other. Together, they form the backbone of your storyboard — a foundation you can adapt depending on what you need to say, and to whom.

Put These Ideas Into Practice

In the Manage to Lead (MtL) program, you don’t just study tools like Mandate and WHAT-WHO-WHY, you apply them directly to your own organization. YOUR CASE IS THE COURSE. By working hands-on with proven frameworks, you and your team surface hidden assumptions, sharpen execution, and accelerate performance. Learn more about the MtL program here »