TKT—003

Commented

CLIENTCommented Inc.PERIOD2023–2024ROLELead Designer

Removing the account barrier from design feedback without exposing private work

DOMAIN	Feedback Tools
TYPE	SaaS Product
URL	commented.io
TEAM	Lead + 2 designers, cross-functional product team
METHODS	Mixpanel, Hotjar, user interviews
TOOLS	Google Meet (interviews)

OVERVIEW

Commented is a web-based tool that lets teams annotate and leave feedback directly on live websites and staging URLs. Designers share a link with stakeholders, who can click anywhere on the page to leave contextual comments.

PROBLEM

Before this project, Commented required either code embedding or a Chrome extension to collect feedback. External reviewers (often non-technical stakeholders) lacked codebase access and wouldn't install a browser extension. The sign-up wall blocked them before a single comment could be left. Onboarding friction was the primary constraint on adoption and revenue growth.

3-5 minutesOnboarding time

6Steps to first comment

01Receive link

02Realize extension needed

03Install Chrome extension

04Hit sign-up wall

05Create account

06Verify email

First comment

FIG 01 — Old reviewer onboarding: 6 steps before the first comment

PROCESS

01
Discovery
Analyzed onboarding funnels in Mixpanel and session recordings in Hotjar. Conducted user interviews via Google Meet to identify where and why users dropped off.
02
Problem Framing
Defined the core tension: sign-up friction blocked adoption, while users feared exposing unfinished work publicly. Both had to be resolved in the same solution.
03
Design & Prototyping
Designed the public commenting flow: username-only entry modal and a time limited public URL. No account, no extension, no code embed required.
04
Validation
Usability tested the new flow with users to confirm the privacy controls were trusted and the entry path was clear.
05
Delivery
Collaborated with the full product team (design, engineering, and stakeholders) to ship. Led visual implementation of all new UI components.

100%

76%

54%

21%

14%

Link openedExtension promptExtension installedSign-up reachedAccount createdEmail verified

FIG 02 — Onboarding funnel: where reviewers dropped off

KEY DECISION

How do you allow anyone to comment on a live project without exposing it to the public indefinitely?

OPTION A

Require a lightweight account: lower friction than full sign up, but still a barrier for nontechnical reviewers.

OPTION B

Open public URL with no access control: removes all friction but introduces unacceptable privacy risk.

CHOSEN APPROACH

Time limited public URL with username only entry. Owners can revoke access at any time. Privacy is controlled; friction is eliminated.

VISUALS

Username entry screen for accountless reviewers — FIG 03 — Before and after: sign-up wall vs. username-only entry

Modal UI where a project owner initiates public commenting and receives a shareable link — FIG 04 — Public commenting activation modal

Username entry screen shown to account-less reviewers before they can start commenting — FIG 05 — Username entry flow for accountless reviewers

Visitor leaving a contextual comment on a live website using Commented without an account — FIG 06 — Reviewer leaving a contextual annotation on a live project URL

OUTCOME

−50%reduction in onboarding time

Previously, reviewers had to create an account before leaving a single comment. After shipping, the only required step is entering a username. Time to first comment dropped to a single interaction.