Are We Automating Trust Out of Our Organizations?

The Unintended Consequences of Process and Technology, especially AI.

A few months ago, I wrote about relationship-based companies and described trust as the “human API” that allows people and teams to work effectively across organizational boundaries. I ended that article by noting that the broader erosion of trust was a much bigger topic. This article goes deeper into that question and introduces a framework for thinking about trust and organizational discipline together.

I have spent much of my career helping organizations become more disciplined through people, process, technology, and data. My work has historically gravitated toward the latter three.

Simon Sinek's work on trust, combined with years of watching organizations transform, has led me to think more deeply about the people dimension: the human architecture that determines how people interact, exercise judgment, and build trust.

It has left me with this question:

In our efforts to institutionalize and automate how organizations work, are we unintentionally weakening the relationships and trust that made them effective in the first place?

Organizations need discipline to execute consistently, scale, and adapt. But institutionalization has an important and frequently overlooked consequence:

It changes who interacts with whom.

As documented and formal processes, organizational structures, and technology replace informal interactions, organizations can become more efficient but with an unintentional weakening of relationships through which trust, institutional knowledge, and shared judgment develop and persist.

Not every eliminated interaction was waste.

The consequences extend beyond weaker relationships. As trust declines, people can increasingly optimize for their own organization, budget, reputation, or near-term results rather than the overall enterprise. Structural silos become cognitive silos. Politics, self-protection, and bureaucracy can occupy space once held by shared purpose and principle-based judgment.

Eventually, an organization may need more process precisely because it has lost the trust that once allowed people to work effectively without it.

Trust is not the absence of discipline. It is discipline internalized through principles rather than externalized through rules.

Building on Sinek's trust-and-performance framework, I consider organizational trust and discipline as two dimensions and use them to examine four organizational archetypes.

The objective is the upper-right quadrant: an organization with both the discipline to execute consistently and the trust to adapt.

Getting there requires deliberately designing how people work together. Team of Teams and persistent product teams offer some complementary approaches to building trust across organizational boundaries and over time.

AI makes these choices even more consequential. Technology will increasingly allow us to eliminate human interactions that once seemed unavoidable. What can be automated and what should be automated are not necessarily the same thing.

In the AI era, the challenge will not be determining which human interactions we can eliminate. It will be determining which we cannot afford to lose.

The goal is to institutionalize discipline without institutionalizing isolation or unknowingly opening the door to politics and short-term thinking.

Trust and Organizational Discipline

Simon Sinek has described individual effectiveness through two dimensions: competence and trust. Organizations can be considered similarly.

At an organizational level, competence is expressed through discipline: the ability to execute consistently, make good decisions, learn, and repeatedly achieve outcomes.

Trust is also more than relationship quality. It develops through relationships, demonstrated performance, and consistency over time. Relationships create the context to understand someone's intent and judgment; performance provides evidence of capability; and repeated experience creates confidence in what to expect. Strong relationships accelerate trust, but relationships alone are not trust.

That discipline resides in four overlapping and interrelated areas:

• People: Judgment, experience, relationships, principles, and institutional knowledge.

• Process: Standards, governance, controls, decision rights, and repeatable ways of working.

• Technology: Automation, workflows, platforms, embedded controls, and increasingly AI.

• Data: Information, transparency, evidence, and organizational memory that enable the other three.

  
  

The goal is not to maximize one of them, but to create the right balance among them.

High trust without sufficient institutional discipline can manifest differently depending on the organization. In a startup, strong relationships and limited process can enable speed and entrepreneurship. In a large, mature organization, long tenure, institutional knowledge, and unwritten ways of working can create extraordinary loyalty and commitment, yet also reinforce the status quo. New ideas, people, and ways of working struggle to gain traction. Trust remains high, but adaptability can suffer.

High discipline without trust presents a different problem. These organizations can execute known work consistently, but increasingly rely on rules, controls, governance, and escalation to coordinate people. As ambiguity and change increase, these structures can inhibit collaboration, judgment, and adaptability.

As trust declines, people become less willing to make trade-offs for the long-term good of the enterprise and more likely to protect their own organization, budget, reputation, and near-term results. Politics, local optimization, and bureaucracy can flourish as people rely on organizational structures rather than relationships and shared purpose to resolve differences.

Neither quadrant is inherently dysfunctional. Both can succeed for long periods, but each relies too heavily on one source of organizational strength.

The goal is the upper right: enough discipline to scale, learn, and adapt, while preserving the trust, relationships, and judgment that enable people to work effectively when process cannot provide the answer.

When Process Replaces Trust

Organizations add process for good reasons. Small teams can operate through relationships, informal communication, and tacit knowledge. Start-ups do this well. People know whom to call, responsibilities overlap, and decisions happen through local conversations. This approach can also work remarkably well even in large organizations with long-tenured employees and deeply established relationships.

However, these organizations can struggle to adapt, scale new capabilities, or maintain consistency as people and circumstances change. Knowledge remains concentrated in individuals, decisions depend on relationships, and new ideas can struggle to gain traction.

The challenge is not organizational size, but recognizing when informal ways of working are no longer sufficient and greater discipline is needed.

