A day in ita day inside wayworks
Five departments. The same four steps.
Every one of these is an ordinary question somebody asks on an ordinary Tuesday. What is worth looking at is not the question — it is the four steps underneath it, and the fact that they are the same four whichever department is asking.
the ask is ordinary.
that’s the point
- 01The ask
Typed in the conversation someone already has open — no new tab, no new password.
- 02The route
wayworks resolves who is asking, what they may see, and which process this belongs to.
- 03The work
The three items are reassigned inside the process that owns them, not in a spreadsheet beside it.
- 04The record
Who asked, what changed, and when — kept with the work rather than in a chat thread.
What is written down afterwards
- Three reassignments, with the reason
- A note on the blocked credit check
- The four-day wait, now visible as a pattern
- 01The ask
A manager’s question, in plain language, on a phone.
- 02The route
Only the people this manager is allowed to see are in the answer.
- 03The work
The request is raised and the reminders go out as part of the joining process.
- 04The record
The joining checklist shows what was missing and when it was fixed.
What is written down afterwards
- An equipment request, raised
- Two reminders, with their history
- A joining checklist that is now current
- 01The ask
Asked once, rather than assembled from three exports.
- 02The route
Policy and thresholds are part of the workflow, not a document about the workflow.
- 03The work
The item is routed to the right approver with the rule that sent it there.
- 04The record
The approval carries the policy it was tested against.
What is written down afterwards
- One routed approval, with its rule
- A note on three threshold exceptions
- An audit line that already exists
- 01The ask
A status question that does not need a status meeting.
- 02The route
Work items, messages and the deploy history are the same record, so the answer does not need to be assembled.
- 03The work
A chase is drafted for a human to send; a ticket is opened where the work is.
- 04The record
The blockage and its cause stay attached to the project.
What is written down afterwards
- A drafted client message, unsent
- One ticket, linked to the deploy
- Two blockers, dated
- 01The ask
One question instead of a weekly export and a pivot table.
- 02The route
Tickets, the product backlog and previous reports are the same base, so “raised before” is answerable.
- 03The work
The tickets are grouped and the pattern is sent onward.
- 04The record
The third occurrence is on the record as the third, not the first.
What is written down afterwards
- Eleven grouped tickets
- A pattern with its history
- One item on the product list, with evidence
The honest part
These are illustrations.
They are written from the processes the platform is built around, not from a customer’s week we are allowed to publish. When we can show a real one, it will be named as a real one — and until then we would rather label these clearly than let them read as case studies.