Fragmented workflow
Composite participants used three or more tools in one review cycle.
Revision Room
Creative review, without the version chaos.
A focused workspace for comparing versions, resolving contextual feedback, approving the right file and delivering with confidence.
00 / Overview
Make the decision visible.
Revision Room keeps artwork, feedback, versions and approvals in one continuous decision trail.
The concept is designed for independent creatives and client teams who need the precision of a professional review tool without professional-tool complexity.
Instead of adding another general collaboration platform, the product stays intentionally narrow: review the work, resolve the conversation, approve the exact version and release the final package.
- Year
- 2026
- Role
- Product strategy, UX/UI and interaction design
- Deliverables
- Information architecture, design system and responsive prototype
- Status
- Interactive concept · Real validation pending
01 / Problem
The file is rarely the problem. The decision trail is.
Creative approvals are often split between messages, email, cloud links, PDFs and calls. The result is a workflow where the latest file, the location of a comment and the meaning of “approved” can all become uncertain.
Synthetic evidence used to structure assumptions · not market research.Version uncertainty
They described difficulty identifying the latest file.
Contextless feedback
Comments arrived without an exact visual location.
Ambiguous approval
Conversational language was mistaken for formal approval.
Integrity note
No real participants were interviewed. Eight composite interviews were created to structure plausible collaboration problems. They are a hypothesis generator, not user evidence.
02 / Product principle
One clear chain from upload to handoff.
- 01Upload V03
- 02Review pins
- 03Resolve feedback
- 04Compare versions
- 05Approve
- 06Deliver
Everything needed to reach a deliberate decision.
- Versioned review
- Pinned annotations
- Resolved and open states
- Version comparison
- Explicit approval
- Final package
Features that would dilute the core workflow.
- Payments and contracts
- Chat and video calls
- Creative-file editing
- AI-generated critique
03 / Core experience
Review work with context.
The dashboard does not compete with the artwork. It shows the current version, the decision owner, unresolved feedback and the next action in one view.
Contextual comments
Feedback stays attached to the right place and the right version.
Every note carries a reviewer, timestamp, comment state and version relationship. Reviewers can resolve a comment without erasing the history behind the decision.
- Open and resolved states
- Exact version relationship
- Visual annotation pins
- Clear decision ownership
04 / Version clarity
Before and after should be obvious.
The comparison view aligns the same artwork in the same position so reviewers can inspect the visual consequence of a decision instead of reconstructing it from memory.
05 / Approval and delivery
Approval is a recorded action, not an interpretation.
The approval step records the exact version, approver, time and optional note. Delivery stays locked until that decision is explicit, while unresolved comments remain visible.
VersionVersion 03
Decision ownerSofia M.
Final packageLinked to the approved file
06 / Responsive behavior
The decision continues away from the desk.
The mobile experience keeps the hierarchy deliberately narrow: artwork first, open feedback next and one clear action at a time.
- Minimum 44 px touch targets
- Legible project metadata
- Persistent version context
- No horizontal interface overflow
07 / UI system
Humanist clarity, precise metadata.
A compact visual language pairs a direct system sans with monospaced metadata. Cobalt signals primary action; cyan, green, amber and red communicate meaningful states without relying on color alone.
- Base rhythm
- 4 px
- Primary accent
- Cobalt · #3E5BFF
- Canvas
- #F5F6F8
- Studio ink
- #111318
08 / Accessibility
Calm, legible and explicit by design.
Contrast
Core combinations target AA contrast and status never depends on color alone.
Keyboard
Comparison, navigation and approval remain operable with visible focus.
Touch
Frequently used controls maintain a minimum target of 44 pixels.
Motion
Transitions support reduced-motion preferences without hiding state changes.
09 / Outcome
One room. One version. One deliberate decision.
The current result is a responsive, navigable product prototype with a focused information architecture and reusable interface system.
What comes next
- Test the end-to-end flow with independent creatives and client reviewers.
- Validate approval terminology and notification priority.
- Run keyboard, screen-reader and 200% zoom checks with real tasks.
Next projectWeb Design for Coffee Shops