2 min read
Those who understand technology don't manage it, and those who manage it don't understand it.
Takeaways
- There is often a gap between deep technical understanding and management roles. Rarely does one person excel at both.
- Technical experts often aren’t in management, and managers usually don’t understand the technical details.
- This can lead to unrealistic expectations, such as when management sets unrealistic expectations because they don’t understand the domain and its complexity. At the same time, engineers are feeling misunderstood.
- Successful organizations bridge this by training managers in tech basics or promoting technically savvy leaders.
Overview
Putt’s Law explains a known concept: that the best engineers aren’t in charge, and those in charge aren’t deeply knowledgeable about the technology. While not universally true, this highlights a real challenge: managing technologists requires some understanding of their work. But managers often come from different backgrounds or have been away from the code for a long time.
The law’s corollary states: “Every technical hierarchy, in time, develops a competence inversion,” meaning the people at the top know less about the work than those below. The gap creates dysfunction: managers set unrealistic deadlines because they don’t understand technical subjects, while engineers build wrong solutions because they don’t understand the business context.
The lesson is clear: technical leadership should maintain technical competence or risk mismanaging the technical work.
Putt’s Law
Examples
Think of a software manager who came from a sales or business background. They might push the team to add complex features at warp speed, failing to understand why quality or testing is needed. They “manage what they do not understand.”
On the other side, a brilliant sysadmin knows precisely how to optimize infrastructure but isn’t involved in management decisions about budgeting or project direction. They “understand what they do not manage.”
Perhaps the manager promises a client a feature by next week (not understanding the technical difficulty), and the engineering team is frustrated because the manager didn’t realize what’s involved. Many startups initially avoid this because founders often manage and deeply understand the tech, but as companies grow, specialization separates roles. One remedy is to have CTOs or tech leads act as a bridge, with one foot in management and one in technical detail.
Origins
Putt’s Law was revealed in the satirical book “Putt’s Law and the Successful Technocrat” (1981). The author used the pseudonym “Archibald Putt.”
The book offers a cynical but insightful look at the dynamics of technical organizations and how competence often gets inverted as people rise through hierarchies. It overlaps conceptually with the Peter Principle (people rise to their level of incompetence) and the Dilbert Principle (incompetent people end up in management).
Further Reading
Want to go deeper?
All 63+ laws are covered with more depth, examples, and practical guidance in the Laws of Software Engineering book.
Last updated: July 20, 2026

Comments
Nothing yet. Say the first thing.
Sign in to join the conversation.