|
|
|
|
|
by zbentley
2221 days ago
|
|
I'm not sure "high functioning" is the right term when discussing individuals rather than teams. I suggest using "leaders" or "mentors", since "high functioning" as in personal contribution productivity is, as you pointed out, often a toxic thing to optimize for. Consider this: a team with one insanely productive contributor and three new/less-than-productive folks is tasked with a bunch of projects. As expected, the productive person does most of the work. The others might learn a bit by example, or not. Productive person moves on/gets bored/gets significant non-work commitments/burns out/gets hit by a bus. The team is no longer productive or functional. Then consider this: a team with one person with a talent for teaching and leadership, and three new/less-than-productive folks is tasked with a bunch of projects. At first, they aren't that high-functioning as a team. The teacher/leader spends a lot of their time mentoring, going over the basics, reviewing, and planning. Over time, they get more productive. If the mentor/leader leaves the mentorship/leadership role, at worst they leave a high-performing team behind. At best they leave a high-performing team of people who are additionally prepared to assume a mentorship/leadership role in the future. Depending on how "10x" (ugh) the developer in the first scenario is, the team in the second example might never reach their productivity. But I think it's pretty obvious that organizations are benefited more by second-example-type teams. |
|
In practice it is more complex - people with a talent for teaching and leadership and are experts are incredibly rare.
What we often end up with is a mediocre dev taking on the teaching role and helping build a mediocre team.