Pillars Reference¶

01.030.034 v20260810.002

Purpose and Authority¶

This page is a derivative operational reference for applying the six Value Realization Pillars. It may add prompts, examples, and working guidance, but it does not redefine the Pillars. The canonical source is 01.014 and its six independent Pillar pages.

Quick Reference¶

Pillar	Use it to examine	Avoid conflating it with
Players	persons, Positions, Personas, expectations, competencies, authority, capacity, participation, and performance evidence	organizations, personality profiles, or attendance
Partners	organizational counterparties, exchanges, obligations, incentives, dependencies, risk, and value capture	individual stakeholders or every collaborating group
Platforms	shared, reusable, extensible foundations and their lifecycle economics and dependencies	every technology, feature, or single-purpose Deliverable
Products	coherent propositions made available to Consumers and the Effects arising from use	Projects, outputs, Platforms, or commercial packaging alone
Practices	repeatable disciplines, methods, Patterns, policies, processes, procedures, protocols, and controls	isolated activities, competencies, or maturity scores
Projects	governed work objects for change, Investment, delivery, transition, and realization	routine task lists, Deliverables, or realized value itself

Classification Decision Guide¶

State the realization boundary, decision context, time horizon, and unit of analysis.
Ask what function the subject performs in that context.
Identify all materially relevant Pillars before selecting a primary Pillar.
Assign a primary Pillar only when it improves governance or analysis.
Record contributing, affected, evidence-producing, and excluded Pillars.
Preserve one record for the object and model cross-Pillar relationships explicitly.
Reconsider the analysis whenever the boundary or function changes.

Pillar Assessment Prompts¶

Players¶

Who is accountable for realized value, and do they possess sufficient authority?
Which competencies, capacity, incentives, relationships, decisions, and adoption conditions matter?
What behavioral, contribution, decision, and outcome evidence is available?

Partners¶

Which counterparties contribute, receive, constrain, govern, or capture value?
Where do contracts, incentives, actual behavior, and dependencies diverge?
Which commitments, concentration, rights, switching costs, or exit conditions matter?

Platforms¶

What foundation is shared and reused across meaningful contexts?
Does it reduce or increase lifecycle effort, delay, duplication, burden, and risk?
What integration, identity, data, control, portability, continuity, or concentration dependencies apply?

Products¶

What coherent proposition is made available, to whom, and for what Effect?
What distinguishes it from a Deliverable, Platform, Offering, Practice, or Project output?
What demonstrates adoption, sustained use, Consumer Effect, and realized value?

Practices¶

Which repeatable means are necessary to realize and sustain value?
Where is performance improvised or dependent on tacit knowledge and heroics?
Does the Practice reduce variation and leakage without disproportionate friction?

Projects¶

What value is the work intended to realize, for whom, and relative to what counterfactual?
What evidence distinguishes activity, progress, delivery, adoption, Effect, and realization?
Who remains accountable after delivery, and what would cause the work to stop or change?

Evidence Record¶

For each material Pillar-related claim, record:

the claim and intended Effect;
realization scope, boundary, and time period;
primary and evidence-producing Pillars;
evidence source, owner, timing, quality, and confidence;
accountable validator;
assumptions and cross-Pillar dependencies;
baseline and counterfactual;
attribution basis;
persistence or sustainability conditions; and
exclusions and limitations.

Pillar scores, checklists, and maturity profiles are diagnostic. They are not automatically financial valuations, performance measures, or evidence of realized value.

Cross-Pillar Interaction Matrix¶

Pairing	Principal relationship
Players and Partners	Individuals enact organizational relationships, while personal participation remains distinct from organizational authority, obligations, incentives, and capture.
Players and Platforms	Access, competency, usability, adoption, workload, decision rights, support, and trust shape effective Platform use.
Players and Products	Players design, govern, provide, support, consume, and experience Products; availability does not establish adoption.
Players and Practices	Competencies support repeatable performance; Practices reduce dependency on particular individuals.
Players and Projects	Governed work requires explicit authority, accountability, contribution, consumption, and post-delivery responsibility.
Partners and Platforms	Counterparties may supply, operate, regulate, integrate, and depend on Platforms, creating commercial and continuity implications.
Partners and Products	Counterparties may contribute to, distribute, buy, regulate, support, or capture value from Products.
Partners and Practices	Procurement, assurance, service management, and relationship governance shape value exchange.
Partners and Projects	Work may establish or change relationships, while organizational obligations and Project responsibilities remain distinct.
Platforms and Products	Platforms enable reusable foundations; Products present coherent propositions. Measure reuse benefit and dependency cost.
Platforms and Practices	Practices govern Platform operation and change; automation may alter Practice performance.
Platforms and Projects	Projects create or change Platforms; Platforms constrain Project speed, architecture, risk, and cost.
Products and Practices	Practices create, provide, operate, support, improve, and retire Products.
Products and Projects	Projects create or change Products, but delivery does not prove adoption or Product value.
Practices and Projects	Practices provide repeatable means; Projects provide governed contexts in which effectiveness can be observed.

Worked Example¶

For an organization introducing an AI assistant into finance operations:

Players: Consumers, process owners, data stewards, security governors, builders, support personnel, and accountable executives.
Partners: model providers, integrators, external data providers, auditors, and regulators acting as organizational counterparties.
Platforms: identity, cloud, data, integration, monitoring, collaboration, and AI foundations reused across workloads.
Products: the assistant and its coherent service proposition.
Practices: financial control, AI governance, model evaluation, change, support, incident, and value-measurement methods.
Projects: the governed work through which the assistant and associated change are selected, funded, delivered, transitioned, and evaluated.

The example is intentionally cross-Pillar. Its usefulness lies in exposing realization conditions and evidence dependencies rather than forcing the initiative into one category.

Applied Metadata Guidance¶

pillar_relationships:
  primary: "Platforms"
  contributing:
    - "Players"
    - "Partners"
    - "Practices"
  affected:
    - "Products"
    - "Projects"
  evidence_producing:
    - "Platforms"
    - "Players"
  excluded: []

The fields describe the item in its applied context. They do not replace canonical definitions or manufacture a Pillar score.

Authority Safeguard¶

This reference may not create a seventh Pillar, redefine a Pillar, treat Pillars as lifecycle stages, encode organization-specific doctrine as portable Framework doctrine, or equate classification and completeness with realized value.