Annotations turned Wake’s running design stream into a place where feedback could be precise, fast, and easy to act on. I led the end-to-end product design for on-canvas comments that link directly into Wake’s conversation stream. The work focused on removing ambiguity in reviews, reducing duplicate feedback, and shortening the time from post to resolution.
Beyond the feature itself, this project was about strengthening a core promise of Wake: that sharing in-progress work should feel lightweight, and that feedback should help teams move forward instead of getting stuck in long, ambiguous threads. Annotations needed to feel native to how teams already used Wake, while quietly raising the quality and traceability of every design conversation.
Problem
Wake’s stream captured the story of a project but not always where feedback applied on the canvas.
This led to:
Vague comments that required follow‑up (“this nav,” “the blue button”)
Designers exporting circled screenshots just to clarify a single point
Duplicate feedback on the same UI element
Teams bouncing between Wake and other tools that did support on‑canvas comments, fracturing the single-stream experience
Design Challenge: Make feedback unambiguous and spatially anchored to x/y coordinates, while keeping the stream as the single source of truth.
Goal
Bring precise, on-canvas feedback into the existing Wake stream so teams keep context without introducing a new mental model or extra workflow.
Make feedback unambiguous. A reader should know exactly what a comment refers to.
Preserve the narrative. Annotations must show up in the same stream so teams can skim chronologically, search, and share to Slack like they already do.
Reduce review time. Shorten time to first actionable comment and time to resolution.
Avoid visual noise. Keep mocks readable at any density and any zoom level.
Ship on Mac app, responsive web, and iOS with consistent behavior.
Approach
I combined qualitative research with product and technical constraints to shape the solution.
Research and Discovery
Interviewed designers, PMs, and engineers on 6 Wake‑heavy teams
Observed critiques and async reviews using Wake
Collected lightweight diary notes on when feedback felt slow or brittle
Constraints
Feedback must remain in the existing stream (no separate “review mode” tool).
Performance had to stay strong with large images and long threads.
Core behavior needed to work on Mac, web, and iOS.
Annotations had to be discoverable by first‑time reviewers (often arriving from Slack).
Existing posts and comments had to keep working with no migration.
Solution
Concept: Pins as First‑Class Stream Objects
Annotations became on‑canvas pins tightly linked to the conversation stream. Reviewers can click or tap directly on the canvas to drop a pin, type feedback, and submit it in one motion; Wake then generates a corresponding stream entry with a thumbnail, author, and deep link back to the exact location.
That object stays navigable and maintainable over time: selecting a stream post smoothly pans and zooms to the pinned region, highlights the pin, and opens the thread, and once the conversation is resolved the pin collapses into a subtle state to reduce clutter while preserving history. Together, this creates two equally valid ways into the same feedback—from the stream for chronological skimming and quick jumps into context, and from the canvas for in-place review while scanning the UI.
Interaction Details
To balance clarity and readability, we defined clear pin states, tuned visibility rules for dense canvases, and added fast keyboard navigation and reliable deep-link behavior across surfaces:
We defined a clear set of pin states—idle, hover, focused, and resolved—to keep the canvas readable at a glance while still making active feedback feel unmistakable. Most of the time pins stay intentionally quiet; only the focused pin expands to reveal its text, so attention goes to the one conversation you’re working on without losing the surrounding context.
To stay usable in dense designs, overlapping pins collapse into a count badge, with simple ways to step through or disambiguate them as you zoom or navigate. We also treated navigation and access as first-class requirements: reviewers can jump between unresolved pins with J/K or the arrow keys, follow a logical tab order with visible focus rings, and rely on deep links (from the stream, Slack, or notifications) to land on the exact pinned region every time.
Outcomes
In pilots with internal teams and early customers, teams reached a useful comment sooner, saw less repeated feedback on the same region, and reported fewer clarification loops. Designers also relied less on marked-up screenshots to explain where feedback applied.
Pilot feedback also described broader participation in critique. Annotations remained in the existing stream and connected to Slack. Anchored, resolvable threads made feedback easier to revisit in context.
Next Opportunities
If I extended this work, I’d explore:
Batch Triage: Tools to select multiple pins and assign, label, or resolve them in one sweep, especially for design leads reviewing large critiques.
Smarter Anchors for Responsive Layouts: Better heuristics (beyond coordinates) to keep pins meaningful as artboards resize or layouts reflow.
Review Analytics: Heatmaps and alerts for clusters of unresolved feedback to highlight risk areas before handoff.