Work Command Centers
Master operating hub coordinating six specialized work crews.
Michael R. Brotherton, PMP, CSM — focused on mission accomplishment while reducing costs and ensuring alignment with organizational objectives.
Specific systems, organizations, and data shown here are generalized for privacy. The underlying architecture and methods are real.
One operating problem became a fleet, a chain of command, and a quality system. Every step came from using the work, catching what failed, and fixing the process—not writing a theory about it.
Brotherton Books — a bi-weekly envelope budget system running on a Google Sheet. I handed the entire bookkeeping job to AI: logging from bank feeds, reconciling every tab, answering “how much is left” without me touching it.
One assistant became a crew. Crews needed coordination, so we built the XO — an executive officer speaking with my authority. Six crews, nine workstreams, all reporting through the chain: crew → XO → main chat → me. Zero exceptions.
Quality wasn’t good enough. So I wrote the control system myself — five Critical-to-Quality gates, two build paths (full and light), golden packets for every defect class my screenshots caught. The machine grades every build. My tap is the final gate.
The QC Machine. Fleet process, five gates, Path F for anything visual. Nothing ships until it clears.
Navigation is king. Command palettes, L1-to-L4 drill-downs, breadcrumbs, status dots. Every number answers “so what?” at a glance.
Research integration. 35 patterns from the best dashboards on earth — Linear’s command palette, Stripe’s progressive disclosure, D3 crossfiltering. Tabular numerals. Semantic color tokens. The details that make it feel inevitable.
Ownership. Each agent takes pride in their baby. Not generic patterns — deep, domain-specific finishing touches. The agent who owns the debt center knows every avalanche calculation. The one who owns commute books knows you listen at night and need a sleep timer.
This portfolio is the proof. Not claims — the actual work, live and clickable.
“Focused on mission accomplishment while reducing costs and ensuring alignment with organizational objectives.”
Michael R. Brotherton, PMP, CSM is Project Management Team Lead at the SC Department of Health and Human Services, Bureau of Provider Support Services, leading five project managers across a portfolio of approximately 40–60 projects.
He brings 25+ years delivering complex, cross-functional programs across military, engineering, energy, and health IT. A dedicated leader with a coach, teach, and mentor style.
PMP #8033996 · CSM #001557 · Lean Six Sigma Black Belt (U.S. Army) · Master Training Specialist (USAF) · U.S. citizen. Previously held Top Secret/SCI clearance (2013–2021); highly re-clearable.
Graduate Certificate, Learning Design & Technology — University of Southern California; B.S., Education and Training (Business minor), GPA 3.5 — Wayland Baptist University; A.A.S., Corporate Training & Development — Wayland Baptist University; A.A.S., Mechanical & Electrical Technology and A.A.S., Instruction of Technology & Military Science — Community College of the Air Force.
Proven ability to analyze a given situation, develop courses of action, and deliver results.
Project Management · Data Analysis · Policy/Operations Expertise · Emergency Management · Risk Management · Lean Six Sigma · Team Development/Management · Strategic Planning · Process Improvement/Development · Complex Problem Solving
Each command center turns a real operating domain into a clear, inspectable interface. Two earlier systems were consolidated into the financial command center—not hidden, but deliberately absorbed.
Master operating hub coordinating six specialized work crews.
Merged financial, debt, and market system with debt-avalanche modeling.
Bi-weekly envelope-budget operating view with reconciliation logic.
Capabilities consolidated into the Financial Command Center.
Capabilities consolidated into the Financial Command Center.
Application pipeline managing 13 active opportunities.
Audiobook player paired with structured knowledge capture.
Program delivery control surface for a 183-row work breakdown structure.
Hierarchical data-classification system built for fast navigation.
Healthcare compliance tracking across complex operational work.
Regulatory gap analysis across bureau and managed-care sources.
Federal regulatory duty reconciliation system.
Shareable compliance workspace adapted for team execution.
Focused work-in-progress tracking for flow and throughput.
Voice-to-Notes OS intake that turns spoken context into structured work.
The command center that monitors the machine building command centers.
One source of truth, many controlled interfaces. Designed and built a two-way sync system connecting Google Sheets — the system of record — to a fleet of web command centers through a Google Apps Script bridge. The bridge is the central gatekeeper: every write authenticated, validated against an action allowlist, written to an append-only audit log. Security is layered — rotating write tokens, kill-switch, fail-closed degraded mode if the bridge goes dark. Each surface gets its own controls: per-center toggles, optimistic updates, timestamp-based conflict resolution. Real collaboration across many interfaces without ever compromising the source of truth.
The machine does not add polish after the work. It changes how the work is produced—each generation carrying forward the controls that proved useful.
Five Critical-to-Quality gates, Path F for full treatment and Path C for light treatment, with verification required before “done.”
Command palette, L1–L4 drill-down, breadcrumbs, status dots, and progressive disclosure turn dense systems into navigable ones.
Research-backed UX patterns drawn from D3.js, Linear, Stripe, Vercel, mobile financial products, Apple HIG, and Material Design 3.
Each agent treats its command center as “their baby,” applying deep domain-specific finishing work rather than generic decoration.
The output is measurable: systems shipped, workloads decomposed, regulatory duties reconciled, and quality gates passed.
The system separates ownership, coordination, and human judgment. That keeps parallel work fast without turning it into parallel noise.
A machine run is not complete when the first outputs land. It ends when every assigned system clears the line.
Nothing ships until Visual, Functional, Content + Data, Chain, and Flow are each checked. Quality is an exit condition, not a suggestion.
Screen recordings reveal what automation misses. Every caught defect becomes a named defect class the machine can recognize next time.
Patterns are ranked by impact and effort, then adapted to the domain. Inspiration that cannot survive implementation does not enter the system.
“Finished products only.”
The public links below open the actual systems. Unshared systems stay clearly labeled instead of sending you to a dead end.
Regulatory gaps organized for review, ownership, and closure.
A shareable compliance workspace adapted for team execution.
Three domains consolidated into one cross-filtered operating view.
A Level 4 work breakdown structure made navigable.
The goal isn’t to make AI look busy. It’s to build a system where good work becomes repeatable.