Applying Hypothesis 2X to Organizational Analysis – Why REET Redefines Leadership and Management beyond SWOT, PESTLE, and the Balanced Scorecard

 

 

Applying Hypothesis 2X to Organizational Analysis – Why REET defines Leadership and Management beyond SWOT, PESTLE and the balance scorecard. 

By: Anastasios Kotzias

 

 

1. Introduction

 

│ Organizations do not fail because they lack information; they fail because they misunderstand their reality. │

Most Organizations have more data than they can use, and less understanding than they need. This tension sits at the heart of contemporary governance. Boards approve multi-year strategies, executives commission diagnostic reviews, and consulting teams populate slides with familiar frameworks, SWOT matrices, PESTLE scans, Balanced Scorecard dashboards, yet many Organizations still experience recurring problems: strategy that does not land, operations that do not stabilize, cultures that fragment, and risk events that feel “surprising” even when they were visible in hindsight. The practical consequence is expensive churn: successive change programs, reorganizations, and performance initiatives that treat symptoms, not causes.

In part, this paradox reflects an analytical mismatch. The dominant Organizational analysis models were designed for an era in which Organizational boundaries were comparatively stable, value chains were more linear, and a firm could separate “inside” from “outside” (Porter, 1985; Mintzberg, 2009).

Today, organizations operate in ecosystems: suppliers codevelop products, customers cocreate services, regulators influence operating models, and digital platforms blur industry lines. Work is cross-functional, cross-organizational, and frequently virtual. Under such conditions, the internal/external split, central to SWOT, becomes ambiguous and, at times, misleading.

Similarly, when executives treat macro-environmental scanning (PESTLE) as if it were a substitute for diagnosing operational reality, organizations can over-invest in strategic narratives while execution decays. When leaders treat metrics systems (Balanced Scorecard) as if measurement alone can engineer behavior, they risk mistaking indicators for causes (Kaplan and Norton, 1996; Kaplan and Norton, 2001).

Orgtology, the science of Organization, was developed to address precisely this problem of mis-seeing. Anchored in Hypothesis 2X, orgtology asserts that every Organizational phenomenon unfolds simultaneously in two inseparable dimensions:

• • a scientific/concrete dimension (systems, processes, resources, measurable outputs) and

• • an abstract/dynamic dimension (intent, relationships, beliefs, perceptions, identity, behavior) (Hendrikz, 2016).

Organizational reality is therefore not a single “thing” that can be captured by a list or a dashboard. It is a dual movement, in which what people believe, value, and do interacts continuously with how activity is structured and resourced. When analysis ignores either dimension, leaders and managers are prone to act on partial truths.

The REET Analysis Model – Relationships, Effectiveness, Efficiency, and Threats – was created to understand organizational reality in a way that is faithful to this duality.

REET does not begin by asking what is internal versus external; it begins by asking what is happening in the organization’s operational and strategic environments and how these interact through receptive (operational) and projective (strategic) movement (Hendrikz, 2016).

It is used as a first step in strategy development, organizational design, strategy review, and root cause analysis because it produces an integrated view of “what is actually going on” before deciding what to change or maintain (UNIORG, 2025a).

This essay argues that applying Hypothesis 2X to organizational analysis changes the practical meaning of leadership and management. Specifically, it shows why REET provides a more accurate and actionable diagnostic logic than SWOT, PESTLE, and the Balanced Scorecard for executive teams and boards.

The argument is not that the traditional models are “wrong” in all circumstances. Rather, it is that they often fail to represent organizational reality under conditions of complexity because they do not explicitly integrate the receptive/projective duality that governs how Organizations perform and remain relevant.

The essay therefore positions REET as a sense-making instrument that clarifies what must be managed (performance/operations) and what must be led (relevance/strategy), and how both depend on relationships and threat mitigation across the two dimensions.

2. Hypothesis and basic assumption

 

The essay is guided by the following hypothesis, stated in the “If-Then-Because” logic required by the Orgtology Institute:

If organizational analysis models fail to distinguish between receptive (operational) and projective (strategic) activity, then leadership and management will become misaligned—causing declining performance and relevance – because Organizations are dual entities whose reality unfolds in scientific and abstract dimensions simultaneously, as described by Hypothesis 2X (Hendrikz, 2016).

