Value Ownership Without Hierarchy: The Æilus Role and Process Model

Full text

1 Introduction

Most organisations can name the owner of every department, budget and process. Few can name the owner of the value that moves through them. This paper presents the role and process model of the Æilus methodology v2.0 as a way to make responsibility for value explicit without adding a layer of command, and examines its operating cycle, risks and open questions.

This is the closing paper of the series "Æilus for Business". Core terms are defined in the first paper of the series, and practices and domains are described in the sixth. Here the focus is on who owns what, which recurring processes keep ownership alive, and which artifacts make it verifiable.

Whose value is measured. The unit of analysis throughout is one value system as defined in Value Management Theory (VMT): a product organisation together with the actors that exchange value with it. Its actors are the external recipients of its outputs (customers and users), the internal transformers (teams, services and functions that consume value and produce new value), the employees whose participation conditions must hold, and the external suppliers of inflows. The boundary is set explicitly in the system-level Value System Schema (VSS). Realized value is always the interpretation of the receiving actor: the customer for external flows, the downstream transformer for internal flows. Value and anti-value count only when observable as elements in flows, for example a delivered capability, an incident, a rework request or a delay. "The value of the company" in general has no meaning outside a defined system (A1, T1) and changes when the boundary changes (T15).

The formal apparatus of VMT, including the Æ value currency, is not re-derived here. It is given in Bolshakov (2026a). The paper relies mainly on the following axioms and theorems of VMT: A1 (context), A3 (representability by flows), A4 (asymmetry of plan and fact), A5 (independence of anti-value), A7 (transformation), A8 (participation), A9 (sustainability), A13 (partial commensurability); and T4 (historical accumulation of resistance), T5 (local optimisation), T7 (violated participation), T8 (loss of transformation roles), T9 (hidden flows), T13 (no universal optimality criterion), T16 (scaling through interpretation) and T17 (interpretational distortion).

2 The problem: everyone owns a process, nobody owns the flow

A functional hierarchy assigns responsibility by specialisation. Development owns development, operations owns operations, support owns support, each with a manager, a budget and local metrics. This suits building expertise and allocating resources. It does not answer whether value reaches the recipient.

By A3, every redistribution of value in the system can be represented as a set of flows. Flows that matter to the customer almost always cross several functional boundaries. A capability is specified in one unit, built in another, deployed in a third and supported in a fourth. Each unit can show that its own process works, while the flow loses value at every handoff: requirements are reinterpreted, work waits in queues and support absorbs anti-value created elsewhere.

Hypothetical illustration. Consider a development team that measures itself by features completed and an operations team that measures itself by stability. The development team ships a feature on schedule. The operations team delays deployment because the change carries an unreviewed risk. Both managers acted correctly within their mandate. The customer has received nothing, and no one is accountable for the space between the two teams.

VMT names several mechanisms behind this pattern. Local optimisation does not guarantee global improvement (T5). Planned value, the sender's interpretation, structurally diverges from realized value, the receiver's interpretation (A4, T3), and a hierarchy that reports planned output from each unit cannot see the gap. Anti-value is not the absence of value but an independent category (A5), so a unit that produces its planned output can at the same time generate anti-value that no one counts. Resistance accumulates historically (T4): handoff problems that are not owned do not disappear, they become the normal way of working. When the formal structure does not explain why the system still functions, latent flows and informal workarounds carry value outside any responsibility (T9).

The diagnosis is familiar: optimising a non-bottleneck does not improve system output (Goldratt, 1984), and value is best understood along the stream that delivers it (Womack and Jones, 1996). The contribution of Æilus is a role and process model that assigns explicit owners to value production, to flows between producers and to system sustainability, while leaving the structure of authority in place.

3 The principles that bear on ownership

Æilus v2.0 rests on ten principles, P1 to P10, published on the methodology principles page. They are framed as methodological constraints rather than recommendations. Six of them bear directly on ownership.

