Recording time,
with less effort.
An original enterprise time-recording challenge, reimagined as a complete working product. I redesigned the journey, connected the states and built a front end you can actually use.
The problem.
The opportunity.
The task has not changed: record the right time against the right work, then submit a complete week. The design challenge is to make that repeated administrative task feel clear, quick and dependable.
From recording a day to completing a week.
Try the prototype.
A working, clickable prototype made with AI in a short period of time. Try it here, inside the page.
Add the four hours missing from Friday. Choose a WBS and task, enter a location or note, then review and submit the week.
Real inputs. Local sample data. Simulated submission. Nothing is sent to Deloitte.
The journey.
The jobs.
From noticing missing time to submitting a complete week, with a way back when something is wrong.
Explore the journey and jobsShow less
The journey
An explanatory route through the documented product.
- 01Review the day
- 02Add missing time
- 03Choose WBS and task
- 04Save the entry
- 05Check the week
- 06Confirm submission
The jobs behind the screens
- 01
Know what is missing
Compare recorded time with the day and week before deciding what to add.
- 02
Record the right work
Choose a valid WBS, task and duration while keeping a recoverable draft.
- 03
Finish with confidence
Review gaps and errors, correct them and explicitly confirm the week.
The original Deloitte work covered time entry, summaries, reminders and submission across BlackBerry and iOS. I returned to that underlying problem with a new Figma design system, a connected screen journey and an executable front end. The reimagining covers ordinary use as well as missing time, invalid entries, cancelled operations and recovery. AI helped accelerate the design-to-code exploration; the working demo itself uses explicit rules and local sample data, rather than an AI service.
The design
decisions.
Make the day legible, keep precise entry approachable and design the recovery states as carefully as the happy path.
Explore the design decisionsShow less
- 01
Make the day legible
Recorded time, remaining time and the weekly total are visible together. Add an entry without losing track of what still needs attention.
- 02
Keep precision approachable
Choose a WBS and task, record duration or start/finish time, and add a location or note. Real controls, five-minute increments and saved drafts make the interaction tangible.
- 03
Design through the awkward states
Review each day before submission. Missing time, validation, edit/copy/delete, undo, sync and submission recovery belong to the journey—not an afterthought.
Interpret the work.
Keep the decision.
AI can help prepare a draft. The person still checks the work, allocation and time before anything is submitted.
Where, why and how AI fitsShow less
AI accelerated this design-to-code exploration. The working prototype uses explicit rules and browser-local sample data; it does not call an AI service.
The product opportunity is to suggest draft entries from permitted calendar and work context, show the source for each suggestion and flag uncertainty. A suggestion must remain editable and rejectable.
WBS eligibility, duration validation and submission state should come from verified rules. The person confirms the final record; AI should not silently allocate billable time or submit a week.
What this
shows.
A connected Figma workflow and a working front end: add the four hours missing from Friday, choose a WBS and task, save the entry, review the completed week and submit it. The demo also supports preferences, CSV export and deliberate recovery scenarios. This is the depth behind the polished screens.
Explore the evidence and scopeShow less
This is an independent reimagining of the original project, not a released Deloitte product. The demo stores sample data in this browser and simulates sync and submission; it has no employer connection or AI backend. AI-generated suggestions from calendar or work context are a future product direction, not a capability claimed by this prototype.