Home › People, Process, Technology and Data
Your execution problem does not belong to one department.
People, Process, Technology and Data have to work as one operating system. Covalent examines the connections between them to find why strategy is not becoming coordinated action.
The visible problem is rarely the whole problem.
A delayed project may look like a planning problem. Underneath it may be an ownership problem, a decision that can only be made in one weekly meeting, a tool that hides a dependency and reporting that does not surface the risk until it is too late.
Treating each symptom separately creates local improvement and system-wide frustration. The four-lens model forces the organisation to examine the full mechanism.
Operating Intelligence is the category. People, Process, Technology and Data are the diagnostic lens used to understand it.
Capable people still fail inside unclear systems.
The People lens does not begin by asking who is underperforming. It asks whether the operating design makes accountability, decisions and priorities clear enough for capable people to succeed.
What we examine
- Outcome ownership
- Decision rights
- Capacity and overload
- Leadership behaviour
- Stakeholder alignment
- Change adoption
- Knowledge concentrated in individuals
- Dependence on informal influence and heroics
Common warning signs
- The same reliable people are pulled into every problem
- Teams wait for one leader to approve ordinary decisions
- Actions are allocated, but nobody owns the outcome
- Work succeeds because someone remembers rather than because the system routes it
- Change is announced but not adopted
If the most dependable person left tomorrow, would the operating system still work?
A process is useful only when it helps work move, a decision happen or a requirement be met.
The Process lens distinguishes necessary control from process theatre. It maps how work moves through handoffs, approvals, meetings and escalation routes, then identifies where the design creates delay, duplication or ambiguity.
What we examine
- End-to-end workflows
- Governance forums
- Meeting purpose and outputs
- Handoffs and dependencies
- Escalation routes
- Portfolio and project controls
- Operating cadence
- Decision and approval paths
Common warning signs
- A meeting exists because the workflow does not
- The same update is rewritten for several forums
- Approval stages have accumulated without a clear risk rationale
- Teams bypass governance because the formal route is too slow
- Everyone follows a process, but nobody can explain what decision it improves
Does this process help the organisation move, decide or comply, or does it merely prove that activity occurred?
Technology should support the operating model, not become a substitute for one.
The Technology lens examines whether tools, integrations, automation and AI are helping work move coherently. It starts with the current estate before recommending another platform.
What we examine
- Tool purpose and ownership
- Adoption and workarounds
- Duplicate systems of record
- Integration gaps
- Manual re-entry and reconciliation
- Automation opportunities
- AI use cases and governance
- Technology decisions disconnected from workflow design
Common warning signs
- Monday, Jira, Notion, Slack and dashboards all contain different versions of the truth
- Staff export data to spreadsheets because systems do not connect
- A new platform reproduces the old broken workflow
- AI tools are purchased without agreed use cases, controls or measures
- Technology creates more reporting but less understanding
Is the tool improving an understood process, or making an unclear process happen faster?
A report has value only when someone can trust it and act on it.
The Data lens looks beyond numerical KPIs. It examines data quality, timeliness, ownership and the qualitative signals people hold before a formal measure turns red.
What we examine
- Source-of-truth integrity
- Reporting timeliness
- Metric definitions
- Leading and lagging indicators
- Qualitative delivery signals
- Data ownership
- Decision evidence
- Whether reporting leads to action
Common warning signs
- Reports stay green until a milestone is missed
- Different functions define the same metric differently
- Leadership spends more time reconciling numbers than deciding what to do
- Teams know a project is in trouble before the dashboard does
- Packs describe activity without identifying a decision or owner
What does leadership need to see early enough to change the outcome?
Most execution failure occurs between the four lenses.
People × Process
A decision route exists, but nobody understands who has authority to use it.
Process × Technology
A workflow is automated before unnecessary approvals are removed.
Technology × Data
The platform creates a dashboard, but the source fields are incomplete or interpreted differently.
Data × People
The risk is visible to the delivery team, but the reporting culture discourages challenging a green status.
People × Technology
A tool is technically capable but rejected because the new behaviour was never designed or reinforced.
Process × Data
A governance forum receives information after the point when it could have influenced the decision.
The four lenses identify the cause. Six dimensions measure the effect.
Inside the Operating Intelligence Diagnostic, evidence from all four lenses is assessed against decision velocity, ownership clarity, meeting effectiveness, workflow coherence, reporting value and AI readiness.
This produces a baseline that is broad enough to see the system and specific enough to prioritise action.
Decision velocity
Ownership clarity
Meeting effectiveness
Workflow coherence
Reporting value
AI readiness
Do not fix one part of the business by making another part carry the cost.
Start with an integrated view of how the organisation executes.