“Bullshit manager” is an ordinary-language category with unusually strong observational content. Workers often recognize a bad boss immediately. They tell stories about the tyrant, the coward, the micromanager, the absentee, the manipulator, the bureaucratic automaton, and the apparently friendly manager whose promises never become commitments. The patterns recur across organizations, industries, and levels of hierarchy.
Matt Groening’s Life in Hell comic “The 9 Types of Bosses” is a compact folk taxonomy of these encounters. Its Angry Behemoth, Robot from Planet X, Mr. Softy, Slippery Eel, Great Unknown, Spitting Cobra, Horny Toad, Wonder Boss, and Psychotic Boss-Monster from Hell are recognizable because they compress recurrent workplace observations into memorable figures.
But the comic does not describe nine institutional roles, much less nine institutions. Formally, there is one general role: management. The nine bosses are recurring ways in which people encounter occupants of that role.
This distinction is the beginning of a science of management failure.
Management is a role within the institution of organized work. Management failure modes are recurrent ways in which enactment of that role fails to perform its coordinating function, exceeds its authorized scope, or corrupts the ownership and allocation of institutional constraint.
“Bullshit management” remains useful as a folk category. It names something workers often detect before they possess a structural explanation for it. But it is not the formal category used in this document. The formal subject is management failure: a collection of distinguishable failures, excesses, abuses, and corruptions in the enactment of a general role.
The purpose of this document is not to create a personality test, identify bad people, or turn workplace resentment into a formal accusation. It is to separate observable behaviour from the institutional machinery that may generate it. The method is the general FLEY and Pancakes research discipline:
Observe carefully. Detect reliable signals. Resist overclaiming. Then, separately, build a model of the hidden system that could explain those signals.
An institution is not identical to any particular person who acts within it. In the IER and Pancakes model, an institution can be described as a state machine: it maintains an organized state, receives inputs, authorizes operations, narrows possible futures, and produces transformed outputs.
A corporation, government department, school, hospital, cooperative, or volunteer organization may all contain management roles. The surrounding institutions differ, but the role has a general function:
The function of management is to organize and coordinate the efforts of the work performed under it so that institutional inputs can be transformed into intended outputs.
Management is vertically recursive. An upper manager may organize divisions, a middle manager may organize teams, and a lower manager may organize individual work. The scale and delegated authority change, but the role-operation remains recognizable.
This recursive structure also means that a manager is often both an authority and a subordinate. A middle manager receives objectives and constraints from above while allocating work, resources, time, risk, and attention below. The same person can therefore bear constraint in one relation and allocate it in another.
The role is not the person. The person is not the institution. The institution supplies a position, powers, expectations, interfaces, and constraints; the person instantiates that position in a particular situation.
Management is frequently described as leadership, supervision, administration, or decision-making. These descriptions capture visible activities but can obscure the underlying operation.
A management role commonly receives:
It acts on these inputs by:
The role participates in value transformation by arranging effort into coordinated action. It does not normally create all of the value itself, nor does it stand outside the work as a neutral observer. Coordination is one operation within the larger production of an institutional outcome.
This matters because a manager’s legitimate authority derives from the requirements of that operation. The role does not provide a general licence to control the people beneath it. It provides bounded powers for organizing work.
Organizing work necessarily narrows futures. A manager continually participates in resolutions such as:
Scarcity, urgency, dependency, risk, and irreversibility cannot simply be managed out of existence. Constraint must land somewhere. Management is therefore not only a coordination role; it is a local constraint-allocation mechanism within the institutional state machine.
In IER terms, the role necessarily exercises bias. Bias here does not mean personal prejudice. It is the geometry of differential switching costs among admissible futures. Prioritizing one project makes another harder to pursue. Protecting one deadline may require another team to absorb delay. Refusing to intervene preserves a default trajectory rather than producing neutrality.
There is no management without allocation, and there is no allocation without consequences. A serious analysis therefore cannot classify every unpleasant consequence as managerial misconduct. Some decisions are legitimately difficult. Some harms are unavoidable. Some situations are tragic: every available allocation imposes cost.
The diagnostic question is not merely, “Did this feel bad?” It is also:
Ordinary discussion tends to collapse all bad encounters with managers into one category. The language of failure modes makes it possible to ask how the role-operation has departed from legitimate performance without assuming that every departure has the same cause.
A failure mode is not a personality type. It is a recurrent way that an operation can produce an invalid, defective, excessive, or corrupt result. The same person may exhibit different failure modes in different situations. The same observable behaviour may also be generated by different mechanisms.
In this document, “failure” is deliberately broader than incompetence. Management can fail through deficiency, as when necessary coordination is absent. It can fail through excess, as when role authority is extended into workers’ personal lives. It can fail through corrupted allocation, even when the manager efficiently produces the institution’s requested output. The reference point is not managerial success as judged by superiors; it is legitimate performance of the management role with appropriate ownership of resolution.
A precise diagnosis must also retain a non-failure comparison case. At least four objects therefore need to be distinguished.
Some managerial acts belong to the coordinating and allocative function even when they are unwelcome. A manager may have to set priorities, reject a request, evaluate work, communicate bad news, impose a real deadline, discontinue a project, or allocate an unavoidable loss.
Legitimate role conduct is not guaranteed to be painless or perfectly fair. Its defining feature is not pleasantness. It is a relevant connection to the role’s function, operation within authorized scope, and ownership of the resolution being exercised.
Role failure occurs when the occupant does not adequately perform the management operation. Priorities remain incoherent. Decisions are indefinitely deferred. Dependencies are ignored. Information does not travel. Workers receive incompatible instructions. Conflicts and impediments accumulate. Workers must perform informal coordination labour because the authorized coordinator is absent, evasive, or incapable.
Role failure can impose enormous costs without necessarily being overreach or corruption. A single bad call, ordinary incompetence, or overwhelmed management may produce harm without establishing a persistent structure of insulation.
Overreach occurs when powers made available for coordinating work are exercised beyond that function. Examples may include:
Overreach is a question of scope: does this act belong to the management operation at all?
The fact that an institution enables an occupant to impose a behaviour does not make that behaviour part of the role. Effective power and authorized function are different things.
Role abuse occurs when an occupant uses powers, access, information, or dependencies supplied by the management role to pursue an extraneous purpose or secure a personal advantage. The role is not merely performed badly; its institutional capabilities are repurposed.
Possible forms include retaliation, coercive favour-seeking, appropriation of credit, deliberate humiliation, exploitation of confidential information, or conditioning work opportunities on personal compliance. Role abuse often involves overreach, but the concepts are not identical. Overreach identifies that authority has crossed its functional boundary. Abuse identifies the use of role-derived power against the purpose or terms under which it was entrusted.
IER defines corruption structurally:
Corruption is the persistent routing of intrinsic constraint away from those with allocation authority and toward those with lower absorption capacity, combined with obscured or displaced authorship.
Corrupt management is therefore not synonymous with cruelty, greed, illegality, or poor character. It can be calm, professional, procedurally correct, and undertaken in good faith. Its signature is persistent constraint flow combined with positional insulation and failed ownership.
Common examples include:
This is not simply bad allocation. Corruption requires recurrence. It appears when the same role remains protected while less powerful roles repeatedly absorb the deformation, and when the authorship of that arrangement is hidden, denied, or displaced.
The distinctions among role failure, overreach, role abuse, and corruption are especially important.
Overreach concerns the boundary of authority. Corruption concerns the topology of constraint and ownership.
A manager may commit a one-time overreach without creating a persistent corruption pattern. A manager may also participate in corruption without obvious overreach: every action may appear to fall within formal authority, yet the arrangement continually protects decision-makers and transfers irreversible costs downstream.
Role abuse concerns the repurposing of management powers. It may be episodic or persistent, and it need not insulate an entire class of allocation-authority roles. If abusive conduct persistently transfers cost downward, protects the role-holder, and obscures authorship, it may also participate in corruption.
Likewise, role failure and corruption are not identical. An indecisive manager may fail everyone, including themself. A corrupt arrangement is more specifically one in which allocation authority remains insulated while the costs of resolution reliably accumulate elsewhere.
These categories can overlap, but they should be tested separately.
The nine bosses in Life in Hell belong to institutional phenology: the study and description of recurring observable forms through which an institutional role appears in lived experience. In ordinary language these forms are recognized as varieties of “bad” or “bullshit” management; in the present framework they are possible signals of management failure modes.
The Angry Behemoth, Robot, Mr. Softy, and Slippery Eel are not explanations of the corporation. They are detections. Each condenses a cluster of signals—tone, delay, volatility, absence, evasiveness, intimidation, intrusion, or suspicious generosity—into an encounterable type.
| Comic type | Observable presentation | Structural question it may prompt |
|---|---|---|
| Angry Behemoth | Intimidation and volatility | Is fear being used to transfer coordination costs or suppress information? |
| Robot from Planet X | Mechanical enforcement | Is procedure obscuring discretion or laundering authorship? |
| Mr. Softy | Indefinite hesitation | Who bears the cost of unresolved decisions? |
| Slippery Eel | Promises without commitments | Are consequences displaced while authorship disappears? |
| Great Unknown | Managerial absence | Who performs the missing coordination work? |
| Spitting Cobra | Persistent hostility | Does emotional harm function as control, deterrence, or insulation? |
| Horny Toad | Sexualized boundary violation | Is positional access being used outside the role’s function? |
| Wonder Boss | Apparently generous management | Is this genuine ownership, a temporary exception, or an unreliable presentation? |
| Boss-Monster | Arbitrary aggression | Has delegated authority become personal domination? |
These are hypotheses generators, not verdicts. The same presentation can arise from different structures. Mechanical behaviour might reflect an individual preference, severe regulatory constraint, inadequate authority, deliberate authorship laundering, or an interface that permits no discretion. Managerial absence might be neglect, overload, institutional fragmentation, or a reasonable delegation that workers have misunderstood.
Phenology must therefore remain disciplined:
Detect the form first. Infer the hidden mechanism separately.
The repetition of management across organizational levels creates a characteristic corruption risk.
An upper manager allocates objectives and constraints to middle management. Middle management interprets and reallocates them to lower management. Lower management schedules, monitors, and enforces work among workers. At every level, the manager can either own some part of the resolution or attempt to purchase local safety by transferring its cost downward.
The statement “I don’t make the rules” may be partly true. A lower manager usually does not control the whole institution. But lack of total control does not imply lack of allocation authority. The manager may still control timing, communication, exceptions, advocacy, escalation, workload distribution, interpretation, or the degree of uncertainty imposed on workers.
The relevant questions are:
If each management layer remains stable by transferring urgency, uncertainty, exhaustion, and failure risk to the layer beneath it, the organization has more than a collection of unpleasant personalities. It has a role-locked corruption topology.
Pancakes should not begin by assigning a boss type or corruption label. It should begin with observations that can be kept distinct from interpretations.
What was said or done? What decision was made or deferred? What changed afterward? Avoid beginning with a character judgment.
Was the manager allocating work, evaluating performance, transmitting information, resolving a dependency, enforcing a constraint, or acting outside the coordinating function?
What scarcity, deadline, obligation, risk, or conflict required resolution? Was the stated constraint real, exaggerated, misunderstood, or invented?
Which parts of the outcome were fixed elsewhere? Which alternatives were available to this role-holder? Effective authority should not be inferred solely from a job title.
Who could absorb the cost reversibly? Who was likely to experience cumulative exhaustion, precarity, exclusion, or permanent narrowing of futures?
Who worked late, lost income, absorbed uncertainty, accepted blame, surrendered autonomy, performed invisible coordination, or carried the operational risk?
Who made or transmitted the resolution? Who acknowledged it? Who accepted consequences for it? Was authorship hidden behind policy, necessity, metrics, customers, algorithms, or unnamed leadership?
Was this a single mistake, a temporary emergency, a repeated personal practice, or a stable feature of the role and institution?
Only after the earlier steps should an observation be provisionally described as legitimate role conduct, role failure, overreach, corruption, tragedy, or some combination.
This framework resists several common errors.
It does not assume that workplace harm can be explained by locating a defective personality. A recognizable boss phenotype may be produced by the interaction of a person, a role, inherited constraints, incentives, interfaces, and organizational history.
It does not assume that any behaviour performed by a manager is therefore managerial. Institutions often enable acts that exceed the function for which authority was delegated.
It does not classify every difficult decision as misconduct. Legitimate allocation can still impose cost, and tragedy remains possible.
It does not treat policy compliance, consistency, or neutrality as proof that constraint was allocated legitimately. Mechanical procedure can reproduce a topology that always protects the same roles.
It does not blame a local manager for every constraint transmitted through them. The inquiry maps the whole chain of authority, discretion, absorption, and ownership.
It also does not allow “the system” to erase the decisions of role-holders. Institutions act through situated operations. Partial constraint does not eliminate partial authorship.
Pancakes is interested in ordinary life, invisible labour, care, reflection, governance, and humane interpretation. Work is one of the major structures through which people’s time and admissible futures are organized. A personal record of work encounters can therefore reveal patterns that isolated incidents conceal.
But this is a sensitive domain. A Pancakes implementation should not automatically diagnose a manager, infer a personality type, or turn a worker’s journal into an accusation engine. It should help the user preserve observations, identify recurring operations, and examine competing explanations.
A humane design might help a person distinguish:
The objective is not organizational surveillance. It is perceptual support: making the operations that shape a person’s working life more legible without pretending that limited observations reveal the entire institution.
This also creates an important privacy boundary. Notes about workplace encounters may contain information about coworkers, managers, health, performance, conflict, or institutional failures. Such records should remain under the user’s control and should not silently become shared reputational profiles of other people.
The following propositions summarize the model:
The science of management failure begins by taking workers’ pattern recognition seriously without mistaking recognition for explanation.
People really do encounter recurring forms of bad management. The tyrant, the automaton, the coward, the manipulator, and the absentee are not imaginary. They are stable enough to become jokes, stories, cartoons, and shared cultural knowledge. That is evidence worth preserving.
But the visible boss is an occupant of a role inside a larger institutional machine. To understand the encounter, we must ask what operation the role was supposed to perform, what authority it possessed, what constraint required allocation, what discretion remained, where the cost landed, and whether the author of the resolution owned any of it.
A manager is not a separate institutional species when the role goes wrong. Management failure is a family of deficiencies, excesses, abuses, and corruptions in the enactment of a general role. Its phenology is visible in behaviour; its explanation lies in the topology of work, authority, constraint, and ownership.
That is the movement from workplace folklore to institutional science.
MGT-COO)| Code | Name | Definition |
|---|---|---|
MGT-COO-001 |
Priority conflict unresolved | Incompatible priorities are assigned without an authoritative ordering or resolution. |
MGT-COO-002 |
Dependency uncoordinated | A known dependency between activities is not scheduled, communicated, or resolved. |
MGT-COO-003 |
Responsibility unassigned | Necessary work has no clearly designated responsible role. |
MGT-COO-004 |
Duplicate assignment | The same work is assigned redundantly without an operational reason or coordination between assignees. |
MGT-COO-005 |
Resource mismatch | Work is authorized without resources reasonably matched to its stated requirements. |
MGT-COO-006 |
Decision deferred | A required decision is postponed beyond the point at which delay begins imposing avoidable downstream cost. |
MGT-COO-007 |
Impediment abandoned | A reported impediment within management scope is neither resolved, escalated, nor explicitly accepted. |
MGT-COO-008 |
Coordination displaced | Workers without corresponding authority are made to perform coordination that belongs to the management role. |
MGT-COO-009 |
Change unsynchronized | A change to objectives, scope, timing, or resources is not propagated to affected roles. |
MGT-COO-010 |
Escalation failure | A constraint exceeding local authority is not escalated to a role capable of resolving it. |
MGT-AUT)| Code | Name | Definition |
|---|---|---|
MGT-AUT-001 |
Scope exceeded | Role authority is exercised outside the management function or beyond its delegated boundary. |
MGT-AUT-002 |
Personal dominion asserted | Institutional authority is presented or exercised as personal ownership of subordinate people. |
MGT-AUT-003 |
Irrelevant conduct controlled | Control is imposed over personal conduct without a relevant connection to the work operation. |
MGT-AUT-004 |
Emotional submission demanded | Access, approval, or safety is conditioned on displays of personal loyalty, enthusiasm, gratitude, or deference not required by the work. |
MGT-AUT-005 |
Retaliatory authority used | Role power is used to punish relevant disagreement, reporting, refusal, or appeal. |
MGT-AUT-006 |
Positional access exploited | Access created by the role is repurposed for personal, sexual, romantic, financial, or other extraneous advantage. |
MGT-AUT-007 |
Confidential access misused | Information available through the role is used or disclosed outside its authorized purpose. |
MGT-AUT-008 |
Coercive ambiguity maintained | The boundary between request and requirement is deliberately or recurrently obscured where refusal carries positional risk. |
MGT-AUT-009 |
Humiliation used as control | Degradation, ridicule, or public embarrassment is used to compel performance or establish rank. |
MGT-AUT-010 |
Appeal obstructed | A person is prevented from accessing an authorized review, complaint, accommodation, or escalation path. |
MGT-ALC)| Code | Name | Definition |
|---|---|---|
MGT-ALC-001 |
Absorption capacity ignored | Constraint is allocated without considering materially unequal capacity to absorb it. |
MGT-ALC-002 |
Avoidable cost routed downward | A cost that could be borne or reduced by an authority role is transferred to a lower-authority role. |
MGT-ALC-003 |
Risk transferred without authority | A role is made to bear risk without corresponding control over the decisions that produce it. |
MGT-ALC-004 |
Urgency manufactured | Avoidable delay or indecision upstream is converted into emergency conditions downstream. |
MGT-ALC-005 |
Workload made non-viable | Assigned obligations exceed available time or capacity without reprioritization, added resources, or explicit acceptance of loss. |
MGT-ALC-006 |
Invisible labour externalized | Necessary coordination, emotional, repair, documentation, or support work is left unrecognized and unsupported. |
MGT-ALC-007 |
Neutrality under asymmetry | Uniform treatment predictably routes greater constraint toward roles with lower absorption capacity. |
MGT-ALC-008 |
Exception asymmetrically denied | Available discretion is withheld from a lower-capacity role while comparable discretion protects a higher-authority role. |
MGT-ALC-009 |
Failure cost displaced | The consequences of an upstream decision are assigned to a downstream role that did not author or control it. |
MGT-ALC-010 |
Recovery capacity consumed | Repeated allocations use the same role’s remaining slack, rest, goodwill, or resilience as an unacknowledged institutional resource. |
MGT-OWN)| Code | Name | Definition |
|---|---|---|
MGT-OWN-001 |
Authorship obscured | The role that selected or materially shaped a resolution is not disclosed or acknowledged. |
MGT-OWN-002 |
Policy laundering | A discretionary decision is represented as mechanically required by policy. |
MGT-OWN-003 |
Necessity laundering | One selected course is represented as having had no alternative when admissible alternatives existed. |
MGT-OWN-004 |
Authority-responsibility split | A role exercises decision authority while another role is assigned responsibility for the result. |
MGT-OWN-005 |
Delegation without authority | Responsibility is delegated without the authority required to discharge it. |
MGT-OWN-006 |
Consequence insulation | A role repeatedly authors resolutions while remaining protected from their relevant costs or consequences. |
MGT-OWN-007 |
Credit captured upward | Credit for downstream work is reassigned to a higher-authority role without an accurate account of contribution. |
MGT-OWN-008 |
Blame routed downward | Responsibility for an authority-level decision or systemic condition is assigned to a lower-authority role. |
MGT-OWN-009 |
Repair obligation displaced | The work of correcting a harmful resolution is assigned to those who bore the harm rather than those who authored or controlled it. |
MGT-OWN-010 |
Decision record falsified | The stated account of who decided, knew, objected, or possessed discretion materially conflicts with the operational history. |
MGT-INF)| Code | Name | Definition |
|---|---|---|
MGT-INF-001 |
Material information withheld | Information necessary for authorized work or informed response is not provided to an affected role. |
MGT-INF-002 |
Instruction ambiguous | An instruction is insufficiently determinate for reliable execution and clarification is not supplied. |
MGT-INF-003 |
Instruction contradictory | A role receives incompatible instructions without an ordering rule or authoritative resolution. |
MGT-INF-004 |
Objective misrepresented | The purpose, success condition, or intended beneficiary of an operation is materially misstated. |
MGT-INF-005 |
Constraint misrepresented | A negotiable preference is described as fixed, or a fixed constraint is described as discretionary. |
MGT-INF-006 |
Feedback channel suppressed | Relevant operational information cannot travel upward without obstruction or positional danger. |
MGT-INF-007 |
Bad news filtered | Adverse information is altered, delayed, or omitted as it travels toward allocation authority. |
MGT-INF-008 |
Surveillance disproportionate | Information is collected beyond what is relevant and proportionate to the management operation. |
MGT-INF-009 |
Context stripped | A report, metric, or statement is detached from context necessary for its proper interpretation. |
MGT-INF-010 |
Informational asymmetry exploited | Unequal access to operational information is used to secure compliance or avoid accountability. |
MGT-EVL)| Code | Name | Definition |
|---|---|---|
MGT-EVL-001 |
Criteria undefined | Work is evaluated against criteria that were not made sufficiently knowable. |
MGT-EVL-002 |
Criteria changed retrospectively | Success conditions are altered after the evaluated work has been performed. |
MGT-EVL-003 |
Irrelevant criterion applied | Evaluation depends on conduct or attributes unrelated to the legitimate requirements of the role or work. |
MGT-EVL-004 |
Comparable cases treated inconsistently | Materially comparable work is evaluated differently without a relevant stated distinction. |
MGT-EVL-005 |
Contribution misattributed | Responsibility, credit, or fault is assigned to a role that did not make the relevant contribution. |
MGT-EVL-006 |
Constraint omitted from evaluation | Performance is judged without accounting for material constraints known to the evaluating role. |
MGT-EVL-007 |
Uncontrolled outcome penalized | A role is penalized for an outcome it lacked meaningful authority or capacity to control. |
MGT-EVL-008 |
Invisible contribution excluded | Necessary but less visible labour is omitted from recognition or evaluation. |
MGT-EVL-009 |
Metric substituted for operation | A proxy measure is treated as the operation’s purpose despite material divergence from the intended outcome. |
MGT-EVL-010 |
Evaluation used coercively | Evaluation is used to secure extraneous compliance rather than assess work against legitimate expectations. |
MGT-COR)| Code | Name | Definition |
|---|---|---|
MGT-COR-001 |
Failure recurrent | The same failure mode recurs across operations or reporting periods. |
MGT-COR-002 |
Deformation visible | Cumulative exhaustion, exclusion, precarity, operational damage, or narrowed futures are observable in affected roles. |
MGT-COR-003 |
Correction resisted | A visible and remediable failure pattern persists despite credible notice or available correction. |
MGT-COR-004 |
Authority role insulated | The role controlling allocation remains stable or protected while affected roles repeatedly bear the cost. |
MGT-COR-005 |
Downstream routing persistent | Constraint is repeatedly directed toward roles with less authority or lower absorption capacity. |
MGT-COR-006 |
Authorship persistently displaced | Responsibility for recurring allocations is repeatedly obscured, denied, or attributed to abstractions. |
MGT-COR-007 |
Procedure protects topology | Formal procedure repeatedly preserves the same distribution of authority, insulation, and downstream cost. |
MGT-COR-008 |
Repair remains cosmetic | Responses alter language, reporting, or appearances without changing the underlying constraint flow. |
MGT-COR-009 |
Failure rewarded | The role or arrangement producing downstream deformation receives status, compensation, security, or expanded authority because of the resulting output. |
MGT-COR-010 |
Ownership structurally absent | No allocation-authority role is required to bear, acknowledge, or repair the recurring cost of its resolutions. |
MGT-GRD)| Code | Name | Definition |
|---|---|---|
MGT-GRD-001 |
Insufficient evidence | Available observations do not support a more specific error classification. |
MGT-GRD-002 |
Mechanism unresolved | A recurring form is detected, but the operation producing it remains unknown. |
MGT-GRD-003 |
Authority unresolved | The relevant distribution of decision authority and discretion has not been established. |
MGT-GRD-004 |
Constraint unresolved | The origin, avoidability, or severity of the governing constraint has not been established. |
MGT-GRD-005 |
Recurrence unresolved | Available observations do not establish whether the event is isolated or persistent. |
MGT-GRD-006 |
Legitimate conduct possible | The observed cost may result from authorized role conduct under an unavoidable constraint. |
MGT-GRD-007 |
Tragedy possible | Every presently known admissible allocation may impose substantial harm. |
MGT-GRD-008 |
Multiple codes applicable | The event contains separable coordination, authority, allocation, ownership, information, evaluation, or corruption failures. |