← Work

Workwize Onboarding Case

Workwize's design case for a Senior Product Designer role: a delivery date means nothing until it is judged against the day the new hire starts.

Year
2026
Track
design
Category
case-study

Tools

  • Concepts
  • Figma
  • Claude Code

In October 2026 Workwize, a platform that ships, tracks and takes back IT equipment for distributed companies, set me a design case for a Senior Product Designer role: find the problem worth solving in how IT admins order equipment, and design the fix in high fidelity. My answer is one rule. A delivery date means nothing until it is judged against the day the new hire starts, so the design checks that one date at three moments, before the order, at the order and after it, and when a parcel comes back the admin hears first, with the recovery ready. I sent ten slides, a journey map, a Figma file and a working prototype. It was a hiring exercise and nothing shipped. Every screen on this page is that prototype, on made-up people and orders.

Open the prototype

  1. Order 48244 for Yusuf Arslan, just placed. A green line reads Ordered for Yusuf. The headline reads Arrives Fri 9 to Wed 14 Oct, 7 days before the start, with two tags, On track and Nothing to do, and Supplier and warehouse lane estimate, calculated today 14:05. Under it a line runs from today to the start date: a green band for the arrival, then a mark reading starts Wed 21. A timeline below runs from Order received, placed by you, up to Delivered. On the right, Yusuf, a marketing lead in Groningen, starts in 15 days, on Wed 21 Oct, from BambooHR, his address confirmed by him, and the kit, 3 items in 2 shipments. Workwize's navy sidebar on the left, with Onboarding chosen and the line Prototype. Every person, company and order is fabricated. at its foot.

Prototype. Every person, company and order is made up.

It runs. See it running, at the foot of this page, opens the prototype at its own size in a new tab.

The admin orders, then chases

Workwize's brief named four pains. Unclear when equipment arrives was the second, and three customer quotes came with it. One of them, paraphrased as my deck printed it: tracking says early, and I still check every day whether it lands before Monday. I read the three quotes as three symptoms of one missing thing. The admin carries that question through every screen, and no screen answers it.

Whose problem first: the IT admin's. The order starts with them, Workwize's Terms make their company the party, and only they can act when something goes wrong. The new hire receives, so ordering by the new hire is left out. The admin's job, as I wrote it down: the right equipment before day one, without chasing, and to know early if it is at risk.

Delivery certainty passes all four tests

The research was done at a desk. I read the brief, Workwize's public API documentation, its Terms and its public pages, and I tallied 45 public voices from review sites and Reddit. I never saw the live product and I contacted nobody at Workwize. 27 of the 45 voices are invited reviews, so the positives are probably inflated, and the sharpest complaints sit inside those invited reviews. It is not a statistical sample, and no public number says how often an order misses a start date.

Four candidate problems came out of the brief and the tally. I put each through the same four tests, and one passes all four. Cost and fees is the loudest theme, but it is mixed and it is a commercial question, so I left the price out on purpose. Retrieval comes after the order. And Workwize's Terms already promise notice of a delay.

Workwize points at itPublic voicesBreaks day oneFixable at the order
Delivery certainty: told latePasses. 1 of its 4 pains, all three recent quotesPasses. Silent failure: 12 of 14 negative, none positivePasses. YesPasses. Yes: the data is on the order
Cost and feesFails. NoFails. 10 of 21 negative, 9 positiveFails. NoPartly. Clarity yes; the price is commercial
Selecting devicesPartly. Named, no quoteFails. 9 of 20 negative, 7 positivePartly. RarelyPasses. Yes
Retrieval and redistributionPartly. Pains 3 and 4, no quoteFails. 3 of 9 negativeFails. NoFails. After the order
  1. Delivery certainty: told late

    Workwize points at it
    Passes. 1 of its 4 pains, all three recent quotes
    Public voices
    Passes. Silent failure: 12 of 14 negative, none positive
    Breaks day one
    Passes. Yes
    Fixable at the order
    Passes. Yes: the data is on the order
  2. Cost and fees

    Workwize points at it
    Fails. No
    Public voices
    Fails. 10 of 21 negative, 9 positive
    Breaks day one
    Fails. No
    Fixable at the order
    Partly. Clarity yes; the price is commercial
  3. Selecting devices

    Workwize points at it
    Partly. Named, no quote
    Public voices
    Fails. 9 of 20 negative, 7 positive
    Breaks day one
    Partly. Rarely
    Fixable at the order
    Passes. Yes
  4. Retrieval and redistribution

    Workwize points at it
    Partly. Pains 3 and 4, no quote
    Public voices
    Fails. 3 of 9 negative
    Breaks day one
    Fails. No
    Fixable at the order
    Fails. After the order

