Power Literacy — The Mechanics of Power

Internalize the academic foundation under everything else: where power actually comes from in organizations, why some people accumulate it and others — often equivalently capable — don't, and what acquiring it does to the acquirer. Build your own power-mapping diagnostic. By the end, your observation of organizations becomes predictive, not just descriptive. Power is the difference between calling a method and triggering the full callback chain. The org chart says who can call which methods — who has commit access, who can approve deploys. The political surface determines whether a given call actually fires the before_save, around_save, and after_commit chain — whether it gets validated, audited, observed, propagated. Two engineers with identical nominal authority call the same method and get systematically different results: one call triggers the audit log and the downstream actions; the other gets quietly swallowed between validation and the database. Pfeffer's research program is, from this angle, documentation of the callback chain on top of organizational authority. Klaas documents what happens to people who learn to fire the full chain reliably: they start believing they are the chain. Every engineer who has worked in a poorly-architected codebase has seen the pattern — operators who stop noticing how much of the work is done by infrastructure they didn't design and don't fully understand. Power is that infrastructure. Pfeffer documents how it works; Klaas documents what happens when its operators forget.