The Enterprise Change Office

The Organisation’s Governing Logic and Enterprise System

How deeper organisational principles shape the system through which capability is developed, strategy pursued and value created.

NB

You need a boundary, but “major” isn’t a satisfactory boundary.

I think your answer lies in the phrase “an organisation’s Enterprise System”. You need to establish that an Enterprise System is an enterprise-level analytical construct; not every local operational adjustment constitutes an adaptation of the Enterprise System.

That distinction should ultimately be developed on the Enterprise System page. Otherwise your HBS criticism can rebound against you: HBS has an undefined lower boundary; your definition could appear to have no lower boundary at all.

Introduction

The webpage A Definition Of Organisational Change provides a definition as:

“The adaptation of an organisation’s Enterprise System and, where necessary, its Governance Logic to support the achievement of its strategy and objectives.”

The definition highlights the Enterprise System and Governing Logic as key areas for organisational change. The Enterprise System includes Culture, Business Model, Value Chain, and Operating Model. Governing Logic refers to the underlying principles and assumptions guiding enterprise-level decisions.

Organisational change may involve adapting the Enterprise System while Governing Logic remains substantially intact or, where necessary, changing the Governing Logic itself. Understanding these constructs is essential to interpreting organisational change as defined on this website.

The Governing Logic

Organisations may change structures, processes, systems, and behaviours without altering the underlying principles and assumptions that guide key decisions. These may evolve over time and may not be consistent across the organisation. Examining Governing Logic allows for a deeper understanding of what is considered appropriate, desirable, or legitimate. The nine dimensions in Figure 1, examined in greater detail here, offer complementary perspectives for this analysis.

Governing Logic Dimension Description
Value Creation The prevailing conception of what constitutes value, for whom value should be created, and how different forms of value and competing stakeholder interests should be prioritised.
Identity & Legitimacy The collective conception of what kind of organisation this is, what it is entitled or expected to do, whose expectations matter, and what forms of action and organisation are regarded as appropriate and legitimate.Row 2, Content 1
Control & Authority The principles that determine where authority should reside, how decision rights should be distributed, how much autonomy should be permitted, and how organisational activity should be controlled.
Strategy The prevailing view of how strategic direction should be determined, who should shape it, how deliberately it can be formulated, and how the organisation should respond to learning and changing circumstances.
Incentive & Reinforcement The established beliefs about what behaviours, decisions and outcomes should be encouraged, rewarded or discouraged, and the mechanisms through which these expectations are reinforced.
Resource Allocation & Investment The principles through which financial, human and other scarce resources are allocated, investment priorities determined, and competing demands resolved.
Risk & Accountability The accepted view of what risks are appropriate, who may take them, where responsibility for decisions and outcomes resides, and how accountability should be exercised.
Information & Transparency The conventions governing who should have access to information, how openly it should flow across organisational boundaries, what should be disclosed, and how information should inform decision-making.
Time Horizon & Cadence The prevailing orientation towards the time horizons over which performance and value are considered, how quickly decisions and results are expected, and the rhythms through which the organisation plans, reviews and adapts.

Figure 1: The Dimensions Of Governing Logic

The nine dimensions are not hierarchical or independent checklist items. Instead, they form a system of mutually reinforcing principles and assumptions, each influencing and being influenced by the others. Their significance varies by organisational context.

Some dimensions, such as Identity & Legitimacy and Value Creation, may be more foundational, shaping the organisation’s self-understanding, stakeholders, and values. However, there is no fixed hierarchy, as other dimensions can reinforce or challenge these core beliefs.

Ideally, Governing Logic would be consciously aligned with the organisation’s purpose and strategy. In practice, it often develops over time through decisions, practices, leadership behaviours, and responses to change, with some assumptions becoming deeply embedded and rarely questioned.

The Enterprise System

The Enterprise System does not replace established concepts such as organisational design, architecture, or operating models. Instead, it serves as an analytical lens that integrates four distinct perspectives to examine organisational capability and change. Considering these together helps identify how changes in one area may affect others, while maintaining clear analytical distinctions.

The perspectives are:

Culture includes the shared assumptions, norms, and behaviours shaped by and interacting with Governing Logic. It influences how people interpret situations and act within the organisation, affecting how formal arrangements function and whether they reinforce or undermine changes in the Enterprise System.

