Integrated Journey
Team Performance ArchitectureA development program for a whole team
Team Performance Architecture is our program for a whole team, together with its leader. Over about six months, the team works through all four Capability OS domains in 12 two-and-a-half-hour labs, applying each one in its own meetings between sessions.
- Duration
- about 6 months
- Rhythm
- one 2.5-hour lab every 2 weeks
- Participants
- the whole team, with its leader
- Format
- on-site or online
Who it’s for
When does a team need Team Performance Architecture?
The problem usually arrives as one sentence: “the people are good, but the team isn’t performing.” Day to day, it shows up like this:
- Meetings are polite, and the real issues get discussed afterwards, in the corridor or in private messages.
- Everyone has a different idea of what the team’s priority is this week.
- Decisions made together get reopened because it was never clear who had the right to make them.
- Commitments from one team meeting are lost by the next.
- Tension between two people ends up slowing the whole team down.
- The team repeats the same mistakes from project to project, and retrospectives change nothing.
Want to develop managers from several teams? Manager Operating System →
Is the problem in the leadership team? Executive Capability Journey →
The journey
What does the team work on in the 12 labs?
Four domains, three labs each. The order differs from the manager program: we start with Dialogue, because in a whole team nothing gets fixed without a base of honest conversation. If people don’t say what they think, clarifying priorities and accountability stay theater. On that base we build Clarity and Accountability, and Learning closes the program with the routines that let the team improve on its own.
01 · Coordination
Dialogue
The base: the team says the hard things, on the issue.
- Lab 1Listen before you answerActive Listening & Understanding
- Lab 2Disagreement that buildsConstructive Dissent & Conflict Navigation
- Lab 3Feedback that changes somethingFeedback Exchange
02 · Direction
Clarity
What we are actually working on, and who decides.
- Lab 4From ambiguity to clear prioritiesPriority Translation
- Lab 5Who actually decidesDecision Ownership
- Lab 6Delegation without ambiguityExpectation Framing
03 · Execution
Accountability
Commitments that are kept, real ownership, correction without drama.
- Lab 7From intentions to commitmentsCommitment Discipline
- Lab 8Real ownershipOwnership & Follow-Through
- Lab 9The correction conversationPerformance Correction
04 · Adaptation
Learning
The routines that let the team improve on its own.
- 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. Dialogue stays first: it is the foundation the other three rest on.
Between sessions
What happens between the labs?
The lab is the smaller part. The change happens in the two weeks between sessions, in the team’s ordinary meetings.
- Before each lab
- a short microlearning: one video and a one-page job aid.
- AI practice, twice a week
- scenarios built on each team member’s real situations, with feedback against the program’s models.
- A field assignment
- every lab ends with something to do together the following week, in the team’s own meetings. The next lab starts from what happened.
- Real cases
- before each lab, the sponsor sends us a live situation from the team, so the drills are about your work, not a generic case study.
- The team leader
- is part of the program alongside the team, not watching from outside. What they practise in the lab goes straight into the meetings they run.
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 team leader observes the same behaviors in each team member 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 of the team, 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 questions 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 team leader’s 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 the team does together in its ordinary meetings. It is built to run alongside the work, not instead of it.
A team that works together day to day, with its leader: a project team, a department, a product team. It fits when the problem is how the team works together, not only the skills of each person. If you want to develop managers from several teams, Manager Operating System is the right format. For the leadership team, there is the Executive Capability Journey.
A team building day brings the team together and can bring people closer. Team Performance Architecture works on how the team functions in its real work: how it says things, how it decides, how it keeps its commitments and how it learns from its own mistakes. Every lab is followed by application in the team’s meetings, and progress is measured before and after.
Because in a whole team, priorities and commitments depend on what people can say to each other. If disagreements stay unspoken, “agreed” priorities aren’t kept and commitments are made for show. After the first domain, the team uses what it has practised to settle what it is actually working on and who decides.
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. Practice between sessions stays in the same language as the labs.
Pricing depends on the size of the team, 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
- 10 factors that raise team effectiveness (and how to find your constraint)
Most lists mix symptoms with causes. Here are the factors that genuinely move team effectiveness, and how to identify the one blocking your team now.
- What makes a team effective? A definition you can actually measure
An effective team isn't one where people get along. There are three outcome criteria and the conditions that produce them, plus a test you can run this week.
- Team cohesion is not team performance. What team building can and cannot buy
Teams that like each other aren't automatically effective. Research separates social from task cohesion: only one tracks performance. Here's which.
- 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.
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.