• P2. Alignment of value interpretations. Planned, realized and retrospective interpretations must be regularly compared and updated, and alignment is admissible only when confirmed by observable consequences of realization. Someone has to own this comparison, otherwise it does not happen.
• P4. Sustainability and participation conditions. Participation conditions, risks and dependencies on external flows must be continuously analysed. This is a system-level responsibility that no single transformer can hold.
• P6. Reduction of flow resistance. Interventions must reduce resistance rather than shift it. Shifting is precisely what happens when each unit optimises its own boundary.
• P8. System-level priority of practices. Practice selection must favour the capability of the transformer and of the system as a whole over local optimisation of process fragments.
• P9. Justified growth of planned value. Growth of planned value is mandatory only when demand is confirmed, inflow is sufficient, deliverability is confirmed, and participation and sustainability are not violated. Growth decisions must state the aggregation assumptions used, because value types are often only partially commensurable (A13).
• P10. Integrity of value interpretations. Interpretations must be formed in good faith and remain verifiable; systematic inflation of planned value or deflation of realized value is a methodological violation. Disagreement is admissible, distortion is not.

P1 (observability) underlies all of these and is implemented through artifacts (Section 6). Together the six principles imply a division of labour: one owner for producing value, another for keeping the system viable, and, when needed, owners for the spaces between producers and for shared constraints.

4 The role model

4.1 Roles are functional, not hierarchical

Æilus defines roles by the function they perform in the value system, not by position in an organisational chart. The same person may hold several roles, several people may share one role, and roles may change as the system evolves. The methodology states the test plainly: what matters is not who holds a role but which responsibility is covered. In VMT a transformer is likewise a role, not an entity (A7). By T8, a system loses sustainability when it can no longer perform a transformation role, and role redundancy increases sustainability; a responsibility that can be shared or reassigned is a structural expression of T8.

4.2 The six roles

The model distinguishes two core roles that are always present, three scaling roles introduced only when complexity requires them, and one support role. The table summarises the roles in the wording of the methodology.

4.3 The core pair: VTO and VSO

The VTO gives every transformer an explicit subject of responsibility for realized value, for the anti-value it produces as a by-product, and for its ability to keep participating without degradation. Without such an owner, the methodology observes, a transformer tends to accumulate anti-value, inflate planned value and erode trust at its boundaries. Notably, the VTO is not obliged to keep increasing planned value: the obligation is to increase realized value, reduce anti-value and resistance, and grow planned value only when P9 is satisfied. This removes a common incentive to over-promise.

The VSO exists so that the system does not collapse through local optimisation of individual transformers (T5), keeps interpretations coherent across actors, and does not lose actors through unnoticed violations of participation conditions (A8, T7). The VSO also owns the value aggregation policy, which states how value of different types is compared and traded off when it is only partially commensurable (A13). Since there is no universal criterion of optimality (T13), this policy is a declared choice, not a discovered truth, and its ownership must be visible.

The VTO and VSO split mirrors the VMT distinction between transformation (A7) and sustainability (A9). The "not responsible for" lists matter as much as the scopes.

4.4 Scaling roles and their admission criteria

Scaling roles are not part of a default organisation chart. The Flow Owner, for instance, is justified only when delivery requires a sequence of connected flows across several transformers, resistance is localised between transformers rather than inside them, planned and realized interpretations diverge systematically, the flow is critical for sustainability, or delivery is unstable. The Flow Owner restores realizability by reducing resistance in the space between transformers, the space that the hierarchy of Section 2 leaves unowned. Flow and Domain Owners share responsibility for preventing interpretation drift, not by enforcing consensus but by keeping interpretations verifiable through consequences. The Practice Owner keeps a shared practice from degrading into ritual; the Domain Owner protects the system from non-admissible anti-value. In the words of the Æilus evolution notes, the model scales by adding roles, not processes, replacing the v1.x notion of a single value stream owner.

5 Processes, events and the operating cycle

5.1 The operating cycle

Æilus runs as a continuous cycle with four layers: Observe (visibility of value elements, anti-value and accumulation), Align (synchronise interpretations between senders and recipients), Intervene (adjust practices to reduce resistance and improve realized value) and Stabilize (keep participation conditions and domain policies satisfied). The cycle has no optimised end state; it aims at a system that is more reproducible and less fragile.

5.2 Mandatory process groups and their owners