Two of the three recent quotes in the brief track a device against a start date; the third heard of a failure from support. The Terms promise delay notice.

45 public voices · the brief · Terms · API

Go deeper

The 45 voices: 10 from G2's first page, 17 from Capterra, 5 from Trustpilot and 13 from Reddit that read as first-person experience. 27 are invited reviews, with an incentive behind them. Reddit is seeded by Workwize and by competitors. Counting the voices that raise each theme, negative first, then mixed, then positive:

  • Exceptions and silent failures: 14 voices, 12 negative, 2 mixed, none positive.
  • Delivery certainty, lead time and start date: 13 voices, 10 negative, 1 mixed, 2 positive.
  • Tracking and status accuracy: 10 voices, 7 negative, 1 mixed, 2 positive.
  • Notifications and channel: 5 voices, 4 negative, 1 positive.
  • Price and fee clarity: 21 voices, 10 negative, 2 mixed, 9 positive.
  • Ordering and product selection: 20 voices, 9 negative, 4 mixed, 7 positive.
  • Support and account team: 20 voices, 4 negative, 3 mixed, 13 positive.
  • HR sync, automation and integrations: 18 voices, 4 negative, 2 mixed, 12 positive.
  • Retrieval, returns and offboarding: 9 voices, 3 negative, 3 mixed, 3 positive.

Across the three themes after the order, 29 of 37 mentions are negative and 4 positive. That is a count of who said what, never a rate.

The start date is never shown

Then I mapped the journey as the brief's four screens show it, with the public API and the Terms beside them, and no live observation. Eight stages, from the start date landing to day one. The platform already holds the start date, through the employee record, and every shipment carries its failure states and a history. None of the brief's screens shows either. So the admin learns of a problem from support, days later, and what the order shows is a lead time, not an arrival. Two of the severe failures are Workwize's own, a parcel stalled at the warehouse and a device marked delivered that is not in stock. Workwize's newer public screens show a status line and an estimate in weeks; the claim here is about the screens in the brief.

The highest-leverage move was not a new screen but a join between two things the platform already holds.

I scored the fixes by reach, severity relieved and data readiness, each from 1 to 3. Two of the three score the full 27, because the data is already on the order.

  1. Fix A.

    Start date

    Opt-in reminder, no order-by day

  2. Pick the person

    Start never shown

  3. Risk 2, a lead time, not an arrival.

    Pick the products

    No arrival date

  4. Fix B.

    Place the order

    Binding, Cancel shown

  5. Risk 1, told late, by support.Fix C.

    Processing

    No stall state

  6. In transit

    Tracked by hand

  7. Arriving

    Estimate: unavailable

  8. Day one

    The hire tells

Told late, by support A lead time, not an arrival The start date, never shown

Highest leverage, scored of 27

  1. Fix A:

    Judge every date against the start date

    reach 3 × severity 3 × data 3

    27 of 27

  2. Fix B:

    Make the confirm the commitment

    reach 3 × severity 3 × data 3

    27 of 27

  3. Fix C:

    Tell early, with whose move

    reach 3 × severity 3 × data 2

    18 of 27

