Where we help/04

We're making decisions on information we don't fully trust.

Leadership keeps asking the same questions and getting different answers. Dashboards exist but nobody believes them. BI reports contradict each other. At the same time, leadership often can't tell whether the IT organisation is performing, whether constraints are real or organisational, or whether the roadmap they've been shown reflects strategy or internal politics. The result: decisions on instinct rather than evidence, and significant budgets approved without real visibility into whether they will deliver.

A bearded facilitator in a tan shirt drawing with a red marker on a fresh sheet of brown paper, next to a wall covered in dense clusters of coloured sticky notes — roles, owners and process steps.
At the wall · Mapping where data lives, who owns it, and where trust breaks

What leaders actually say

I ask three people the same question and get three different numbers.

We have dashboards but nobody actually uses them to make decisions.

IT tells me it'll take 18 months. I don't know if that's true.

We approved a budget two years ago. I still don't know what we got for it.

What's actually going on

  • Multiple systems holding the same entity with no golden source of record.
  • Data governance either absent or existing on paper but not in practice.
  • No consistent data lineage — nobody knows where numbers come from.
  • IT roadmap presented without business linkage — leadership can't evaluate it.
  • Technical debt used as an excuse for inaction rather than a problem to be managed.
03Where we've seen this

Evidenced by

Top-tier Nordic banks

Customer-definition reconciliation across legal, compliance, audit, and technology; PSD2 and PCI-DSS alignment across a complex legacy payments estate. (Named on request.)

Single signed-off customer-population breakdownSingle coherent PSD2 trajectory
Practitioner — Lars
→

When the answer was don't build it

Danish public sector, multi-year IT initiative.

Walk-away vindicated four years later
Practitioner — Lars
→

How we engage on this

This is where Lars's experience leads. The work usually starts with a Depth Checkto read the situation across business, logical, and physical layers, followed by an Analysisthat produces a written brief leadership can act on — independent of the IT organisation's own narration. Implementation that follows often combines architectural specification, governance, and remediation roadmap. The output is a single defendable answer in a domain where four professional perspectives are each producing their own.

Start here

“When you suspect the picture you're being shown isn't the whole picture, a third independent read is the cheapest move you can make.”

Start a conversation →