Mosaic's work request system

Mosaic was scaling fast, and the work was outrunning the org chart. Requests moved through chat threads, hallway conversations, and forwarded emails. Nobody owned them. Nothing was recorded. A designer in one time zone would wait on an answer from an estimator in another, and neither knew a request existed. With eight teams spread across six time zones, work didn't get dropped because people were careless. It got dropped because there was nowhere to put it.

I built the work request system to fix that. On the surface it was an Asana-based ticketing system. Underneath, it was a catalog: more than 50 documented request types, and every one had three things attached. A named owner. An SLA. A defined deliverable. If you needed a pro forma, a contract review, a schedule update, or a drone flight, there was exactly one way to ask for it, one person accountable for it, and one agreed definition of done. On top of that catalog we layered integrations, training materials, and workload dashboards.

Here's the part most people miss. The software was the easy half. The hard half was sitting with each team and forcing the questions the tool would enforce: what do people actually ask you for, who owns each of those things, how fast should it turn around, and what does finished look like? Documenting request types with owners and SLAs is org design. The tool just makes the design impossible to ignore.

That design got stress-tested. Over the life of the system, the roles using it turned over more than 100 percent. Every seat changed hands, some more than once, and the system kept running. A new hire didn't inherit a predecessor's inbox and tribal knowledge. They inherited a queue, a catalog of what their role owed the company, and the clock on each item. The process outlived every person in it, which is the whole point of a process. These were pro formas, contract reviews, and schedule changes, not IT tickets, so the volume was never the point. Through all of that turnover the queue kept moving.

It also changed how accountability worked. The dashboards included past-due views, so anyone could see what was late, who owned it, and how long it had been sitting. Status stopped requiring status meetings. Nobody had to chase anyone down or convene a room to find out where things stood. The view was just there, and being visibly late is its own motivator.

The system worked well enough that folding the capability into our own ERP made the product roadmap, which is the strongest compliment a process can get. The roadmap outlived the company. What did pay off, inside the life the system actually had, was the workload data. When the dashboards showed a team's queue growing faster than it could close, that was a hiring signal backed by numbers instead of a manager's gut.

The lesson: if a request has no owner, no deadline, and no definition of done, it isn't a request. It's a hope. Write the catalog first. The software is just how you keep your promises.

More on the platform this sat beside: Building Mosaic's operating layer. Full history: Work.