Reach × severity relieved × data readiness, each from 1 to 3.

One date, three moments

A notice, a timeline or an estimate can only say late against a start date, so the start date comes first and every other fix hangs off it. The new flow keeps the journey's eight moments and checks the one date at three of them. Before the order: who starts soon with nothing ordered, grouped by whose move, with the day to order by. At the order: the date comes from the HR system and is confirmed, not typed, and every product is sorted by when it arrives against it. After it: the estimate drawn as a line against the date, one timeline in plain words, whose move it is, and the recovery ready before anything goes wrong. Every screen answers five questions: what do I know, what do I predict, how sure, whose move, and what can I do now.

The same eight moments as the journey above. A number marks where each check happens.
  1. 1 · Before the order

    1. Check 1, before the order.

      Start date lands

      Order-by day shown

  2. 2 · At the order

    1. Employee and date

      Date from HR

    2. Check 2, at the order.

      Choose by arrival

      Sorted by arrival

    3. Review and place

      What locks, said

  3. 3 · After it: told early

    1. One timeline

      House words, dated

    2. Check 3, after it: told early.

      Told early, once

      One Slack thread

    3. Prepared recovery

      Default and options

    4. Day one

      Confirmed, or covered

I drew it on the iPad first, over sheets with an empty screen frame on them. Five of the sketches are below, each beside the screen it became. The first sketch was the flow itself, four boxes with a Slack message as the trigger, and it froze as the eight moments above.

  1. A hand drawn order page over a pale wireframe. Delivery at Risk, with a bar half green and half red, and a note: each option updates the line, the estimation algorithm. Est delivery Nov 2. A green Primary button and a More options button, with a note: hidden on purpose, discoverability risk, no cognitive load. Then, depending on the situation, one action to solve. A timeline from Order placed up to Receiver is not at address.
  2. Order 48213 for Elif Demir. The headline reads Coming back to sender: nobody home on Tue 6 Oct, with two tags, At risk and Your move. Under them: Workwize holds the parcel until you choose; resends Thu 8 Oct 16:00 if nobody acts, tagged assumed. The line runs to starts Mon 26, with an outlined band for Tue 13 to Thu 15. What happened: UPS tried her address at 09:12, nobody home, and the parcel returns to the Workwize warehouse. A card marked Recommended, in time, without customs, Elif confirms the day: Resend to her confirmed address, arrives Tue 13 to Thu 15 Oct, 11 days before the start, with Resend and Other options. On the right, Elif, a product designer in Amsterdam, starts in 20 days. Workwize's navy sidebar on the left, with Onboarding chosen and the line Prototype. Every person, company and order is fabricated. at its foot.
  1. A hand drawn order page. Est Time Oct 23 to 26, over a line from today to the worst case date with a green band and a person's mark for the start date, and notes on how it is calculated and a small laptop moving along it. A timeline of stages from In transit, the carrier, UPS Netherlands, and on the right the receiver, John Doe, the address and the items sent, under an Actions menu. Beside it: options for comms? Slack, Mail.
  2. Order 48244 for Yusuf Arslan, just placed. A green line reads Ordered for Yusuf. The headline reads Arrives Fri 9 to Wed 14 Oct, 7 days before the start, with two tags, On track and Nothing to do, and Supplier and warehouse lane estimate, calculated today 14:05. Under it a line runs from today to the start date: a green band for the arrival, then a mark reading starts Wed 21. A timeline below runs from Order received, placed by you, up to Delivered. On the right, Yusuf, a marketing lead in Groningen, starts in 15 days, on Wed 21 Oct, from BambooHR, his address confirmed by him, and the kit, 3 items in 2 shipments. Workwize's navy sidebar on the left, with Onboarding chosen and the line Prototype. Every person, company and order is fabricated. at its foot.
  1. A hand drawn order step split in two. On the left, Sending, with three rows to choose from, and a note that you can still change the items; an arrow carries the chosen row across. On the right, John Doe, the address, a calendar tile reading Oct 26 for the starting date, and Est date as a line with a green band before the start. Above it: what if we do out the head split? and good mental model, sending these to the person.
  2. Create order for Yusuf Arslan, step 1 of 3, Employee and date: Who is this for, and when do they start? Yusuf is chosen, with the standard kit, and Send to offers Employee, Office and Warehouse, Employee chosen, to his confirmed home address. On the right, his start date, Wed 21 Oct, in 15 days, from BambooHR, with Change, which tells the HR manager on Slack. Under it the line from today to the start, and Order by Mon 12 Oct to arrive before the start. Workwize's navy sidebar on the left, with Onboarding chosen and the line Prototype. Every person, company and order is fabricated. at its foot.
  1. A hand drawn product step. Selecting for John Doe, start date Oct 26, Sort by and Filter, with a note that you can filter out non delivery in time. Three product rows, each ending in a line against the start date, the last running past it in red. Beside them: sort by ETA and show with ranges. Above: this whole step can be more flexible.
  2. Step 2, Choose products for Yusuf. The standard kit suggests four items that together arrive Fri 9 to Wed 14 Oct, 7 days before the start, with Add all 4 and Choose one by one. Below, filters for Arrives in time, Your stock and New from suppliers, sorted by arrival. Each row has its own line against starts Wed 21: a MacBook Pro 14 from your stock arrives Fri 9 to Tue 13 Oct, before the start, with express offered for Wed 7 to Thu 8 Oct. Workwize's navy sidebar on the left, with Onboarding chosen and the line Prototype. Every person, company and order is fabricated. at its foot.
  1. A hand drawn onboarding list. A toggle between a calendar and a row view, with a note that the calendar should be uncomplicated, 4 weeks or monthly. Three groups, Failed, At risk and On track, each opening with a caret. Each row has a person, their items and a line against the start date, red past it for Failed, green then red for At risk.
  2. Onboarding, starts in the next 8 weeks from BambooHR, with a key to the line: in time, covered by a loaner, not ordered yet, the start date, order by. Under Your move, four people. Sofia Marques starts Mon 12 Oct, At risk, not ordered, and express still makes it. Yusuf Arslan starts Wed 21 Oct, Not ordered, good time to order, order by Mon 12 Oct, with Start order. Elif Demir starts Mon 26 Oct, At risk, coming back to sender, nobody home, with Pick option. Daan Visser starts Tue 27 Oct, Not ordered, no rush, order by Fri 16 Oct, suggested day Mon 12 Oct, with Schedule. Under Workwize is on it, Jonas Weber, On track, stuck at the warehouse, next update by 16:00. Then On track, six people. Workwize's navy sidebar on the left, with Onboarding chosen and the line Prototype. Every person, company and order is fabricated. at its foot.

