This essay expands on the “Team and Growth” thread in Management Retrospective.
Team growth is often mistaken for two things: having more people, or bringing in a few very experienced ones. These can certainly raise the team’s ceiling, but they do not automatically form a team that can keep solving problems.
I prefer to understand team growth as a systemic capability: whether members can reliably do things well, whether experience can be passed on, and whether collaboration keeps running as people and circumstances change. It takes time, and it takes sustained investment in efficiency, succession, and continuity.
Time: Capability Cannot Be Built in a Single Expansion
A team usually grows more slowly than an individual. One person can gain strong feedback from a single difficult task; a team needs people of different backgrounds and experience levels to gradually build a shared language, trust, and a way of working.
Temporarily adding a few experienced members may quickly relieve pressure and bring fresh perspectives. But integration takes time: newcomers must understand the goals and constraints, existing members must adjust how they collaborate, and everyone must confirm how things should be done. The other path is developing the people you already have; it is slower, but it lets experience take root. The two are not substitutes for each other — the key is whether people and shared principles can gradually form a combined force.
So, to judge whether a team has grown, you cannot just look at whether it completed more projects in some period. What matters more: Has its efficiency and quality of problem-solving become stable? Are members beginning to take on more complete problems? When familiar people temporarily leave, do things immediately fall apart? The answers usually only become clear over six months, a year, or even longer.
Efficiency: It Is Not About Packing Everyone Tighter
The high efficiency a team pursues is not everyone being busier, but doing the important things more reliably with less needless waste.
First, you need reasonably clear boundaries of responsibility. Different people can do different things, but each area should have a clear primary owner and a backup who can take over. This reduces the gap where “everyone assumes someone else will handle it,” and lets experience accumulate continuously in one direction. Clear responsibility is not about locking people inside boundaries; it is about knowing who initiates, who decides, and who follows up when collaboration is needed.
Second is a standard for collaboration: how to start a piece of work, how to confirm goals and risks, how to check quality, and how to notify, fix, and review when problems arise. Standards are not about forcing everyone to use the same approach; they are about making sure key information is not missed. When a team keeps running into the same kind of problem, the cost is not just the time spent fixing it, but also interruptions, rework, and eroded trust. Reducing these costs is part of improving efficiency.
Scheduling is also part of a team’s efficiency. Cutting meetings that reach no conclusion, leaving continuous blocks of time for important problems, and consolidating scattered feedback all come closer to effective collaboration than filling the calendar to the brim. A good process does not add steps; it lets people focus their attention where judgment is actually needed.
Succession: Making Experience Visible and Transferable
Even with basic processes in place, a team’s efficiency will still hit bottlenecks. A reasonable gradient of experience means complex problems do not always have to be shouldered by a few people alone, and it lets newcomers get concrete feedback faster.
For example, two people who are both new to a field groping their way forward together is usually different from a more experienced person moving forward with a newcomer. The latter may not finish every small step faster, but can point out key constraints earlier, explain trade-offs, and help the newcomer waste less time falling into the same pit repeatedly. The value here is not creating dependence, but making experience visible and discussable, so that more people can eventually become independent.
Developing people takes real energy. If one person is at once carrying heavy direct collaboration, project advancement, and mentoring, all three often suffer. A team needs people at different experience stages to take on matching responsibilities: some focus on concrete execution, some help break work down and check it, and some maintain the longer-term direction and the collaborative environment. That way newcomers get more concrete support, and more experienced people are not dragged down by every detail.
Succession is not about ranking people high or low; it is about confirming that, when someone steps forward, the team has people who can offer the right feedback, practice opportunities, and room for responsibility — and that when they are ready to take on more, there are real problems for them to try to solve.
Continuity: Still Doing Things Well Amid Change
Ultimately, team growth comes down to whether it can endure. When members change, the scope of work expands, or external conditions shift, can the team still hold a basic consensus on “what it means to do something well” and keep delivering reliable results?
Continuity does not mean preserving past practices exactly as they were. It is more like keeping a set of principles that can adapt to change: being clear about the goals you serve, being willing to surface problems, being able to improve from failure, and giving new members the chance to understand and contribute their own judgment. As a team scales, challenges multiply; a shared language, trustworthy commitments, and transferable experience are what keep chaos at bay.
From this angle, being “reliable” is not a judgment about character but a systemic outcome: members are willing to take responsibility, collaboration has clear boundaries, problems get surfaced promptly, and experience can be used again next time. Such a team is far more likely to reorganize itself amid change and keep growing.
Conclusion
Team growth is not a single expansion, nor the launch of a set of processes. It is long-term construction: letting time settle shared judgment, letting efficiency reduce needless waste, letting succession pass on experience, and letting principles endure through change.
Only when a team keeps turning experience into more reliable action the next time does its capability stop belonging to just a few people — and to just one smooth stretch of time.