Techbanq

Data · decisions

A dashboard nobody acts on is a report with a refresh button

Most dashboards are built from the metrics a system can produce, opened once out of curiosity, and then never returned to. A dashboard that earns its place is built the other way round: start from a decision a specific person makes on a specific rhythm, put the number that settles it in front of them, and leave off everything that does not. In the Gulf that also means it reads in Arabic, because a screen people cannot skim in their own language is a screen they do not use.

Serving Saudi Arabia from our Riyadh office and our engineering hubs in Lahore and Karachi

Market
Saudi Arabia
Written for
COO, Commercial Director
Decision
Build dashboards people act on rather than glance at

Enterprise delivery credentials

  • ISO

    ISO/IEC 27001

    ISO/IEC 27001 certified

Certifications & registrations

The familiar failure

The dashboard everyone opened once and nobody decided from

We do not have an office in Saudi Arabia

We serve organisations there from our Riyadh office and our engineering hubs in Lahore and Karachi, travelling for the parts of an engagement that need to happen in person.

The pattern repeats across organisations. A team commissions a dashboard, a supplier delivers a page crowded with every chart the data could yield, everyone admires it in the launch meeting, and within a month it is a bookmark nobody clicks. It failed not because the charts were wrong but because it was built from what the systems could show rather than from what anyone had to decide. A screen answering questions nobody was asking is impressive and useless at the same time.

A dashboard that gets used is built backward from a decision. We start by naming who looks at it, what they decide when they do, and how often — the head of operations checking each morning whether any site is running behind, the commercial director deciding on Sunday which accounts to chase. Then the design earns every element: the number that drives the decision is large and unmissable, the context that explains it is one glance away, and everything that does not change the decision is left off. Restraint is the feature. A busy dashboard is not more informative; it is harder to decide from, which is the only thing a dashboard is for.

From question to action

Following a single decision from the question to the number that settles it

A dashboard is designed one decision at a time. This is the path a real one takes, and every element on the screen has to serve a step in it or it does not belong.

01

The recurring question

A manager arrives each morning needing to know one thing: is anything off track today.

We identify that question and the threshold that makes the answer yes, so the dashboard leads with it rather than burying it in a grid.

  • The decision
  • The threshold
02

The number that answers it

They need the one figure that settles the question, not a page they have to read to find it.

We place that figure large and first, defined against a governed source so it means the same as it does everywhere else.

  • Headline metric
  • Governed definition
03

The context, one glance away

If something is off, they need to know where and how bad before they act.

We put the breakdown that explains the headline within reach but not in the way, so drilling in is a choice, not a requirement.

  • Breakdown
  • Drill path
04

The action it triggers

The point of the screen is the manager doing something differently because of what it showed.

We test the design against that action: if the dashboard could not change what the person does, it has not earned its place on their morning.

  • The action
  • The follow-up

Two kinds of screen

The difference between a metric that looks busy and one that changes what you do

The two can look similar in a screenshot and behave nothing alike in use. This is what separates the dashboard that gets abandoned from the one that becomes part of a routine.

OptionWhat it answersWho reads itWhat changes afterHow it agesBest for
The vanity dashboardEverything the data can show, whether or not anyone asked.Admired at launch, then no one in particular.Nothing — it informs without prompting an action.Grows more crowded as every request adds a chart.Impressing a room once.
The decision dashboardOne recurring question a named person has to answer.The specific decider, on a known rhythm.A concrete action the reader takes or does not.Stays lean because anything that does not drive the decision is refused.A decision someone actually repeats.

Our role

What we design and what your decision-makers keep owning

  1. 01

    Design from the decision out

    We start every dashboard by naming the decision it serves and the person who makes it, so the design has a test to pass rather than a canvas to fill.

  2. 02

    Bilingual, laid out properly

    We build the Arabic layout as a first-class design that reads right-to-left, not an English screen with the words swapped, because a Gulf reader notices the difference immediately.

  3. 03

    Numbers that agree everywhere

    We define each metric against a governed source, so a figure on one dashboard matches the same figure on another and nobody spends a meeting arguing about which is right.

Which decisions matter enough to earn a screen, and where the threshold between fine and off-track sits, are yours to set; we build the dashboard that puts the settling number in front of the right person and leaves off everything that would only slow them down.

Common questions

What buyers ask

How is a dashboard different from the reports our systems already produce?+

A system report shows you what one system holds; a dashboard is designed around a decision that usually needs several systems joined and a definition agreed between them. The deeper difference is intent. A report is generated because it can be; a good dashboard exists because a named person makes a recurring decision and needs the one number that settles it, without reading a page to find it. If your existing reports already drive the decisions people make, you may not need a dashboard at all — and we would rather tell you that than build a screen that duplicates them more attractively. The value is in serving a decision, not in prettier output.

Should the dashboard be in Arabic, English, or both?+

For most Gulf organisations, both, and the Arabic has to be a real design rather than a translation bolted on. Executives and operators here read fluently in Arabic, and a screen they cannot skim at a glance in their own language is one they quietly stop opening. Building the Arabic properly means laying the whole interface out right-to-left — the reading order, the axis direction, the alignment of numbers — not mirroring an English page and hoping. We build both layouts as first-class and let the reader use the one they think in, because a dashboard is judged on whether it is glanced at and acted on, and language is part of whether that glance works.

Why do so many dashboards get built and then abandoned?+

Almost always because they were built from the data outward instead of from a decision inward. A supplier is handed access to the systems and produces every chart the data supports, the result looks comprehensive, and it dies because comprehensiveness is the opposite of what a busy person needs when they have one decision to make. The abandoned dashboard answers questions nobody asked and buries the one they did. The fix is discipline about what to leave off: we name the decision and the decider first, show the number that settles it, and refuse the charts that do not change what the reader does. A dashboard survives because it earns a place in someone routine, and it earns that by being decided from, not admired.

Next step

Name the decision first

A working session that names the decisions each dashboard has to serve and the person who owns each, before a single chart is placed.