Team Accounting: The practice of mapping your team's current shape, depth, and appetite before designing any capability or innovation programme. A diagnostic of what you are actually working with before you decide what to build into it.

I-Shaper: A team member with deep expertise in a single field. High depth, limited breadth. Excellent inside a defined lane, and less equipped for work that requires cross-functional thinking or situational adaptability.

T-Shaper: One deep vertical combined with genuine curiosity across adjacent disciplines. The current default goal in most team development conversations and the standard most capability programmes are designed to produce.

M-Shaper: Multiple deep verticals operating at genuine expert level. Not surface familiarity spread across several areas. Real depth in more than one distinct discipline, built from time and application.

X-Shaper: An M-Shaper who applies multi-domain depth across the full spectrum of human and technical contexts. Connects disciplines that shouldn't connect. The shape that changes the quality of the questions a team asks before it gets to answers.

Polymath: Multi-domain mastery at the level that produces original thinking across fields. Not a career goal you set for someone. A shape someone grows into across a lifetime of deliberate, compounding learning.

I get a version of the same question on LinkedIn at least twice a week. Someone in people transformation or a from someone in a People product experience team wants to know which capability programme to run, which frameworks to train the team on, which methodology to bring in. The question is always about the method. It is almost never about the team.

That is where the money goes. The time, the motivation, and the credibility of the people trying to move things forward all follow the same path, straight into a programme designed for a team the organisation assumed it had rather than the one it actually built.

The method is the last thing to choose. Before the method, you need the accounting.

Team Accounting is a diagnostic step before any capability investment. It is the practice of sitting with your team's actual composition and asking a straightforward question: who is here, what shape are they, and what does this team actually want to become?

The term takes its logic from Innovation Accounting, the discipline of measuring what your innovation work is producing before you decide to scale it. The same principle applies to teams. You do not scale capability into a team without first understanding whether that team has the foundation and the appetite to compound it.

You are looking at three things: shape (the depth and breadth profile of each team member), dynamics (how the shapes complement or cancel each other in practice), and appetite (whether the team genuinely wants to grow, or whether the organisation has already trained them out of trying).

When you skip this step, you get well-designed programmes running into teams who were not ready for them, or teams who were ready but were handed the wrong thing.

These are the five shape profiles you are looking for, most teams are a mix. Most leaders have not mapped it.

Deep in one field, committed to that depth. Excellent at what they do inside a defined lane, and less equipped for work that requires cross-functional thinking or the ability to shift context under pressure. Every team needs I-Shapers. But if your innovation or EX function is built entirely of people with this profile, the team will keep producing excellent single-discipline work in a world that increasingly requires thinking across disciplines.

One deep vertical with genuine curiosity across adjacent areas. This is the shape most team development conversations are aiming for. Most LinkedIn posts about capability building from 2023 onwards are quietly making the case for T-shaped thinking without calling it that.

M People released "Moving on Up" on September 13, 1993. It reached number 2 in the UK. The song was about ambition, one clear track upward and enough energy to keep going. T-shaped thinking has been around that long, longer than it has been a LinkedIn staple. One strong foundation, enough curiosity to engage what is around it. The idea is not new. The execution of it still is, for most teams.

T-shaped is the right baseline goal. The issue arises when it becomes the ceiling. Once your whole team is T-shaped, you have created a stronger floor. You have not built a capability edge.

Multiple deep verticals. Not surface familiarity spread across several areas, but genuine depth in more than one distinct discipline, built from time, application, and the refusal to stop learning once one field became comfortable.

This is the shape that changes a team's thinking architecture. M-Shapers do not just bring more knowledge. They bring different mental models running in parallel, and that changes how they see problems. When an M-Shaper is in the room, the quality of the diagnostic question tends to improve before anyone has got to the solution.

They are also the shape most likely to be misread in hiring. They look generalist on paper. They interview as someone who has done a lot of different things. What they actually are is someone who has gone to genuine depth in several places, and that distinction is worth knowing how to spot. Ask them to teach you something from a field outside their primary one. The quality of that answer will tell you whether the depth is real.