Prototype. Every person, company and order is made up.

Go deeper

What I weighed along the way, one line each. The readiness list grouped by whose move or by verdict. A calendar view beside the list, which the test killed. The start-date check inline on the rail rather than as a gate before step 2. Products as rows rather than a card grid. One prepared move on the order rather than a menu of actions. The failure headline as the event rather than the verdict. Costs on the confirm page rather than on a layer of their own. One way to draw the line against the start date at every width. A gesture to confirm, decided against on desktop. A confirm that tells rather than one that is tight. And the order window as a selector, which was logged and then built inside the scheduling sheet.

One IT analyst tried it

Then one person tried it. An IT analyst, not a Workwize customer, who onboards four or five people a month and keeps five to seven laptops on a shelf. One session of about thirty minutes on a video call, recorded with consent, thinking aloud through the live prototype: the onboarding list, a new order, a returned order and a stalled one. The Slack alert was not shown. The core idea held. The groups by whose move read without help, and on the returned order he took the recommended resend. Two controls did nothing when pressed, and three things were too quiet: own stock against new, the missing kit item, and a row with ten days of slack. Three things he said changed the design, and ten changes followed in all. One session validates nothing. The next round would be the same test with five admins from Workwize's customers.

Now I could resend.

Read the groups unaided; took the recommended resend

  1. I prefer list.

    Killed.

    The lanes view, the day it was tried. It was removed after the session.

  2. No, it's too early.

    Now: no rush.

    1. Onboarding, starts in the next 8 weeks from BambooHR, with a key to the line: in time, covered by a loaner, not ordered yet, the start date, order by. Under Your move, four people. Sofia Marques starts Mon 12 Oct, At risk, not ordered, and express still makes it. Yusuf Arslan starts Wed 21 Oct, Not ordered, good time to order, order by Mon 12 Oct, with Start order. Elif Demir starts Mon 26 Oct, At risk, coming back to sender, nobody home, with Pick option. Daan Visser starts Tue 27 Oct, Not ordered, no rush, order by Fri 16 Oct, suggested day Mon 12 Oct, with Schedule. Under Workwize is on it, Jonas Weber, On track, stuck at the warehouse, next update by 16:00. Then On track, six people. Workwize's navy sidebar on the left, with Onboarding chosen and the line Prototype. Every person, company and order is fabricated. at its foot.

    Daan's row on the start list: no rush, with the day to order by.

  3. So in this case, I control the stock.

    Keeps laptops on a shelf: a second persona to test

    1. Step 2's product rows for Yusuf, sorted by arrival, each with Your stock or New and its own line against starts Wed 21. A MacBook Pro 14 from your stock arrives Fri 9 to Tue 13 Oct, before the start. A used MacBook Air 13 from your stock in the UK crosses customs, arrives Mon 12 to Wed 14 Oct, before the start. A new MacBook Pro 14 from Apple arrives Wed 14 to Mon 19 Oct, before the start. A new Lenovo ThinkPad X1 Carbon arrives Tue 27 to Thu 29 Oct, after the start, in red. Workwize's navy sidebar on the left, with Onboarding chosen and the line Prototype. Every person, company and order is fabricated. at its foot.

    Every product row now says Your stock or New.

