# Agency Project Management: The System That Keeps Everyone Sane — Troy Dean ## 🗂️ Triage — annotated highlights surfaced > [!note]- Cross Reference > - **Tool migration can't fix an undefined process** — reframes "which PM tool" as "which process"; a systems-not-symptoms diagnostic. #xref > - **One owner per task** — load-bearing precondition for every downstream fix (Definition of Done, weekly rhythm). #xref > - **Silence, not bad news, drives client friction** — supports proactive-communication SOPs over reactive firefighting. #share ## 🧭 Bib capsule Troy Dean (Agency Mavericks), "Agency Project Management: The System That Keeps Everyone Sane," 2026, https://www.agencymavericks.com/agency-project-management-the-system-that-keeps-everyone-sane/ ## 🧠 Author's thesis (Adler Q1+Q2) Agency chaos is a process-definition problem wearing a software costume: swapping PM tools never fixes a workflow nobody wrote down. In detail, Dean prescribes rules of engagement — visibility, single-owner accountability, and repeatable SOPs — plus a hard Definition of Done, a 70-80% capacity buffer, strategy-not-status meetings, and a proactive "no-surprise" client policy, arguing the owner's real job is to become the system's director rather than its chief firefighter. It reads as marketing content backed by unverified anecdote, funneling to Dean's paid offer. ## 🧩 Key arguments - A PM tool only reflects the process you feed it; the fix happens on a whiteboard before any software. - Three pillars — visibility, accountability (one owner per task), repeatability (SOPs covering ~80% of work) — plus a defined "done" are the scope-creep defense. - Resource buffers (cap utilization at 70-80%) and proactive client communication protect margin and retention; the owner must stop being the growth ceiling. ## 🗒️ Notes — Literature atoms ### One task owner prevents diffused accountability > [!quote] > "When everyone is responsible, nobody is responsible." - **Where**: "Accountability" pillar section - **Why**: Every downstream fix assumes single-owner task assignment as a precondition. ### Tool migration can't fix an undefined process > [!quote] > "The tool is just a digital filing cabinet. If you put garbage in, you get organised garbage out." - **Where**: "The Tool Trap" — the article's central thesis - **Why**: Reframes "which tool" questions as "which process" questions; useful for any PM-tool selection or ops audit. ### Silence, not bad news, drives client friction > [!quote] > "The biggest cause of client friction is silence. When a client hasn't heard from you in four days, they assume nothing is happening." - **Where**: "Client Communication as a Project Management Function" - **Why**: Supports proactive-communication SOPs over reactive account firefighting. ## 🔖 Permanent candidates - A system needs one owner per task to function — A task assigned to more than one person has no real owner, so default every task, delegated or your own, to exactly one named accountable person. [already_covered_guess: null] ## Links - [[Product & Startup Instincts MOC]] — agency operating-model advice: pricing, capacity, accountability, and owner-as-bottleneck are core startup-instinct patterns. - [[Your System Is the Practice]] — same core claim from a different angle: the operating system underneath the work is the actual discipline, not the tool. - [[A System Failure That Looks Like a Performance Failure Never Gets Fixed]] — matches the tool-trap logic: mislabeling a process problem as a software problem keeps the real failure invisible. - [[How to Raise Your Agency Prices Without Losing Clients]] — the pricing counterpart: capacity/accountability systems only pay off if margins are set by delivered value. ## ✅ Processing checklist - [x] Claim atoms carried from deep-read analysis - [ ] Permanent candidates reviewed for promotion - [ ] Version History Diff check