An M-Shaper applying multi-domain depth across the full spectrum of human and technical contexts. This is the shape that connects things that should not connect. An X-Shaper works at the intersection of disciplines rather than within any single one of them, and the value they generate comes from that intersection.

If you have an X-Shaper in your EX or innovation team, you have a structural advantage that most organisations have not named and therefore do not protect. They will reframe the problem before most of the room has finished describing it.

Multi-domain mastery at the level that produces genuinely original thinking across fields. Think Leonardo Da Vinci, Nikola Tesla, Benjamin Franklin, Marie Curie, Mary Somerville

This is not a career goal you design a programme towards. It is a shape someone grows into across a lifetime of deliberate, compounding learning. Polymaths are rare inside organisations, and when they exist they are often underused, because the system does not know what to do with someone who does not fit the job architecture.

If you have one, protect them from bureaucracy. That is the only capability intervention they need.

Once you have mapped the shapes, you have three things to work with.

The first is a clear picture of what your team can actually produce right now. Not what the job titles say. What the shapes allow. A team made up entirely of I-Shapers with one T-Shaper will not generate systems thinking regardless of what the programme teaches them. The shape sets the ceiling before the learning starts.

The second is a gap map. Where does the team need to move, and who is closest to the next shape? Moving an I-Shaper toward polymath is not a programme design. It is wishful thinking. Moving a T-Shaper toward genuine M-shaped depth is both achievable and worth designing for deliberately.

The third is an appetite read. This matters more than the shape map. A team with the right shapes and no appetite to grow is harder to work with than a team with average shapes and genuine hunger. Appetite is shaped by the organisation more than by the individuals in it. If the culture has systematically punished people for going beyond their lane, you are not starting with a capability problem. You are starting with a culture problem that needs to be named before any programme begins.

Most capability programmes start with the method because the method is the visible part. The workshops are visible. The frameworks are visible. The team shape is invisible until someone looks for it.

The accounting comes first. Before the external faculty. Before the methodology selection. Before the dates are set in anyone's calendar. You map what you have, name what you need, and read the appetite in the room honestly.

What you will find is that the programme you were about to run is the wrong one for this team. Or that it is the right programme but needs to start somewhere different. Or that the team you have is more capable than the business believes, because nobody had mapped the shapes clearly enough to make the case for it.

You do not fix a cold oven by changing the recipe.

What is Team Accounting in the context of an EX or innovation team?

Team Accounting is the practice of mapping your team's current shape, depth, and growth appetite before designing any capability programme. It draws on the logic of Innovation Accounting and applies it to team composition. The goal is to understand what you are actually working with before deciding what to build into it.

What is the difference between an I-Shaper, T-Shaper, M-Shaper, X-Shaper, and Polymath?

I-Shapers have single-field depth. T-Shapers add genuine curiosity across adjacent disciplines to one strong vertical. M-Shapers carry real depth in multiple verticals, not surface familiarity. X-Shapers apply M-shaped depth across human and technical contexts simultaneously. Polymaths operate at multi-domain mastery across a lifetime of compounding expertise.

Why do capability programmes fail even when the design is strong?

The most common failure is skipping the diagnostic step. Strong programmes are designed for an assumed team and run into a real one. The shapes do not match the methodology. Or the appetite is low because the culture has already taught people not to try. Team Accounting is the step that prevents this mismatch from costing time and credibility.

How do I identify an M-Shaper in hiring or inside my current team?

M-Shapers look generalist on paper. They have done a lot of different things. The distinction is depth: they have gone to genuine expert level in more than one area, not just accumulated varied experience. Ask them to teach you something from a field outside their primary one. The quality of that answer will tell you whether the depth is real or just CV width.

What is team appetite and why does it matter more than team shape?

Appetite is the team's actual will to grow, experiment, and apply new thinking under real conditions. It is shaped by culture more than by individual personality. A team with the right shape profile but low appetite will not compound capability regardless of what programme you run. If appetite is low, the diagnosis is cultural before it is methodological.

When should you run Team Accounting and how long does it take?

Run it before any capability investment, innovation programme, or team restructure. It is a diagnostic step, not a standalone project. A properly facilitated Team Accounting session for a team of eight to twelve people can be completed in a half day, with a clear output mapping current shapes, gaps, and appetite levels.