The Culture Canvas, as presented in Figure 2, summarises the main facets through which an organisation’s culture can be systematically examined and assessed.

Figure 2: Culture Canvas

Culture influences the Business Model, Value Chain, and Operating Model by shaping how each operates in practice. It affects perceptions of value and stakeholders, interactions across the Value Chain, and the functioning of structures and processes in the Operating Model. These elements can also reinforce or alter the organisation’s culture.

Culture and Governing Logic overlap, as both involve deeply embedded organisational assumptions. The distinction here is primarily analytical focus:

  • Governing Logic concerns the principles and assumptions that shape enterprise-level choices about matters such as value creation, authority, strategy, resource allocation, risk and legitimacy.
  • Culture concerns the socially established assumptions, norms and patterns of behaviour through which people interpret situations and act in organisational life.

The two are closely connected. Governing Logic shapes Culture, while established cultural patterns can reinforce or challenge Governing Logic. Organisational culture is discussed in more detail here

The Business Model explains how the organisation creates, delivers, and captures value, tailored to its nature and purpose. The Business Model Canvas, as presented in Figure 3 and explained here, summarises the key elements needed to understand this process.

Figure 3: Business Model Canvas

The presented canvas is designed for private sector organisations and should be adapted for public and third sector contexts.

Michael Porter developed the Value Chain, which maps the connected activities that create and deliver value as described in the Business Model. It provides a cross-functional view, showing how activities combine to produce outcomes rather than focusing on individual processes or departments.

Figure 4 presents an adapted Value Chain, described in more detail here. The primary activities shown are generic and should be tailored to the specific organisation being assessed.

Figure 4: Value Chain

The Operating Model describes how the organisation organises and enables the activities identified in the Value Chain. The Operating Model Canvas in Figure 5 provides a structured view of the main organisational arrangements supporting these activities.

Figure 5: Operating Model Canvas

Some frameworks use Operating Model to include aspects of the Business Model and Value Chain. This website treats them separately, as each addresses different analytical questions: how value is created, through which activities, and how those activities are organised and enabled.

The Relationship Between The Governing Logic And The Enterprise System

Governing Logic is reflected in the Enterprise System. Assumptions about value creation shape the Business Model and Value Chain; assumptions about authority and accountability influence the Operating Model; and assumptions about behaviour, identity, and legitimacy are expressed and reinforced through Culture.

The relationship is reciprocal. The Enterprise System does not merely implement Governing Logic; experiences, behaviours, and outcomes within the system can reinforce or challenge existing assumptions. New practices may prompt reconsideration of previously unquestioned beliefs. Governing Logic and the Enterprise System are mutually influential but remain analytically distinct.

Summary

Governing Logic and the Enterprise System offer complementary perspectives on organisational capability. Governing Logic describes the deeper principles shaping enterprise-level choices, while the Enterprise System integrates Culture, Business Model, Value Chain, and Operating Model to examine capability. Together, they explain how an organisation pursues strategy and creates value through operational continuity.

The relationship between Governing Logic and the Enterprise System is reciprocal, not hierarchical. Governing Logic shapes the Enterprise System, while experiences and outcomes within the system can reinforce or alter Governing Logic. Neither is an organisational capability on its own; their interaction shapes the organisation’s capabilities. Figure 6 summarises these relationships.

Explore More

Understanding The Governing Logic

This website adopts a strategy-led framework that examines the relationships between strategy, the Enterprise System, Operational Continuity, Governance Logic, and the Two Orders of Organisational Change.

Mapping The Enterprise System

This website adopts a strategy-led framework that examines the relationships between strategy, the Enterprise System, Operational Continuity, Governance Logic, and the Two Orders of Organisational Change.
error: Content is protected !!

The Potential Weaknesses Of An Organisational Change Playbook

Some of the potential weaknesses of an Organisational Change Playbook and possible mitigations are addressed below.

Potential Weakness Mitigation
Bureaucracy and unnecessary work Lean processes, proportionate governance, and only the documentation necessary.
Rigidity and reduced agility Explicit tailoring provisions, alternative approaches and professional judgement within defined governance boundaries.
False confidence in competence Defined competence requirements, appropriate training, specialist support, assurance and escalation arrangements.
Outdated or ineffective guidance Accountable stewardship, regular review, feedback from practice and evidence-based improvement.
Fragmentation and duplication A coherent process architecture linking activities, decisions, responsibilities, methods and information.
Limited use in practice Integrate with normal management activities, provide accessible guidance, set leadership expectations, and offer practical support.
Disproportionate costs Assess organisational need, develop incrementally, and evaluate the value delivered.

