4 management lessons for scaling your team
What broke when his company grew from 10 to 90 people, and the four management shifts that fixed it.
Writing
Heroics don't scale. Delegate outcomes, keep the decision, and build ways to see what is really happening once you can't hold the context yourself.
What broke when his company grew from 10 to 90 people, and the four management shifts that fixed it.
AI erodes the entry-level work that builds engineering judgment. Four practices to keep juniors thinking instead of parroting output.
Why burnout is a management problem, with the story of keeping a 90-person team working after the invasion of Ukraine.
Three signals to invest in developer training, how to tie it to business goals, and how to measure ROI, with a $10,000-a-month cloud saving as the example.
Why AI tooling tires engineering teams through micro-decisions and tool sprawl, and how to adopt it without burnout.
How to spot a skills gap early (quality drops, lead overload) and close it with 360 reviews, development plans and mentoring.
Five leadership skills AI cannot replace, illustrated with situations from running a 90-person engineering team.
Five practices for Ukraine, US and Europe teams: a written communication policy, agreed progress reporting, audience-adapted presentations, a knowledge base.
A concrete cadence for developer growth: tests, sprint experiment days, monthly clubs, and how to diagnose a stalled engineer.
Why technical leaders over-control, a five-step delegation system, and the team that shrank a 16 TB database to 1 TB on its own.
Four traits that mark product-minded engineers, and the retention practices behind five-to-eight-year average tenure.
I'm always interested in thoughtful conversations about technology, engineering organizations, AI and ambitious products.
Get in touch opens LinkedIn in a new tab. Email reaches [email protected].