Operational Intelligence

It sits inside Chain Development, Nordleid's discipline for connecting capabilities across a development chain and deciding which of them a situation actually justifies. Operational Intelligence is one of the patterns that decision can produce. It is used wherever the work is to see something earlier and respond to it responsibly, rather than to build something new.

Many organisations already run a CRM, an ERP or PSA, HR and resource-management systems, project and time systems, business intelligence, Microsoft 365 or SharePoint, and other operational systems besides. Operational Intelligence does not ask an organisation to replace any of them.

The friction usually sits between the systems rather than inside any one of them: signals live in separate places, the business context that would make sense of them is fragmented, decisions arrive later than the evidence for them existed, ownership of a given signal is unclear, the response stays manual, the feedback loop back to whoever decided is weak, and outcomes are not captured consistently enough to learn from.

Operational Intelligence is the work of closing those gaps around the systems and responsibilities an organisation already has.

The pattern has one shape, applied differently to every situation it is used for.

01 — Signal

A relevant event, deviation, trend, risk or opportunity becomes visible.

02 — Context

Business rules and real operating conditions determine what the signal means.

03 — Intelligence

The signal is evaluated, prioritised, classified or turned into a recommendation.

04 — Action

A concrete response becomes possible.

05 — Accountability

A defined role owns the decision, the exception or the next step.

06 — Outcome

The effect is observed and used to improve the system over time.

A system that stops at signal, context and analysis may be valuable reporting or business intelligence. Nordleid does not call it Operational Intelligence unless it also carries an action, an owner and a way of learning from the outcome.

Operational Intelligence connects the systems an organisation already uses to the decisions and actions that need to happen next.

It is not business intelligence or reporting on its own, not a data warehouse, and not a platform meant to replace the enterprise systems already in place. Where a dashboard ends at a chart, Operational Intelligence continues to the owner who acts on it and the outcome that is checked afterwards.

Margin & Capacity is the first concrete scenario Operational Intelligence has been designed around.

A consultancy or delivery organisation may already know today's utilisation. The harder question is which teams are likely to become underutilised eight weeks from now, and what can still be done about it while there is time left to act. That question is illustrative rather than a claim of predictive accuracy. The value of the pattern is in raising the question early enough for a decision to still change the outcome, not in a guaranteed forecast.

Typical inputs include pipeline and its commercial probability, project completion dates, availability, skills and resource plans, and project economics.

Typical responses include flagging emerging capacity risk, identifying a possible internal match, triggering a staffing review, re-prioritising commercial activity, re-planning delivery, escalating, assigning ownership, and tracking what the response actually achieved.

In a delivery organisation, people and delivery capacity carry costs whether or not all available time is assigned to paid work. When demand falls below available capacity, those costs can put pressure on margins. The effect depends on pricing, contractual terms, delivery efficiency and the wider cost structure. Operational Intelligence is designed to make that exposure visible early enough for an informed response, with clear responsibility for the action taken.

Margin & Capacity Signal Assessment identifies where value is exposed, which decisions arrive too late and what the smallest useful system should do.

• Economic context. Where margin and capacity currently sit, and what depends on them.
• Decision mapping. Which decisions matter, who currently makes them, and how late.
• Signal inventory. What signals already exist across current systems, and what is missing.
• Risk diagnosis. Where the exposure is largest, and how much time is actually available.
• Minimum system scope. The smallest connected system that would change the outcome.
• Development path. How that system would be built, and by which Nordleid capabilities.

Operational Intelligence is delivered as Chain Development applied to this kind of problem: the business problem is established, the decisions it actually depends on are defined, the signal and data landscape is read against them, a scoped pilot is built and tested, a production system follows, and the system keeps developing as operating conditions change.

Which Nordleid capabilities are involved is composed to the problem rather than fixed in advance. Business & Product Direction and Experience & Service Design typically shape what the decision should look like. Data, Integration & Decision Systems and AI Integration & Automation typically build the connection between the signal and the action. Digital Products, Platforms & Apps and Platform, Reliability & Assurance typically carry the system into production. Ongoing Development & Application Responsibility keeps it accountable to what the business needs next.

Explore Chain Development