Talk it through with Aurelius
Library›Aurelius›The problem
Aurelius · Work & Leadership
Knowledge + Guidance

Why can I run a program but not make it land org-wide?

You can design a program, sequence the work, and deliver it. That part you have mastered. Then you try to make it stick across the whole organization, and it stalls — not because the plan is bad, but because people who were never in the room must now agree to change how they work. This is not a flaw in you. It is a different craft from the one you've built. Running a program rewards clear thinking and discipline. Landing it everywhere rewards reading people — who holds real power, who feels threatened, who needs to be asked rather than told. Stop blaming the plan. The plan was never the problem. Go learn who decides, and what they need from you before they will say yes.

◆ How this problem reads on the two dials
GuidanceKnowledge
More coaching
Some to learn
1:1 with AureliusWith others (a Pod)
Mostly you & the coach
A little with peers
You already know how to run a program; the missing piece is acting differently with people, which is learned by doing, not by more theory.
How the two dials adapt to you →
What’s really going on

Your program works. The organization hasn't moved, because moving an organization is a human act, not a technical one. You cannot run it into people the way you ran it into a system. Find who actually decides, learn what they need to say yes, and give it to them. That is the entire skill.

🔒 What you’ll build togetherUnlock by starting
A moveMap the real decision-makers — not the org chart, the people whose yes actually matters.
A moveBefore you pitch anyone, ask what they need to see to say yes. Build that first.
A moveFind who loses something if this change lands. Go to them before they come to you.
A moveChoose one ally with real standing. Let them explain the change — not you.
A moveStop measuring progress by how finished your plan is. Measure it by who has said yes.

What changes unlock by starting

  • You can name the people who actually decide whether this lands, not just who outranks you.
  • You walk into the next rollout with a plan for resistance, not just for execution.
  • You stop mistaking a good plan for an accepted one.
  • You have at least one person inside the organization carrying the message for you.
One object, two jobs: a public answer to a real problem, and — the moment you start the chat — Aurelius’s live plan for your version of it.