
Waiting for a free lane
- 1The status reads Backlog, in the same chip as every other state.
- 2The banner says why it waits and what happens next, one sentence each.
- 3Route request stays live, so operations can still put it in a lane by hand.
Case study · Workspace Global
Workspace Global gives a business a creative team on one monthly plan: design, web, video and marketing. I designed all of it, the client app on iOS, Android and web, and the internal tools that turn a client's message into finished work.



The problem
On Workspace a client never fills in a brief. They type what they need, the way they would text a friend. Behind that message, operations checks and routes it, an art director turns it into a proper brief, and a designer or writer from the talent pool takes it on. Then it comes back to the client for approval.
My job was to make that whole trip feel like one conversation to the client, and like a clear checklist to everyone behind it.
Types what they need in one box, on a phone or the web.
Sees every request in one queue and decides where each one goes.
Turns the summary from operations into a Golden Brief.
Receives a clear brief, picked by name or offered to the pool.
Types what they need in one box, on a phone or the web.

What this screen showsThe client describes the work in their own words. Quick picks cover the most common asks.
Sees every request in one queue and decides where each one goes.

What this screen showsEvery client request in one list, with requester, client, priority and a status from Received to Complete.
Turns the summary from operations into a Golden Brief.

What this screen showsThe brief is written from the summary operations left: title, task points, due date, deliverables, references and files.
Receives a clear brief, picked by name or offered to the pool.

What this screen showsEach part of the brief goes out on its own: the carousel to a named designer, the copy to the pool, where the first to accept takes it.
The client side
Clients are buying creative work, not learning a tool. So every request reads the same way on the web and on a phone: a five-step tracker on the card, each file approved or sent back on its own, and the revision rounds left in plain sight.
Every request card carries the same five-step tracker, so a client can tell where their work stands at a glance.

Each submitted file can be approved or sent back on its own, and the rounds left sit next to the deadline.

When every file is approved the tracker completes, and the final files stay ready to download.

A file opens full screen with two clear choices: approve it, or request a revision.

Behind the request
Fast only helps if what arrives is right. So the internal tools put a person at every handover: one before the work is assigned, one before it leaves the team, and one that decides exactly what the client receives.
The summary is drafted by AI and flagged until someone reads it. Only then can an art director be picked.


Every file from talent is approved or sent back with a note. Nothing here reaches the client yet.


Only work approved inside the team can be picked. The client is notified and the request moves to Delivered.


Going back in
Files reached the client marked Draft, and nothing on the screen could change that. I went back into two screens to put that decision in the client's hands, and kept a before and after of each so the team could see exactly what moved.

BeforeAfter
BeforeAfterAsking for changes does not create a third state. The file stays a draft until it is approved, and a line under it tells the client what happens next.


The system underneath
A client's plan comes with a set number of lanes. Each lane works on one request, and anything else waits its turn, then starts by itself when a lane frees up. The rule only works if nobody has to remember it, so I wrote it into the screens: every waiting request says why it waits and what happens next.


Shipped
Workspace Global is in clients' hands today. Everything on this page is the product as people use it, designed end to end by me.



Requests, files, brands, campaigns, meetings and billing, on iOS, Android and the web.
The Ops dashboard for operations, value creation and revenue, with the request lifecycle at its centre.
Where designers and writers pick up briefs, send their work and track their points.