Read the room
- Number of screens
- Camera streams and aspect ratios
- Active and recent speakers
- Shared content and audio state
POLYCOM · INVENTION
A video layout is easy when every room has one screen and one camera. The real design problem begins when every endpoint is different.
SITUATION
A call could connect a one-screen room to two- or three-screen rooms, each contributing one or several camera streams. A layout that worked for one combination could crop people, shrink the active speaker, introduce empty space, or reshuffle the entire meeting when a new site joined.
My contribution was to turn those configurations into a product-behavior model: rules that balanced human attention, video integrity, room geometry, and technical constraints.
FROM COMPLEXITY TO BEHAVIOR
The design contribution was not a single arrangement. It was a decision model that could adapt as the room, call, and content changed.
TASK
Rather than draw a separate screen for every permutation, I established priorities the system could use when choosing among valid layouts. The rules made tradeoffs explicit and gave design and engineering a shared basis for evaluating edge cases.
Protect the active speaker. Give the person speaking the largest useful area while accounting for camera count and the integrity of each video stream.
Preserve the source. Avoid cropping, stretching, or wrapping multi-camera streams in ways that break the spatial relationship of the room.
Show as many sites as possible. Prioritize the active speaker, recent speakers, and unmuted video without creating a visually noisy wall of tiny windows.
Avoid disruptive movement. Keep layouts stable when participants join or leave so attention stays on the meeting instead of the interface.
Treat content as a first-class mode. Let shared content take precedence while the remaining displays continue to provide useful meeting presence.
APPROACH
The model accounted for monitor profiles, camera count, the aspect ratio of combined streams, whether content was being shared, speaking history, audio state, and user-selected layouts. That let the experience adapt without pretending every endpoint was identical.
The most important design decision was persistence: changes should feel intentional. A new participant should not automatically destroy the speaker position or force everyone to relearn where people are on screen.
RESULT
The multi-screen layout concepts contributed to Polycom’s patent-related work and demonstrate a form of product design that is easy to overlook: not styling a screen, but defining how a complex system should make decisions.
I use the same approach today—frame the experience goals, expose the variables, establish priorities, and make the rationale visible before teams commit to a solution.