This hypothesis contains two practical claims.

• • First, analysis methods shape executive attention. What leaders choose to look at becomes what they choose to change.

• • Second, misalignment is not simply a “people issue”; it is a systemic effect of using models that do not map the organization’s dual reality.

Hypothesis 2X implies that effective Organizational diagnosis must:

(a) identify the concrete mechanisms through which work is done (processes, targets, resources, constraints), and

(b) identify the abstract dynamics through which intent is negotiated and behavior is shaped (relationships, beliefs, cultural norms, power, identity).

REET is designed to do both at once (Hendrikz, 2016).

3. Literature review: what the mainstream models do well—and where they distort reality

 

3.1 SWOT: clarity through categorization, ambiguity through the internal/external split SWOT remains one of the most widely taught strategic tools because it is easy to use and easy to communicate. It encourages teams to identify Strengths and Weaknesses (internal) and Opportunities and Threats (external). In stable contexts with clear boundaries, SWOT can be a useful starting point for discussion.

However, research and practitioner critiques have long noted its limitations: it tends to produce unprioritized lists, it is vulnerable to cognitive bias and groupthink, and it provides weak guidance for turning insight into action (Hill and Westbrook, 1997).

From an orgtology perspective, its most fundamental problem is ontological: it assumes organizational reality can be separated cleanly into “inside” and “outside.” As work becomes increasingly boundary-spanning, that split becomes analytically fragile.

Consider an organization delivering an end-to-end customer journey that depends on a platform partner, a logistics provider, and a fintech service. Is the reliability of the logistics provider internal or external? The customer experiences this as part of the organization’s service, but the organization does not “own” it.

Similarly, in a matrix environment, is a regional governance board internal or external? These questions are not trivial; they determine accountability, resourcing, and risk responses.

SWOT offers no mechanism to resolve them. In practice, SWOT often collapses into a narrative of preference: what senior people want to be true becomes the “strength,” what they dislike becomes the “weakness,” and the model lacks built-in checks against that drift (Mintzberg, 2009).

Hypothesis 2X reframes this problem. Boundary ambiguity is not an anomaly; it is a feature of modern organizational life. Diagnosis must therefore focus on how activity and relationships connect across boundaries.

REET does this by focusing on relationships and threats, spanning both operational and strategic domains, rather than assuming they are either internal or external (Hendrikz, 2016).

3.2 PESTLE: macro scanning without integration into operational reality

PESTLE is a useful way to explore macro factors – political, economic, social, technological, legal, and environmental – that may create opportunities or threats. It can broaden strategic thinking beyond immediate competitive concerns, and it is often used in regulated or geopolitically sensitive sectors. However, PESTLE is a scanning tool, not an organizational reality tool. It tells executives what is happening “out there,” but does not show how the Organization’s current operating model converts those forces into results. 

A team can produce a sophisticated PESTLE analysis and still fail to answer the operational questions that determine whether the Organization can respond:

What must change in our processes? What relationships must we renegotiate? What threats must we mitigate to continue business if disruption occurs?

Complexity scholars emphasize that organizations are complex adaptive systems, where small changes in context can cascade through networks of interaction and where cause and effect are not always linear (Stacey, 2011; Snowden and Boone, 2007). In such contexts, macro scanning must be coupled with an internal diagnosis of capability, constraints, and relational dynamics. Otherwise, organizations can over-index on external storytelling while under-investing in operational containment.

Hypothesis 2X suggests the core question is not only “What is changing in the environment?” but also “How do those changes interact with our concrete systems and abstract dynamics?”

REET’s Effectiveness and Threats windows can incorporate PESTLE inputs, but only after the organization’s operational reality is understood through Efficiency and Relationships (Hendrikz, 2016).

3.3 Balanced Scorecard: a strategic management system, but often a measurement trap

The Balanced Scorecard (BSC) was introduced to correct the over-reliance on financial measures by adding customer, internal process, and learning and growth perspectives (Kaplan and Norton, 1996). 

