Skip to content
Not Yet a Team All fifty notes

Who is still here

When a team is younger than it looks

A group of experienced people can be a four-month-old team. The figure that tells you which, and the three decisions it should change.

The people this page is about, and which of them have ever worked together

010203020304
  1. 01The team's managerTwo of this person's five working pairs
  2. 02The senior engineerOn the team from the first day
  3. 03The second engineer
  4. 04The product managerThe third person in this role in fourteen months
Have worked on something togetherHave only been in the same meetingHave never done either

four people · 6 possible pairs · 3 of them have worked on something together · 1 has only been in the same meeting · 2 have never done either

Four of the eight, and only the pairs that run between those four.

Home / Who is still here

Argument

For a distributed group, teams can check current details here to review where work travels, where it stalls, and whether responsibility is concentrated in one person.

For a separate perspective on teams and working practice, consult Workhuman.

All eight, with the two rows that could not be drawn

WhoMonths in the company, latest at the rightMonths

The team's manager

14 on the team61 in the company

The senior engineer

14 on the team38 in the company

The second engineer

11 on the team11 in the company

The QA engineer

9 on the team52 in the company

The engineer who joined in March

7 on the team7 in the company

The designer

5 on the team44 in the company

The data analyst

4 on the team19 in the company

The product manager

3 on the team3 in the company
Months in the companyOf those, months on this team

eight people · median 9 months on this team · the longest-standing has 14 months · five of them have been on it for less than half the time they have been in the company

Two further lines were given to this panel and are not drawn. One puts more months on the team than in the company, which cannot happen. The other gives no company time at all, so there is no track for the segment to be a part of; it was somebody who started the following Monday and had been added to the list early.

Add up the company tenure of these eight and you get two hundred and thirty-five months — nearly twenty years of accumulated knowledge of the organisation. Add up their time on this team and you get sixty-seven.

By the first figure this is a seasoned group. By the second it is a team that is fourteen months old whose median member arrived nine months ago. Both numbers are true, and only one of them predicts anything about how the team works.

The three things team age governs

How many pairs have had time to form. A working relationship takes something like a quarter of shared occasions to become one. A team whose median membership is nine months has had time for perhaps two or three rounds of that per person, which is consistent with the six pairs on its grid.

Whether the recurring things have recurred. Planning rounds, seasonal peaks, audits, renewals. A team younger than a year has met each of them once at most, and the first encounter with an annual event is always more expensive than the second.

Whether anybody can answer why. The most expensive gap in a young team is not skill; it is that every decision older than the team has to be reconstructed from artefacts rather than recalled.

The error this causes

A manager with a group of experienced people reasonably concludes that the team needs less support than a group of new hires, and that conclusion is correct about individual capability and wrong about everything structural.

Experienced individuals in a new team still have no pairs, still have no shared vocabulary, still do not know what each other means by "done", and still cannot answer each other's questions about this team's history, because there is none.

What they do have is the ability to get things done outside the team, which masks the problem for a while. Each person routes around the missing network using their own organisational connections, which works and leaves the team exactly as sparse as it was.

Reading the two sums together

Divide the team tenure by the company tenure and you get a rough figure for how much of this group's experience is experience of each other. Sixty-seven over two hundred and thirty-five is a bit under a third, and that is on the low side.

A figure close to one — people who joined the company and the team together — means a team built by hiring. More things are written down, because nothing could be assumed, and there are fewer routes out into the rest of the organisation.

A low figure means a team assembled from inside, which is faster to start and has the specific hollowness described above.

What to do differently with a young team

Three adjustments, none of them expensive.

  • Write down decisions for a year longer than feels necessary. On an old team the reasons live in people; on a young one there is nobody to hold them, and the cost of reconstructing one is a day.
  • Pair deliberately for the first year, then stop if it is no longer needed. The mechanisms in the last part of this site are most valuable in a team's first four quarters and become unnecessary in a team that has developed its own occasions.
  • And resist reading the first annual cycle as a performance. A team meeting its first planning round, its first peak and its first audit will handle all three worse than it will next year, and attributing that to the people is the commonest unfair judgement in this subject.

The team that is older than it looks

The opposite case exists and is rarer, and it has its own failure.

A team whose members have been together for four years, in a company most of them joined for this job, has deep shared memory and a grid that stopped changing a long time ago. Everybody knows who to ask. The pairs that exist are strong and the ones that do not exist have had four years not to form, which is its own kind of evidence.

What such a team loses is routes out. Nobody has organisational connections anywhere else, so every question that cannot be answered inside the team becomes a formal request. It is a team with a dense rim and no spokes pointing outward, and it is as fragile in its own way.

The lines that could not be drawn

Two of the rows given to the panel above are impossible. One puts twenty months on a team inside fourteen at the company. The other gives somebody no company time at all — they were on the list a week before they started.

Neither is interesting as an error. Both are interesting because a table would have accepted them silently, and a drawing cannot: a segment that runs past the end of its track, or a track with no length, is visible from across the room.