Technology & AI · ML & AI

Decide with Data — Daloy Mobility's 90-Day Analytics Mandate

A four-round, advanced data-science-for-decisions simulation set inside Daloy Mobility, a Metro Manila ride-hailing and last-mile logistics platform (~46,000 driver-partners, ~1.9 million trips/week, PHP 24B gross bookings, PHP 4.3B net revenue, near break-even).

4 rounds Executive English, Español

Preview

About this simulation

A four-round, advanced data-science-for-decisions simulation set inside Daloy Mobility, a Metro Manila ride-hailing and last-mile logistics platform (~46,000 driver-partners, ~1.9 million trips/week, PHP 24B gross bookings, PHP 4.3B net revenue, near break-even).

A competitor with venture funding and superior ETA accuracy has entered the market, cancellations have climbed to 14%, and the board has handed the new Chief Analytics Officer a single flagship machine-learning mandate: one quarter (90 days), a PHP 90M budget, and a demand for measurable decision lift in production — not model accuracy.

The board pays for lift, not AUC; the wrong problem, the wrong model, or the wrong threshold burns the team's credibility in a single quarter.

Round 1: frame the prediction problem — score demand forecasting, ETA prediction (cleanest data, but the rival already leads there) and cancellation prediction (messier data, but it targets the 14% rate bleeding margin); define success as a decision outcome, not a model statistic, and weigh business value against data convenience.

Round 2: the core accuracy-versus-cost trade-off — a simple gradient-boosted model (~82%, PHP 15M, 6 weeks, ships in the window) versus a deep spatio-temporal net on raw GPS (~89%, PHP 65M, 14 weeks, past the 90-day window) versus a black-box vendor API; plus the data strategy and an A/B-test measurement design.

Round 3: set the deployment threshold that maximizes cost-weighted business value, not accuracy, knowing a missed cancellation (false negative) costs PHP 180 a trip while a needless intervention (false positive) costs PHP 40 — so the value-maximizing threshold sits well below the accuracy-maximizing 50%; design the human-in-the-loop boundary and a drift-monitoring rollback plan.

Round 4: defend the initiative to the board as decision lift and pesos (not 0.86 AUC), and absorb a live shock — concept drift, a tougher rival, or a privacy regulator querying granular GPS — without over-claiming or abandoning the data-driven discipline.

The math wires the concept's numbers and common errors into sticky, run-defining penalty flags: chasing the high-accuracy model that misses the deployment window yields a brilliant notebook and zero live lift; forgetting the threshold means the model changes no decision; the convenient problem cannot clear the lift bar; an accuracy-tuned threshold leaves money on the table; no drift monitoring lets the lift decay; and reporting accuracy to a board that buys lift risks the next round of funding.

Final KPIs track decision lift (points on the target operating metric), net annual value (PHP M/yr), model accuracy (%) and deployment status — and the defining lesson is that a deployed, value-tuned 82% beats an undeployed 89%.

Who it is for

An advanced simulation for participants used to working with the main frameworks and trade-offs of the subject, designed for executive education and experienced professionals.

How a session runs

  1. The instructor creates a session from the Eureka dashboard and invites the participants.
  2. Participants play 4 rounds. In each one they submit their decisions and the simulation calculates the results.
  3. The simulation can be run in English, Español.
  4. The instructor follows each participant's progress and results from the dashboard, and uses the class results for the debrief.

Decisions participants make

The decisions participants make during the simulation:

  • Which prediction problem gets the single flagship slot?
  • Define success as a… (state the target metric crisply)
  • Write the one-sentence problem statement linking prediction → decision → KPI.
  • How much weight do you give business value vs. data convenience when you choose? (%)
  • Choose the modeling approach under the accuracy-versus-cost trade-off.
  • Data strategy.
  • How will you prove the model created value against a baseline?
  • Engineering throttle: how hard do you push to deploy inside the 90-day window? (%)
  • What does the deployment threshold maximize?
  • Set the intervention threshold — the predicted probability above which Daloy acts. (%)

What participants track

What participants follow on screen as the rounds go by:

  • Decision Lift, Net Value & Accuracy Trajectory

Subjects covered

Designed for courses in ML & AI.

Ready to use Decide with Data — Daloy Mobility's 90-Day Analytics Mandate with your students?

Contact us and we'll set you up with a free trial session.

Contact us