← All work
Enterprise · B2B SaaSSelf directed case study2026Logistics · Fleet Operations

RouteLogic Velocity

Removing execution friction from the dispatcher's daily workflow.

A self-directed case study exploring a realistic but fictional B2B fleet-operations scenario. It is a product exercise, not professional employment at a SaaS company.

RouteLogic Velocity — Removing execution friction from the dispatcher's daily workflow.

Executive summary

Problem
Fleet Dispatchers were leaving RouteLogic mid workflow to finish time sensitive compliance work in spreadsheets and phone calls, then returning only to update records.
My bet
If compliance verification happens inside the route assignment workflow, dispatchers will complete it in product without Operations Managers losing the reporting they depend on.
What I designed
A narrow One click Compliance Checklist inside route assignment, with automated pass/fail verification and preserved audit logging; one wedge, not a platform rebuild.
How I'd validate it
A 4-week pilot across 3 selected accounts against a 48% → 58% completion target, with Manager adoption guardrailed and ship / iterate / kill rules set in advance.

Success measures

Pilot target, not a measured result. 48% is the modelled baseline; 58% is the threshold I set for a ship decision.

Baseline
48%Compliance workflow completion rate
Pilot threshold
58%+10 percentage points
Guardrail
≤ 2ppManager Reporting Suite adoption decline

The work

01 · The problem

Dispatchers were doing the work outside the product.

Fleet Dispatchers were navigating complex workflows and relying on manual work arounds to complete time sensitive operational tasks. The problem was not simply that RouteLogic lacked capability; execution friction was pushing users toward spreadsheets, phone calls, and external tools before they returned to RouteLogic to update records and complete reporting requirements.

  1. 01Open RouteLogic
  2. 02Encounter workflow friction
  3. 03Move to external tools
  4. 04Coordinate operations
  5. 05Return to RouteLogic
  6. 06Complete reporting
FrictionUser impactProduct risk
Complex workflowsSlower task completionReduced workflow adoption
Manual work aroundsDuplicate effort and data entryOperational inefficiency
Fragmented executionMore context switchingLower trust in the daily workflow
Reporting dependencyUsers return mainly to complete required recordsProduct becomes a system of record rather than the preferred execution tool

02 · What I learned

RouteLogic was trusted for records. The execution moment was where competitors were winning.

The workaround analysis revealed an important distinction. Users still relied on RouteLogic for enterprise data, scale, and compliance; but operational work was increasingly happening elsewhere when speed and simplicity mattered. The product opportunity was not to rebuild the entire platform; it was to identify a narrow, high friction workflow where RouteLogic could help users complete work faster without abandoning the system.

What users needed

  • Fewer workflow interruptions
  • Faster task completion
  • Less manual verification
  • Less duplicate entry

What the business needed protected

  • Required reporting preserved
  • Audit records intact
  • Manager adoption of the Reporting Suite

Future state journey map

The moments redesigned around speed, trust and simplicity.

03 · The product decision

A narrow wedge, protected by guardrails.

I scoped the MVP around a One click Compliance Checklist within the route assignment workflow. The decision was intentionally narrow: reduce manual compliance effort for Fleet Dispatchers while preserving the Reporting Suite adoption that Operations Managers rely on.

Product decisionReason
Focus on compliance workflow completionDirectly addresses a measurable point of friction
Keep the workflow inside RouteLogicReduces context switching and manual work arounds
Provide automated pass/fail verificationMakes compliance checks faster and clearer
Preserve audit loggingProtects operational visibility and reporting needs
Guardrail Manager adoptionPrevents improvement for one user group from harming another

04 · What I built

One click compliance verification inside the existing workflow.

The MVP introduces a One click Compliance Checklist within the route assignment workflow. Fleet Dispatchers can complete compliance verification with automated pass/fail feedback while audit records are preserved for reporting and operational oversight.

  1. 01Route assignment
  2. 02Compliance check
  3. 03Pass / fail verification
  4. 04Dispatch continues
  5. 05Audit record preserved
Primary user
Fleet Dispatcher
Secondary stakeholders
Operations Managers and Customer Success Leads
Core value
Faster compliance completion with less manual effort
Protection
Manager adoption of the Reporting Suite remains a guardrail

05 · Interactive prototype

Experience the core dispatcher workflow.

This interactive prototype demonstrates the proposed RouteLogic Velocity workflow developed as part of this self-directed case study.

Experience the core dispatcher workflow: select a route, run compliance verification, explore pass and fail states, and see how compliance results are automatically recorded for audit.

What you can explore

  1. Select a pending route. Review the route and its current compliance status.
  2. Run compliance verification. Trigger the one click compliance check without leaving the dispatch workflow.
  3. Explore pass and fail states. See how the system handles successful checks as well as compliance failures and blocked dispatches.
  4. See the audit trail. Watch compliance results automatically appear in Recent Compliance Activity.
Explore Interactive Prototype
lilianadeiwa.live

06 · Validation and pilot

A measurable pilot with explicit decision rules.

The pilot was structured to determine whether the One click Compliance Checklist could improve compliance workflow completion for Fleet Dispatchers without negatively affecting Manager adoption of the Reporting Suite.

MeasureDefinition
Primary metricCompliance workflow completion rate
Baseline48%
Target58%
Minimum detectable lift+10% relative improvement
GuardrailManager adoption decline must not exceed 2 percentage points
Pilot duration4 weeks
Pilot scope3 selected accounts
DecisionShip, Iterate, or Kill based on pilot evidence

Project artifacts

  • PRD & MVP scope

    Available on request

  • Future state journey map

    Included below

  • Pilot & GTM plan

    Available on request

What I'd do next

The pilot is the real decision point; not launch day. What I'd validate next is whether the One click Compliance Checklist improves workflow completion for Fleet Dispatchers without reducing Operations Managers' adoption of the Reporting Suite. The evidence would determine whether to ship, iterate, or stop the rollout.

Next case study

Juno PM Prioritization Copilot

An evidence backed AI copilot that helps PMs prioritize with confidence.