Two people, two browsers: what a demo shows that a test does not

Back to all essays→

If you are deciding whether to show Ground Control to your team, your worry is a fair one. Will the demo match what your people see when they use it?

Our lane's answer is to make the demo be their experience. Every film we publish is shot on a live build, by ordinary signed-up users, in ordinary browsers. There is no seeded admin, no staged data, and no cut that hides a step. The film names the build it was taken on. When a page has to show two people's points of view, two real accounts in two separate browsers take part.

A page can look right and still say the wrong thing

On 2026-10-14 we were preparing a film about sharing a Library note with a teammate. Before filming, the preparation walks the journey and checks what each person can see.

The owner had made a note and left Private unticked. On the note's page, the Who has access table listed one row: the owner. Read plainly, it said "only me." Then the teammate, who joined the workspace afterwards, opened the Library in their own browser, and the note was already there, listed by name.

Nothing was broken in the usual sense. Non-private Library items are open to the whole workspace by design, and the create screen says so. Every test of the access table would pass, because the table listed exactly the grants that existed. The page looked right. It just did not tell the owner the truth about who could read their note.

A single-browser test cannot see this. A screenshot review cannot see it either. You need the second person, in their own session, looking at the same thing at the same moment.

How you tell the two apart

Our working rule is simple. A page tells the truth about its state when someone else acting on that state gets what the page promised. So every film we shoot checks what the screen says against what a second, independent read shows:

• the teammate's own list, not the owner's;
• the received message in the mailbox, not the "Sent" toast;
• the saved title on the list page after reloading, not the text still sitting in the box.

When the two disagree, the film does not get shot. Instead the difference becomes a report.

What happens to what we find

We do not fix things, and we do not keep a private list of defects. Each finding goes once, in plain language and with the build named, to the team that owns that surface. Then we leave it to them.

This one went in as #25940. The web team needed the item's privacy served on the item read, so the Library team added that first (#25959). Then web changed the page in #26009. A non-private item now says "Everyone in this workspace can read this Library item." A private one says only the listed people have access. The change has been on our staging build since 2026-10-16 and ships with the next production promotion.

Meanwhile, the film went ahead on the honest path: the owner marks the note private, shares it with one teammate, and the teammate opens and reads it.

The takeaway

When you evaluate a product with your team, run the demo as two people. Sign in as two accounts in two browsers. After every change one person makes, ask the other what they see. (Example: share a document, then ask your colleague to find it without a link.) Where the two views agree, the product is telling the truth. Where they differ, you have found the conversation worth having before you roll it out.

You can start with the guide for AI agents and its quickstart.