Dilbert Principle | Laws of Software EngineeringThis site works best with JavaScript enabled. Search and filtering require JavaScript.<br>Skip to main content<br>← Back to LawsDilbert Principle<br>✓?<br>Teams<br>Senior
Copied!
✓?
2 min read<br>Companies tend to promote incompetent employees to management to limit the damage they can do.<br>Takeaways
Organizations sometimes deal with underperformers by promoting them into management, removing them from hands-on work.<br>It reflects a cynical view that lower-level employees do real work while some managers add little value.<br>Technical excellence and people leadership require different skills. Failing at one does not qualify someone for the other.
Overview
The Dilbert Principle suggests that instead of addressing poor performance directly, companies often promote struggling employees into management roles where their impact is perceived as less immediately harmful. The satire resonates because it reflects a fundamental flaw: many organizations treat management as the default career path for engineers without considering what those employees actually want or are suited for.<br>When promotion replaces accountability, management layers fill with people lacking either technical credibility or leadership ability. The result is bad decisions, wrong priorities, and loss of trust between engineers and leadership.
Dilbert Principle
Examples
Many engineers share anecdotes that feel straight out of Dilbert. A mediocre programmer or failing project lead gets “promoted” to a management or architect role. Sometimes these moves are less about recognizing leadership talent and more about getting a problematic person away from critical work. The result is counterproductive: you now have an incompetent manager and one fewer developer.<br>On a positive note, awareness of the Dilbert Principle has made some organizations more careful. Modern tech companies increasingly offer dual career tracks (technical vs. managerial) to avoid forcing great engineers into management.<br>When an underperforming employee can’t succeed in engineering, good companies try coaching or reassignment, and if all else fails, let them go rather than make them the boss.
Origins
Scott Adams introduced the Dilbert Principle in his 1996 book “The Dilbert Principle.” As with much of Dilbert, the framing is exaggerated, but the underlying organizational critique proved uncomfortably familiar to many engineers.
Dilbert vs. Peter
The Dilbert Principle is often compared to the Peter Principle, but they describe different mechanisms. The Peter Principle says competent people get promoted until they reach a role where they’re incompetent. The Dilbert Principle says incompetent people get promoted precisely because they’re incompetent.<br>Both lead to the same outcome (incompetent managers) but through opposite paths. Together, they explain why management quality is such a persistent challenge in organizations.
Further Reading
The Dilbert Principle - Wikipedia<br>Overview of Scott Adams' satirical management theory
The Dilbert Principle - Amazon<br>The original 1996 book by Scott Adams
A Cubicle's-Eye View of Bosses, Meetings, Management Fads and Other Workplace Afflictions<br>Scott Adams (1996) - the satirical take on corporate dysfunction that popularized the principle
How to cite this page<br>When referencing this law in articles, papers, blog posts, or AI responses, use one of the following citations:<br>APA: Dr. Milan Milanović. (2026). Dilbert Principle. Laws of Software Engineering. https://lawsofsoftwareengineering.com/laws/dilbert-principle/<br>Plain text: "Dilbert Principle" — Dr. Milan Milanović, Laws of Software Engineering, https://lawsofsoftwareengineering.com/laws/dilbert-principle/<br>BibTeX: @misc{milanovic_dilbert-principle_2026, author = {Dr. Milan Milanović}, title = {Dilbert Principle}, year = {2026}, url = {https://lawsofsoftwareengineering.com/laws/dilbert-principle/}, note = {Laws of Software Engineering} }
Want to go deeper? All 63+ laws are covered with more depth, examples, and practical guidance in the Laws of Software Engineering book.
Get the Book
Last updated: June 24, 2026
Related Laws
Teams<br>Peter Principle<br>In a hierarchy, every employee tends to rise to their level of incompetence.<br>?⚙⚙<br>Teams<br>Putt's Law<br>Those who understand technology don't manage it, and those who manage it don't understand it.
Teams<br>Brooks's Law<br>Adding manpower to a late software project makes it later.