A live review works when everyone looks at the same detail and leaves knowing what was decided. The aim is not to collect as many comments as possible. It is to end with a short list of findings that each have an owner, and a page that is clearly better at the next check.
Agree on the scope before opening the page.
Pick a small set of pages, states or questions. A review of the booking journey has a different focus from a visual polish pass, and naming the focus makes it easy to park unrelated ideas without losing them.
Confirm the address, production or staging, and the screen sizes you will look at. Check that every participant can open the project and, if it is protected, the website itself.
- Before
- Share the scope in one line: pages, states and screen sizes. Send the project link.
- First 20 minutes
- One person drives the page. Everyone else follows along and pins findings as they come up.
- Last 10 minutes
- Merge duplicates, give each finding an owner and a priority, and write the decisions into their threads.
Let one person drive.
When everyone scrolls on their own, the conversation splits. Ask one person to move through the page while the others watch, point and pin. Live cursors make “this one, here” easy to follow.
Presence shows who is in the review. It supports the conversation; the lasting record is still the pinned finding and its thread. You can run the review alongside your usual call tool.
Turn observations into pins as you go.
When something deserves a change, pin it to the element right away and write the observation in one or two sentences. A finding that lives only in the spoken conversation is usually gone by the next day.
The person who pins does not need to solve the issue on the spot. Capture the evidence and the outcome you want, then agree who will look into it.
- One finding per pin, even when two issues sit on the same element.
- Name the screen size or state when it matters.
- Give it an owner and a priority before moving on.
- Write down the decision when the group agrees on a direction.
Keep roles and access clear.
A shared session does not mean everyone needs the same rights. Give people the project role that fits their work: reviewing a finding and managing who has access are different jobs.
Realtime updates, presence and live cursors come with every project, on Core and Pro. What each participant can change still depends on their role.
Finish with the decisions, not the meeting.
In the last minutes, read the new findings together. Remove duplicates, fill in missing owners and rewrite any note that only makes sense to the person who wrote it. Group related work into tasks when that makes the handoff easier.
Agree how the changes will be checked: another short session, or the owner checking the live page against each note. Either way, the evidence stays with the work.
TAKE IT INTO YOUR NEXT REVIEW
One scope, one driver and a pin for every decision: the call ends, the work continues.
Explore the feature