Glossary

Decision Structure

The backbone that turns scattered KPIs into a path for judgment.

Decision Structure is the underlying logic that connects KPIs, drivers, and actions into a clear path through the dashboard. It defines what comes first, what follows, and how people move from “what happened” to “what we do next.”

Definition

What we mean by “Decision Structure”

Decision Structure is the explicit arrangement of metrics, views, and questions so that decisions can be made in a consistent order. It makes clear which KPI represents the outcome, which metrics explain changes, and which signals suggest the next reasonable step. Without it, dashboards feel like lists, not arguments.

Why it matters for decisions

Why this changes how people read a dashboard

When Decision Structure is missing, every review starts from a different place. People jump between charts, pick their favourite slice of data, and leave with different stories about what is happening. Even strong analysts struggle to align on the same “path” through the numbers.

  • Outcome KPIs are mixed with explanatory and reassurance metrics, so no one is sure which graph should anchor the conversation.
  • Two people can look at the same dashboard and walk away with conflicting priorities, because the structure does not nudge them through the same steps.
How it connects to symptoms

When you will feel this term in real life

You notice weak Decision Structure when dashboards feel busy but do not tell you where to start or how to move.

  • Too many KPIs on one dashboard — everything looks important, so nothing guides the order of discussion.
  • Meetings drift — people keep opening new pages instead of following a consistent flow from outcome to cause to action.

Decision Structure gives a quiet “script” for how to walk a dashboard, even when that script is never written down.

Related guides

Decision Structure runs underneath all Decision Guides, but is most visible here:

See also

Related terms in this glossary

Decision Structure sits alongside these ideas:

This glossary is a reference, not an entry point. Start from a Symptom or Decision Guide, then return here when you need to name the structure under the dashboard.

Where to go next
Use Decision Structure to quietly script how your team walks the dashboard.
Open the Decision Breakdown Guide