Real-time multiplayer editing in Figma - Real Business Scenario

Scenario Mode

👤 Your Role: You are a product manager at a software company developing a collaborative design tool.

📋 Request: Your manager wants a dashboard to monitor real-time multiplayer editing activity to understand user collaboration patterns and system performance.

📊 Data: You have access to live data showing user sessions, number of active collaborators per document, edit events per minute, and latency metrics.

🎯 Deliverable: Create a dashboard that shows active users per document, edit frequency over time, and system latency to help the team optimize collaboration experience.

Sample Data

Timestamp	DocumentID	UserID	ActiveCollaborators	EditEventsPerMinute	LatencyMs
2024-06-01 10:00	DocA	User1	3	15	120
2024-06-01 10:00	DocB	User2	2	8	100
2024-06-01 10:01	DocA	User3	3	18	110
2024-06-01 10:01	DocB	User2	2	10	105
2024-06-01 10:02	DocA	User1	4	20	115
2024-06-01 10:02	DocC	User4	1	5	130
2024-06-01 10:03	DocA	User3	4	22	112
2024-06-01 10:03	DocC	User4	1	6	128
2024-06-01 10:04	DocB	User2	3	12	102
2024-06-01 10:04	DocA	User1	4	25	110

1

Step 1: Create a table visual showing the number of active collaborators per document over time.

Rows: Timestamp, DocumentID; Values: MAX of ActiveCollaborators

Expected Result

Table shows active collaborators count per document at each timestamp, e.g., DocA has 3 collaborators at 10:00.

2

Step 2: Create a line chart to display edit events per minute trend for each document.

Axis: Timestamp; Legend: DocumentID; Values: SUM of EditEventsPerMinute

Expected Result

Line chart shows how edit events change over time for DocA, DocB, and DocC.

3

Step 3: Create a card visual to show average system latency in milliseconds.

Measure: AVERAGE(LatencyMs)

Expected Result

Card displays average latency around 113 ms.

4

Step 4: Add a filter to select a specific document to analyze collaboration and latency details.

Slicer on DocumentID

Expected Result

User can select DocA, DocB, or DocC to update visuals accordingly.

5

Step 5: Arrange visuals on a dashboard with clear titles and legends for easy interpretation.

Dashboard layout: Top-left table, top-right line chart, bottom card, filter on side

Expected Result

Dashboard is easy to read and interact with, showing real-time collaboration metrics.

Final Result

Real-time Multiplayer Editing Dashboard

+---------------------------+  +---------------------------+
| Active Collaborators      |  | Edit Events Per Minute     |
| Timestamp | DocA | DocB | DocC|  |                           |
| 10:00     | 3    | 2    | -   |  |  *                       |
| 10:01     | 3    | 2    | -   |  |  **                      |
| 10:02     | 4    | -    | 1   |  |  ***                     |
| 10:03     | 4    | -    | 1   |  |  ****                    |
| 10:04     | 4    | 3    | -   |  |  *****                   |
+---------------------------+  +---------------------------+

+---------------------------+
| Average Latency (ms)       |
|          113              |
+---------------------------+

[Document Filter: DocA | DocB | DocC]

✓DocA consistently has the highest number of active collaborators and edit events.

✓Latency remains stable around 110-130 ms, indicating good system performance.

✓DocC has fewer collaborators and lower edit activity, suggesting less usage.

Bonus Challenge

Add a heatmap visual to show peak collaboration times across all documents.

Show Hint

Use Timestamp on one axis and DocumentID on the other, color-coded by sum of ActiveCollaborators.