Team Organization: what it is and how to measure it

"It is often unclear who is responsible for what." That statement is in the PEAKTEAMS Snapshot survey, and it is worded negatively on purpose. Most survey items are phrased so that agreement is good, and people who are tired or in a hurry drift towards agreeing with everything. A reversed item catches that drift. It also happens to be the single most diagnostic sentence for Team Organization: if a team agrees with it, very little else in this KPI will be in order.

Team Organization is the Input KPI about structure. Hackman (2002) called it an enabling structure: the roles, the composition and the norms that make it possible for a group of capable people to act as a team rather than as a collection of individuals. PEAKTEAMS breaks it into three questions.

Question one: does everyone know who does what?

Role clarity is the oldest finding in this area. Rizzo, House and Lirtzman defined role ambiguity in 1970 as the absence of clear information about what is expected and how performance will be judged, and the research since has been consistent. Tubre and Collins' meta-analysis (2000) found role ambiguity negatively related to job performance across the studies they pooled, with the relationship stronger in some kinds of work than others. The practical version: people cannot do well what nobody has told them they own.

In a team, ambiguity rarely looks like confusion. It looks like two people quietly doing the same thing, or nobody doing a thing everyone assumed someone else had, discovered the week before a deadline. The Deep-Dive item "Decision rights are clear" covers the version that bites hardest: everyone knows their tasks, but nobody knows who gets to say yes.

Question two: can the team do the job?

The second group of items asks about skills and composition. Does the team have the mix of skills its goals require, are the strengths complementary, is the size right, and does knowledge move between people rather than sitting with one. Mathieu, Maynard, Rapp and Gilson's review of a decade of team research (2008) treats composition as one of the primary inputs that shape team processes, and the sensible reading is that there is no process fix for a skill the team does not have. A team can be well organised and still too small, or well staffed and badly shaped: four people who can all do the same thing and nobody who can do the other thing.

Hackman's advice on size is still the simplest guidance available: smaller than you think, with stable membership. Coordination costs grow faster than headcount.

Question three: is the load fair?

Workload distribution and onboarding are the items people tend to underrate until they score badly on them. An unfair distribution usually means one or two people are the bottleneck for everything, which shows up later as missed delivery and, eventually, as the one person who leaves. Onboarding and cover for absences are the resilience side of the same question: can the team keep functioning when its composition changes, as it will.

High and low, side by side

How PEAKTEAMS measures it

The Snapshot survey takes each member about 12 minutes and asks three statements for Team Organization, including the reverse-keyed one. Agreement with it is flipped before scoring, so that agreeing lowers the KPI.

The Deep-Dive adds twelve more across the three questions above: role definition, skill mix, workload fairness, team size, onboarding, cover for absences, silos, decision rights, composition, complementary strengths, knowledge sharing and the use of diverse perspectives.

Team Organization is an Input KPI, so a low score here should be read before the Process KPIs, not after. The Consensus Matrix, which plots each survey item's average against how much members agree on it, is particularly useful for it: read this KPI's items together, because wide disagreement on role clarity usually means the people at the edges of the team (new members, the person who sits between two sub-teams) are the ones who do not know what they own. Results appear only once at least five team members have answered; the owner's own answer does not count.

How to improve it

• Write down who owns what, one line per area, and put it where the team looks daily. Rizzo and colleagues' definition of ambiguity is the absence of information; the cure is mostly information.
• Agree decision rights for the recurring decisions. Who can approve a scope change, who can say no to a request, who picks the tool. Five such rules remove most of the "who decides" friction.
• Build a simple skills map and look for single points of failure. Any skill only one person has is a risk to the cover-for-absences item and to that person's holidays.
• Make workload visible before rebalancing it. A shared view of who has what is enough to make unfairness obvious, and makes the rebalancing a team decision rather than a complaint.
• Give every new member a named buddy and a thirty-day plan. Onboarding is the one item in this KPI that is almost entirely within the team's control.

Related KPIs

Environment & Resources asks whether the team has enough people; Team Organization asks whether the people it has are in the right shape. Leadership Principles covers the decision-making side at the level above the team. On the Process side, a low score here often shows up as low Delivery Methodology, because a way of working cannot compensate for unclear roles.