Value Realization™ Domains¶

Value Realization™ Domains provide a canonical completeness model for how value originates, how it is governed, and where it exists and is realized. Domains are intended to be used as both:

A philosophical lens. A way to think about the origination and structure of value.
A coverage lens. A way to ensure value realization work touches the full system of actors, means, and work objects required to convert potential value into verified outcomes.

Domains are not stages and are not sequential.

Canonical Domains¶

Players¶

Definition. The role types and player abstractions that participate in and contribute to value realization, including contributors, consumers, leaders, governors, specialists, and other participants. Players are understood by their positions, expectations, competencies, relationships, and performance evidence, not merely by organizational chart position or individual identity.

Guidance.

Preferred term is Players, not People, Personnel, Resources, or Human Capital.
Players may be internal or external.
Players play Positions. A Position defines the role-like place through which a Player participates in value realization.
Personas are used to understand typical perspectives, priorities, principles, concerns, and decision patterns associated with common roles, titles, or positions. Personas are not substitutes for named Players or evidence of performance.
Player-level analysis must distinguish among characteristics, competencies, expectations, and performance. These are related, but not equivalent.

Performance and Expectations. Player performance is understood through the expectations associated with a Position, Project, Practice, Product, Platform, Partner, or other value realization context. Expectations should be expressed in RACI-like terms extended for Value Realization™ use:

Accountable. Owns the outcome and is answerable for whether expected value is realized.
Responsible. Performs or leads the work required to produce or enable the outcome.
Consulted. Provides input, expertise, review, challenge, or interpretation before or during execution.
Informed. Receives relevant information to support awareness, alignment, downstream action, or governance.
Contributor. Contributes effort, expertise, data, assets, relationships, judgment, or decision support to the realization of value.
Consumer. Receives, benefits from, uses, or is affected by the realized value.

Sponsor should not be treated as a separate expectation type. Sponsorship is usually expressed through Accountability or Responsibility depending on level and context. An Executive Sponsor is typically Accountable for the outcome, while a project, program, or portfolio sponsor may be Accountable or Responsible depending on the governance model.

Standard Relationships. Player analysis should identify reusable relationship patterns among Players, Positions, Personas, and other value realization actors. Standard Relationships describe typical value exchanges, decision rights, interaction patterns, friction points, and governance considerations. They are reusable relationship patterns, not interpersonal assumptions about specific individuals.

Competencies. A Competency is an observable proficiency possessed or developed by a Player. Competencies are Player-level means to create value, expressed as developable and assessable proficiencies. Examples include Financial Analysis, Negotiation, Cloud Cost Analysis, Change Leadership, Stakeholder Communication, and Governance Design.

Competency Profiles. A Competency Profile is the composition of relevant competencies associated with a Player, Position, Persona, team, or assignment, including the maturity level of each competency. Competency Profiles support development planning, role design, succession preparation, and capability coverage analysis.

Competency Development Plans. A Competency Development Plan is a prescribed pathway for progressing one or more targeted competencies from a current maturity level to a desired maturity level. It should specify the target competency, current maturity, desired maturity, progression actions, evidence of progression, expected value contribution, and review cadence.

Competency Maturity. Competencies may use the same maturity labels as capability maturity where useful: Improvising, Normalizing, Rationalizing, Optimizing, and Harmonizing. A Competency Maturity Progression describes the maturity of a Player-level proficiency. A Capability Maturity Progression describes the maturity of an organizational ability. They share maturity language, but they remain distinct constructs.

Core principles.

Personality Does Not Equal Performance. Individual characteristics may influence how a Player approaches work, learns, collaborates, or responds to pressure, but they do not constitute performance evidence. Personality models may describe tendencies. Competency models describe observable proficiency. Performance measures describe realized outcomes.
Competency Independence Principle. Competencies shall be modeled independently of the personalities, preferences, motivations, styles, values, or assessment profiles of the Players who currently possess or express them. This prevents competency modeling from becoming a disguised personality framework.
Competency Does Not Equal Capability. A Competency is a Player-level observable proficiency. A Capability is an organizational ability to reliably produce an outcome. Both are means to create value, but they operate at different levels of abstraction and should not be collapsed into one another.

Partners¶

Definition. External organizations and counterparties that contribute to, constrain, enable, or capture value, including vendors, integrators, alliances, channels, and customers.

Platforms¶

Definition. The physical, digital, informational, and conceptual foundations upon which value is realized. Platforms include systems and assets, but also the data and conceptual substrates that enable outcomes.

Products¶

Definition. The discrete commercializable artifacts that directly provide value, including intellectual assets, methods, templates, tools, and deliverables. Products are the “what” being delivered or made available.

Practices¶

Definition. Repeatable behaviors, disciplines, policies, procedures, and protocols that govern how value is pursued, verified, and sustained. Practices are the “how” at an organizational capability level.

Common practice disciplines. Common management disciplines may be treated as Practice-domain constructs when they describe repeatable methods, governance practices, management disciplines, operating behaviors, standards, or protocols used to pursue, verify, govern, or sustain value.

Common practice disciplines include, without limitation:

