korrents
Ben Kuhn

What Ben Kuhn thinks about management

@ben-kuhn · 23 positions · On ppll ↗

Software engineer and writer; former CTO of Wave, now at Anthropic. Blogs at benkuhn.net on attention, engineering management and doing hard things well.

Ben Kuhn did not write this page.

We collected these quotes from things they published elsewhere, and every quote links to where it was said. They have no account here and have not endorsed this site. Quotes are word for word; the short line under each one is our own restatement, not their wording. Their own site. Is this you? Claim it or ask us to remove it. Or tell us what is wrong here.

13 dated positions, 2023 to 2025, in their own words. Our reading of what Ben Kuhn has said — not written or endorsed by them.

  1. People who can be trusted to make something inevitable are really rare, and are typically the bottleneck for how many different things a team or company can do at once.

    ↗Impact, agency, and tastebenkuhn.net 2nd of 3 in this piece

  2. 3 weeks earlier
  3. you should expect to have something like 10-20% less individual output per engineer you manage, depending on how experienced you are, they are, etc., and with substantial week-to-week variance.

    ↗Advice for time management as a managerbenkuhn.net 1st of 2 in this piece

  4. The stereotype is that new managers often micromanage, but at Wave, I've noticed that new managers often err on the side of undermanaging, or being too hands-off, perhaps out of a desire to signal that they trust their reports.

    ↗Advice for time management as a managerbenkuhn.net 2nd of 2 in this piece

  5. 2 weeks earlier
  6. One of the most common megaproject failure modes is to not freak out soon enough, and having a concrete plan is the best antidote.

    ↗How I've run major projectsbenkuhn.net 1st of 3 in this piece

  7. The best project-managers are often not the strongest technical ICs.

    ↗How I've run major projectsbenkuhn.net 2nd of 3 in this piece

  8. 8 months earlier
  9. Team leadership covers a huge array of things-as you can see from how long this post is-and trying to find someone who can be great at all of them is often a unicorn hunt.

    ↗Categories of leadership on technical teamsbenkuhn.net 1st of 3 in this piece

  10. The bar I typically suggest is that the people manager doesn't need to have the most technical depth on the team, but they need enough depth that they can follow most discussions without slowing them down, understand who's correct in most debates without needing to rely on trust, and generally stay oriented easily.

    ↗Categories of leadership on technical teamsbenkuhn.net 2nd of 3 in this piece

  11. Good project management is barely visible-it just feels like "things humming along."

    ↗Categories of leadership on technical teamsbenkuhn.net 3rd of 3 in this piece

  12. 8 days earlier
  13. mental models

    Trust comes from common knowledge of shared mental models, and that takes investment from both sides to build.

    ↗Trust as a bottleneck to growing teams quicklybenkuhn.net 1st of 2 in this piece

  14. In a large, fast-growing company you'll probably never get to the utopian ideal of full pairwise trust between everyone-it takes too long to build.

    ↗Trust as a bottleneck to growing teams quicklybenkuhn.net 2nd of 2 in this piece

  15. 5 months earlier
  16. Sometimes this is true, but usually problems aren't a single person's fault!

    ↗How I build and run behavioral interviewsbenkuhn.net 3rd of 3 in this piece

  17. 10 months earlier
  18. Manage projects according to the owner's level of task-relevant maturity.

    ↗Some mistakes I made as a new managerbenkuhn.net 1st of 3 in this piece

  19. People with low task-relevant maturity appreciate some amount of micromanagement (if they're self-aware and you're nice about it).

    ↗Some mistakes I made as a new managerbenkuhn.net 2nd of 3 in this piece