A healthy organization institutionalizes and increasingly automates what is repeatable, predictable, and well understood, while preserving the human judgment and relationships necessary to navigate ambiguity and change. AI dramatically expands what technology can automate, making the distinction between what can and should be automated increasingly important.

Yet institutionalization has a less obvious consequence: it changes who interacts with whom.

In relationship-driven organizations, ambiguity forces interaction. People seek one another out, solve problems together, exchange institutional knowledge, and learn how other parts of the organization operate. Over time, these interactions build organizational trust.

As organizations become more structured, some of these interactions disappear. Functions specialize, boundaries become clearer, and work moves through defined handoffs. The organization may become more efficient, but people can become increasingly isolated within their organizational structures.

Eliminating ten unnecessary conversations may be valuable, but not every eliminated conversation was waste. Some were how people challenged assumptions, discovered problems, built relationships, and learned whom they could trust.

An organization can become more disciplined while simultaneously weakening the very mechanisms through which trust develops.

When process and technology eliminate meaningful human interaction, the organization may accumulate a rarely measured form of organizational debt: the gradual erosion of relationships, shared context, and trust.

The problem accelerates when process stops supporting trust and begins replacing it.

As trust in people's judgment declines, organizations compensate with more approvals, policies, governance, controls, and increasingly detailed roles. Each addition may be rational in isolation, but together they can create a reinforcing cycle:

Less trust can create more processes or a breakdown within the organization. More processes and technology can reduce meaningful interaction and opportunities to exercise judgment. Weaker relationships and shared context further reduce trust, creating demand for still more process.

Eventually, the organization needs process precisely because it no longer possesses the trust that once allowed it to operate without that process.

Politics and short-term thinking can emerge as particularly damaging consequences. As relationships weaken, people increasingly interpret decisions through organizational boundaries and personal agendas. Protecting one's organization, budget, or reputation can begin to outweigh the long-term interests of the enterprise.

Politics fills some of the space previously occupied by trust.

Team of Teams: Rebuilding Trust Across Boundaries

The answer is not to recreate an organization where nothing is documented and everything depends upon relationships.

The better question is how to retain institutional discipline while deliberately creating the interactions that develop trust. One operating model I have found can help is General McChrystal’s Team of Teams model.

Modern organizations need specialized teams. Complexity makes that unavoidable. But specialization does not require isolation.

A Team of Teams approach creates strong individual teams while deliberately connecting them through shared purpose, shared context, transparency, and relationships across organizational boundaries.

The organization becomes more matrixed, not simply through reporting relationships, but through how work actually gets done.

In this environment:

Trust becomes the human API between teams.

An API allows independent technology components to work together without becoming a single monolithic system. Trust performs a similar function organizationally.

Teams can retain specialized expertise, autonomy, and accountability while working fluidly across boundaries because people understand one another's context, capabilities, intent, and judgment.

Not every interaction requires a formal handoff. Not every ambiguity requires escalation. Not every cross-functional decision requires another governance process.

Trust does not replace discipline.

It makes disciplined organizations more adaptive.

Product Mode: Extending Trust Across Time

Traditional project structures create another challenge. Projects are intentionally temporary.

A team is assembled. A plan is established. Scope, milestones, funding, and deliverables are defined. The project executes. The objective is delivered. The team disbands.

That structure is appropriate for some work. But when it becomes the dominant mechanism for delivering change, it creates a short-term orientation.

Teams are frequently reorganized just as they have developed deep domain knowledge, strong working relationships, and collective judgment.

The organization effectively liquidates some of the human capital it just spent years creating.

Another complementary approach is Product Mode, which I have found works particularly well alongside Team of Teams and Agile.

A product-oriented operating model changes the dynamic and I have come to see and believe in its effectiveness over the last 10+ years.

Persistent teams remain accountable for an outcome or capability over time. They don't simply deliver something and leave. They build it, operate it, learn from it, improve it, and live with the consequences of their decisions.

That persistence matters.

People develop deeper relationships. They accumulate domain knowledge. They see the downstream consequences of architectural and design decisions. Technical debt is no longer somebody else's future problem. Customer outcomes continue after launch.

Most importantly, the time horizon changes.

Projects naturally ask:

What do we need to deliver by the end date?

Persistent product teams are more likely to ask:

What do we need to build and learn so this continues to create value over time?

Product mode therefore creates something that traditional project structures often struggle to produce: long-term accountability combined with short-cycle learning and agility.

Team of Teams helps build trust across organizational boundaries.

Product mode helps build trust, judgment, and institutional knowledge across time.

Together, they provide structural mechanisms for moving an organization toward the upper-right quadrant. Put Team of Teams and Product Mode together and you have cross team trust, long-term accountability, and true enterprise thinking.

The Hidden Cost of Short-Term Thinking

Trust is cumulative. It develops through relationships, demonstrated performance, and consistency over time. Repeated experience allows people to understand one another's capabilities, intent, judgment, and reliability. People become more effective together by repeatedly solving difficult problems, understanding one another's strengths and weaknesses, and experiencing the consequences of their decisions.

