Operating the program

The 5-step rollout is how the program starts. This page is how it stays alive.

Behavior-change research is consistent: leadership programs die between weeks six and ten unless they have a sustained operating rhythm. That six-week gap is where most programs quietly become paperwork — the language is still on the wall, but nobody is using it on real work. This page is the operating rhythm that prevents that gap.

This is the longest page on the site. Most readers will not need it. The people running the program need it.

Why a rhythm matters more than the content

The content of the program is already strong. It is not the bottleneck. Two real failure modes break programs like this one:

1. No structural reinforcement past day 30. Without a rhythm beyond the initial training, the median manager reverts to prior behavior by week eight. The training stuck just long enough to be remembered but not long enough to take root.
2. A senior leader fumbles the first hard escalation. A single visible mishandling of bad news within the first quarter teaches everyone in earshot that the new language is performative. The program loses credibility faster than it built it.

The first failure mode is solved by a regular cadence of small, disciplined check-ins. The second is solved by preparing the senior leaders specifically and explicitly before anyone else gets the program. Both are covered below.

The review rhythm: 30, 60, 90, 180 days

One review is not enough. The rhythm below is what behavior-change practice considers the floor — not the ceiling.

Day	Pulse	What you are listening for
30 days	Process pulse	Did we hold the meetings? Did we use the templates at all? Did the agreed habits get tried?
60 days	Skill pulse	Are people getting more comfortable with the language? Where are we still awkward? Which template is helping; which feels like paperwork?
90 days	Outcome pulse	Are decisions visibly faster or clearer than 90 days ago? Are escalations arriving earlier? Are meetings ending with owner, next step, and date?
180 days	Cultural pulse	Has behavior shifted when nobody is watching? Do people use the language with each other in side conversations, not just in formal meetings?

Each review is 30 to 45 minutes with the leadership cohort. Run them on a single recurring calendar series so they stay on calendars even when the quarter gets busy.

If you skip the 60-day review, the 90-day one will look like a post-mortem instead of a checkpoint.

Peer-coaching pairs for 90 days

The single cheapest, highest-leverage move available to any program like this. Pair every leader in the cohort with one other leader for the duration of the six sessions plus 90 days after.

How the pairs work

• One pair, two people. Not a triad. Not a group.
• 15 minutes per month, scheduled on a recurring series. Either in person, on a video call, or on a walk.
• Two questions, in order:
  1. Where did you use the language this month?
  2. Where did you not use it, and what would you do differently?
• That is the entire format. Resist the urge to add structure.

How to assign the pairs

• Pair across business units when possible. Same-unit pairs reinforce existing patterns; cross-unit pairs surface them.
• Avoid manager / direct-report pairs. The peer dynamic is the point; power asymmetry compromises it.
• Do not let people pick their own pair. The friend-pairs predictably drift into venting; the cross-unit pairs predictably surface real observations.
• Rotate pairs every 90 days if the program continues. New pairings surface new patterns.

What the pairs are not

• Not a coaching certification.
• Not a performance-review input.
• Not graded or reported to HR. Aggregate themes from anonymous opt-in notes are useful; named observations are not.

The one-habit anchor

Each leader picks exactly one habit from the program and commits to it for 90 days. Just one.

The cognitive-behavioral research is consistent: one specific habit practiced for 90 days outperforms five intentions practiced for one quarter. Given five new behaviors to try, most people will try all five poorly for two weeks and then drop all five.

Examples of a one-habit anchor

• “I will end every meeting I run with owner, next step, and date — even when the meeting is short.”
• “I will use green / yellow / red / blocked on my own weekly status, in writing, every week without skipping.”
• “Every time bad news arrives at my desk, my first sentence will be ‘thank you for raising this now.’”
• “Every project I own will have a written not doing line before I start it.”

Where the one-habit anchor lives

• On the leader’s Quarterly Goal Sheet, as a dedicated field.
• In the peer-coaching pair’s monthly conversation — question 1 (“where did you use the language”) is in practice the one-habit check-in.

Templates audit at 60 days

The 60-day review includes a templates audit. The rule is simple:

Each leader brings one template they have used on real work in the last 30 days. Not the one they filled out in a session. The one they used on real work.

If a leader cannot bring one, that is data. No punishment. No performance flag. Just visibility into which templates are pulling weight and which are paperwork.

What we do with the data

• If a template has not been used by anyone after 90 days, retire it. The program should be willing to shrink its surface area when evidence justifies it. Most programs only grow.
• If a template is used heavily but feels like paperwork, the template probably needs a shorter form. Ask the users to redesign it, not the program owner.
• If a template is used heavily and feels useful, mark it as a “core template” in the next program cohort’s rollout. Lead with the templates that win.

This audit is the only mechanism in the program that catches a template becoming busywork before it spreads.