One session with one IT analyst, not a Workwize customer; the Slack alert was not shown. Next: five customer admins.

Prototype. Every person, company and order is made up.

Go deeper

The ten changes, in the order they were made. Express became a choice on the row, carried into the kit's estimate. Your stock against new from a supplier became a visible pill on every row, with a filter for each. The missing kit item reads as the next action. A row with room to spare says no rush, and when to order by. The lanes view went. Send to became a segmented control with a line naming the destination. The chosen person's strip lost its filled block. Two dead controls got handlers, and the change-date layer confirms after saving. An early order can be written now and scheduled for a suggested day, with the stock reserved at once, under a new group, Scheduled. And an assistant builds the kit with the admin and says why for each item. The last two came after the session, not from it.

The order starts from the start date

The order as sent, in five screens. The onboarding list opens on who starts in the next eight weeks, grouped by whose move, each row with its line against the start date and the day to order by. Step 1 takes the person, and the start date arrives with them from the HR system, confirmed by the admin and never typed; changing it tells the HR manager. Step 2 sorts every product by when it arrives against that date, your own stock beside new from a supplier, and a pick that would land after the start is allowed and confirmed, never blocked, because arrival is the sort and not a gate. A suggested kit comes with a reason for each item. Step 3 says what locks when you place it, the address and the items, which is what Workwize's Terms lock at submit. Placing is a commitment, so the order becomes the parcel on the person's card and the estimate becomes the line.

An order for Yusuf

