Progress through five stages: clarify value, design accountability, connect processes, test in operation and improve continuously. Start with the business outcome to improve, then align organisation and decision mechanisms. Use end-to-end processes to test whether responsibilities work together and use operating evidence to establish whether the mechanisms function. Policies, workflows, measures and system requirements are designed together, extending reform beyond organisation charts and documents. Each stage closes with explicit outputs and progression conditions, keeping reform milestones aligned with the quality of actual operation.
ZHICE / VALUE TO EXECUTIONChoose a stage to explore the work and conditions for progress.
THE QUESTION TO ANSWER
Which business outcome should management reform improve first?
01 / 05
HOW THE WORK PROCEEDS
Translate strategy into value drivers such as reliability, customers, efficiency, cash flow and risk. Verify problems and their effects through interviews, process samples and operating data.
WORK PRODUCTS
Value-driver tree; problem evidence map; reform priorities
CONDITIONS FOR PROGRESS
Reform objectives have clear definitions and distinguish symptoms, causes and judgements still to test.
Across every stageBusiness valueAccountabilityData and evidenceRisk boundaries
Operating evidence informs judgement. The approach evolves with conditions.
THE DECISION CONTEXT
Understand the relationships. Then choose the tools.
Select a factor to see how it connects to the operating decision and shapes our analysis.
Operating outcomesZHICE / DECISION LINKS
01 / THE CONNECTION
Clarifies who decides
Align access to information, decision authority and accountability.
02 / THE CONNECTION
Connects hand-offs
Trace the full business chain to identify waiting, rework and the cost of local optimisation.
03 / THE CONNECTION
Tests operating conditions
Bring asset condition, funding plans and actual business records into one diagnosis.
04 / THE CONNECTION
Updates the mechanism
Use exceptions and results from trials to revise the rules before scaling.
Read the full analysis
Management problems in energy businesses often cross professional boundaries. Maintenance plans affect production availability, procurement affects downtime, trading depends on operations and forecasting, and asset renewal is constrained by funding plans. A department may meet its own targets while increasing total cost or risk. ZHICE follows the process of realising value: clarify the outcome to improve, then examine connections among accountability, processes, assets and data. Diagnosis starts with actual cases and evidence to identify where problems originate and how they travel across functions.
Management designs must be tested in practice. ZHICE translates the target operating model into critical decisions, business handovers, role behaviours and data requirements, using representative operating trials to reveal conflicts and burdens. Mature activities require standards and stable operation; exploratory work needs bounded autonomy and stage-based validation. Progress is assessed through both formal policies and practical conditions: whether staff understand them, data are available and exceptions can be resolved. Reviews feed operating evidence back into rules so that new mechanisms can be adopted and maintained.
PRINCIPLES IN PRACTICE
How judgements are formed.
A method makes the relationships between evidence, choices and accountability open to discussion and testing.
01
Several disciplines jointly produce operating outcomes, and departmental measures may conflict. If purchasing savings increase waiting and rework, or faster handling shifts review work downstream, the whole business chain must be assessed. ZHICE connects outcome measures with their drivers while imposing quality, reliability and risk constraints. Diagnosis does not dismiss an individual department's objectives; it explains their combined effect on operations and adjusts metric relationships, accountability and conflict-resolution mechanisms accordingly.
IMPLICATIONS FOR THE ENGAGEMENT
Use a cross-functional business process as the unit of analysis and examine the complete cycle and cost from need to outcome. Every improvement proposal should explain upstream and downstream effects and retain measures capable of detecting displaced problems.
02
A responsibility table may list participants without resolving who decides. Critical decisions require a distinction between initiation, specialist assessment, approval, execution and oversight, considering where information is created, who has the expertise and who bears risk. ZHICE tests rights and responsibilities through actual cases, identifying duplicate approvals, informal vetoes and accountability gaps. Delegation is accompanied by capability, information and oversight. Fewer approval layers are not in themselves proof of reform, and extra approvals cannot substitute for professional judgement.
IMPLICATIONS FOR THE ENGAGEMENT
Define responsibility interfaces around frequent or high-impact decisions, including escalation triggers, response times and disagreement resolution. Test delegation through real cases and verify that accountability remains traceable when outcomes differ from expectations.
03
Management design rests on business understanding, but process exceptions, staff habits and data gaps often emerge only in operation. ZHICE uses bounded trials with essential controls to test whether rules reduce problems, increase workload or produce new workarounds. AI assistance and automation are assessed on the same basis: task quality, review effort and differences in user outcomes. Expansion is justified only when rules, roles, data and exception handling work together.
IMPLICATIONS FOR THE ENGAGEMENT
Define the baseline, scope and stop conditions before a pilot, recording exceptions and reasons for revision during it. Expansion evidence should include actual adoption and outcomes; completed training, published policies or system go-live alone are insufficient.
FROM INQUIRY TO EXECUTION
Five stages, with clear progression.
Each stage produces an outcome and establishes what the next step requires. Expand a stage for activities, evidence requirements and review criteria.
01
PHASE / Which business outcome should management reform improve first?
Clarify value
The value-clarification stage establishes the operating problem and its impact before starting with organisational change or system development. ZHICE translates goals into observable business outcomes and compares management judgements, frontline experience and records, distinguishing facts, symptoms and causal explanations that still require validation.
How the work proceeds
Translate strategy into value drivers such as reliability, customers, efficiency, cash flow and risk. Verify problems and their effects through interviews, process samples and operating data.
01
Select the outcome to improve and define the applicable business, observation period and evaluation criteria. Record how different disciplines understand the problem and where they disagree on priorities.
02
Trace how results arise through specific business cases. Combine interviews, samples and data to identify waiting, rework, responsibility breaks and risk exposure, building a factual chain.
03
Organise reform issues by impact, controllability and dependencies. Distinguish immediate fixes, issues requiring deeper diagnosis and matters needing management decisions.
Stage review
Reform objectives have clear definitions and distinguish symptoms, causes and judgements still to test.
01Objectives specify business outcomes and evaluation definitions well enough to assess whether later actions improve the problem.
02Critical problems have factual support and priorities. Symptoms, causes and recommendations are kept distinct.
02
PHASE / Who decides, who provides expertise and who owns the result?
Design accountability
Accountability design builds organisational mechanisms around real decisions. Different matters require different expertise, response speeds and checks, so authority across headquarters, regions and sites needs an explicit rationale. ZHICE examines whether decision-makers receive the information and capability they need, and how cross-disciplinary disagreements and exceptions are handled.
How the work proceeds
For investment, production, trading and asset decisions, define authority at headquarters, regional and site levels, escalation conditions and essential checks. Distinguish management approaches for mature and exploratory businesses.
01
Review critical investment, procurement, maintenance and trading cases, separating initiation, assessment, approval, execution and oversight. Identify informal authority and gaps in accountability.
02
Compare delegation approaches against risk, maturity and professional capability. Define the conditions and boundaries for common standards, routine delegation and escalation of exceptions.
03
Design organisation, roles, performance, review meetings and oversight together. Examine cross-functional interfaces so that additional responsibilities come with the necessary resources and authority.
Stage review
Every critical decision has an accountable owner, with authority matched to risk responsibility.
01Each critical decision has a clear ultimately accountable owner, with authority matched to information, expertise and risk responsibility.
02Disagreements and exceptions have executable escalation routes. New responsibilities include resources, oversight and transition arrangements.
03
PHASE / Does accountability remain continuous as work crosses departments?
Connect processes
Process integration connects policy requirements with actual work. Equipment, work orders, contracts and settlements are interrelated; a single department cannot explain the full outcome. ZHICE follows objects and events to identify handovers and control points, reducing unnecessary waiting and rework while retaining essential professional review and risk controls.
How the work proceeds
Connect end-to-end processes through business objects and events. Identify waiting, rework, duplicate entry and information breaks; design delivery standards, exception paths and data responsibility together.
01
Map the complete path from business need to final outcome. Link equipment, work-order, procurement and settlement objects, and compare actual events with policy requirements.
02
Review inputs, outputs, acceptance conditions and time requirements at critical handovers. Analyse causes of waiting, returns and duplicate entry; assign ownership and escalation requirements for each exception type.
03
Design process measures, data definitions and system requirements together. Distinguish steps suitable for standardisation from tasks requiring judgement, and assess upstream and downstream effects.
Stage review
Critical handovers specify inputs, outputs, time requirements and exception handling.
01The process connects to a complete business outcome, with clear handovers, exceptions and control responsibilities, rather than a departmental flowchart alone.
02Improvement does not depend on weakening necessary controls or shifting workload. Metrics and available data support actual evaluation.
04
PHASE / Can the new mechanisms work reliably under real operating pressure?
Test in operation
Operating trials test whether the design holds under real work pressure. The scope should be representative while allowing problems to be detected and corrected promptly. With essential controls retained, ZHICE observes role understanding, handovers, data availability and exception handling, assessing operational improvement alongside additional burden and unsuitable contexts.
How the work proceeds
Use real cases in representative business units to test processes, authority, meetings and measures. Retain safety and compliance controls while recording workload, conflicts and unanticipated issues.
01
Define pilot activities, participants, baseline and observation period. Specify critical rules to validate and stop conditions, with exception handling, accountability communication and necessary role training.
02
Run new processes, authority and measures on real cases. Record execution variance, manual recovery and coordination costs, observing adoption across people and operating contexts.
03
Review jointly across disciplines, distinguishing design flaws, capability gaps, data limitations and execution variance. Revise rules and retest the actual effects of critical changes.
Stage review
Trial evidence shows that responsibilities are executable, data can be obtained and exceptions can be resolved.
01Trials show that roles are executable, data can be obtained and exceptions resolved. Major issues have been revised and appropriately retested.
02Expansion recommendations state applicable scope and prerequisites, provide evidence of improvement and disclose unresolved issues and limitations.
05
PHASE / How will issues be identified, resolved and converted into organisational learning?
Improve continuously
Continuous improvement establishes ownership for maintaining the new mechanisms. Operating conditions, personnel and systems change; processes may become ineffective or encourage meeting measures at the expense of their original purpose. ZHICE connects operating reviews with process maintenance, requiring explanations for material variances and completion evidence plus effectiveness checks for corrective actions.
How the work proceeds
Establish a rhythm of operating reviews and process improvement. Use business-event data and frontline feedback to identify variance, linking corrective actions with policy updates and staff development.
01
Establish reviews aligned with operating rhythms. Consider results, process measures and frontline feedback together to identify recurring problems and new exceptions.
02
Define actions, owners and completion evidence for important variances. Check that actions address causes and assess their effects on other processes and functions.
03
Write operationally validated changes back into policies, roles, measures and system requirements. Preserve versions and reasons, arrange staff learning and track subsequent implementation effects.
Stage review
Every material issue has an owner, completion evidence and a review of its effect.
01Material issues have owners, deadlines and evidence of effects. Recurring variances trigger deeper causal analysis.
02Management mechanisms have continuing ownership, and operating experience informs policies, capabilities and later business decisions.
ANALYTICAL FRAMEWORK
Figure 1 | Connecting operating objectives to daily work
Four interdependent layers: objectives define outcomes, processes organise work, decisions allocate responsibility, and data support judgement and feedback.
Swipe to explore the complete figure
01
Value and constraintsDefine the customer, efficiency, cash-flow and reliability outcomes to improve, together with safety, compliance and risk limits that must be respected.
02
End-to-end processesOrganise complete processes around equipment, work orders, contracts and settlement. Identify handovers, controls and outcomes shared across functions.
03
Decision interfacesSeparate initiation, specialist assessment, approval, execution and oversight. Define authority, required inputs, escalation and disagreement resolution.
04
Data and evidenceAlign definitions for metrics, events and samples. Verify data quality and feed execution, exceptions and results back into processes and decisions.
ZHICE analytical framework. Layers describe management relationships, not fixed organisational levels, and do not require new departments.
ANALYTICAL FRAMEWORK
Figure 2 | Evidence links objectives, operation, intervention and learning
Continuous improvement works around real problems. Each intervention must produce action and a result that can be reviewed.
Swipe to explore the complete figure
01
Set goals and baselineDefine scope, outcomes and constraints. Verify the current state and data definitions to create a comparable starting point.
02
Observe operationsCombine business events, asset condition and staff feedback to identify waiting, rework, exceptions and risk, separating record gaps from actual problems.
03
Make bounded changesDefine actions, owners, resources and trial scope. Preserve essential controls and set stop or escalation conditions for major variance and unsuitable contexts.
04
Review and updateAssess results and additional burden, distinguishing completed actions from resolved problems. Standardise effective practices and continue analysing unresolved issues.
ZHICE analytical framework. This illustrates working relationships for continuous improvement; it is not evidence of project outcomes or a substitute for professional safety assessment.
EVIDENCE & ACCEPTANCE
Make deliverables useful to decisions.
Go beyond document names to define purpose, evidence and verification. Agree the work scope against actual conditions at project initiation.
DECISION TOOL
Management consulting: stage outputs and review requirements
Swipe to explore the complete table
Stage and decision task
Required work products
Participation and accountability
Conditions for progression
Clarify value: Translate reform ambitions into concrete operating problems, defining scope, effects and evaluation criteria.
Value-driver relationships, problem evidence and reform agenda, separating facts, causal judgements and open verification tasks.
Executives confirm objectives; business teams provide real cases; finance and specialists jointly verify impacts.
Material problems have facts and priorities. Objectives are clear enough to evaluate subsequent improvement.
Design accountability: Allocate rights and responsibilities around critical decisions and define headquarters, regional and site interfaces.
Target operating model, decision responsibilities and escalation rules, with roles, oversight, performance and transition arrangements.
Management confirms delegation principles; business teams verify needs; HR and specialists align capabilities and policies.
Critical decisions have accountable owners, matched authority, capability, information and risk responsibility, plus exception routes.
Connect processes: Join cross-functional work through business objects and events, defining handovers and essential controls.
End-to-end processes, critical handovers and exceptions, with measures, data ownership and system-change requirements.
Process owners coordinate outcomes; each stage owns delivery; data and systems teams confirm supporting conditions.
Processes map to actual roles and events; controls remain effective; data and measures enable operating assessment.
Test in operation: Use representative real work to verify that rules, roles, data and exception handling function together.
Pilot baseline, operating records, revisions and effects, with the scope for expansion and unresolved matters stated.
Business units operate; specialists retain essential controls; the project team records, reviews and validates revisions.
Major defects are resolved and verified. Benefits and burden have evidence, with clear prerequisites and limitations for expansion.
Improve continuously: Connect operating reviews and mechanism maintenance so effective changes enter daily work and future decisions.
Improvement register, effectiveness checks and policy-change records, with ownership, communication and staff learning.
Executives drive resolution of major issues; mechanism owners maintain rules; frontline staff report adoption and exceptions.
Improvements have outcome evidence; recurring issues are traced; rules remain aligned with roles, data and systems.
ZHICE project framework. Responsibilities and acceptance arrangements should be agreed against governance requirements, business risk and engagement scope.
OUR PRACTICE
Explore the critical questions.
Each practice examines diagnosis, solution design, implementation and delivery requirements in detail.
We translate management research and technological advances into working methods for energy businesses. The frameworks below are ZHICE's synthesis of the research and industry questions.
Charles A. O’Reilly III、Michael L. Tushman / Academy of Management PerspectivesOrganizational Ambidexterity: Past, Present and Future · 2013
Application in the ZHICE approachDraws on organisational design for exploiting mature activities while exploring new businesses, distinguishing management approaches and arranging necessary coordination.
Scope and limitationsThe research discusses multiple approaches and their conditions of use; it does not imply that every firm should create a separate innovation organisation.
Wil M. P. van der AalstNo AI Without PI! Object-Centric Process Mining as the Enabler for Generative, Predictive, and Prescriptive Artificial Intelligence · 2025-07-31
Application in the ZHICE approachUses research combining object-centric process mining and AI to support process diagnosis and intelligent-application design through business objects and event relationships.
Scope and limitationsThis source is a preprint of a conference keynote paper offering a research perspective. It does not establish universally effective product capabilities or verified enterprise benefits.
Erik Brynjolfsson、Danielle Li、Lindsey Raymond / The Quarterly Journal of EconomicsGenerative AI at Work · 2025-02-04
Application in the ZHICE approachUses empirical differences in AI-assisted performance by worker experience to incorporate individual variation, quality and learning into task and evaluation design.
Scope and limitationsThe study concerns customer-support work in one firm. Its results cannot be directly extrapolated to expected improvements in energy production, trading or management roles.
International Organization for Standardization (ISO)ISO 55001:2024 — Asset management system — Requirements · 2024-07
Application in the ZHICE approachDraws on the public overview of lifecycle management oriented to organisational objectives and the balance of asset performance, risk and expenditure.
Scope and limitationsUses only the publicly available overview, without quoting paid standard clauses. The website methodology is not a certification or conformity conclusion.