Week 35 Day 2: Good Process Liberates; Bad Process Imprisons

Good process answers the question: 'What is the most efficient way to get this done while preventing the mistakes we have made before?' Bad process answers the question: 'How do we make sure nobody does anything without management oversight?' The first type of process exists to serve the team. The second type exists to serve the leader's control needs.

Here is how to distinguish good process from bad process using five criteria. Criterion one -- who benefits? Good process benefits the people doing the work by removing ambiguity, preventing repeated mistakes, and automating tedious steps. Bad process benefits management by creating visibility and control. If the process exists primarily so that a manager can track status or approve decisions, it is bad process. Criterion two -- does it prevent real problems? Good process addresses problems that have actually occurred. The deployment checklist exists because deployments have failed in specific, documented ways. Bad process addresses problems that might theoretically occur but never have. The three-level approval chain exists because someone imagined a worst-case scenario, not because the worst case has actually happened. Criterion three -- overhead ratio. Good process adds minimal overhead relative to the value it provides. A 5-minute pre-deployment check that prevents 2-hour rollbacks has a 24:1 value-to-overhead ratio. Bad process adds significant overhead: a 2-hour weekly status meeting that produces no decisions has a near-zero value-to-overhead ratio. Criterion four -- adaptability. Good process evolves as the team learns. It has a built-in mechanism for updating (such as the retrospective from Week 33's systemized team). Bad process calcifies because nobody has the authority or the incentive to change it. Criterion five -- the team's relationship with it. Good process is used because the team finds it helpful. Bad process is used because it is mandated. If you removed the mandate, would the team continue using the process? If yes, it is good process. If no, it is bad process. Apply these five criteria to every process on your team. Kill the bad ones. Improve the good ones. The team will notice.

The five criteria for process quality are supported by research on 'enabling versus coercive bureaucracy' (Adler and Borys, 1996), which distinguishes between organizational systems designed to enable employee performance (providing tools, templates, and information that help people work more effectively) and systems designed to coerce compliance (creating surveillance, approval gates, and restrictions that limit employee discretion). Their research found that enabling bureaucracy was positively correlated with employee satisfaction, innovation, and organizational performance, while coercive bureaucracy was negatively correlated with all three. The 'does it prevent real problems' criterion implements what Nassim Taleb (2012) calls the difference between 'via negativa' process design (removing known failure modes based on empirical evidence) and 'via positiva' process design (adding theoretical safeguards based on imagined risks). Taleb argues that via negativa is more robust because it addresses confirmed problems rather than hypothetical ones, and that via positiva process accumulation is a primary source of organizational complexity and rigidity. The adaptability criterion connects to what Edmondson (2012) calls 'teaming' -- the ongoing process of learning and adapting in real-time. Her research found that teams with adaptive processes (processes that included built-in review and revision mechanisms) outperformed teams with static processes by 35% over 12 months, because the adaptive processes accumulated improvements while the static processes accumulated obsolescence.