Stephanie Oley

Why your numbers need a translator – not a presenter

When technical teams struggle to explain the 'why' behind their metrics, business momentum stalls. Here are three tactics to try.
05.08.2026
Why your numbers need a translator

Data never truly speaks for itself. When technical analysts or finance managers drop raw metrics into an executive paper without context, they leave the interpretation entirely to chance. This often leads decision-makers to jump to the wrong conclusions.

It’s a concept known as confirmation bias – our natural human tendency to process information in a way that aligns with our own beliefs. When technical professionals present naked figures, stakeholders inevitably project their own assumptions onto the page. That’s a risk that can have costly implications.

Instead, embed a team approach of translating data so the reader is always guided past their biases and towards the true narrative.

Context gives numbers their value

Whether your team is presenting financial forecasts to a board or reporting safety metrics in heavy industry, numbers without context are like map coordinates but no topography. To help decision-makers land in the right place, leaders must coach their specialists to build context around three key areas:

  • Baseline validity – Make sure that date ranges and comparison periods reflect normal operations rather than an anomaly. Don’t let a one-off asset sale or seasonal disruptions distort the whole narrative.
  • Proportional scale – Be transparent about small-base percentages. A line item showing a ‘100 per cent increase in complaints’ sounds alarming until leaders realise the figure moved from two complaints to four.
  • Correlated factors – Make sure that any cost increases or profit margin shifts are linked to their underlying operational causes, such as deferred maintenance spending or inventory build-ups.

Testing data narrative with AI

Team leads can speed up the process of interpreting data by using generative AI as a sounding board to test whether a data story is clear or misleading. For example:

  • During drafting: Have your analysts input key figures alongside their proposed narrative to check for logical gaps.
  • During review: Prompt AI to play the role of an inquisitive board member:

‘Act as a non-executive director in a commercial enterprise. Review these key financial metrics and bullet points. Identify three potential misunderstandings or missing contextual factors that might cause a reader to jump to the wrong conclusion.’

This quick step ensures your team catches data distortions before the report reaches executive hands.

Help your team translate data into action

When technical teams struggle to explain the ‘why’ behind their metrics, business momentum stalls. Give your analysts or department managers the practical frameworks to present data with clarity and authority.

More Articles

Why your numbers need a translator

When technical teams struggle to explain the ‘why’ behind their metrics, business momentum stalls. Here are three tactics to try.

Read More
Picture of audience in auditorium

When a business case or board paper stalls, the issue is rarely a lack of technical expertise. It’s almost always a failure of stakeholder alignment – burying critical decision-making points beneath slabs of irrelevant detail.

Read More

The five-slide mandate: Why executive caps on presentation decks are really about cognitive discipline.

Read More
Scroll to Top