Figure best viewed on tablet or above

These mitigations reduce risks but do not guarantee Playbook effectiveness. Its value depends on the quality of underlying practices, user competence, and leadership’s willingness to address deficiencies.

Does First-Order And Second-Order Change Still Apply?

First-Order and Second-Order Change were developed long before current descriptions of organisational environments such as VUCA (Volatility, Uncertainty, Complexity, Ambiguity) and BANI (Brittle, Anxious, Nonlinear, Incomprehensible). Organisations are now seen as continually adapting, rather than moving episodically between stable states. It is therefore reasonable to question whether a distinction from an earlier context remains useful.

The distinction remains relevant because First-Order Change does not necessarily mean simple, predictable, or incremental change. It can be extensive, continuous, complicated, complex, emergent, and highly uncertain. Organisations may repeatedly adapt structures, processes, technologies, and ways of working while their underlying organisational order remains intact.

VUCA and BANI may increase the frequency, interconnectedness, and unpredictability of adaptation. However, neither uncertainty nor complexity determines the order of change. An organisation can experiment, learn, and adapt continuously without fundamentally changing its organisational order.

Second-Order Change identifies a qualitatively different situation: the underlying organisational order itself becomes subject to reconsideration and potential change. Developments in markets, technology, regulation, societal expectations or other conditions may eventually challenge fundamental assumptions about how an organisation creates value, understands its identity, exercises authority, allocates resources or determines accountability. Adaptation within the existing order may then no longer be sufficient.

The boundary is not always clear. Successive First-Order adaptations may gradually challenge the existing organisational order. However, uncertainty, emergent outcomes, or experimentation alone do not make change Second-Order. The distinction lies in the level at which change occurs, not its size, frequency, or predictability.

Although the organisational environment has changed since these concepts were introduced, the distinction remains relevant. In fact, under ongoing uncertainty and adaptation, distinguishing between change within an existing order and change to that order may be even more important.

Linda Ackerman and Three Types of Change

Linda Ackerman developed an influential distinction between Developmental, Transitional and Transformational Change in Ackerman (1986). At the time, she was primarily an Organisation Development practitioner and consultant.

Ackerman defined Developmental Change as improving existing conditions. Transitional Change involves moving from a current state to a clearly defined new state, with the transition managed over a controlled period. In contrast, Transformational Change results in a fundamentally different state that emerges over time and cannot be fully specified in advance.

This distinction means Transformational Change is qualitatively different from improving an existing organisation or implementing a predetermined design. Figure 2 illustrates these three forms.

Developmental Change Improvement of what is; new state is a prescribed enhancement of the old state. 26_11
Transitional Change Design and implementation of a desired new state that solves an old state problem; requires management of the transition process to dismantle the old state while putting in place the new state; managed timetable. 26_12
Transformational Change

Market requirements force fundamental changes in strategy, operations, and worldview.

New state is unknown - it emerges from visioning, trial and error discovery, and learnings.

New state requires fundamental shift in mindset, organising principles, behaviour, and or culture, as well as organisational changes, all designed to support new business directions.

Critical mass of organisation must operate from new mindset and behaviour for transformation to succeed and new business model or direction to be sustained.

26_13

Figure best viewed on tablet or above

Adapted from Ackerman (1986) and Ackerman Anderson (2016) 

Figure 2: Ackerman’s Classification Of Change

On this website, daschange.info, Ackerman’s Developmental and Transitional Change are interpreted as forms of First-Order System Change, while her Transformational Change is interpreted as Second-Order Transformational Change. This is an analytical mapping made within this website and is not part of Ackerman’s original model:

  • Developmental and Transitional Change are treated as forms of First-Order Change because both can occur while the underlying organisational order remains substantially intact.
  • Transformational Change is associated with Second-Order Change, where that underlying organisational order itself becomes subject to reconsideration and potential change, and the eventual future state cannot necessarily be specified in advance.

References

