Replicon / Mobile product design

Replicon Timesheets

A timesheet people can read before they save.

My role
Product designer
Partners
Product, support & iOS
Product
Mobile timesheets
Focus
Entry, reuse & visibility
01 / Problem

Recording time had become work of its own.

People needed to understand what they had recorded and make changes without repeatedly opening each entry.

The record should explain itself where people are working.Hours and entry details are brought into the daily view where they can be understood together.
The record should explain itself where people are working.
02 / What exists today

The mobile timesheet put important details several taps away.

Metadata was hidden inside entries, delete was two levels down, and people struggled to understand when their work needed saving. These issues were cataloged by support.

Support’s issue catalog described details and actions kept apart.Entry metadata, deletion and save state sit apart from the timesheet where people need them.
Support’s issue catalog described details and actions kept apart.
03 / What’s wrong

The record was hard to read where people were working.

An entry’s hours and their meaning were separated. Save state was unclear, and repeating or correcting work involved too much movement through the interface.

Reading and correcting an entry required too much movement.A time entry is separated from the context and actions needed to review or change it.
Reading and correcting an entry required too much movement.
04 / What I explored

Bring the entry and its actions into the day.

I explored day cards with visible metadata, a weekly summary, copy and delete at the card, multi-day entry, custom fields and partial-day time off. Product, support and iOS engineering worked with me through the proposed flows.

Bring context and useful actions into the day.Day cards, a weekly summary and entry-level actions explore a more readable timesheet.
Bring context and useful actions into the day.
05 / Low-fi architecture

Connect an entry to the day and the week.

The model keeps client, project, task and activity beside the hours they describe. Daily totals and the weekly summary give each entry a visible place in the period.

System flowHow the pieces connect
Inputs
  • Day in the period
  • Work + time off
  • Entry metadata
The interaction
  1. 01Read the day card
  2. 02Copy or add an entry
  3. 03Review the week
Outputs
  • Visible daily totals
  • Timesheet status
  • Submission

Review → reopen the day → correct the entry.

06 / Wireframes

Add, review and submit in one readable sequence.

These reconstructed wireframes explain the original design. The example entries are illustrative, and the submission example shows a pre-submission state.

Wireframe sequenceExplore the sequence
01 / 03

Read the entry in context

Monday / Timesheet
Mon •Tue •WedThuFri
Work · 4 hours
Client / Project
Task / Activity
Entry details
Time off · 2 hours
Partial day
Add time
01Hours and their metadata sit together. The day selector shows where entries exist.

Reconstructed from the documented design; sample content is illustrative.

07 / Solution

Show the details and keep useful actions beside them.

Day cards expose the entry metadata; copy and delete sit at the card level. The repeat-entry flow and original interface below show how related work and time off fit into the same daily context.

The timesheet flow / 01

Give the empty day a next step.

An empty state explains how to add the first time entry.

A reading of the original interaction design. Example entries are illustrative.

08 / Research

Support’s issue catalog grounded the redesign.

Support stayed involved alongside product and iOS engineering. A further evaluation should check save-state understanding, discovery of repeat-entry controls and recovery from mistakes; the source does not provide those measured results.

Support grounded the redesign; these interactions still need measured evaluation.Questions focus on understanding save state, finding repeat-entry controls and recovering from mistakes.
Support grounded the redesign; these interactions still need measured evaluation.
09 / Outcome

A released redesign with a clearer entry model.

The presentation records release and influence on the wider mobile widget style. It supports the visible changes to the interface, but does not measure a reduction in errors or entry time.

The released entry model also informed the wider mobile style.The released timesheet design connects visible entry context with its influence on wider mobile widget patterns.
The released entry model also informed the wider mobile style.
1ONICA FM

Choose a perspective. Access is approved personally.

Public mode is open to everyone. Other perspectives open by invitation.

Level 010 XP

100 XP to the next level

Your progress stays in this browser.