The 5 C's Framework
A field-tested model for optimizing engineering group dynamics, establishing high-performance teams, and executing decentralized command — built on the Crucial C's of Adlerian psychology, adapted to engineering teams, and extended with a fifth.
The Core Philosophy
The 5 C's Framework is explicitly designed as a guide for setting up technical teams and managing complex group dynamics. Four of the five — Connect, Count, Capable, Courage — are not mine. They are the Crucial C's identified by Dr. Betty Lou Bettner and Dr. Amy Lew in their research on what makes classrooms and families function, first published in Raising Kids Who Can (1989) and grounded in Alfred Adler's Individual Psychology. The fundamentals that hold in a healthy classroom hold in a healthy team, because the underlying human needs don't change when the people get older.
I first wrote this up in 2017 as Everything I Need for Scrum I Learned in Kindergarten — the observation being that the fundamentals effective teachers practise map directly onto forming a team, because the underlying human needs don't change when the people get older.
The fifth, Choice, is my addition. Autonomy is what turns compliance into intrinsic motivation, and a team only does its best work when it is self-directed. What I've added beyond that is the translation: what these five look like when the team is shipping certified software, and what they cost you when they're missing. Maneuver Warfare and the Marine Corps' decentralized-command doctrine are the operating model I run them through — execution at the lowest level, against a clear commander's intent.
The critical shift in the 5 C's is moving the organization from blame-oriented 'Why' questions (which trigger defensive postures) to discovery-oriented 'What' questions (which drive systemic solutions).
The 5 Pillars of Team Dynamics
Connect: Collaboration & Integration
Engineers cannot operate in silos. 'Connect' ensures the structural and relational pathways exist for cross-functional collaboration. It focuses on how teams integrate their outputs and maintain a continuous feedback loop across the enterprise architecture.
Count: Impact & Alignment
Every team member must understand how their specific tasks translate to the broader mission. 'Count' is the relentless alignment of daily engineering work with enterprise-level strategic impact, ensuring no effort is wasted on misaligned objectives.
Capable: Competence & Resources
A team cannot be held accountable if they lack the means to execute. 'Capable' demands that leadership provides the exact technical competence, training, and physical/budgetary resources required to meet the objective before assigning responsibility.
Courage: Innovation & Risk
Strict compliance environments often stifle creative engineering. 'Courage' establishes psychological safety, empowering engineers to identify technical debt, take calculated risks, and drive innovation without the fear of punitive action for necessary experimentation.
Choice: Autonomy & Ownership
The ultimate goal of the framework. 'Choice' is the absolute execution of decentralized command. It is not about character or abstract connection; it is the concrete delegation of authority, allowing the engineers closest to the problem to make the technical decisions and own the outcomes.