Frontier Research — Stanford GSB

Trust and Its Consequences

Stanford's Corporate Governance Research Initiative on what trust does — and what its absence costs — inside an organization.

Stanford CGRI·6 min read·1 primary source

01Why "The Spread of Workplace Trust and Its Consequences" matters to an operations consultancy

Most operating-model work is, at the surface, about workflows, instrumentation, and decision rights. Underneath it, almost all of it is about trust: whether the team trusts the data, whether leaders trust the team, whether customers trust the company to follow through.

Stanford's CGRI series is one of the few places where this gets written about with real research rigor rather than as a leadership-book platitude. "The Spread of Workplace Trust and Its Consequences" — Closer Look #52 — is the canonical entry on the subject: what trust does, what its absence costs, and how it propagates inside an organization.

02The operational signature of low trust

We can usually diagnose a trust deficit from operating data alone, before we talk to a single person. The signs cluster: meeting load that exceeds 60% of senior calendars, decisions that require more than three approvers, escalation rates that grow rather than shrink as the team matures, documents that get longer and more cautious over time rather than sharper and shorter.

Each of those is a workaround. The system is producing them because trust isn't doing the work it's supposed to do. People can't take action on a colleague's word, so they require a meeting. They can't trust a single sign-off, so they add a second. They can't trust the document to be read carefully, so they pad it. The Stanford research is what gives those individual symptoms a unifying diagnosis.

03Why adding process makes it worse

The reflexive leadership response to a trust deficit is to add structure: more documentation, more meetings, more approval gates, more dashboards. The Stanford research is part of a body of work showing this typically deepens the problem rather than fixing it.

New process accreted to compensate for low trust signals to the organization that low trust is the steady state — that it's the thing the system has been engineered around. The actual repair is to remove the conditions that produced the trust deficit, not to scaffold around them. That's an unusual recommendation to make to a leadership team that has spent six months adding the scaffolding.

"Trust is not a soft variable. Its absence shows up as additional meetings, slower decisions, and bigger handoff costs. Those are operating-model symptoms, not culture symptoms — and adding more process is the wrong fix."

How this maps to the work

We cite this paper in engagements where leadership wants to fix the symptoms — too many meetings, slow decisions, friction between functions — without addressing the underlying trust environment that's generating them. Adding more process to a low-trust environment doesn't fix it. It entrenches it.

Our work in those cases is part diagnosis, part design: identify the operational symptoms that are downstream of trust gaps, then design the operating-model changes that rebuild trust as a side effect — clearer ownership, better visibility, smaller handoffs, faster feedback. The trust improves because the system stopped requiring people to compensate for missing structure.

Three engagements we run against this thesis.

None of these require a multi-year transformation. Each is scoped to land specific operating-model improvements with a measurable result.

01

Trust-as-data diagnostic

We measure the operational symptoms of trust gaps — meeting load, decision latency, escalation rate, document drift — and use them to map where trust is degraded before survey work would catch it.

02

Process-removal audit

The under-asked engagement: which of your existing processes are workarounds for missing trust, and what would it take to remove them? Often the most valuable operating-model change a client makes in a year is subtractive, not additive.

03

Post-event trust recovery design

After a layoff, leadership change, or public failure, we install the visibility and cadence patterns that rebuild trust deliberately — not as a culture initiative, as a structured operating-model change with a defined arc.

If this maps to what you're carrying — let's talk.

Most engagements start with a 30-minute conversation about the specific operating-model question on your desk this quarter.