CRE Chat

Overview

CRE Chat replaced a patchwork of informal communication tools (personal texts, Google Chat, WhatsApp, Qualcomm, email, phone calls) with a single auditable platform for driver coordination. The hard part was never building a chat app. It was designing a system that created accountability without adding friction, in a time-sensitive environment where every extra click has a real cost.

The Problem

Operations teams at C.R. England coordinated with drivers through a patchwork of unapproved tools: personal text messages, Google Chat, WhatsApp, Qualcomm, email, phone calls, whatever each team found fastest and whatever their drivers happened to have access to. There was no single channel, no shared visibility, no way to know if a message had even been received, let alone acted on.

Time-sensitive decisions during active dispatch had no documented context. Drivers had unequal access depending on personal devices. Escalation paths were unclear. And when issues arose, there was no audit trail to understand what happened or who was responsible.

The lack of traceability made it impossible to improve processes, resolve disputes, or hold anyone accountable. Every team was solving the same communication problem in its own way, and none of those solutions talked to each other.

Process

1. Discovery Interviews. Led interviews across dispatch, driver management, fleet operations, and roadside support. The pattern was consistent: fragmentation, no traceability, no shared visibility.
2. User Story Mapping. Co-authored 32+ user stories across 5 epics, each tracked from discovery through development. Writing stories surfaced design tensions early — like how hiding other reps' messages breaks context for driver replies.
3. Observing Communication Patterns. Watched teams work in real time, documenting where coordination broke down during time-sensitive situations. Revealed friction they'd stopped noticing.
4. Defining 40+ Use Cases. Mapped every escalation path and edge case with product, engineering, and BAs. Key decision: templates managed by business analysts, not developers — removing a permanent engineering dependency.
5. Designing for Traceability Without Slowing People Down. The core tension: traceability vs. speed. Solution was smart defaults — sender roles, timestamps, and urgency indicators built in automatically, so every message has context without adding friction.

Scoping Version One

Defining what was in scope for version one, and just as importantly, writing down what wasn't, turned out to be one of the most important decisions of the project. It gave the team clarity, set stakeholder expectations, and meant we shipped something complete instead of something half-built.

Key Decisions

Outcome

Delivered an enterprise communication platform that ended the reliance on informal channels and gave the org an auditable record for operational decisions for the first time. Teams got shared visibility with explicit urgency and clear ownership, which let people make faster decisions mid-flow without switching between tools.

The documentation-first approach (interviews, user stories, scope definition, all before design started) meant the development team had clear, unambiguous requirements from day one. Edge cases that would normally surface mid-sprint got resolved before design even began.