Onboarding, starts in the next 8 weeks from BambooHR, with a key to the line: in time, covered by a loaner, not ordered yet, the start date, order by. Under Your move, four people. Sofia Marques starts Mon 12 Oct, At risk, not ordered, and express still makes it. Yusuf Arslan starts Wed 21 Oct, Not ordered, good time to order, order by Mon 12 Oct, with Start order. Elif Demir starts Mon 26 Oct, At risk, coming back to sender, nobody home, with Pick option. Daan Visser starts Tue 27 Oct, Not ordered, no rush, order by Fri 16 Oct, suggested day Mon 12 Oct, with Schedule. Under Workwize is on it, Jonas Weber, On track, stuck at the warehouse, next update by 16:00. Then On track, six people. Workwize's navy sidebar on the left, with Onboarding chosen and the line Prototype. Every person, company and order is fabricated. at its foot.
Who starts in the next eight weeks, grouped by whose move.
Create order for Yusuf Arslan, step 1 of 3, Employee and date: Who is this for, and when do they start? Yusuf is chosen, with the standard kit, and Send to offers Employee, Office and Warehouse, Employee chosen, to his confirmed home address. On the right, his start date, Wed 21 Oct, in 15 days, from BambooHR, with Change, which tells the HR manager on Slack. Under it the line from today to the start, and Order by Mon 12 Oct to arrive before the start. Workwize's navy sidebar on the left, with Onboarding chosen and the line Prototype. Every person, company and order is fabricated. at its foot.
The start date comes from the HR system. Confirm it, never type it.
Step 2, Choose products for Yusuf. The standard kit suggests four items that together arrive Fri 9 to Wed 14 Oct, 7 days before the start, with Add all 4 and Choose one by one. Below, filters for Arrives in time, Your stock and New from suppliers, sorted by arrival. Each row has its own line against starts Wed 21: a MacBook Pro 14 from your stock arrives Fri 9 to Tue 13 Oct, before the start, with express offered for Wed 7 to Thu 8 Oct. Workwize's navy sidebar on the left, with Onboarding chosen and the line Prototype. Every person, company and order is fabricated. at its foot.
Every product sorted by when it arrives against the start.
Step 3, Review and place: What locks when you place it: the address and the items. The kit for Yusuf, 3 items in 2 shipments, each with its arrival, and a warning: No mouse chosen, it is in the standard kit. The kit arrives Fri 9 to Wed 14 Oct, 7 days before the start. Then the address, with a lock, the start date from BambooHR with 2 setup days before it, and the costs. Workwize's navy sidebar on the left, with Onboarding chosen and the line Prototype. Every person, company and order is fabricated. at its foot.
What locks when you place it: the address and the items.
Order 48244 for Yusuf Arslan, just placed. A green line reads Ordered for Yusuf. The headline reads Arrives Fri 9 to Wed 14 Oct, 7 days before the start, with two tags, On track and Nothing to do, and Supplier and warehouse lane estimate, calculated today 14:05. Under it a line runs from today to the start date: a green band for the arrival, then a mark reading starts Wed 21. A timeline below runs from Order received, placed by you, up to Delivered. On the right, Yusuf, a marketing lead in Groningen, starts in 15 days, on Wed 21 Oct, from BambooHR, his address confirmed by him, and the kit, 3 items in 2 shipments. Workwize's navy sidebar on the left, with Onboarding chosen and the line Prototype. Every person, company and order is fabricated. at its foot.
Placed. The estimate becomes the line.

Prototype. Every person, company and order is made up.

Go deeper

Where the date comes from, and what happens without one. The start date is read from the employee record the HR system fills, and the admin confirms it rather than typing it. A person with no start date gets no verdict, since there is nothing to judge against, and the admin can add a date by hand. When HR moves the date, the order's line moves with it. The address goes to the new hire to confirm in one tap, because it locks when the order is placed.

Prototype. Every person, company and order is made up.

When it goes wrong, the admin hears first

The failure is the deepest part of the prototype. Order 48213, placed for Elif, is coming back: nobody home. The headline is the event in plain words, not a carrier status. Under it the verdict, at risk, and whose move, yours. If nobody acts, Workwize resends to her confirmed address on Thursday at 16:00. That default is tagged assumed on the screen, because what Workwize does today is unknown, and it would be my first question for operations. One option is recommended, with its reason and the new arrival against the start, and the rest are one click away. The carrier's own text sits behind a disclosure, so the admin reads one vocabulary.

