hebel. today · 13 November 202647 / 80

Career · Leadership in Tech

Engineering leads transition from individual output to team multiplication

Gregor Ojstersek spent his first four months as an engineering leader attempting to remain the team's top coder, a habit that triggered near burnout before he shifted his focus to team outcomes. He now…

Gregor Ojstersek spent his first four months as an engineering leader attempting to remain the team's top coder, a habit that triggered near burnout before he shifted his focus to team outcomes (Joel Salinas from Leadership in Change). He now defines his role by the collective performance of his engineers, noting that the technical skills required to excel as an individual contributor differ from those needed to guide a team. This identity shift allows leaders to build credibility by shipping complex projects through their team, a process that establishes the trust necessary for an organization to assign increasingly significant work (Joel Salinas from Leadership in Change).

High-performing teams now leverage small, elite groups of two to six people where every member functions as a high-output contributor (Stay SaaSy). Leaders who prioritize these A+ teams remove roadblocks to allow these contributors to multiply their collective impact, a strategy that alters company trajectories more effectively than spreading expertise across larger, less focused groups (Stay SaaSy). By decoupling personal value from technical output, managers enable their teams to operate with the speed and precision of commandos, as the automation of on-call duties and codebase queries reduces the friction previously associated with reallocating resources.

  • Asana’s 2019 survey found that knowledge workers spend 60% of their time on coordination tasks and only 27% on their core professional responsibilities (Techcubator).
  • McKinsey found that 61% of 1,200 managers report that at least half the time spent making decisions is ineffective due to overreliance on consensus (Nick Martin from WorkshopBank).

Try today · 30 min

Identify one specific, complex project your team is currently executing and document the exact roadblock you will remove this week to increase their output speed.

Focus on a bottleneck that prevents your team from shipping, not on your own technical contribution.

One email instead of your newsletter pile.

Forward the newsletters you already get (a Gmail filter does it) and tell Hebel your goals. Every morning it reads them with 20,000 others and sends one short email, with one small thing to do today. Fewer emails, not more. Free during beta.

Start my paper →
LinkedIn X

Sources

  1. Techcubator on hebel. →This survey data highlights the high cost of coordination and consensus-based work in modern management roles.

  2. Nick Martin, WorkshopBank on hebel. → ✎ Written by a personThis piece outlines the 20-minute decision meeting format to prevent consensus traps from delaying project progress.

  3. Joel Salinas, Leadership in Change on hebel. → ✎ Written by a personThis interview explains the identity shift from individual contributor to team leader and the risks of holding onto technical tasks.

  4. Stay SaaSy on hebel. →This article describes the shift toward small A+ teams and the role of leaders in removing roadblocks for high-output contributors.

More in Career

Build your network through specific contribution

Protecting the creative core from daily drift

Teams split on whether AI oversight requires proof or process

Test your next professional identity through small-scale experiments

Promotion announcements reveal the blueprint for your next role

Leadership in Tech yesterday

Managers pivot from routing code to managing agent workflows

Sign in to Hebel first

Likes, your collection and done Hebel need an account. We email you a six digit code; no password.