Reading · Laws of Software Engineering

2 min read

Companies tend to promote incompetent employees to management to limit the damage they can do.

Takeaways

Organizations sometimes deal with underperformers by promoting them into management, removing them from hands-on work.
It reflects a cynical view that lower-level employees do real work while some managers add little value.
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.

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.

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.

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.