On the phone the Slack message carries the same words and the same buttons. Nothing is sent while an order is on track, and there is one thread per order, edited in place, so there is never a stale option to press. The resend takes one press, and the order says what you chose.

  1. Order 48213 for Elif Demir. The headline reads Coming back to sender: nobody home on Tue 6 Oct, with two tags, At risk and Your move. Under them: Workwize holds the parcel until you choose; resends Thu 8 Oct 16:00 if nobody acts, tagged assumed. The line runs to starts Mon 26, with an outlined band for Tue 13 to Thu 15. What happened: UPS tried her address at 09:12, nobody home, and the parcel returns to the Workwize warehouse. A card marked Recommended, in time, without customs, Elif confirms the day: Resend to her confirmed address, arrives Tue 13 to Thu 15 Oct, 11 days before the start, with Resend and Other options. On the right, Elif, a product designer in Amsterdam, starts in 20 days. Workwize's navy sidebar on the left, with Onboarding chosen and the line Prototype. Every person, company and order is fabricated. at its foot.

Prototype. Every person, company and order is made up.

Coming back to sender, on a phone

A Slack thread for order 48213 for Elif Demir, marked Mock, at phone width. Workwize's message reads: Elif's laptop is coming back to sender. Nobody home on Tue 6 Oct. Then What happened, and Recommended: resend to her confirmed address, arrives Tue 13 to Thu 15 Oct, 11 days before the start. The line to starts Mon 26. Whose move: yours, until you choose, Workwize holds the parcel. If nobody acts: Workwize resends to the confirmed address on Thu 8 Oct at 16:00. Three buttons: Resend to confirmed address, Other options and Open order.
The Slack message: the event, the recommendation, whose move.
Order 48213 at phone width, under Workwize's navy bar and a strip naming Elif Demir, starts Mon 26 Oct, address confirmed. Coming back to sender: nobody home on Tue 6 Oct, At risk, Your move, and the default if nobody acts tagged assumed. The line, and What happened. Resend and Other options are fixed at the foot.
The order, told the same way.
The same order scrolled to the recommended card: Resend to her confirmed address, arrives Tue 13 to Thu 15 Oct, 11 days before the start. Elif gets a one-tap check by text to confirm the day. Resend and Other options, then the timeline: Resend, if you choose it, Coming back to sender, Delivery attempt failed.
The recommended resend, with the new arrival against the start.
The order after Resend: Resending: arrives Tue 13 to Thu 15 Oct, 11 days before the start, now On track and Workwize is on it. A green note reads You chose: resend to the confirmed address. Text sent to Elif to confirm the day. Slack message updated.
Chosen. The order says what you chose, and the Slack thread is updated.

Prototype. Every person, company and order is made up.

Prototype. Every person, company and order is made up.

Go deeper

The failure states that can be walked in the prototype: returned to sender, a stall at the warehouse, a customs hold, no estimate yet, a late pick at ordering, a missing start date, an unconfirmed address, a start date moved by HR, an overdue parcel with no scan, late but covered by a loaner, an order-by day passed with nothing ordered, a kit in two shipments, the undo window, nobody acting on a failure, two vocabularies, and the scheduled order's three cases. Fourteen more are documented as frames, from a delivery after the start to a second failure on the same order. Who hears when a company has many admins was left out. Lost or damaged parcels, wrong items, returns, invoices, approvals and the new hire's own tracking page were not designed at all.

Two slots, never mixed

