Leadership Team Development: A 90-Day Plan
Leadership team development is the work of turning a group of senior individuals into one decision-making unit. Most organizations buy individual development instead, then wonder why the executive meeting still runs the way it did in March.
What is leadership team development?
Leadership team development is the work of making a group of senior individuals function as one decision-making unit. It targets what happens between the members: how a decision gets made and whether it stays made, how disagreement surfaces, how fast bad news travels upward, and whether a commitment made on Tuesday still holds on Friday. That is a different problem from developing each executive as a leader, and it fails most often because organizations buy the second and expect the first.
The distinction matters commercially. Individual development is easier to sell, easier to schedule and easier to deliver, so most of the market is built around it. Then the coaching finishes, everybody has a stronger personal profile, and the Monday executive meeting runs exactly as it did before.
Developing individuals versus developing a team
Both are legitimate. They do different jobs and they are measured differently, and confusing the two is the single most expensive planning error I see in December budget conversations.
| Question | Individual leadership development | Leadership team development |
|---|---|---|
| What it targets | One person's capability, judgment and self-awareness | The relationships and operating habits between members |
| What it changes | How that person leads their own function | How the group decides, disagrees and holds commitments |
| What it cannot fix | A decision process that reverses itself outside the room | A member who lacks the capability for the seat they hold |
| How it is measured | 360 feedback, promotion readiness, personal goals | Decision quality and speed, team-level behavior scores, the spread between members |
Read the last row carefully, because it is where most programs fail. A 360 report tells you how one executive is experienced by the people around them. It says nothing about whether the eight of them together can make a decision that survives contact with the corridor. For a broader view of what the individual job involves, team leadership covers the person side of this. Everything below is about the unit.
The four ways senior teams actually fail
Thirty years of sitting in these rooms, first as a Marine and then with executive teams, and the failures are consistent. Four patterns cover almost all of it.
Decisions get reversed outside the room. The team agrees. Two people walk out unconvinced, have a corridor conversation, and the decision is quietly renegotiated over the following week. Nobody lies. The decision simply was not real, because the disagreement was never spoken while there was still time for it to count. Teams with this pattern tend to look calm in the meeting and slow everywhere else.
An unresolved two-person conflict that everyone routes around. Two executives stopped working directly with each other eighteen months ago. Their teams now coordinate through a third function, agendas get built to keep them apart, and half the organization has learned the workaround without ever being told about the problem. The cost is carried by people four levels down who have no idea why the process is shaped that way.
An unspoken pecking order. Formally the team is flat. In practice, two voices carry, one is ignored, and one person speaks only when directly asked. A functioning senior team is not one where everybody talks equally. It is one where the quietest member's objection changes the outcome when it is right. If nobody can remember the last time that happened, the order is doing the deciding.
A CEO who runs the meeting as a series of one-to-ones. Each member reports, the CEO responds, the others wait for their turn with laptops open. Nothing in that format requires the team to be a team, so it never becomes one. This is the most common pattern of the four and the easiest to change, because it lives entirely in how one meeting is run.
Robert W. Jones puts it well: no one person owns trust. In a senior team, that is not a sentiment. It describes why the CEO cannot fix any of these four alone, and why a program aimed only at the CEO does not move them.
What has to be true before a program will work
Three conditions. When they are missing, the money goes anyway and the result is a pleasant two days that changes nothing.
The leader participates as a member. Not an opening address followed by a departure for a board call. If the CEO is in the room for the diagnostic and the difficult session, the team treats the work as real; if not, the team correctly reads the priority and behaves accordingly.
There is a real baseline. Something measured before the work starts, so that in ninety days there is evidence rather than an impression. Senior teams are the population most likely to overrate their own trust, and there is data for that: the 2024 Edelman Trust Barometer Special Report on Trust at Work found 91% of executives say they trust their employer while only 70% of front-line associates do, and that just 19% of associates trust their CEO to tell the truth about the organization against 52% of executives. The gap between how it feels at the top and how it works further down is exactly what a baseline catches.
The problem has a name. Not the development of the leadership team. A specific behavior, written in plain language, that the team agrees is costing something: decisions taking three weeks that should take three days, or two functions that have stopped escalating to each other. A named problem gives the program a finish line and gives the offsite something to be about.
The 90-day sequence
Ninety days, four phases. The proportions matter more than the exact dates: a short diagnostic, a short intensive, a long practice window, and a hard stop where you decide what continues.
Days 1 to 14: baseline and diagnostic
Score the team against defined behaviors and interview every member individually. Both. The scores give you a comparable number and a spread; the interviews give you the thing nobody writes down in a form, which is usually the two-person conflict from the section above. Keep individual scores private and report the team view. Announce what you are doing and what happens to the results before you collect anything, because a senior team that discovers it has been measured in secret will spend the next quarter proving it.
The five-day compressed version of this baseline is in how to score your team's trust in one week, and it works perfectly well for a first pass.
Days 15 to 21: an offsite with a method, not an agenda
Two days, ideally away from the building, built around the diagnostic rather than around a speaker. The team sees its own data, argues about whether it is true, and leaves with a small number of named behaviors. What separates this from every offsite the team has already survived is that the content comes from the room rather than from a deck. The way we structure this in executive team building engagements is diagnostic first, method second, and no content that the team has not already seen a version of in its own numbers.
Days 22 to 60: practice, with named behaviors
This is where the quarter is won or lost, and it is the phase most programs skip. Each member picks two behaviors, with a practice window attached: which meeting, which moment, what it looks like when it happens. These are Micro-Trust Activations™, small repeatable acts rather than initiatives. Stating the owner and the date at the end of every decision. Raising an objection in the room rather than after it. Closing the loop on a commitment without being chased.
Five weeks is long enough for the behavior to be tested by a genuinely bad week, which is the only test that counts.
Days 61 to 90: re-score and decide what continues
Same instrument, same wording, same people. Compare. Then make an explicit decision about what carries into the next quarter and what stops, and say the stopping part out loud. A program that fades out teaches the team that senior commitments expire, which is the exact behavior the work was meant to change.
What to put in the offsite, and what to leave out
Put in the diagnostic data, unedited. Put in a structured conversation about the two lowest-scoring behaviors and the one with the widest spread between members. At least one live decision the team actually has to make belongs there too, run with the new method while somebody watches how it goes. And the conflict, if there is one, handled with preparation rather than sprung on people.
Leave out the trust fall and its descendants, and anything else where the insight is supplied by the facilitator at the end. Personality profiling should not be the centerpiece; it is useful as a language for why two people irritate each other, and useless as a substitute for the decision being avoided. The values exercise can go too. Every senior team in the world can produce four words on a wall by lunchtime, and none of those words has ever changed what happens in a Tuesday meeting.
The test for any session: could a member describe, on the following Monday, a specific thing they will do differently and the moment they will do it? If not, it was entertainment.
How to measure a leadership team
Score behavior, not sentiment. In the TrustFlow™ methodology the instrument is the 12 Cs of Trust, twelve observable behaviors in four quadrants, each rated 1 to 5 by every member of the team. The roll-up is the Team TrustFlow Index (TTFI), expressed from 1.00 to 5.00, and it reads in three bands: 1.00 to 2.49 is Constrained Trust, 2.50 to 3.74 is Developing Trust, and 3.75 to 5.00 is Sustained TrustFlow. The full method is in how to measure trust.
Two readings matter more than the headline number. The first is the spread between members on a single behavior: when four executives rate Communication a 4 and two rate it a 2, those two are describing a different company, and that is worth more attention than any average. The second is movement on the named behaviors. A quarter in which the overall index barely moves but Clarify goes from 2.4 to 3.5 and the spread narrows is a genuinely good quarter, and a program that reports only the average will miss it entirely.
The reason to bother with any of this is that the underlying relationship is well established. De Jong, Dirks and Gillespie's 2016 meta-analysis in the Journal of Applied Psychology, covering 112 studies and 7,763 teams, found intrateam trust to be a consistent predictor of team performance with an above-average effect size, holding after controls for trust in the leader and past team performance, and Dirks and Ferrin's earlier 2002 meta-analysis in the same journal found trust in leadership consistently related to performance and citizenship behaviors across the studies they pooled. Zak's 2017 Harvard Business Review work on high-trust companies reports 50% higher productivity and 76% more engagement than low-trust ones. None of these say your program will produce a number. They say the thing you are measuring is worth measuring.
What to do in January if the budget is not approved yet
Run the diagnostic anyway. It costs a week and one uncomfortable hour, and it converts a vague sense that the senior team is not working into a page of specifics you can take to whoever controls the budget. A named problem with a number attached gets approved. A request for leadership team development does not.
Then change the meeting, which is free. Three edits, in order of effect:
- Every decision leaves the room with a named owner and a date, written where everyone can see it. Read them back at the end. This alone kills most of the corridor renegotiation.
- Add a standing five-minute item where any member can name a decision they have doubts about. The CEO goes last in that item, always.
- Stop the round-robin reporting format. Written updates circulated beforehand, and the meeting time spent on the two or three things that need the whole team in the room.
Do those three for six weeks, re-score, and you will have either a much better meeting or hard evidence that the problem is deeper than the meeting. Both outcomes are worth having, and the second one is the business case. A quick directional read is available from the scorecard at trust score if you want a number before you commit anyone's time.
Frequently asked questions
What is leadership team development?
Leadership team development is structured work aimed at making a group of senior leaders operate as one decision-making unit: how they decide, how they disagree, how they hold each other to commitments, and how information moves between them. It targets the relationships and the operating habits between the members rather than the capability of any individual member, which is what separates it from leadership development.
How long does it take to develop a leadership team?
Plan for a quarter to see behavior change that survives a bad week, and longer for it to become the way the team operates without effort. Ninety days is enough to baseline the team, run an offsite, practice a small number of named behaviors, and re-measure. It is not enough to resolve a long-running conflict between two executives, which usually needs separate work alongside the program.
What is the difference between leadership development and leadership team development?
Leadership development builds the capability of a person: their judgment, communication, and self-awareness, usually measured through feedback and promotion. Leadership team development changes what happens between people: the quality of decisions, the speed of escalation, and whether commitments hold. A team of individually excellent leaders can still make slow, reversible decisions together, and no amount of individual coaching fixes that.
Should the CEO attend?
Yes, for the whole thing, and the program is usually not worth running otherwise. The CEO sets the standard for what gets said out loud in the room, and a senior team reads absence accurately: this matters to us, not to them. A CEO who attends selectively also removes the one person most able to change the meeting habits the program is trying to change.
How do you measure a leadership team's progress?
Score the team against defined behaviors rather than sentiment. In the TrustFlow approach, each of the 12 Cs is rated 1 to 5 by every member and rolled up into a Team TrustFlow Index between 1.00 and 5.00, with bands at 1.00 to 2.49 for Constrained Trust, 2.50 to 3.74 for Developing Trust, and 3.75 to 5.00 for Sustained TrustFlow. Track the named behaviors and the spread between members, not only the average.