Mobile Timesheets, the never ending…

I guess most companies have their own sea snakes. The Mobiles Timesheets was one of ours. The project consists in offering a mobile experience of the desktop Timesheeting module in Sciforma. This mobile experience project had been initiated by Camille Despringhere (ex-Sciforma, now eBay Product Designer). At that time, he had conducted user research, as well as multiple design iterations, and was finishing up the project before implementation. We would meet each week, and I would help with specific pain points, giving him another vision and an exterior point of view.

After a freezing period, this project has been re-opened by our new Product Team, composed of resources from both Sciforma and One2Team.

The project has been delivered on my last week of work, and I am very proud of all that''s been done. Kudos to all the team.

Simple: we want users to be able to declare how much time they have spent working on what tasks, each day/week/month. This helps project managers track time spend on projects, and therefore adapt them to real life.
The desktop version is for all users. The 2 main use cases/persona for the mobile are:
-Friday Night Submitters "Went offsite and realized you forgot to submit your timesheet? You need quick access to do so before reaching home. Every day, every week, your choice"
-Offsite workers “You are not an office worker and you find it tedious to connect to Sciforma only for that? Just take out your phone and fill in your Timesheet wherever you are”
The main features are:
-Ability to enter time on tasks, whether they have been planned by the user’s manager or not
-Declare non-working tasks such as sick days or training hours
-Submit a timesheet that complies with the company’s rules (min/max hours, on working days)
-Review comments or reworks by the manager
-Check status on past Timesheets

This is the process that the team followed… until we got to the initial deadline and started doing everything at the same time. Whoops.

Building Blocs

User Flow

The first task was to identify the mobile use cases from the desktop version. With the project manager, we then prioritized the features for the MVP. That gave us a rough idea of the screens that needed to be designed.
Prototypes

Several of them were created, to challenge the user flow, validate hypotheses, or get a better idea of the full experience. I like to use prototypes early in the design process, as they help refine the scope. They also help defining the right scale for elements on mobile.
Later, a more general “happy/most common path” prototype is created to provide development teams with a bigger picture, rather than chopped up into user stories. This also includes transitions or animations that are invisible on fixed mockups.
User Stories

The full flow is broken down by the project manager into user stories that are documented with functional specifications. Our job is to provide design mockups to illustrate each use case.
Component Building

For our designs to be consistent, and in order to industrialize our process, we create design components that we are able to reuse across the board. These are also linked to the master design system of the product.