In its mature form, BSC is intended to translate strategy into objectives, measures, targets, and initiatives, and to align organizational activity to strategy (Kaplan and Norton, 2001). Many organizations have used BSC effectively to improve strategic clarity and performance monitoring.

Yet the BSC approach carries a risk: it can encourage the belief that what matters most is what can be measured. When Oorganizations treat scorecards as “the reality,” they can inadvertently manage the indicators rather than the system. Scholars have warned against metric fixation and Goodhart-type effects, where measures become targets and stop being good measures (Strathern, 1997).

In executive coaching practice, this often appears as a behavioral pattern: leaders become “dashboard leaders,” confident in numbers but surprised by culture, relationships, and informal power dynamics that are not captured by the scorecard.

Hypothesis 2X helps explain why. A scorecard primarily captures the scientific dimension. 

Even when it includes learning and growth or employee engagement measures, the abstract dimension is represented indirectly, often as lagging proxies.

REET, by contrast, treats relationships and threats as primary fields of analysis, not as sub-measures. It also explicitly differentiates effectiveness (having an effect on the environment) from efficiency (outputs exceeding inputs) and locates these in the projective and receptive domains respectively (Hendrikz, 2016). 

This distinction matters because leadership work is often about influencing what cannot be controlled—stakeholders, market perception, regulators – whereas management work is often about controlling what can be controlled – process discipline, resource utilization, operational risks (ISO, 2018).

3.4 Organizational risk analysis methods: COSO/ISO as complements, not substitutes

 

Modern risk frameworks such as COSO ERM and ISO 31000 provide structured approaches to identifying, assessing, and treating risk (COSO, 2017; ISO, 2018). They are valuable for governance, compliance, and risk appetite discussions. Yet, like PESTLE and BSC, they can become compliance exercises if not anchored in a diagnostic understanding of how the Organization operates and behaves.

Orgtology’s Hypothesis 2X Root Cause Analysis approach argues that root causes are frequently both concrete and abstract: a process breakdown may coexist with cultural norms that discourage escalation, or a governance gap may coexist with leadership behaviors that avoid conflict (UNIORG, 2025a).

REET provides a practical front-end to risk thinking by locating threats in both operational and strategic environments and by linking threat mitigation to efficiency (operational containment) and effectiveness (business continuation through strategy) (Hendrikz, 2016).

4. REET as a Hypothesis 2X tool: mapping Organizational reality through dual movement

 

REET stands for Relationships, Effectiveness, Efficiency, and Threats. Its central purpose is to provide an overview of organizational reality so that decisions about change and maintenance are grounded in understanding (Hendrikz, 2016).

Its basic assumption is that an adequate analysis must cover both the operational and strategic environments of an organization, because the organization must perform (operations) and remain relevant (strategy). 

This maps directly onto Hypothesis 2X: operations are primarily receptive activity (cycling processes, executing within constraints), whereas strategy is primarily projective activity (influencing the environment, changing direction, negotiating intent).

A defining feature of REET is its inverse relationship between operational and strategic concerns. Organizations draw operational and strategic activity from the same resource pool; allocating more energy to one reduces capacity for the other (Hendrikz, 2016).

This is not a moral judgement; it is a structural reality. When executives over-allocate resources to strategic initiatives in response to external pressure, operations can destabilize, increasing operational threats.

Conversely, when managers over-allocate resources to operational containment, organizations can become efficient but irrelevant, missing opportunities and losing market effect.

REET makes this trade-off explicit, enabling board-level discussions about equilibrium rather than ideology.

REET also reframes leadership and management. REET’s receptive domain – below the inverse line – relates to management, performance, and operations. Here, efficiency is the key output: organizing activity so output exceeds inputs. Managers “connect” to activity: they coordinate, direct, communicate, and establish rules and targets to stabilize processes. They also mitigate operational threats through controls, process design, and monitoring (ISO, 2018).

REET’s projective domain – above the inverse line – relates to leadership, relevance, and strategy. Here, effectiveness is the key outcome: influencing the environment and exploiting opportunities. Leaders “negotiate” with people and entities they do not control. They influence stakeholders, reposition strategy, build alliances, and secure business continuation under disruption. Effectiveness is not produced by control; it is produced by influence, negotiation, and adaptive intent (Snowden and Boone, 2007).

