Collaborate in real time

Collaborate in real time in Figma — with the four heights of help laid out: do it now, make it easier for the next person to accept, work out the right move when you are stuck, and learn the pattern so it stops coming back.

4prompt heights
Open it in the interactive atlas →

The four heights

The same task, four distances: today's deadline, the next reviewer, the stuck moment, the pattern.

Execute — do the immediate task

+
This meeting is about the product details that need real‑time signoff. Invite Alex in product, Sam…
This meeting is about the product details that need real‑time signoff. Invite Alex in product, Sam the lead engineer, and Priya the founder to the file now and ask them to review the onboarding flow frames Release‑v1 and Release‑v1‑mobile; track comments live and pin the three decisions we need by Wednesday.

Improve — make it easier to accept

+
Before we open the file to everyone, make collaboration frictionless: surface the three open…
Before we open the file to everyone, make collaboration frictionless: surface the three open questions at the top, add numbered comment anchors on the problematic screens, and set up a shared comment thread for Alex, Sam, and Priya so they can resolve decisions in one pass. Suggest phrasing for each anchor to reduce back‑and‑forth.

Decide — diagnose the stuck moment

+
I just invited Alex, Sam, and Priya to review the onboarding screens and only Sam left detailed…

I invited stakeholders but only one person commented in detail.

I just invited Alex, Sam, and Priya to review the onboarding screens and only Sam left detailed comments; I am afraid the product decisions will stall without Priya's input and Alex is overloaded. I cannot tell whether Priya is unavailable or avoiding the file. Should I ping Priya directly, extend the review deadline, or summarize and make the call without her? Recommend the next action and a short message to send to Priya that will get a timely response.

Become — change the pattern

+
We repeatedly waste cycles because stakeholders open the file but do not resolve decisions, leaving…

Collaboration sessions frequently end with unanswered decisions and rework.

We repeatedly waste cycles because stakeholders open the file but do not resolve decisions, leaving engineers blocked. Which practice change will most reduce stalled reviews: require a 15‑minute sync with all reviewers, lock the file until the review window, or assign a single decision owner per screen? Recommend one habit to adopt, two rules to make it stick, and a one‑line prompt to include when inviting reviewers.

Next to this one

Other interface design work people do in Figma.

Every task here came from the work, not from a feature list — which is why the prompts name what you want done and never the button that does it. The tool changes; the work does not.
Copyright © LLOS.ai · 2026 — original pedagogy, voice, and design — all rights reserved.

The rest of the map

Same library, five ways in.