⚔️ THE ATTEMPTNot Selected2026

Waypoint Dispatch Intelligence

Tech-Triathlon 2026 Designathon | Waypoint Group

A shared delivery-operations concept connecting dispatchers, drivers, loaders, and store managers through role-specific views of one delivery record.

Engineering Role

Team Lead & Full-Stack Developer

Sprint Duration

Five-day Designathon phase

Team Configuration

Legacy Aurora

Outcome Status

Did Not Advance

Delivery OperationsFour User RolesOffline-FirstDesignathonWaypoint Group

01 // PROBLEM DOSSIER

The Challenge & Core Problem

High-Level Briefing

The design blueprint frames Waypoint Group’s core issue as fragmented information, not simply logistics. Dispatchers plan from spreadsheets, drivers report by paper and phone, loaders use stale lists, and store managers lack delivery confirmation and reliable ETAs.

Formal Technical Problem Statement

"Create a shared source of truth for deliveries, with role-specific workflows that help teams plan, load, update, and confirm deliveries even when drivers lose connectivity."

Hard Timebox & Rules

Five-day Designathon phase

The proposal was grounded in analysis of more than 90,000 delivery records.
Fresh deliveries had to arrive before 8 AM, within a 270-minute Fresh trip budget.
The Designathon scope excluded route optimization, real-time traffic maps, multi-depot coordination, consumer tracking, and inventory management.

Open Risks & Pressure Factors

Drivers in hill-country routes face intermittent connectivity, so the mobile workflow must work offline and sync later.
Dispatch plans must account for vehicle capacity, trip budgets, van-only outlets, mall delivery windows, and deferral history.

02 // LEADERSHIP & ARCHITECTURE

Leadership & Personal Contribution

Team Lead & Full-Stack Developer

Led team Legacy Aurora and contributed as its full-stack developer.

Developed the product strategy around shared delivery awareness across four operational roles.

Defined role-specific screen flows and degraded-connectivity scenarios for the Designathon submission.

Real-Time Architectural Dilemmas Under Clock Pressure

DILEMMA #1

Should the Designathon concept prioritize route optimization or the information gaps affecting each delivery role?

➔ Action Taken: Focused the design on a shared delivery record and four role-specific workflows, leaving route optimization to a separate competition phase.

Engineering Rationale: The submission prioritizes the information fracture identified in its data analysis and keeps the five-day scope focused.

DILEMMA #2

How should the driver workflow behave on routes with poor mobile coverage?

➔ Action Taken: Designed an offline-first route view with local progress updates and automatic sync when connectivity returns.

Engineering Rationale: The blueprint highlights hill-country delays and connectivity loss as operating conditions, not exceptional cases.

03 // SYSTEM ARCHITECTURE

The Technical Solution

The concept gives dispatchers a command dashboard, drivers an offline-first route app, loaders a live reverse-order loading list, and store managers delivery status, ETAs, and receipt confirmation.

Data Flow & Architecture

Each role works from a shared delivery record. Dispatchers create plans and assign vehicles, loaders confirm items and flag shortages, drivers record arrivals or issues with offline sync, and store managers track ETAs and confirm receipts.

Critical Data Pipelines

[1]Dispatchers plan orders against vehicle capacity, trip budgets, time windows, and deferral history.

[2]Loaders use the current plan to confirm items in reverse delivery order and report shortages.

[3]Drivers record arrivals, issues, and proof of delivery, saving updates offline until synchronization is available.

[4]Store managers receive delivery status and ETA updates and confirm receipt or report discrepancies.

04 // RETROSPECTIVE

The Retrospective: What Worked & What Needs Work

What Worked

✓The blueprint reframed the challenge around information silos and a shared delivery record.
✓Four role-specific interfaces were grounded in Sri Lankan locations, devices, and connectivity conditions.
✓The submission explicitly scoped out features that did not fit the five-day Designathon phase.

What Still Needs Work

✕The team was not selected to advance to the next stage.
✕The blueprint lists persona validation and an interactive prototype as planned next steps, not completed submission evidence.