Relationships and threats span both domains. Relationships are necessary for performance and relevance: teams require meaningful internal relationships to execute operations, and organizations require meaningful stakeholder relationships to remain relevant. Threats affect both domains: operational threats disrupt processes; strategic threats disrupt business continuation.

REET therefore provides guidance for executive teams: when relationships are failing, both management and leadership must act; when threats are rising, both operational containment and strategic repositioning may be required (Hendrikz, 2016).

5. Comparative analysis: why REET reframes leadership and management beyond SWOT, PESTLE, and BSC

 

5.1 REET versus SWOT: from internal/external to receptive/projective reality

SWOT’s internal/external division is increasingly difficult to apply in boundary-spanning environments. REET replaces that division with a more operationally meaningful one: receptive/projective movement. Instead of debating whether a risk is “internal” or “external,” REET asks whether the Organization can control it directly (receptive/operational) or must influence it through negotiation (projective/strategic). This distinction is immediately useful in boardrooms because it clarifies accountability and the nature of required action.

For example, a customer churn problem may be interpreted in SWOT as an “external threat” (competitors) or an “internal weakness” (service quality). REET forces a more precise diagnostic: Is the churn driven by operational inefficiency (e.g., long response times), by weakened relationships (e.g., loss of trust), by reduced effectiveness (e.g., weak market proposition), or by rising threats (e.g., a regulatory change undermining the model)? In practice, the answer is often a pattern across multiple windows. REET’s value is not that it produces a single label, but that it reveals the cross-field logic that sustains the problem (Hendrikz, 2016).

5.2 REET versus PESTLE: from scanning the environment to understanding operational reality

PESTLE is valuable for understanding macro conditions, but it does not diagnose operational capability. REET can incorporate PESTLE insights in its Effectiveness and Threats windows, but only as part of a broader understanding of how the Organization operates. This sequencing matters. Many Organizations mistake environmental scanning for Organizational diagnosis. The result is strategic theatre: leaders talk about megatrends while operational relationships and process efficiency quietly collapse. REET prevents this by anchoring the conversation in operational reality—efficiency, relationships, and operational threats—before constructing strategic responses (Stacey, 2011; Snowden and Boone, 2007).

5.3 REET versus Balanced Scorecard: from measuring performance to understanding causality

Balanced Scorecard systems can create alignment, but they can also produce metric fixation. REET shifts attention from measures to causes. For example, a BSC might show declining customer satisfaction and rising cost-to-serve. 

REET asks: which processes are inefficient, which relationships are breaking, what threats are rising, and where is strategic effectiveness weakening? This does not replace measurement; it makes measurement interpretable. In Hypothesis 2X terms, REET integrates the scientific signals (metrics) with the abstract dynamics (relationships, behavior) that explain why the signals are moving (Kaplan and Norton, 2001; Schein, 2017).

Dimension	SWOT	PESTLE	BSC	REET
Human behavior	Weak	Weak	Moderate	Integral
Duality (2X)	No	No	Partial	Core
Leadership vs Management	No	No	Limited	Explicit
Reality accuracy	Low	Medium	Medium	High
Change guidance	Weak	Weak	Moderate	Strong

6. Cross-industry executive scenarios: how REET works where other models mislead

 

The following scenarios illustrate how REET functions as an executive-level Organizational health check and why it can be preferable to SWOT, PESTLE, or BSC in complex contexts. The scenarios are simplified composites drawn from common boardroom patterns, presented for analytical clarity.

6.1 Financial services: “We need strategy” when the problem is operational reality

A retail bank experiences declining profitability and increasing customer attrition. A consulting team runs a SWOT. Regulatory pressure and fintech competition are listed as threats; legacy systems are listed as weaknesses; brand reputation is listed as a strength. The board mandates a digital transformation and a new strategy narrative.

Twelve months later, the bank’s digital program is delayed, costs have increased, and attrition continues. Leadership becomes frustrated: “We have the strategy; why are we not winning?” Management becomes defensive: “We are overwhelmed with initiatives; operations are breaking.”

