Alignment Needs Bounded Ownership
When organisations talk about alignment, the conversation often moves towards shared goals, shared terminology and common ways of working.
That sounds reasonable. It can also lead to a harmful conclusion: if people are misaligned, everyone must use the same frameworks, models and follow decisions from a central place more closely.
Most organisations are too varied for that. A company-wide processes, models or outcomes will either remain vague or favour one part of the business. Central decisions can provide direction, but they cannot contain the local knowledge needed for every situation. Teams still need room to interpret that direction and act on what they know.
But on the otherhand local autonomy becomes risky when its boundaries are unclear. A team can optimise an outcome it cannot meaningfully influence or make a decision whose consequences fall on another part of the organisation.
Alignment needs ownership with clear, visible edges.
Shared direction, different models
Domain-driven design gives us a useful way to think about this. A bounded context defines where a particular language and model are valid. The word Customer may mean the person using a mobile application in one context, a billing account in another and a member of a loyalty programme in a third.
None of these models needs to become the organisation-wide truth. Each exists because people are making different decisions.
The same idea can be applied beyond software architecture. An organisation contains many places where decisions are made: executive leadership, business areas, product teams, platform teams, security, operations and finance. Each works with its own view of the organisation. Each also has different authority.
I think of the organisational version as bounded ownership.
Bounded ownership defines an area within which a group can interpret intent and act without waiting for central approval. It includes:
the language and models that are valid inside it;
the outcomes it can reasonably influence;
the decisions it has authority to make;
the knowledge for which it is the owner;
the evidence it can observe;
the matters it must negotiate with another owner.
An area of ownership may correspond to a team, but it does not have to. A team can have several areas of ownership, and one area may involve people from several organisational units. The useful boundary follows responsibility and authority, not the boxes in an organisation chart.
Local decisions now have a home, and their limits are easier to see.
Responsibility without authority produces waiting
Teams are often told to own outcomes while the decisions that affect those outcomes are made elsewhere and without the teams influence.
Imagine a checkout team that is expected to reduce purchase abandonment. It can change the user interface, adjust the order of steps and run experiments. It may not be allowed to change payment authentication rules, pricing, campaign promises or the range of available delivery options.
Those limits are reasonable. Payments, marketing and fulfilment have knowledge and obligations that the checkout team does not.
The trouble starts when the organisation talks as if the team owns the entire outcome. The team becomes accountable for something it can only partly influence. It either waits for every dependency, or it begins making assumptions about decisions owned elsewhere.
Bounded ownership gives a more honest account of responsibility. The checkout team can own the decisions within its influence and show where progress depends on another owner. If payment authentication appears to cause abandonment, the team can bring evidence and a proposal to the payment owner. It cannot quietly weaken authentication because its local metric would improve.
The team also needs access to evidence from the part of the customer journey it is expected to improve. Without that, it can make changes but cannot judge them responsibly. Authority, influence and observable evidence should describe roughly the same area. Large gaps between them cannot create real accountability.
Authority also needs to be real enough for the team to act. If every local choice still requires approval from a central group, the boundary describes responsibility without granting autonomy. Work slows down, and decisions move away from the people who have the most relevant knowledge.
Healthy alignment sits between two failures: central control over decisions that need local understanding, and local freedom without clear limits or obligations to the wider system.
Boundaries make autonomy safer
Local autonomy is sometimes presented as a cultural question: leaders should trust teams, and teams should take ownership. Trust matters, but it does not tell a team which decisions are actually theirs.
A clear ownership boundary makes autonomy more concrete.
Inside the boundary, people should be able to interpret intent, compare options and make choices without repeatedly asking for permission. They know which outcomes they are trying to influence and which constraints they must respect. They also own the consequences of those local choices.
At the boundary, the behaviour changes. A question that affects another owner becomes a negotiation rather than an internal decision.
Owners will still influence each other. A product team may need a new payment capability. Operations may need a product change to reduce support load. Security may need stricter controls that affect the customer experience.
The boundary makes the interaction visible. One group can explain its need, provide evidence and propose a change. The other owner decides how that request fits its own model, constraints and responsibilities.
Without that boundary, influence easily turns into accidental authority. The product team defines a security rule because it needs faster delivery. A platform team standardises a domain concept because several services use similar data. Executives choose implementation details because a strategy is not specific enough to guide local judgement.
Every choice may look efficient in isolation. Over time, nobody is quite sure who is allowed to change what.
Owners still need each other
Boundaries often raise a predictable concern. If every group owns its own language and decisions, will the organisation fragment into silos?
It can, if ownership becomes a reason to ignore everyone else.
Each area of ownership receives direction from the wider organisation and operates within shared constraints. Its choices should contribute to outcomes beyond its boundary, even though it cannot control those outcomes alone. It also has a responsibility to make relevant decisions and knowledge available to the other owners that depend on them.
These areas remain different because their work is different. Alignment comes from making those differences compatible enough for the organisation to act as a whole.
The same principle appears in contracts between software contexts. An ordering system does not need the customer system's complete internal model. It needs an agreed way to obtain the few facts required for ordering decisions. The contract protects both sides from having to share one model.
Organisational ownership boundaries need the same discipline. People need to know what comes from another owner, what they may decide locally and when a change requires negotiation. The boundary should be permeable, but crossing it should be deliberate.
AI needs a mandate, not only access
AI makes these questions harder to ignore because it can move across existing boundaries with very little friction.
An AI assistant may be able to read strategy documents, product metrics, architecture descriptions and source code. A coding agent may be able to edit several repositories. Access to all of that material can create the impression that the AI has one complete view of the organisation.
What it has is material produced within different areas of ownership, using different models and backed by different kinds of authority.
Giving AI more context helps it produce a more informed answer. It does not tell the AI which decisions it is entitled to make.
Within a clear area of ownership, AI can have useful agency. It can interpret the knowledge owned there, connect a local goal to the available evidence, develop options and support decisions. With suitable controls, it may also carry out decisions that fall clearly within that authority.
The boundary should limit that agency. Suppose an AI working with the checkout team concludes that changing payment authentication could reduce abandonment. It can explain the dependency, assemble the evidence and draft a proposal. It should identify Payments as the owner and ask for a decision there.
It should not interpret technical access, an ambiguous goal or silence from another team as permission to make the change.
I think of this as constrained agency. The constraint is broader than a list of tools or files the AI may access. It includes semantic and organisational authority:
which model it may treat as valid;
which sources it may interpret as authoritative;
which options it may act on;
which decisions require another owner;
where uncertainty must become a question.
These limits are useful for people as well. AI simply exposes how rarely organisations have made them explicit.
A boundary should sometimes stop the work
There is pressure to treat every interruption as inefficiency. A team raises a dependency, an architect asks for clarification or an AI agent stops before completing a change. It is tempting to remove the boundary so the work can continue.
Sometimes stopping is the correct result.
If nobody can identify who owns a decision, that is important information about the organisation. If two groups both believe they have authority, the conflict already exists. If a team has an outcome but no meaningful decisions within its control, its responsibility has been defined badly.
An AI assistant should make these gaps visible instead of smoothing them over. It can describe the missing authority, identify the affected owners and formulate the question that needs a decision. Completing the task by inventing one would only hide the alignment problem for a little longer.
Clear boundaries do not guarantee good decisions. A team can still optimise the wrong outcome or hold an outdated model. Boundaries do, however, keep one actor from silently deciding on behalf of another. They make local autonomy safer and give disagreements a place to surface.
The next question is how these areas of ownership communicate without collapsing their models into one. A decision made within one boundary often becomes knowledge that another owner needs. For that to support alignment, it must remain understandable beyond the place where it was created, while still carrying its ownership and limits with it.
