Stralya

Data

Decision optimization consulting

The right information, at the moment someone decides, in a form they can act on: decision mapping, analytics embedded in workflows, alerts and dashboards built for action, and trained teams.

Decision mappingEmbedded analyticsTeam training

In short

Decision optimization is the work of improving recurring business decisions by delivering the right data, forecasts or recommendations to the people who decide, at the moment they decide, in a form they can act on. Stralya maps each decision first, then wires analytics into existing workflows and trains the teams who use them.

2 to 4 weeks

Decision mapping

Interviews and observation of how key decisions are made today, with gaps and quick wins.

6 to 8 weeks

Typical pilot

One recurring decision redesigned, data delivered into the workflow, results compared with the old process.

Dubai, Paris

Offices

Senior consultants based in the United Arab Emirates and France, working with teams worldwide.

What is decision optimization?

Most organizations do not lack data or dashboards. They lack a reliable path from information to action. Decision optimization focuses on that path: it takes a recurring decision, such as approving a discount, reordering stock, assigning a technician or escalating a late payment, and redesigns how information reaches the person making it.

The approach is deliberately narrow. Instead of building another reporting layer for everyone, we look at who decides, how often, with what information and under what time pressure. Then we change what they see and when they see it: an alert in the tool they already use, a recommendation with its reasons, or a dashboard built around one question instead of fifty metrics.

The scope can be a single high-volume operational decision or a set of management routines, like weekly performance reviews or monthly planning. In both cases, success is measured by how the decision changes, not by how many people open a report. Our data consulting practice provides the strategy, governance and models that feed these decisions.

Signs your decisions need optimizing

The symptoms are often mistaken for a tooling problem. In practice, they point to a gap between where information is produced and where decisions are actually made, and buying another BI licence rarely closes that gap.

  • Dashboards are built but rarely opened

    Usage drops after launch because the reports answer questions nobody asked, or force people to leave the tool they work in.

  • Meetings review numbers but end without actions

    Weekly reviews walk through charts, but decisions are deferred because the data does not point to what should change.

  • Front-line staff decide without the data that exists

    Sales, operations or service teams make frequent calls on instinct while useful signals sit in a warehouse they never see.

  • The same situation gets different answers

    Two managers facing the same case choose differently, and nobody can say which choice produces better results.

  • Insights arrive after the window to act

    Monthly reports reveal problems that needed action weeks earlier, such as stock running low or a key account going quiet.

These signs do not call for more data. They call for a closer look at the decision itself: who owns it, what triggers it, what information would change the answer and what would make the right choice easier than the wrong one.

What our decision optimization engagement covers

The engagement starts with how decisions are made today and ends with a redesigned process your teams use without prompting. Each deliverable below is tied to a specific decision, never to reporting in general, so every hour spent can be traced to a choice that improves.

  • Decision inventory and mapping

    The recurring decisions that matter, with their owner, frequency, inputs, time constraints and the cost of getting them wrong.

  • Decision design

    For each priority decision, the information needed, the trigger, the format and the place it should appear in the workflow.

  • Analytics embedded in workflows

    Alerts, scores or recommendations delivered into your CRM, ERP, ticketing or messaging tools, where the decision is actually made.

  • Decision-support dashboards

    A small number of views built around specific questions, with thresholds and suggested actions instead of raw metrics.

  • Training and adoption plan

    Hands-on sessions with the people who decide, feedback loops to refine the design, and usage measured after go-live.

Each redesigned decision comes with a short playbook: what the signal means, what action it suggests and when to override it. That playbook is what lets new team members use the system confidently without depending on us or on the colleague who attended the original workshops.

Which decision costs you most?

A decision mapping assessment typically takes 2 to 4 weeks and ends with your priority decisions ranked and a redesign plan for each.

Book a free discovery call

How we optimize decisions: four phases

Every phase involves the people who actually make the decision, not only their managers. Each one ends with something they can test, so the design improves through use rather than through presentations and sign-off meetings.

PHASE 01

Observe

Shadow decision makers, map inputs, timing and outcomes.

PHASE 02

Redesign

Define triggers, formats and where information should appear.

PHASE 03

Pilot

Deliver the new flow to one team and compare results.

PHASE 04

Scale

Roll out, train, measure adoption and refine with feedback.

