Develop the configuration-aware political literacy that the FTE-calibrated literature ignores: the three-party contractor relationship (you ↔ agency ↔ end-client), the open-source maintainer's political surface, and the politics inside a company you build — the first hire, advisors, equity, and the founder-with-a-day-job line. The contractor configuration is a microservices architecture where the FTE configuration is a monolith. The monolith has fewer organizational boundaries and faster internal information flow; the microservice configuration introduces network calls across boundaries with all the familiar failure modes — timeouts (the stakeholder in another org and time zone didn't respond; it isn't personal), partial failures (one scope item in dispute while the engagement keeps running), version mismatches (the agency's understanding and the client's have drifted and nobody noticed), observability gaps (you can't see what's said about you in either leadership room; you see only consequences), and the difficulty of debugging across services (the cause is usually at the boundary and requires reconstructing events across organizations). The political work of contractors is the operational work of microservices teams: explicit contracts at the boundaries, careful versioning of expectations, defensive communication, and runbooks written calm and rehearsed before needed. The Trust Topology Map is the architecture diagram; the Escalation Protocol is the on-call runbook; the Extension Plan is the migration plan before the major upgrade. None of it ships features — and it is the infrastructure without which the productive work degrades silently. Founder politics, meanwhile, is system design done early so the system doesn't crush you later: the choices you make at two employees determine the political shape at twenty, the way early decisions about isolation and access control determine everything possible at scale. The first-hire conversation is the first major architectural decision. You don't get to redo it cheaply.
This course unlocks once you've finished its prerequisite. Open prerequisite →
The thing I want to name first is the seductive narrative that has to be refused before this module can do its work: I'm just a contractor; I just do the work; the politics aren't…
Almost every operational claim in the political canon — Pfeffer, Cialdini, Grant, Ibarra, Fournier, Hogan, Larson, Reilly — assumes a configuration many working engineers do not i…
Approach: Essential
Approach: Essential
Approach: Important
Approach: Important
Approach: Important
Run the configurations that apply to you; do at least two deliverables.
8 lessons. Read in order; spiral back when you need to. By the end you'll have used the core ideas twice — once on the abstract, once on something you'll meet at work next week.