The published methodology defines eight mandatory process groups, each tied to principles (the archived 2.0 document lists the first seven; Interpretation Validation was added later). Processes are owned, not "performed by everyone". The owner column is derived from the published role ownership of processes, assuming that a loop falls back to the VSO or VTO where a scaling role is not introduced. The cycle column is this paper's own mapping.

Process group 8 detects cases where the narrative about planned value changes without a matching change in realized or retrospective value. It is the operational form of T16 and T17: scaling through unconfirmed interpretation is structurally unstable and accumulates anti-value.

5.3 The minimum set of events

Æilus prescribes no calendar but recommends a minimal set of events, more frequent in fast-changing systems.

• Value System Review: boundaries, critical actors, key flows, dependencies (VSO).
• Interpretation Alignment Session: planned, realized and retrospective interpretations on a critical flow (facilitated by the Æilus Master).
• Flow Resistance Review: bottlenecks, undelivered value, resistance accumulation (Flow Owner, or VSO).
• Practice Review Board: adopt, adapt or retire practices by observed effects (VTOs, Practice and Domain Owners).
• Value Retrospective: retrospective value as input to future interpretations (facilitated by the Æilus Master).

Good operation is described by three observable outcomes: interpretations stay synchronised, resistance decreases over time, and participation conditions hold under change. These concern the direction of signals, not a target level, consistent with T3: a zero gap between plan and fact is an unstable special case.

6 Artifacts and reports per role

Æilus treats artifacts as decision instruments under one strict rule: every artifact must have an owner, an update loop and a decision purpose; otherwise it creates anti-value through maintenance cost and false confidence. The methodology lists nine artifact groups and a minimum report set but does not map them to roles. The table proposes such a mapping, derived from the role scopes; it is this paper's allocation.

Two points follow. First, the VSS appears at two levels, transformer and system, and the two owners must keep them consistent; the system-level schema is where the boundary of the value system, and therefore the answer to "whose value", is recorded. Second, reports in Æilus are value system diagnostics showing trends, not performance reporting. If reports are expressed in Æ units, the formalization in Bolshakov (2026a) applies; the role model itself does not depend on a particular unit.

7 Coexistence with hierarchies and agile frameworks

The Æilus role model does not replace line management; the methodology states that it imposes no specific organisational forms. Its roles define responsibility for value, not authority over people. Hiring, budgeting and legal accountability stay where they are, and Æilus roles are layered onto existing positions. A head of a department may also hold the VTO role for the transformer that department forms. An executive accountable for a product line may hold the VSO role for the corresponding value system. A senior engineer may act as Domain Owner for security or availability.

Agile frameworks raise a similar question. The Scrum Guide (Schwaber and Sutherland, 2020), for example, defines accountabilities within a team, including a Product Owner accountable for maximising the value of the product resulting from the team's work. Such a person can hold a VTO role. A team framework organises work inside a transformer and is, in Æilus terms, a practice subject to validation and retirement; Æilus asks how value moves between transformers and whether the system remains viable.

This paper makes no claim that the Æilus model outperforms other operating models: no comparative data exist, and by T13 there is no universal optimality criterion. The claim is structural: the model gives explicit owners to flows between units, interpretation gaps and system-level participation conditions, which often have none.

8 Adoption path

The published training programme follows the three layers of Æilus v2.0 (VMT, the methodology, Æilus Design Practice) and is organised by role paths, which suggests an adoption sequence.

1. Shared language first. A foundation course covers planned, realized and retrospective value, anti-value, resistance and participation conditions.
2. Core roles and a first VSS. Name a VSO for one bounded value system and VTOs for its main transformers. Record the boundary in a system-level VSS. Start the Value Element Registry with the few elements that matter most.
3. A support role early. An Æilus Master keeps events from becoming ritual while habits form.
4. Minimal events. Begin with a Value System Review and an Interpretation Alignment Session on one critical flow.
5. Scaling roles by evidence. Introduce a Flow Owner, Practice Owner or Domain Owner only when the admission criteria of section 4.4 are observed.
6. Role tracks and applied labs. Planned on the training page; enrolment is not yet published.

9 Risks and safeguards

A role model for value can itself become a source of anti-value. Three risks stand out.