Ackerman, L. S. (1986) ‘Development, Transition, or Transformation: The Question of Change in Organizations’, OD Practitioner, 18(4), pp. 1–8.

Ackerman Anderson, L. (2016) ‘Organization Development and Transformation: What It Takes’, in Rothwell, W.J., Stavros, J.M. and Sullivan, R.L. (eds.) Practicing Organization Development: Leading Transformation and Change. 4th edn. Hoboken, NJ: John Wiley & Sons, pp. 60–78

Jean Bartunek And Michael Moch And The Orders Of Change

The Organisational Development scholars Jean Bartunek and Michael Moch developed the distinction between different orders of organisational change from a cognitive perspective. In Bartunek and Moch (1987), they examined how schemata could help explain different forms of organisational change.

Schemata are organising frameworks people use to understand and interpret events. Bartunek and Moch described First-Order Change as incremental change occurring within schemata already shared by organisational members. Second-Order Change involves modification of those shared schemata themselves.

They also introduced Third-Order Change, which they described as developing the capacity of an organisation’s members to recognise their existing schemata and change them as circumstances require.

Their work suggests that fundamental organisational change may require changes to the shared frameworks through which organisational reality is understood, rather than only to structures, processes or behaviours.

References

Bartunek, J. M. & Moch, M. K. (1987) ‘First-Order, Second-Order, and Third-Order Change and Organization Development Interventions: A Cognitive Approach’, The Journal of Applied Behavioral Science, 23(4), pp. 483–500.

Amir Levy And Second-Order Change

Amir Levy was an organisational theorist whose work in the 1980s helped apply First-Order and Second-Order Change specifically to organisations.

Levy (1986) distinguished between change within an existing organisational framework and Second-Order Change, which involves more fundamental organisational transformation. Together with Uri Merry, he further developed these ideas in Levy and Merry (1986), examining organisational transformation through perspectives including organisational paradigms, culture, myths, purpose, and approaches to managing Second-Order Change.

Their work reinforced an important distinction: organisational transformation concerns a qualitative shift in the organisation and its underlying paradigm, rather than simply the quantity, scale or difficulty of change undertaken.

References

Levy, A. (1986) ‘Second-Order Planned Change: Definition and Conceptualization’, Organizational Dynamics, 15(1), pp. 5–23.

Levy, A. & Merry, U. (1986) Organizational Transformation: Approaches, Strategies, and Theories. New York: Praeger.

Paul Watzlawick And The Two Orders Of Change

Paul Watzlawick was a psychologist, communication theorist and influential figure at the Mental Research Institute in Palo Alto, California. Working with John Weakland and Richard Fisch, he drew on systems theory to examine why attempts to solve problems sometimes leave the underlying conditions that generate them unchanged.

Watzlawick et al. (1974) distinguished between First-Order and Second-Order Change. First-Order Change occurs within an existing system: its components, behaviours or processes may change while the rules governing the system remain substantially intact. Second-Order Change alters the system itself by changing the rules, assumptions or relationships through which it operates.

This distinction provides an important conceptual foundation for the Two Orders of Organisational Change used within this website.

References

Watzlawick, P., Weakland, J. H. & Fisch, R. (1974) Change: Principles of Problem Formation and Problem Resolution. New York: W. W. Norton & Company.

Ecosystem

The Office of Government Commerce And P3O®

The Office of Government Commerce (OGC) was a UK government body established in 2000 to promote efficiency and best practices in public sector procurement, project management, and programme management. One of its significant contributions was the development of the P3O® (Portfolio, Programme, and Project Offices) framework, first published in 2008. This framework provides principles and guidance on designing and operating effective support structures for delivering change. P3O® was created in response to the growing need for organisations to align their strategies with execution and to standardise the roles of PMOs across different contexts.

In 2014, the stewardship of the OGC’s best practice portfolio was transferred to AXELOS, a joint venture between the UK Cabinet Office and Capita. AXELOS continues to maintain and publish the official P3O® guidance, with the most recent version being “Portfolio, Programme and Project Offices: P3O® Guidance” (AXELOS, 2013).

The guidance outlines a hierarchy of structures, which is summarised in Exhibit 1. It also notes that “projects” can stand alone and do not need to be part of a “programme”.

Exhibit 1: P30® Hierarchy