Yet many organizational practices work against this accumulation. Frequent reorganizations can reset relationships. Temporary project teams repeatedly assemble and disband. Career models reward mobility, incentives favor near-term delivery, and outside hiring can be valued more highly than institutional knowledge and proven track records. Leaders rotate before experiencing the long-term consequences of their decisions.

Organizations need new talent, fresh ideas, and change. The problem emerges when short tenure and short planning horizons become the dominant organizational rhythm.

People behave differently when they expect to work side by side with one another, and with their decisions, for a long time. And when they want to stay with an organization for a long time.

Long-term relationships create accountability that is difficult to reproduce through process. If I know I will work with you for years, my reputation matters. If my team will operate what we build, maintainability matters. If I expect to experience the consequences of today's decisions, long-term outcomes matter. Shared experience also allows us to resolve future problems with less process, not more.

As time horizons shorten, people increasingly optimize for what is measurable during their tenure: delivering projects, achieving annual targets, protecting budgets, or demonstrating their own leadership's success.

The rational unit of optimization can gradually shift from the enterprise to the individual, the initiative, or the function.

That creates fertile ground for politics. Functions protect their interests, leaders defend budgets, and information becomes a source of power rather than a shared enterprise asset. The boundaries on the organizational chart become boundaries in how people think.

Silos become more than structural. They become cognitive. Instead of asking, “What is right for the enterprise?”, people ask, “What is my organization responsible for?”. Rather than exercising judgment based on shared principles, they increasingly rely on policies, governance, and escalation paths.

Principle-based behavior gradually gives way to compliance-based behavior.

As trust declines, rules feel safer. More governance and controls are introduced to resolve disagreements and prevent undesirable behavior. The bureaucracy may be responding rationally to a real problem, but it can also reinforce it.

The organization may initially continue producing good results, making the cost difficult to see.

Financial statements do not show declining institutional knowledge. Project dashboards do not measure relationships that have deteriorated. Traditional productivity measures may even improve as seemingly inefficient human interactions disappear.

Yet organizational capital can be declining even when those indicators are postive.

The organization becomes increasingly effective at executing within its existing boundaries and ways of working, while becoming progressively less capable of changing them.

Long-tenured, high-trust organizations are not immune. Deep relationships can create extraordinary loyalty while reinforcing established norms and resistance to outside ideas. The same relationships that allow an organization to operate with relatively little formal process can also make change difficult.

The objective is not simply longer tenure or stronger relationships, but an organization where institutional knowledge, new ideas, enterprise principles, and long-term accountability reinforce one another.

Team of Teams and persistent product teams offer some ways to build relationships across organizational boundaries and preserve them long enough to accumulate knowledge, experience consequences, and develop shared accountability.

The organization begins optimizing not merely for today's delivery, but for its ability to make better decisions tomorrow.

Technology and AI Make the Human System More Important, Not Less

Technology has progressively automated the interactions required to operate an organization.

AI will accelerate this dramatically.

More information will be generated automatically. More workflows will be automated. More decisions will be supported, or potentially made, by technology. Coordination costs will continue to decline.

But there is an important distinction.

What isn't getting automated is trust. Or judgment shaped by shared experience. Or the ability to align quickly around a goal when things are ambiguous.

As technology removes more transactional interactions, organizations need to become increasingly intentional about preserving meaningful human ones.

Otherwise, technology will also unintentionally accelerate the same problem process created: removing the interactions through which organizational relationships were formed.

The bottleneck is shifting.

Not to technology. To how effectively people work together and, more importantly, adapt to change together.

Designing for the Upper Right

The evolution of a healthy organization should not be from relationships to process, but toward institutional discipline that deliberately preserves relationships, judgment, and trust.

When introducing new processes, technology, or operating models, leaders must ask more than whether they improve efficiency:

Which human interactions will disappear? Which are waste, and which create trust, shared context, and institutional knowledge? Where will those relationships develop instead?

Team of Teams and persistent product teams offer some ways to deliberately build human connectivity and long-term accountability across organizational boundaries while maintaining discipline and agility. Not the only ways.

This may be one of the defining organizational challenges of the AI era. We will become extraordinarily good at removing friction. But some friction is productive. It creates traction.

Interactions that appear inefficient today can create enormous value over time. They create relationships. Relationships create trust. Trust enables judgment.

And judgment allows organizations to adapt without writing a rule for everything.

The objective is neither the relationship-dependent organization of the past nor the process-dependent bureaucracy that often replaces it.

It is an organization with enough discipline to scale and enough trust to adapt.

That is the upper-right quadrant.

Measuring What We Usually Cannot See

If trust, relationships, institutional knowledge, organizational politics, and time horizons are forms of organizational capital, leaders need ways to understand whether that capital is accumulating or being consumed.

Traditional employee surveys are not nearly enough, especially when institutional and interpersonal trust is already low.

In Part Two, I will explore how we might measure these less visible dimensions of organizational health, including trust across boundaries, relationship networks, decision-making patterns, and long-term versus short-term behavior. The objective is to recognize when organizational capital is deteriorating before the consequences appear in financial performance.