Decision support tools for people.

A rough problem is enough.

You do not need a specification. Tell me what keeps causing friction or what you are trying to make clearer.

The work on upstream decision making has led to a number of practical tools. These include dashboards, simulators, planning prototypes and debrief systems that help teams see what they are committing to before pressure arrives.

Send a rough problem

The aim is not to tell people what to decide. It is to create better conditions for judgement: clearer information, visible assumptions, usable rehearsal and a record of what was traded.

Some of this work is maritime and pilotage-focused. Some of it is broader. The common thread is simple: decisions always cost something; sometimes it's not noticed until later.

Current work

Decision support tools

Making the decision visible

Small tools that help people see assumptions, margin, cost, people and commitment before they are hidden by pace or pressure.

One clear picture for the day

Dashboards that bring weather, tide, notices, activity, constraints and local links into one practical view.

Rehearsal before pressure

Simple simulation and fast-time tools for exploring plans, turning space, speed, margin and control before the job begins.

Seeing what actually happened

Replay, scoring and review tools that turn a track, plan or exercise into something that can be examined without blame.

From booking to shared awareness

Lightweight planning systems for marine activity, approvals, map displays and the daily operational picture.

Examples in practice

Two sanitised examples of practical tools built around real operational questions. No sensitive operational information is shown.

Operational dashboard

Bringing the day into one view

A private, noindexed dashboard brought weather, tide, notices, local links and status checks into one browser view.

See the sanitised example →Pilotage simulator

Making a manoeuvre discussable

A browser-based rehearsal prototype made speed, turning room, stopping distance, track and margin visible before the operation.

See the sanitised example →

How the work stays aligned

Pull, not push The work starts where there is already resonance, curiosity or a real operational problem. It does not create urgency for its own sake.
Support, not instruction The tools are there to help people examine judgement. They do not replace responsibility or tell people what to decide.
Small before large A simple working version is usually the right first step. The question is whether it changes the conversation.
Operational before polished The tool has to work for people on the day, under time pressure, with the information they actually use.

Start a conversation

Send the rough problem

Tell me what keeps causing friction or what you are trying to make clearer. Matt will read and reply personally.

Prefer email? matt@decisionskill.co.uk