The annual 360 prompt

Once a year, the people each leader leads answer one prompt:

Does this leader actually use the program’s behaviors? Specifically:

• Do they end meetings with owner, next step, and date?
• Do they respond to bad news with thanks rather than blame?
• Do they fix processes before blaming people?

Give one example for each that you would point to.

Why this works when most 360 reviews do not

Most 360 instruments measure vague competencies (“exhibits leadership presence”) that nobody can falsify. This one is anchored in three observable behaviors with a real answer pattern. “Did this person end the Tuesday review with an owner and a date?” is a yes-or-no question that can be answered honestly.

Rules of use

• Anonymous responses, aggregated.
• The aggregate goes to the leader and the leader’s leader, in that order.
• Specific examples are written; specific complaints are not. The point is observation, not grievance escalation. Anyone with a grievance has HR.
• The annual rhythm matters: more often than yearly degrades into performance noise; less often than yearly fails to catch drift before it cements.

This is the only mechanism in this entire program that meaningfully catches the gap between what a leader says they do and what they actually do. It is heavy. It is also the load-bearing structure of the program’s long-term integrity.

The “program is being used as a weapon” channel

A simple email address or short form — for instance, program-watch@aspiriq.example — where any employee can flag:

“[Person] used [phrase or behavior from the program] in [situation] to do [thing that contradicts the program’s intent].”

HR receives. Patterns are tracked privately. The point is not punishment per report. The point is surfacing the gap between stated values and lived reality before it metastasizes invisibly.

The HR commitment that makes this work

This channel only works if HR acts on patterns. If reports go in and nothing visibly changes, the channel becomes proof that the program does not hold its own line — and the cynicism deepens.

The commitment to staff at launch is something like:

“We will not investigate one-off reports. We will track patterns. If we see a pattern that suggests the program is being used in ways the Guardrails prohibit, we will act. If we choose not to act, we will be able to explain why.”

Without that commitment, do not launch the channel. A dead channel is worse than no channel.

The program’s own success measure

The program teaches every leader to write goals with measures. The program itself needs the same discipline.

Simple version (recommended for the first cohort)

At 180 days, do meetings of the participating cohort end with owner, next step, and date 80% of the time?

This can be sampled by a single observer (HR or a designated cohort member) attending a randomized sample of 10 meetings and counting. That is enough to know.

If yes, the program is working at its most basic level. If no, the program is paperwork regardless of what surveys say.

Rigorous version (year 2 and beyond)

Compare two counts in the 90-day window before the program and the 90-day window starting 90 days after the program:

• The number of escalations raised by participants’ teams.
• The number of project surprises (a deliverable misses a date or changes scope without prior status warning).

A program working as designed produces:

• Escalations: up. People are surfacing problems earlier.
• Surprises: down. Early surfacing is paying off.

A program being used cosmetically produces:

• Escalations: flat or down. People are still hiding things.
• Surprises: flat or up. The hiding is catching up to teams.

Two simple counts. Honest signal. Nothing fancy.

Session 0: senior leaders go first

Before the main rollout reaches the broader team, run a separate session with only the senior leadership cohort. This is not a content session — they have read the guide. It is a structured 90-minute session where senior leaders:

• Publicly commit, in front of each other, to which two or three behaviors from the program they will be personally observed on this quarter.
• War-game the Session 4 “Good” response to the two or three most likely “first hard escalations” the company could plausibly receive in the next 90 days.
• Practice the receive-bad-news pattern with each other before any subordinate tests it.
• Grant each other explicit permission to be called out by peers when they violate the program.

The full Session 0 facilitator script lives on its own training page (coming next; see Training plan). The point is that this session is non-optional for senior leaders. The program’s biggest risk is a senior leader who has not done this work.

When to retire content

Most programs only grow. This one is committed to pruning.

• If a template has not been used in real work by anyone in the cohort after 90 days, retire it.
• If a session derailment pattern shows up in fewer than 10% of sessions, drop it from the redirect table to reduce cognitive load on the facilitator.
• If a principle is never quoted, never used in a conversation, and never referenced in a Look-Back Review for two full cohorts — it is dead text. Cut it.

This page itself should be reviewed every two years. If the operating rhythm is now habitual and nobody needs the explicit instructions here, this page can shrink. That is success, not failure.

A short note to the program owner

You will be tempted to skip the 60-day review when the calendar gets busy. You will be tempted to let the peer pairs degrade into “coffee” with no notes. You will be tempted to launch the weaponization channel without the act-on-patterns commitment because it feels easier.

Resist all three.

This is not a content program. The content is fine. This is an operating-rhythm program. The rhythm is what makes the content stick. Without the rhythm, the language survives for one quarter. With it, the practice survives for years.