A REET analysis reframes the problem. In the Efficiency window, evidence shows fragmented end-to-end processes, duplicated controls, manual rework, and unclear process targets, classic drivers of low efficiency. In Relationships, evidence shows mistrust between front-line teams and central functions, low psychological safety for escalation, and incentive conflicts across channels, conditions that degrade operational execution (Schein, 2017). 

In Threats, operational risks are rising: service outages, compliance breaches, and fraud exposure. In Effectiveness, the bank’s market proposition is not the primary failure; rather, its operational reality prevents it from delivering the proposition consistently.

The REET diagnosis suggests that leadership’s strategic intent is necessary but insufficient. Management must first stabilize receptive activity: simplify processes, define operational targets, repair operational relationships, and mitigate operational threats. Only then can projective activity – digital strategy – be executed without overwhelming the system. In board terms, this is an equilibrium problem: resources were over-allocated to projective initiatives while receptive capability was decaying (Hendrikz, 2016).

6.2 Healthcare/public service: “Culture change” when the problem is relationships and operational threats

A healthcare Organization faces long waiting times, staff burnout, and declining patient experience scores. Leaders respond with a culture initiative: new values posters, “patient-first” campaigns, and leadership town halls. Balanced Scorecard dashboards track patient satisfaction, staff engagement, and throughput, but the metrics remain stubborn.

REET reveals a different reality. Efficiency analysis shows poorly designed scheduling processes, bottlenecks in triage, and frequent handoff failures between departments. Threats analysis identifies operational risks: staff shortages, safety incidents, and burnout-driven turnover. 

Relationships analysis reveals conflict between clinical and administrative teams and a norm of “heroic workarounds” instead of systemic problem-solving. Effectiveness analysis shows that the organization’s purpose is strong, but its operational model prevents that purpose from being realized.

The practical leadership-management implication is clear. Culture cannot be “installed” as a projective narrative while operational threats remain uncontained. Management must reorganize activity: redesign patient flow, establish targets, remove structural bottlenecks, and mitigate operational risks. Leadership must negotiate strategic relationships – funders, unions, regulators – to secure resources and enable sustainable work. 

REET therefore differentiates what must be managed (process redesign, operational risk) and what must be led (stakeholder negotiation, strategic resource acquisition). The outcome is not “more culture messaging,” but a coherent systemic intervention across both dimensions (ISO, 2018; Schein, 2017).

6.3 Technology platform: effectiveness outpaces efficiency

A fast-growing technology platform has strong market traction and a compelling vision. PESTLE scans highlight technological shifts and competitive forces; leadership doubles down on product expansion. Yet customers complain about reliability, service incidents, and poor support. Employee turnover rises.

REET shows an imbalance. Effectiveness is high: the Organization has an effect on the market, creates demand, and attracts users. But efficiency is low: incident response processes are immature, engineering work is fragmented, and support workflows create rework. 

Threats are rising: outages, reputational damage, and regulatory scrutiny. Relationships between product, engineering, and operations degrade as blame cycles emerge.

 

Traditional tools might suggest “increase investment” or “improve strategy.” REET shows a different executive coaching message: the Organization has outgrown its operating model. Management must build receptive capability – define process constructs, stabilize operations, establish targets, and reduce rework – while leadership negotiates external expectations and communicates a realistic path to reliability. 

Without this, effectiveness will be consumed by threats, and relevance will erode through performance failure. REET helps executives see that scaling is a dual challenge: projective growth and receptive containment must mature together (Snowden and Boone, 2007; Hendrikz, 2016).

6.4 Cross-Organizational ecosystem: where SWOT collapses and REET clarifies

A public-private partnership delivers infrastructure services through multiple entities. Failures occur at handoffs: project delays, cost overruns, public complaints. A SWOT workshop fails because no one can agree what is “internal” or “external.” Each entity lists the others as threats.

REET reframes the system as a shared organizational construct. Relationships analysis maps stakeholder interfaces, contract governance, escalation paths, and trust levels. Efficiency analysis maps process flows across organizational boundaries and identifies duplication and misaligned targets. 

Threats analysis distinguishes operational threats (handoff failures, safety risks) from strategic threats (political shifts, funding instability). Effectiveness’ analysis examines the partnership’s effect on its environment and whether strategy remains relevant.

