Case Study: Wake Versioning: Design History Without the Overhead
Wake helps design teams share in-progress work and get feedback without breaking flow. Versioning turns a loose stream of uploads into a clear visual history of how designs evolve over time, so teams can quickly answer: What changed since last time? Why did we choose this direction? I led 0 → 1 product design for Versioning across web, iOS, and macOS defining how snapshots are captured, stacked, compared, and discussed within Wake’s existing stream (the main activity feed where teams share work and leave feedback). I led the end‑to‑end design of on‑canvas annotations across Mac, web, and iOS. The goal was to make feedback precise and traceable without breaking Wake’s simple, stream‑based mental model.Wake helps design teams share in-progress work and get feedback without breaking flow. Versioning turns a loose stream of uploads into a clear visual history of how designs evolve over time, so teams can quickly answer: What changed since last time? Why did we choose this direction? I led 0 → 1 product design for Versioning across web, iOS, and macOS defining how snapshots are captured, stacked, compared, and discussed within Wake’s existing stream (the main activity feed where teams share work and leave feedback). I led the end‑to‑end design of on‑canvas annotations across Mac, web, and iOS. The goal was to make feedback precise and traceable without breaking Wake’s simple, stream‑based mental model.
What I Did
Product Leadership
UI/UX
Research & Interviews
0→1
Team
Product Leadership
UI/UX
Research & Interviews
0→1
10hr
Faster time to consensus
Faster
With inline version compare
1 Thread
For every design history
Problem
Wake’s stream (its main activity feed) was great for seeing what people were working on, but weak at showing history.
Iterations were scattered across multiple posts like “Homepage v2” and “Header refinement.” That split the discussion and led to duplicate questions plus constant “which version is this?” confusion. Teams tried to patch the gap with hacks like naming files “v3 / final_final,” digging through old posts, or linking out to design tools.
Wake needed a lightweight way to bundle related iterations into one durable narrative without turning into heavy version control.
Insights
Teams wanted version history to live inside Wake so they could share work fast and stay in flow while still trusting clear timestamps and brief human notes over automated diffs.
On the implementation side, Sketch document IDs and art board identifiers emerged as reliable anchors for tying uploads back to the right version stack.
Solution
We treated each post as a container for a stack of snapshots, not a single upload.
How it works:
Designers share art boards from Sketch via the Mac app, just as before. Wake uses Sketch document + art board IDs to decide whether to:
Create a new item (new art board), or
Add a new snapshot to an existing item (same art board).
Each snapshot stores image, author, timestamp, and an optional user-generated note like “Header nav tightened 8 px.”
Inside the post, Versioning adds:
Inline history view to browse snapshots over time without leaving the stream.
Compare mode to scrub through versions or pick two snapshots for side‑by‑side comparison via a simple slider.
A conversation model that separates threaded comments for big-picture decisions across versions. Snapshot-specific annotations for precise, on-canvas feedback.
The result is one canonical thread where visuals, comments, and annotations evolve together.
Key design decisions
One thread, many snapshots: Use underlying IDs instead of fragile filenames so updates are predictable and safe.
Compare in place: Keep history and compare inside the post, rather than on a separate history page, so reviewers never lose context.
Conversation-first: Preserve a single comment thread while anchoring precise feedback to individual snapshots.
Prioritize reliability and speed: Deprioritize heavy automation and one-click restore in the MVP in favor of predictable stacking, fast capture, and a simple, stream-centric mental model.
Impact
We measured how Versioning changed sharing and review behavior.
Outcomes:
Duplicate posts per project dropped from dozens to just a few as teams learned to update existing posts instead of creating new posts.
Conversation consolidated around canonical threads, increasing comments per post and reducing “which version is this?” confusion.
Teams reached design consensus faster, spending less time reconstructing history before reviews.
Stakeholders reported higher confidence that they were looking at the latest version and could still see “how we got here” in one place.
Qualitatively, designers described Versioning as turning Wake from a stream of screenshots into a living project history.
Next Opportunities
Future improvements included letting reviewers tag key snapshots with milestone labels like usability testing, stakeholder review, or dev handoff. We also saw room for optional visual diff overlays on complex screens when teams need finer change detection. Longer term, deeper integrations with design tools and source control could capture important versions automatically at commits or merges and project-level overviews could highlight where work is changing and where feedback is still unresolved.