Dr. Neil's Notes
General > People
Shared Outcomes, Not Shared Methods
Introduction
A common mistake in distributed teams is trying to create consistency of method across a group of people working in different contexts. It rarely works. The team in one location has different constraints, different working hours, and often a different cultural relationship to how work gets organised. Trying to align everyone on the same process tends to produce nominal compliance and actual fragmentation.
What can be aligned, and what actually matters, is the why and the what. Consistency in the destination, not the route.
Making the Mission Real
Abstract purpose statements do not move people in the same way that real stories do. A mission statement is a starting point. What actually creates shared meaning is a specific account of a person whose situation was different because of the work the team did, or a concrete instance where the product or service improved something real.
The leader who regularly tells stories, about decisions, about customers, about failures and what was learned, is building a shared culture one narrative at a time. A principle stated once is easy to forget. A story told well stays with people.
Principles Over Rules
Rules require enforcement. They become outdated. They create edge cases that no one anticipated, and they require escalation when reality does not fit the prescribed scenarios. Principles, when genuinely internalised, guide behaviour in situations the rule-maker never imagined.
The difference in practice is between "here is the process for this situation" and "here is why we do things this way, and here is what we are trying to protect". The second approach requires more investment to communicate clearly, but it creates a team that can act well in novel situations rather than one that is well-behaved within defined parameters and lost outside them. I have written more about this in Agility from Diversity.
Visible Progress
Distributed teams suffer when they cannot see how they are doing. In a small team in a co-located setting, a lot of progress visibility is ambient. You hear conversations, you see what is on the board, you pick up the general mood of the room. None of that travels across larger teams, or teams that operate across multiple time zones.
Making progress explicit and visible, through shared tracking, clear metrics, regular updates on how the work maps to the outcomes the team has committed to, keeps people oriented and energised. It also makes it harder for silos to form quietly, since it becomes obvious when one part of the team is pulling in a different direction.
Resisting the Drift Toward Silos
In distributed teams, people can gradually retreat to the familiar edges of their own domain. Anything outside those boundaries quietly becomes someone else's problem. This is not usually a deliberate choice. It is the path of least resistance when the team is not actively working against it.
A truly empowered team collectively owns the outcome. Not everyone needs to do the same work, but everyone should be pulling toward the same destination and willing to step in where needed, regardless of whose territory it technically falls within. Creating rituals, retrospectives, shared reading, regular conversations about how the team as a whole is doing, builds the connective tissue that resists that drift.