ANUSHREE ROY PRODUCT DESIGNER
← SELECTED WORK

Version control that starts with the document.

I redesigned a broad, timeline-first file versioning concept into a focused workflow for reviewing and managing editable documents.

Role
Product design
Focus
UX strategy, flows, interface
Iterations
Two design directions
Status
Design concept
New document-first version control screen, with the document central and details and timeline at its side
The redesigned entry point places the document at the centre of the experience.FINAL DIRECTION · V2

01 / OVERVIEW

Making history useful in the moment.

The goal was to give teams a way to keep track of evolving files, review proposed changes, and return to earlier versions. I began with a wide scope: one version control experience for documents, PDFs, images, audio, and video.

As the first design took shape, feedback exposed a more basic issue. People had trouble finding their way through the workflow. The screen that appeared first was a timeline of activity. It explained what had happened to a file, but did not make the file itself or the next action clear.

The design question became: how might version history support the work people came to do, without becoming the first thing they have to understand?

02 / THE FIRST DESIGN

A system built around its history.

V1 opened in a Review Room with the timeline selected. Upload, pending reviews, and version history were separate destinations. This made sense as a map of the system, but it asked people to interpret a history of events before reaching the document.

Earlier Review Room interface opening on the timeline
The earlier entry point showed a list of updates and statuses before the document.V1 · TIMELINE FIRST
01 / SCOPE

Too many file types

The same versioning idea had to account for many formats and different ways people work with them.

02 / ENTRY POINT

The wrong first screen

A timeline was useful for looking back, but did not answer “what am I working on?” or “what do I do next?”

03 / FEEDBACK

The problem was bigger than navigation labels.

The feedback was that V1 felt complicated and difficult to navigate. I looked at the first screen and the breadth of the product together. Changing a label would not resolve the underlying order of the experience: it still led with the system’s history rather than the user’s document.

I decided to reduce the scope to editable documents only. Other file types are excluded from the redesigned version control workflow. That gave me a clearer object to design around and a more coherent path from editing to review.

“Start with the document. Bring in version history when it becomes relevant.”

V1 timeline screen
BEFORE · The timeline is the starting point
V2 document screen
AFTER · The document is the starting point

04 / RETHINKING THE FLOW

From files and events to people and decisions.

I mapped the relationship between an owner and contributors on a whiteboard. The questions included whether version control should apply to one document or a folder, what a contributor could submit, how an owner would review a proposed version, and what should happen after approval or rejection.

That exploration helped define a more legible workflow: a contributor proposes a change, the owner reviews it in the context of the document, and the decision becomes part of its history. Comments and reversion remain available when needed.

Whiteboard ideation mapping owner and contributor roles, proposed versions, owner review, comments, and revert
Early flow mapping for contributor submissions, owner review, comments, and reverting.PROCESS ARTIFACT
CONTRIBUTOR

Propose a version

Give a change a title and description, attach the revised document, and send it for review.

OWNER / REVIEWER

Make a decision

Inspect the proposed changes, discuss them, then approve or reject the submission.

USER FLOWV2 · CONTRIBUTOR AND OWNER
Version control user flow: a contributor proposes a version and the owner decidesContributor: open the document, download a copy and edit it, go to Commit Version, add a title, description, file and reviewers, and send it for review. Owner: go to Review Changes, inspect the changes in the document, and decide. Approve: V2 becomes the current version, and any version can be reverted later. Suggest changes: the owner adds comments and it goes back to the contributor. Reject: V1 stays the current version. Each outcome is logged in the timeline.CONTRIBUTOROWNER / REVIEWERAPPROVESUGGEST CHANGESBACK TO THE CONTRIBUTORREJECTContributor opensthe documentDownload a copyand edit itGo to CommitVersionAdd a title,description, fileand reviewersSend for reviewGo to ReviewChangesInspect the changesin the documentOwner’scall on V2Add commentsV2 becomes thecurrent versionAny version can bereverted laterV1 stays thecurrent versionLogged inthe timelineVersion control user flow: a contributor proposes a version and the owner decidesContributor: open the document, download a copy and edit it, go to Commit Version, add a title, description, file and reviewers, and send it for review. Owner: go to Review Changes, inspect the changes in the document, and decide. Approve: V2 becomes the current version, and any version can be reverted later. Suggest changes: the owner adds comments and it goes back to the contributor. Reject: V1 stays the current version. Each outcome is logged in the timeline.CONTRIBUTOROWNER / REVIEWERAPPROVEREJECTSUGGEST CHANGES · BACK TO EDITINGContributor opensthe documentDownload a copyand edit itGo to Commit VersionAdd a title,description, fileand reviewersSend for reviewGo to Review ChangesInspect the changesin the documentOwner’scall on V2V2 becomes thecurrent versionV1 staysthe currentversionLogged inthe timelineAny version can bereverted later
My whiteboard flow, cleaned up. On the board the outcomes were perfect, changes and reject; in the product they’re Approve, Suggest changes and Reject, and each one is logged in the timeline.USER FLOW