The practical outcome is not a new list; it is a shared narrative of reality that enables boards and executives across Organizations to act coherently. In Hypothesis 2X terms, REET integrates the scientific (process flows, contractual mechanisms) with the abstract (trust, negotiation, identity) across the ecosystem. This is exactly the kind of context where REET is superior to internal/external frameworks (Hendrikz, 2016; Porter, 1985). 

6.5 Manufacturing and supply chain: when threats are misread as external shocks

A manufacturing firm experiences repeated production stoppages due to supplier delays and quality failures. A PESTLE scan highlights geopolitical volatility and transportation disruptions; a SWOT workshop frames “supply chain instability” as an external threat. The board authorizes a diversification strategy and new supplier contracts.

REET reveals a more nuanced reality. In Efficiency, the firm’s planning process is brittle: inventory policies are misaligned with variability, quality controls generate rework, and escalation paths are unclear. In Relationships, procurement and production operate with low trust and conflicting incentives, and supplier relationships are transactional rather than collaborative. In Threats, operational exposure is high not only because of external shocks, but because internal process design amplifies shock impact. In Effectiveness, the strategy to diversify suppliers is sensible, but without operational and relational redesign the firm will continue to experience stoppages.

The REET implication is that “external threats” are rarely purely external. They interact with receptive capability. Boards can still pursue supplier diversification, but they must also invest in process resilience and relationship renegotiation, moving from contract policing to joint problem-solving. This aligns with risk guidance that resilience is built through system design and governance, not scanning alone (Porter, 1985; ISO, 2018).

6.6 Non-profit/NGO: high purpose, weak efficiency, and hidden threats

An international NGO has a strong mission and is widely respected. Yet program delivery is inconsistent across countries, donor reporting is late, and staff turnover is rising. A Balanced Scorecard is introduced with KPIs for program reach, donor satisfaction, internal process, and learning. Metrics improve temporarily, then regress.

REET identifies the underlying pattern. Effectiveness is strong: the NGO has environmental impact and stakeholder goodwill. But Efficiency is weak: duplicated reporting processes, inconsistent project management practices, and unclear decision rights create rework. Relationships are strained between headquarters and country offices, with identity conflicts (“field vs head office”) undermining collaboration. 

Threats are rising: donor compliance risk, reputational risk, and burnout risk.

In this scenario, REET prevents a common error: treating a mission-driven organization as if it were exempt from operational discipline. Management must design efficient processes that respect local context, while leadership must renegotiate relationships and governance norms across the network. This protects relevance (mission legitimacy) by improving performance (delivery reliability), illustrating REET’s Relevant and Performing Organization-RPO logic (Kaplan and Norton, 2001; Hendrikz, 2016).

7. Practical application protocol and executive implications

 

7.1 Practical application protocol: using REET as a diagnostic front-end to strategy, design, and risk work

A practical reason REET “lands” with executives is that it behaves like a structured conversation that produces evidence. In consulting practice, REET is often initiated through a questionnaire and then validated through interviews, observation, and document review (Hendrikz, 2016). For boards and executive committees, the method can be simplified into a disciplined protocol that still honors Hypothesis 2X.

Step 1: Define the problem as an observable pattern. The problem statement should specify what is happening (e.g., “customer churn increased 18% in two quarters”, “project delivery variance exceeded 25%”, “regulatory findings doubled”), where it is happening, and why it matters. 

This keeps the REET exercise anchored in the scientific dimension rather than drifting into untestable narratives.

Step 2: Cluster evidence into the four REET windows. Evidence should be explicit: data points, incidents, process measures, verbatim quotes, stakeholder feedback, audit findings, and performance trends. In Hypothesis 2X terms, the “evidence” includes both concrete artefacts (process maps, incident reports) and abstract artefacts (themes from interviews about trust, identity, or leadership credibility). Importantly, “opinions” are treated as data about perception, not as conclusions (Hendrikz, 2016).

Step 3: Create a narrative around each REET area, which explains the evidence found. The narrative explains what the evidence suggests and how it connects. This is where REET moves beyond SWOT listing. A Relationships narrative, for example, might explain how incentive conflicts create friction, how silo identities produce blame cycles, and how that undermines process handoffs (Schein, 2017). An Efficiency narrative might explain how rework loops, unclear targets, and excessive approvals consume resources. A Threats narrative should separate operational threats (process disruption) from business continuation threats (strategic viability).