Change Management;
Benefits Realization Management;
Technology Business Management;
IT Financial Management;
IT Business Management;
IT Investment Management;
IT Service Management;
Governance, Risk, and Compliance Management;
Vendor Management;
Sourcing Management;
Capability Management;
Portfolio Governance, where the emphasis is on repeatable governance practices rather than the Project-domain object itself.

These common practices may involve Players, Partners, Platforms, Products, and Projects, but their primary domain classification is Practices when the subject is the repeatable management discipline or operating method.

Value Realization interpretation. The Value Realization Framework may recognize common practices without adopting their external doctrine wholesale. A Value Realization-based perspective should normally use a "yes, and" posture:

yes, the common practice contributes useful discipline, language, artifacts, and professional structure;
and, Value Realization extends, constrains, or reinterprets the practice by requiring clearer linkage to value logic, economic effects, evidence, validation, and realized outcomes.

Guidance.

Do not allow an external practice model to redefine Value Realization doctrine unless expressly adopted through canon governance.
Do not treat practice maturity as realized value by itself.
Do not treat practice adoption as sufficient value evidence unless the applicable Valuation Approach supports that treatment.
Do not collapse practice disciplines into Products or Platforms merely because they may use tools, templates, or systems.
Do not collapse practice disciplines into Players merely because the practice requires competencies or role participation.

Projects¶

Definition. Discrete initiatives, assignments, and work objects through which value realization is pursued. Projects are the units of work that progress from identification through verified realization.

Project, program, and portfolio disciplines. Project Management, Program Management, and Portfolio Management may be treated in two different ways depending on the subject of analysis:

as Projects-domain constructs when the subject is the work object, aggregation structure, delivery object, investment vehicle, initiative, program, portfolio, or accountable unit through which value realization is pursued;
as Practices-domain constructs when the subject is the repeatable management discipline, methodology, governance practice, toolset, professional standard, or operating protocol used to manage those objects.

PMI-sourced thinking. PMI-sourced thinking on Project Management, Program Management, Portfolio Management, and Organizational Project Management should be treated as a model-specific perspective, not as governing Value Realization doctrine.

A Value Realization-based perspective should normally recognize the usefulness of PMI constructs and then extend them by asking:

What value is the project, program, or portfolio intended to realize?
Which Effects are intended, protected, or contributed to?
What Value Statement or value hypothesis governs the work?
What evidence distinguishes progress, completion, delivery, benefit, and realized value?
What realization conditions must persist after delivery?
How are investments, baselines, assumptions, risks, dependencies, and counterfactuals governed?

Guidance.

Preferred term is Projects, not Programs, for discrete value realization work objects until a canon decision changes this.
Programs may exist operationally, but the framework currently treats Projects as the atomic unit for accountable value progress.
Do not treat project completion as value realization.
Do not treat portfolio prioritization as economic optimization unless value logic, investment logic, and evidence are governed.
Do not import PMI terms into controlled vocabulary unless expressly adopted through taxonomy governance.

Competency and Capability Distinction¶

Competency and capability are both means to create value, but they are expressed at different levels.

Competency. A Competency is a Player-level observable proficiency. It describes what a Player can do, how maturely they can do it, and where development may increase contribution. A competency can be matured through training, experience, coaching, practice, exposure, feedback, and deliberate progression.

Capability. A Capability is an organizational-level ability to reliably produce an outcome. It may depend on Players, competencies, processes, platforms, patterns, data, governance, decision rights, and operating practices. A mature capability should not depend on one individual Player, even where highly mature Players contribute materially to its performance.

Examples.

Financial Analysis competency. A Player's proficiency in interpreting financial data, constructing financial models, explaining variance, and supporting economic decisions.
Financial Management capability. An organization's ability to plan, govern, control, and optimize financial performance.
Negotiation competency. A Player's proficiency in structuring agreements, resolving competing interests, and improving exchange outcomes.
Procurement Management capability. An organization's ability to source, contract, acquire, manage, and govern goods and services.
Cloud Cost Analysis competency. A Player's proficiency in interpreting cloud spend, consumption, commitment, and capacity data.
Cloud Financial Management capability. An organization's ability to govern and optimize cloud-related cost, consumption, commitment, capacity, risk, and value.
Change Leadership competency. A Player's proficiency in guiding people through adoption, transition, resistance, and sustained behavioral change.
Workforce Planning capability. An organization's ability to anticipate, model, supply, develop, and govern the Players and competencies required to realize value.

Usage¶

Framework content. Use Domains to structure doctrine and the Body of Knowledge.
Applied patterns. Tag patterns and practices by Domain to enforce completeness.
Implementation-specific materials. Where an implementation uses broader operating terms such as Programs, the relationship to the canonical Domain model should be stated or governed through a canon decision.
Common-practice materials. Where an implementation references common practices such as Change Management, Benefits Realization Management, Technology Business Management, IT Financial Management, IT Business Management, Project Management, Program Management, or Portfolio Management, classify the material by whether it is primarily a Practice-domain discipline or a Projects-domain work-object concept.
Assessment content. Specific personality, motivation, values, emotional intelligence, work-style, or facilitation assessment models should not be embedded in the Value Realization Framework. Those models may be addressed in organization-specific applied practices or position papers, provided the canonical Players Domain remains assessment-neutral.