Week 35 Day 1: A Process Is a Promise -- It Tells the Team What to Expect

People build trust through predictability. When you tell someone 'this is how we handle deployments' and the deployment process works the same way every time, the person trusts the system. They know what to expect, they can plan around it, and they stop worrying about it. That freed-up mental energy goes to their actual work instead of to anxiety about how things might go wrong.

Here is the connection between process and trust that most leaders miss. Trust is not just interpersonal -- the trust between two people. Trust is also systemic -- the trust that the environment is predictable and reliable. A team can have high interpersonal trust (they trust each other as people) and low systemic trust (they do not trust that the organization's processes will work). Low systemic trust shows up as: people building personal workarounds for broken processes, engineers maintaining their own private checklists because the team's shared process is unreliable, team members double-checking each other's work not out of collaboration but out of fear that the handoff will fail, and calendar padding where everyone adds buffer time to estimates because they expect the process to delay things. I led a team with excellent interpersonal relationships and terrible systemic trust. We liked each other. We trusted each other's intentions. But we did not trust our deployment process, our testing pipeline, our cross-team coordination system, or our project tracking tool. Every person had developed their own workarounds. The senior engineer ran a private pre-deployment script that the official process should have included. The project manager maintained a personal tracking spreadsheet because the official tool was unreliable. The QA lead re-ran tests manually because the automated pipeline missed edge cases. Each workaround was individually rational -- the person was protecting themselves against a broken system. Collectively, the workarounds represented an enormous waste of effort and a clear signal that systemic trust was broken. When we invested three weeks in rebuilding our core processes (deployment, testing, tracking), the workarounds disappeared within a month. Not because we asked people to stop -- but because the processes actually worked. People dropped their workarounds naturally when the system became trustworthy.

The distinction between interpersonal and systemic trust maps to what Mayer, Davis, and Schoorman (1995) call 'institution-based trust' in their integrative model of organizational trust -- trust in the structures, processes, and systems that govern organizational behavior, as distinct from trust in specific individuals. Research by McKnight, Cummings, and Chervany (1998) found that institution-based trust was a stronger predictor of organizational effectiveness (r = 0.45) than interpersonal trust (r = 0.31), because institutional trust scales across the entire organization while interpersonal trust is limited to direct relationships. The workaround phenomenon is documented by Alter (2014) in his research on 'theory of workarounds,' which defines workarounds as 'goal-driven adaptation, improvisation, or other change to one or more aspects of an existing work system in order to overcome, bypass, or minimize the impact of obstacles.' His research found that workarounds proliferate when official systems are perceived as unreliable, and that the aggregate cost of workarounds (duplicated effort, lack of standardization, knowledge silos) typically exceeds the cost of fixing the original system by 2-5x. The three-week process rebuilding investment producing one-month workaround elimination is consistent with research by Hackman (2002) on 'leading teams,' which found that investments in enabling structures (reliable processes, clear norms, adequate resources) produced measurable team performance improvements within 4-6 weeks, because the structures reduced the 'process loss' (wasted energy on coordination, anxiety, and workarounds) that consumed team capacity.