From Data Sprawl to a Single Source of Truth

05Design around decisions

Roadmap|Step 5

Design Around Decisions

Start where friction shows up every day, and design the path from signal to action.

Start with daily friction

With priorities agreed, decide where to start and how information should be organized. Start where friction shows up every day.

The last step of CLEAR is a roadmap: what to tackle now, what comes next, and what can wait.

Then design around a simple path. A signal tells someone that something needs attention. Context tells them what it means. Investigation lets them dig into the cause. Action closes the loop. Most dashboards stop at the signal: a red tile, and then you’re on your own.

From signal to action

Follow one alert along the path. Most dashboards stop at the first step.

  1. Tells someone that something needs attention.

    Gas compression availability on one platform drops below its target.

  2. Tells them what it means.

    One compressor has tripped twice in 24 hours, and the other two trains are running near capacity.

  3. Lets them dig into the cause.

    The trip log points to high discharge temperature, and the cooler was due for cleaning last week.

  4. Closes the loop.

    The maintenance lead schedules the cleaning, and production adjusts the plan for the next shift.

How to apply it

01 / 05
  1. Start

    Choose your starting point.

    Pick the experience people use every day and struggle with most. For many operators, that’s daily reporting and exception handling.

  2. Focus

    Pick one role and one recurring decision.

    Design that well before designing everything.

  3. Path

    Define the path.

    The signal that should catch attention, the context needed to understand it, the route for investigating it, and the action that resolves it.

  4. Tiers

    Sort information into three tiers.

    Always visible, available on demand, and revealed during investigation. Keep the first tier small.

  5. Context

    Add context only when you can name the decision it supports.

    Maps, 3D models and live market data are powerful when they make a decision faster or clearer, and decoration when they don’t.

In the field

The oil and gas company started with daily reporting and exception management, built on its SQDCP core. Context was added only where it helped a decision.

Each view earned its place because some questions are easier to answer when you can see where something is and what it’s connected to.

Context views
05

Where they started

  • Daily reporting
  • Exception management
  • Built on the SQDCP core

Context, only where it helped

  • Hurricane map
  • Price per barrel
  • Flaring by platform
  • Booster gas compressor in 3D
  • Underwater pipelines and wells

What goes where

That path also decides what goes where on the screen. Some information has to be visible at all times. Some is useful only on request. Some only matters once someone starts investigating. Important doesn’t mean equal space.

  1. Always visible

    Keep the first tier small.

  2. Available on demand

    Useful only on request.

  3. Revealed during investigation

    Only matters once someone starts investigating.

Context views