05 / KEY DECISIONS

Three shifts shaped the redesign.

01 · FOCUS THE SCOPE

Design for editable documents

Concentrating on one kind of work made the review and version flow easier to define. The new design does not include other file types.

02 · CHANGE THE ENTRY POINT

Open the document first

The current document is the anchor. Its details and recent activity remain visible, while the fuller timeline becomes a destination for looking back.

03 · CONNECT REVIEW TO CONTEXT

Bring decisions closer to the change

Reviewers can inspect a submission and comment, approve, or reject in one flow rather than treating review as a disconnected activity list.

06 / THE NEW EXPERIENCE

One document, with its work around it.

V2 centres the document and organizes the supporting actions into Home, Review Changes, Commit Version, Timeline, and Settings. The surrounding panels keep the current version, contributors, and recent activity within reach.

01 · LAND

Begin with the document

The document opens as the primary view. Highlighted changes and a side panel connect the content to its version details and recent activity.

Document with highlighted changes and a contextual timeline
Document content stays visible while the user explores changes.V2 · DOCUMENT VIEW
02 · REVIEW

Evaluate a proposed change

A review item expands to show the submitted document. The reviewer can comment and make an approval decision alongside that submission.

Expanded review submission with document preview and approve or reject actions
A proposed change and its decision controls appear together.V2 · REVIEW CHANGES
03 · COMMIT

Explain the next version

The version form asks for a title, description, attached document, and reviewers. These fields give a proposed revision a reason and an audience.

Commit new version form with title, description, attachment, and reviewers
The submission records what changed and who should review it.V2 · COMMIT VERSION
04 · TRACE

Keep the past accessible

The dedicated timeline brings together status, author, comments, and reversion controls for moments when someone needs to inspect the document’s history.

New timeline view listing changes, authors, review status, and revert
History remains available without becoming the first screen.V2 · TIMELINE

07 / STYLE GUIDE

White and grey, so the document leads.

Colour is saved for meaning: blue shows where you are, green and rose show what changed, and amber marks what's still waiting for review. The type splits the same way, with a clean sans for everything you scan and a serif for the document's own name.

STYLE GUIDEV2 · COLOUR AND TYPE
NEUTRAL
White#FFFFFF
Pages, panels and the document itself
Grey#F2F2F2
The tray that holds the document preview
Charcoal#4C525E
The main button, Commit New Version
Blue tint#F1F8FF
Behind the active tab and selected rows
ACCENT AND STATUS COLOURS
#3B83F6Active tab, links and the timeline
#C7F8C1Text that was added
#FCC9C5Text that was removed
#E0AE20Waiting to be reviewed
TYPOGRAPHY
Report_Feb_2025_Draft V4
A Garamond-style serif for the document's own name and panel titles like Details and Timeline.
A clean sans for everything you scan (names, dates, tabs and buttons) and a serif for the document's name, so the file always feels like the main thing.
Regular for reading. Medium for the one button that matters, Commit New Version.
Regular 400Medium 500

08 / REFLECTION

The first screen defines the mental model.

This project taught me to question the order in which a product reveals its complexity. Version history is central to the system, but people need to see the document and understand their task before a timeline is useful.

The redesigned concept addresses the feedback through a tighter scope and a document-first flow. A next step would be to test V2 with people completing specific tasks—finding the current document, reviewing a proposed revision, and returning to an earlier version—to see where uncertainty remains.

This case study documents the design process and qualitative feedback on V1. No measured outcome for V2 is claimed.