Step 4: Create an “As-Is” map that relates problems, as identified in the narrative, across the REET areas. Here the Orgtologist asks: how do relationship dynamics create inefficiency, how do inefficiencies raise threats, and how do threats constrain effectiveness? This cross-window mapping is the practical expression of Hypothesis 2X: abstract dynamics influence concrete systems, and concrete constraints reinforce abstract behaviors.

Step 5: Define a desired state. The desired state is not a slogan. It specifies what must change in each window, and why. The solution narratives translate REET insights into three Orgtology change areas, efficiency (system/process), effectiveness (strategy/impact), and behavior (abstract dynamics), so that interventions are coherent rather than scattered (UNIORG, 2025a).

Step 6: Create a solution narrative for every problem identified in the “As-Is” REET map. This is where REET can interface with a Balanced Scorecard: scorecards and KPIs become instruments for monitoring the solution, not substitutes for diagnosis. REET answers “what is real and why,” while BSC can track whether the organization is moving toward the “to-be” state (Kaplan and Norton, 2001).

Step 7: Cluster possible solutions under one of the three orgtology change areas (efficiency, effectiveness, and behaviour)

Efficiency solutions address receptive activity and focus on process design, system stability, resource allocation, and operational risk containment. Effectiveness’ solutions address projective activity and focus on strategy, stakeholder influence, market positioning, and business-continuation threats. 

 

Behavioral solutions address the abstract dimension and focus on leadership conduct, management practice, relationship dynamics, accountability norms, and decision-making patterns. 

This clustering discipline prevents organizations from attempting to solve strategic problems with operational fixes or operational problems with leadership rhetoric. It also ensures that behavioral dynamics are treated as a structural requirement rather than a secondary concern.

Step 8: Create a “To-Be” map that relates the solutions narrative across the REET areas

Rather than listing initiatives, the “To-Be” REET map illustrates how improved efficiency reduces operational threats, how behavioral alignment strengthens relationships, and how enhanced effectiveness mitigates strategic threats. It allows leaders and managers to anticipate unintended consequences, such as strategic initiatives that overwhelm operational capacity. 

In Hypothesis 2X terms, the “To-Be” map visualizes a future state in which receptive and projective activity are intentionally balanced. This step ensures that change is designed as an integrated system rather than as disconnected initiatives.

Step 9: Develop an action program

 

The action program translates the “To-Be” REET map into a sequenced and governed set of actions. It specifies what will change, who is accountable, and how efficiency, effectiveness, and behavioral interventions will be paced to avoid organizational overload. Management typically leads efficiency actions, leadership leads effectiveness actions, and behavioral actions remain a shared and continuous responsibility. 

The program is reviewed periodically using REET as an organizational health check to sustain equilibrium and maintain a Relevant and Performing organization.

7.2 Executive coaching lens: how REET changes leader behavior and board conversation

From an executive coaching perspective, many leadership breakdowns are not failures of intent but failures of sense-making. Leaders may respond to operational volatility by escalating strategic rhetoric, or respond to strategic uncertainty by tightening operational control. Both are understandable reactions, but both can be counterproductive. REET creates a coaching mirror: it makes visible when a leader is trying to “lead” an efficiency problem or “manage” an effectiveness problem (Hendrikz, 2016).

Leaders often default to projective language – vision, purpose, and transformation-  when they feel pressure. REET asks: what is the state of operational relationships? Are we exposing people to unmanaged threats? Are our processes efficient enough to sustain the promised experience?

Conversely, managers may default to tightening controls when strategy is unclear. REET asks: are we negotiating the right stakeholder relationships? Are we having an effect on our environment? Are we treating relevance as if it were a process metric? These questions shift board conversations from blame to diagnosis and from slogans to equilibrium (Snowden and Boone, 2007; Stacey, 2011).

7.3 Implications for boards, executive teams, and Certified Orgtologists