Role inflation. Scaling roles may be filled by default everywhere, adding coordination and diluting accountability. Safeguard: explicit admission criteria. A reasonable additional rule is that a scaling role is reviewed in the Value System Review and removed when the condition that justified it no longer holds.

Bureaucracy. Nine artifact groups and seven reports can turn into a documentation programme. Safeguard: the artifact discipline rule. An artifact without an owner, an update loop and a decision purpose is, by the methodology's own definition, anti-value. The cost of maintaining an artifact is itself consumed value and belongs in the Transformer Efficiency Report (P7).

Value theatre. The greatest risk is that roles, events and reports become a performance of value management while the actual flows are unchanged. This is the classical problem that a measure turned into a target loses its informative power (Goodhart, 1975). Safeguards: P10 makes inflation and deflation of interpretations a methodological violation; realized value is validated by the receiving actor, not by the sender; process group 8 checks that interpretation changes are confirmed by consequences (T16, T17); and the Æilus Master is explicitly responsible for detecting cargo-cult adoption. None of these safeguards is automatic. Each depends on a role holder willing to report an uncomfortable gap.

A fourth risk is conflict with positional authority. The role model has no enforcement power of its own; if a sustainability signal is overridden, participation conditions of affected actors, including employees, may be violated unrecorded (A8, T7). Recording such overrides in the System Sustainability Signal Report is the minimum safeguard.

10 Limitations and research agenda

This is a methodological analysis with no measured outcomes, because the sources contain none; claims about effects are hypotheses. The mapping of artifacts to roles (section 6) and of process groups to cycle layers (section 5.2) are proposals of this paper, not parts of the published methodology. The admission criteria for scaling roles are qualitative; the methodology does not state thresholds. The model assumes that role holders can observe realized value at the receiving actor, which may be difficult when recipients are external and diffuse. Finally, the model's effect depends on its interaction with existing authority structures, which the methodology deliberately leaves open.

A research agenda for ÆVRI follows from these gaps:

• Longitudinal case studies that record, before and after introducing VTO and VSO roles, the observable signals the methodology itself names: the gap between planned and realized value, recorded resistance, and violations of participation conditions.
• Operational criteria for introducing and retiring scaling roles, tested against resistance registers.
• Comparative studies of how Æilus roles combine with team-level agile frameworks and with line management, including cases where the combination fails.
• Indicators for value theatre: patterns in interpretation change logs that signal distortion before it shows up as anti-value.

11 Conclusion

Functional hierarchies are good at owning processes and poor at owning flows. Value, which by VMT exists only in flows and is realized only at the receiving actor, therefore often has no owner. The Æilus role model addresses this by separating ownership of value production (VTO) from ownership of system sustainability (VSO), and by adding owners for flows, shared practices and domains only when the system shows a need. A support role, the Æilus Master, protects the method from becoming ritual.

The model does not compete with line management or agile frameworks; it covers responsibilities they usually leave implicit. Whether it improves realized value, reduces resistance and preserves participation conditions in real organisations is an open empirical question. The model's own instruments, gap reports, resistance registers and sustainability signals, are the means to answer it. With it, the series "Æilus for Business" closes on the ownership that holds the earlier topics together.

References

• Bolshakov, V. Value, Anti-Value and Value Flows: A Working Vocabulary for Practitioners. ÆVRI, 2026.
• Bolshakov, V. Value Management Theory and Employee-Centric Competitive Advantage: A System-Level Perspective. ÆVRI, 2026a.
• Bolshakov, V. Æilus Methodology v2.0: Principles, Roles, Processes and Events, Artifacts and Reports. aeilus.tech/methodology/, 2026b.
• Bolshakov, V. Evolution of Æilus. aeilus.tech/methodology/versions/, 2026c.
• Bolshakov, V. Æilus Training: Role-Based Learning Paths. aeilus.tech/training/, 2026d.
• Goldratt, E. M. The Goal. 1984.
• Goodhart, C. A. E. Problems of Monetary Management: The U.K. Experience. 1975.
• Schwaber, K., Sutherland, J. The Scrum Guide. 2020.
• Womack, J. P., Jones, D. T. Lean Thinking. 1996.