Before the rule, every row said its state in one slot and the words drifted. Not ordered showed in grey, amber and red. Workwize is on it came in two tones. Needs you and your move named one idea, and late but covered sat in green inside on track. A word that changes colour, or two names for one idea, makes the admin learn the screen twice. So every row and every order says two things, in two slots, and a word never moves between them or changes colour. The verdict slot answers one question, will it be there on day one: on track, covered or delivered for yes, at risk or overdue for maybe, late for no, and grey when nothing is judged yet. The whose-move slot has one name per actor: your move, Workwize is on it, the new hire's move, customs' move, nothing to do. An event, coming back to sender or stuck at the warehouse, never takes the verdict slot; it leads the reason or the headline. So a parcel stuck at the warehouse can still be on track, with Workwize on it, which is the point. Six states of one order are below. Late shows on a row in the prototype, and no order page renders it.

One order, six states

6 states

State
Order 48213 for Elif Demir reading Arrives Wed 7 to Thu 8 Oct, 18 days before the start, tagged On track and Nothing to do. Workwize's navy sidebar on the left, with Onboarding chosen and the line Prototype. Every person, company and order is fabricated. at its foot.
on track

Nothing to do.

covered

Nothing to do.

at risk

Nothing to do. We tell you if it tips.

overdue

Workwize is on it. Next update by 16:00 today.

stuck at the warehouse

Workwize is on it. Still on track if it ships by Thu 8 Oct.

held at customs

Customs' move. No estimate until it is released.

Prototype. Every person, company and order is made up.

The first two weeks, then six

None of this ran. What went with the prototype is a plan in two parts. The first two weeks check the riskiest assumption before anything is built: is the delivery estimate usually right? Week one compares past estimates with real arrivals, route by route, while Workwize's own IT team places a real order and sees a new state of the prototype each day. It ends with a decision on how exact the promise can be. If the estimate fields are mostly empty, or arrivals fall outside the range on most routes, the promise becomes a date we confirm rather than a range. Week two ends with what gets built first. The measures are proposals. What the gap costs Workwize today is unknown, and no number stands in for it.

Then the six-week cut: build first what today's data already supports. One designer and two engineers is the frame of the question, not a known Workwize team. The sizes come from the journey map's effort per item, and engineering would confirm them at the end of week two, before anything is built.

A plan. Nothing in it ran.

The first two weeks: check whether the delivery estimate is usually right, before anything is built

Measure of success: new hires with their device delivered and confirmed before they need it, per route.

Leading signs: time from a shipment problem to the admin knowing; at-risk orders acted on the same day.

  1. Check past estimates against real arrivals: Week 1.

  2. Follow a real order with Workwize's own IT: Both weeks.

  3. Interview admins, then test the prototype: Most of both weeks.

  4. Measure what late devices cost today: Week 1.

  1. End of week 1: decide how exact the promise can be
  2. End of week 2: decide what to build first

Then test: alerts sent by hand to five busy accounts, then switched on route by route, so every account gets them and only the timing varies. Stop if over half the alerts prove false, or mutes or ordering time rise.

Build first what today's data already supports

The six-week cut: one designer and two engineers ship First; Next and Later are cut.

  1. First · the data exists today

    • Show the start date on every order

      S size · engineering

    • Show each item's arrival against it

      M size · engineering

    • Alert once when a shipment fails or may miss the start

      M size · engineering

  2. Next · needs an operations rule

    • Schedule an order for a later day

      To size in week 1 · ops

    • Show each recovery's cost before the choice

      To size in week 1 · ops

    • Share one order timeline with support

      L size · data, ops

  3. Later · needs new data

    • Spot a parcel stuck at the warehouse

      To size in week 1 · data

    • Undo after placing, and customs updates

      To size in week 1 · ops, data

    • An ordering agent that checks the start date

      To size in week 1 · engineering

Left out: ordering from the HR system, employee self-ordering, catalogue, approvals, pricing, offboarding, invoicing, reporting

Week 1 sets how exact First's arrivals can be; First also covers orders from the HR system.

What went to Workwize: ten slides, the journey map, the Figma file and the prototype, and I presented it in the interview. Every person, company and order in it is made up. I built it.

More case studies

See all 31