For boards, REET provides a governance-level distinction between issues of control and issues of influence. It helps boards ask better questions: “Is this a performance problem or a relevance problem?” “Are we spending too much energy on projective change while receptive capability is failing?” “Which threats require operational controls, and which require strategic repositioning?” 

This strengthens oversight without pushing boards into management detail (COSO, 2017; ISO, 2018).

For executive teams, REET reduces the tendency to oscillate between strategy and operations in an unstructured way.

It offers an integrated language for cross-functional alignment: relationships are not a “soft” add-on but a structural condition for efficiency and effectiveness; threats are not only risk register items but signals of misalignment between operations and strategy (Schein, 2017; Hendrikz, 2016).

For Certified Orgtologists, REET provides a publishable contribution to the Orgtology Body of Knowledge because it turns Hypothesis 2X into a practical diagnostic discipline. In particular, the REET protocol (problem definition, evidence clustering, narrative building, as-is mapping, to-be design, action programming) provides a methodological spine that can be taught, replicated, and improved through practice (Hendrikz, 2016; UNIORG, 2025a).

8. Conclusion: REET as an Organizational health check for Relevant and Performing Organization (RPO) maintenance

 

This essay has argued that applying Hypothesis 2X to Organizational analysis changes how executives should diagnose and intervene. Traditional tools such as SWOT, PESTLE, and Balanced Scorecard can be useful, but they often misrepresent organizational reality under complexity because they do not explicitly integrate the dual dimensions through which organizations operate. As a result, leadership and management can become misaligned: strategy is treated as an operational fix, operations are treated as a leadership narrative, and organizations drift away from equilibrium between relevance and performance.

REET offers a superior sense-making logic because it is built for duality. By analyzing Relationships, Effectiveness, Efficiency, and Threats across receptive and projective domains, REET clarifies what must be managed and what must be led. It supports the maintenance of a Relevant and Performing Organization-RPO by treating relationships and threats as spanning both performance and relevance, and by making resource trade-offs explicit. For boards and executive teams, REET functions as an organizational health check: it does not merely describe the Organization; it reveals the logic of what sustains or undermines it (Hendrikz, 2016).

│ In practical terms, the argument is a call for executive discipline:

 

• • Before deciding what to change, understand reality.

• • Before claiming a “strategy problem,” check operational efficiency and relationships.

• • Before launching culture programs, check operational threats and process design.

• • Before trusting dashboards, investigate causality.

Hypothesis 2X reminds us that Organizations are both systems and human communities. REET provides a way to see and act on that truth. │

 

 

References:

 

 

• • ISO (2018). ISO 31000: Risk management—Guidelines. International Organization for Standardization.

• • COSO (2017). Enterprise Risk Management: Integrating with Strategy and Performance. Committee of Sponsoring Organizations of the Treadway Commission.

• • Hill, T. and Westbrook, R. (1997). ‘SWOT analysis: it’s time for a product recall’, Long Range Planning, 30(1), pp. 46–52.

• • Kaplan, R.S. and Norton, D.P. (1996). The Balanced Scorecard: Translating Strategy into Action. Boston: Harvard Business School Press.

• • Kaplan, R.S. and Norton, D.P. (2001). The Strategy-Focused Organization. Boston: Harvard Business School Press.

• • Mintzberg, H. (2009). Managing. San Francisco: Berrett-Koehler.

• • Porter, M.E. (1985). Competitive Advantage: Creating and Sustaining Superior Performance. New York: Free Press.

• • Schein, E.H. (2017). Organizational Culture and Leadership (5th ed.). Hoboken: Wiley.

• • Snowden, D.J. and Boone, M.E. (2007). ‘A leader’s framework for decision making’, Harvard Business Review, 85(11), pp. 68–76.

• • Stacey, R.D. (2011). Strategic Management and Organizational Dynamics (6th ed.). Harlow: Pearson.

• • Strathern, M. (1997). ‘“Improving ratings”: audit in the British university system’, European Review, 5(3), pp. 305–321.

• • Hendrikz, D. (2016). Orgtology: The Science of Organization. International Orgtology Institute.

• • UNIORG (2025a). Root Cause Analysis: Integrating Orgtology’s Hypothesis 2X with established RCA tools. UNIORG.