Spreadsheets drift
Rotation rules live in rows, colors, comments, and memory. After a few sessions, nobody is sure whether the order is still fair.
Critique Queue
Run design critique without the spreadsheet.
Critique Queue keeps presenter rotation fair, visible, and auditable, so recurring design reviews start faster and no one loses their place when they skip.
Product flow
From presenter selection to a visible queue update.
The facilitator selects presenters, composes multiple sessions, and keeps the queue visible so the team understands why people were selected or skipped.
Company access
Switch companies without mixing critique queues.
The same signed-in person can be invited into multiple company accounts. Inside each company, critique workspaces stay separate.
The problem
Critique rotation should not depend on memory.
Availability breaks fairness
People on vacation or overloaded get skipped, then accidentally lose their place or come back in the wrong order.
Facilitators become referees
When selection feels subjective, the person running critique has to explain why someone was picked again.
What it replaces
Keep the tools. Replace the rotation glue.
Figma, FigJam, Slack, and Calendar can stay where they are. Critique Queue replaces the fragile process around them: who presents next, who skipped, and what needs to be remembered.
- Spreadsheet rotations
- Slack thread bookkeeping
- Notion status tables
- Random picker tools
- Facilitator memory
- Calendar-doc agendas
Company and workspace model
One company can run many critique workspaces.
A company account owns billing, sign-in, admins, members, and audit policy. Workspaces sit inside that company, one per recurring critique ritual.
Company account
The customer boundary for billing, company sign-in, admins, members, and audit policy.
Critique workspaces
Each recurring critique ritual gets its own queue, rotation rules, history, and workspace settings.
Multi-company access
Consultants and operators can be invited into more than one company without mixing their critique queues.
How it works
Make the rules visible before the session starts.
01
Pick the presenter
Start from the person leading the critique. Critique Queue previews the attendee selection before anything is committed.
02
Review the rotation
The queue stays visible. Unavailable people remain in place, so skips do not silently change fairness.
03
Commit the session
Save the result, rotate the selected people, and keep a history that explains what happened later.
Why teams use it
Fairness becomes operational, not political.
Critique Queue gives design ops and team leads a simple way to show how attendee selection works, who was skipped, and what changed after each session.
- Visible queue order
- Unavailable people skipped without losing position
- Session history for auditability
- Less spreadsheet maintenance
- Fewer fairness debates
- Clearer design ops rituals
ROI
A weekly critique only has to save minutes.
At a $75/hour loaded cost, a $19 workspace pays for itself when it saves about 16 team-minutes per month. That is less than four minutes of total confusion across one weekly critique.
Pricing direction
Pilot
Free for 30 days
One critique workspace, unlimited attendees, and help importing the current spreadsheet.
Team
$19 / workspace / month
Fair rotation, skip history, and queue visibility for one recurring critique ritual.
Business
From $79 / company / month
Multiple workspaces, company sign-in, admin controls, audit exports, and priority integrations.
Integrations roadmap
Fit the critique ritual into the tools teams already use.
Critique Queue should not become another design canvas or notes app. The roadmap is about reminders, artifact links, calendar cadence, migration, and follow-up work.
- Slack / Teams reminders
- Figma / FigJam links
- Google Calendar / Outlook
- CSV / Google Sheets import
- Linear / Jira follow-up
- SSO / SCIM for larger companies
Start with one critique workspace.
Send the queue, team list, and current critique rules. I can turn that into a pilot your team can try before changing the way sessions are run.
Ask about a pilotCompany admin
Keep operations visible after the session ends.
Critique Queue includes company-sign-in admin views for access, audit trails, workspace settings, and queue maintenance, so design ops can manage each ritual without shared passwords or spreadsheet archaeology.
Admin controls
Manage business units and people without touching the underlying queue data by hand.
Audit trail
Review recent changes, who made them, and which company records were affected.
Invites and access
Use company sign-in, invite teammates, adjust roles, and handle pending access requests from one place.
Workspace settings
Tune branding and rotation behavior so each workspace matches the team ritual.