Integrated Journey
Manager Operating SystemA development program for managers
Manager Operating System is our development program for middle managers and team leads. Over about six months, a cohort of 8–12 managers from different teams works through all four Capability OS domains in 12 two-and-a-half-hour labs, applying each one with their own team between sessions.
- Duration
- about 6 months
- Rhythm
- one 2.5-hour lab every 2 weeks
- Cohort
- 8–12 managers (15 at most)
- Format
- on-site or online
Who it’s for
When does an organization need Manager Operating System?
The problem usually arrives as one sentence: “our managers don’t lead consistently.” Day to day, it shows up like this:
- Teams list different priorities, and the priorities shift from one meeting to the next.
- Decisions get reopened two weeks later, and too many of them climb back up to directors.
- Commitments made in meetings have no owner, and nobody follows them up.
- Hard conversations, about performance or disagreement, wait for the annual review.
- The same mistakes come back from one project to the next.
- Managers have been on courses, yet each one still leads their own way.
Working with one team and its leader? Team Performance Architecture →
Is the problem in the leadership team? Executive Capability Journey →
The journey
What do managers work through in the 12 labs?
Four domains, three labs each, in the order a team actually runs: direction first, then execution, then the conversations, then learning. We open with Clarity and Accountability because that is where change shows up fastest in day-to-day work.
01 · Direction
Clarity
What matters now, and who decides.
- Lab 1From ambiguity to clear prioritiesPriority Translation
- Lab 2Who actually decidesDecision Ownership
- Lab 3Delegation without ambiguityExpectation Framing
02 · Execution
Accountability
Commitments that are kept, real ownership, correction without drama.
- Lab 4From intentions to commitmentsCommitment Discipline
- Lab 5Real ownershipOwnership & Follow-Through
- Lab 6The correction conversationPerformance Correction
03 · Coordination
Dialogue
The conversations the team avoids.
- Lab 7Listen before you answerActive Listening & Understanding
- Lab 8Disagreement that buildsConstructive Dissent & Conflict Navigation
- Lab 9Feedback that changes somethingFeedback Exchange
04 · Adaptation
Learning
What the team does with what it finds out.
- Lab 10From experience to lessonReflection & Sensemaking
- Lab 11Test, don’t debateExperimentation & Adaptive Action
- Lab 12The lesson becomes routineKnowledge Integration & Team Learning
If the diagnostic flags one domain as critical, it moves up to second place. Never first: the opening domain has to deliver quick wins for the rest of the program to build on.
Between sessions
What happens between the labs?
The lab is the smaller part. The change happens in the two weeks between sessions.
- Before each lab
- a short microlearning: one video and a one-page job aid.
- AI practice, twice a week
- scenarios built on each manager’s real situations, with feedback against the program’s models.
- A field assignment
- every lab ends with something to do with your own team the following week. The next lab starts from what happened.
- Real cases
- the sponsor sends us live situations from the organization before each lab, so the drills are about your work, not a generic case study.
- The participants’ own managers
- get a briefing at the start and a short weekly prompt on what to watch for and what to ask. At the start and at the end of each domain, they run a structured observation of the same behaviors.
How it runs
The same spine, adapted to the program.
The program spine: from diagnostic to review
Measurement
How is progress measured?
- Baseline
- at the start, the first domain’s questionnaire plus organization-level signals; for each later domain, a pre-test about ten days before it opens.
- After each domain
- a post-test at the end of the two-week application period, in which participants also rate how much they feel they have changed on each capability. The line manager observes the same behaviors twice, at the start and at the end of the domain.
- At the end
- a full re-measurement across all 12 capabilities: a before-and-after map, the centerpiece of the final review.
- For the sponsor
- a 30-minute review as each domain closes, and an executive review at the end.
The rubrics are the same before and after, so progress can be compared rather than described. How much participants feel they have changed is reported next to the measured change and the managers’ view, and never goes into the score.
Frequently asked questions
One 2.5-hour lab every two weeks, twelve in all, over about six months. Between labs: a short microlearning before each session, AI practice twice a week, and a field assignment with their own team. It is built to run alongside the work, not instead of it.
Middle managers and team leads from different teams, in a cohort of 8–12 people (15 at most). If you want to work with one team and its leader, Team Performance Architecture is the right format. For the leadership team, there is the Executive Capability Journey.
A course delivers content over a day or two. Manager Operating System builds behavior over time: every lab is followed by application with the team, practice, and the line manager’s observation, and progress is measured before and after against the same rubrics. The content matters, but the change happens between sessions.
Yes. Each domain also runs on its own, as a Domain Lab. We recommend starting with the diagnostic, then the domain with the largest gap, and extending to the full journey once you have seen the before-and-after map for that first domain.
Yes. Labs run at your offices or online, in Romanian or English. Mixed cohorts with managers from several countries work in English. Practice between sessions and the material for line managers stay in the same language as the labs.
A before-and-after map across the 12 capabilities for the whole cohort, a 30-minute review as each domain closes, and a final executive review. The map shows where behavior has moved and where it still needs reinforcing.
Pricing is set per cohort and depends on the number of participants, the language, the format (on-site or online), and how much we tailor the cases. We give you a concrete price after the first conversation, once we know what you want to change.
Further reading
- The newly promoted manager: what's missing isn't character, it's a mandate
A newly promoted manager rarely fails on character. What Gallup and CMI research shows, and the four things to put in writing in the first week.
- Why managers think they are clear (and their teams do not)
Leadership clarity isn't a communication style. It's three capabilities: priority translation, decision ownership, expectation framing. Here's the evidence.
- Why accountability fails in most teams (and what actually fixes it)
Accountability isn't toughness or pressure. It's three capabilities: commitment discipline, ownership, and correction. Here's the research and the practice.
- Why polite teams underperform (and how to build dialogue capability)
Most teams confuse politeness with dialogue. Real dialogue is three capabilities: listening, dissent, feedback. Here's the research and the practice.
- Why most lessons-learned reviews change nothing (and what builds real learning)
Organizational learning isn't retrospectives. It's three capabilities: reflection, experimentation, integration. Here's the research and the practice.
Start with a conversation
Tell us the behavior you need to change. We’ll show you the system that changes it.
A 30–45 minute diagnostic conversation, no pitch deck. You’ll leave with a sharper read on the capability gap, whether or not you work with us.