Observation is the phase that most often changes the plan. Watching a planner or a sales manager work for a few hours reveals constraints a workshop misses: the screen they never leave, the call that interrupts every afternoon, the spreadsheet they trust more than the official report. Senior consultants do this work in person or remotely, and design around what they see.

Alert, recommendation or dashboard: which fits?

The right format depends on how often the decision is made, how much time the person has and how much judgment it requires. We choose per decision, and often combine two formats for the same decision.

FormatBest forExampleLimit
AlertRare events needing fast actionA key account’s orders fall below their usual patternToo many alerts and people stop reading them
RecommendationFrequent decisions with clear optionsSuggested reorder quantity or next best offerNeeds visible reasons, or users ignore it
Decision dashboardPeriodic reviews comparing options or trendsWeekly capacity review with thresholds and actionsFails if it tries to answer every question
Automated ruleHigh-volume, low-risk, well-understood choicesAuto-approving small refunds within agreed limitsRequires monitoring and a clear override path
Playbook onlyJudgment-heavy decisions with good existing dataEscalation criteria for late paymentsDepends on training and regular refreshers

When a recommendation needs a forecast or a score that does not exist yet, we build it through our advanced analytics work as part of the same plan. When the underlying figures are disputed, definitions are settled first with data governance, because no format survives data that people do not believe.

Risks that block adoption

Decision optimization fails when people do not change how they work. The risks below are about behavior as much as technology, and we plan for each of them from the first observation session onward.

  • Alert fatigue

    Too many notifications teach people to ignore all of them. We set thresholds with users and review alert volume after go-live.

  • Recommendations nobody trusts

    A suggestion without reasons feels arbitrary. We show the main drivers behind each recommendation and let users flag when it is wrong.

  • Designing for managers instead of users

    Dashboards built for executives rarely help the person making daily calls. We design with the decision maker, then derive management views.

  • No feedback loop

    Without knowing which decisions worked, the design cannot improve. We record outcomes where possible and review them with the team.

  • Losing human accountability

    Automation can blur who is responsible. Every automated or assisted decision keeps a named owner and a documented way to override it.

Adoption is measured, not assumed. After go-live, we track how often the new signals are used, how often they are overridden and how outcomes compare with the old process. Those observations drive the refinements in the final phase and the review cadence that follows.

Decision optimization pricing

Every engagement starts with a diagnosis and ends with a fixed quote. Durations are typical, not promised, and depend on how many decisions are redesigned and how many tools the new signals must reach.

FormatDurationPrice
Decision mapping assessment2 to 4 weeksFixed quote after diagnosis
Single-decision pilot6 to 8 weeksFixed quote after the assessment
Adoption review cadenceMonthlyMonthly fee quoted at handover

What changes the price: number of decisions in scope, number of tools the information must reach, need for new predictive models and the size of the teams to train.

The quote covers senior consultants only, a defined scope and the deliverables of each phase, including playbooks and training material. Licences for BI, workflow or messaging tools are separate from our fees, and we design around the tools you already pay for whenever they are sufficient.

Decision optimization FAQ

Is this the same as building dashboards?

No. Dashboards are one possible output. We start from a specific decision and choose the format that changes it, which is often an alert or a recommendation inside an existing tool rather than a new report.

Which decisions should we start with?

Recurring decisions with a clear owner, a measurable outcome and data that already exists. High frequency or a high cost per mistake makes a decision a strong candidate. The mapping phase ranks them for you.

Do we need new software?

Often not. Most of the work uses your existing CRM, ERP, BI and messaging tools. When a gap exists, we compare options against your needs and recommend a purchase only if it is clearly justified.

How do you measure success?

By changes in the decision and its outcome: faster response, more consistent choices, fewer missed signals and better results than the old process. Dashboard page views alone are not a success metric for us.

What if people ignore the new process?

Then the design is wrong, not the people. We pilot with one team, collect feedback, and adjust triggers, formats and thresholds until the new flow is easier to follow than the old one.

Can decisions be fully automated?

Some can, when volume is high, risk is low and the rules are well understood. Even then, we keep a named owner, monitoring and an override path. Most decisions are better assisted than automated.

Who needs to be involved on our side?

The people who make the decision, their manager and someone who knows the systems involved. Their time is needed mainly for observation, the redesign workshops and the pilot itself.

Reviewed by

Julien Mauclair

Co-founder, technical delivery · Stralya

Last updated:

Decisions made on instinct? Let’s talk

Reply within 24h · First call, no commitment