People-First Meeting Rooms: Beyond Platform-First
Enterprise
Beyond the OS: Why “People-First” is the New Benchmark for the Modern Shared Workspace
''Push Beyond” the room’s operating system.
In shared workspaces, one interpretation is practical: pushing beyond the assumption that the meeting room should be optimised primarily for a single platform ecosystem.
Platform alignment with Microsoft Teams, Zoom, and other UC environments is strategically important. Few organisations can ignore those ecosystems, particularly when enterprise standardisation and security scrutiny are rising. But a consistent pattern has emerged alongside this platform-first paradigm: when the room is optimised for the platform ahead of the person, friction often follows.
That friction rarely shows up as a dramatic failure. It appears as delays, awkward workarounds, and “small” moments of confusion that compound across estates especially in enterprise and education, where reliability and repeatability matter as much as feature depth. Over time, those moments can become a cost paid in lost time, increased IT tickets, reduced adoption, and lower confidence in the workspace.
This article, Ryan McElvaney, Head of Channel Sales & Alliances, explores a people-first alternative: designing meeting spaces around the human constant (how people actually collaborate) while treating the platform as a variable. Ryan also considers what that shift means for the channel as resellers and integrators increasingly move from AV specialists towards workflow partners responsible for outcomes at scale.
The platform-first paradigm and why it became the default.
A platform-first strategy is straightforward to explain and often straightforward to procure. Standardising on an ecosystem such as Teams Rooms or Zoom Rooms can simplify decisions, reduce room variation, and align with enterprise IT strategies. In many environments, that clarity has been valuable.
The limitation is not the platform itself. It is the assumption that work happens neatly inside one ecosystem and that all users, use cases, and meeting scenarios will conform. Real-world collaboration is less predictable:
customers and partners invite across different meeting platforms
external guests join from their own preferred tools
users vary by confidence, role, accessibility needs, and working style
security requirements demand more governance, not less
rooms are used for more than “one-touch join” calls (content sharing, walkthroughs, training, hybrid workshops, sales conversations)
When the room experience is designed primarily as an extension of one platform, organisations may experience a form of lock-in by default. The lock-in is not just commercial; it can be behavioural and operational: rooms become “walled gardens” that work well in ideal scenarios but add friction when reality deviates.
The result is a practical question for workplace and channel leaders: what should the modern shared workspace be optimised for the ecosystem, or the human experience of collaboration?
The hidden tax of platform-first: three friction patterns that repeat.
Meetings are already a high-frequency part of modern work. Research cited by Harvard Business Review found executives spend nearly 23 hours per week in meetings on average a figure that has risen substantially over decades. When meetings consume that much time, even small amounts of friction at the start of meetings become meaningful at scale.
Platform-first room design tends to generate friction in three repeatable ways.
1) The interop gap: “We standardised on Teams, but the invite is Zoom”
A platform-first room assumes the meeting environment will match the room’s optimised ecosystem. In practice, organisations often have mixed realities:
a strategic customer sends a Zoom invite
a partner hosts on Webex
an internal team uses Teams, but a guest joins via Google Meet
a meeting’s platform changes late, or the link differs from expectation
When this happens, a room designed primarily for a single ecosystem can push users into awkward choices: switch rooms, switch devices, compromise on experience, or involve IT. Even when solutions exist, the decision burden lands on the user in the moment.
In enterprise estates, the interop gap often becomes a governance question: how reliably can the organisation support external collaboration without exceptions, workarounds, or “special rooms”? In education, it can become an equity and access issue: different departments or campuses experience different levels of usability depending on who is inviting and what they are using.
2) The login hurdle: identity and security traded for convenience
Many collaboration room approaches introduce a recurring tension: users want personal access to calendars, content, and collaboration tools but IT teams want rooms to be secure, consistent, and low-risk.
A platform-first model can encourage behaviours that create friction and risk:
users signing into shared PCs and needing to remember to sign out
personal data exposure if sign-out is inconsistent
ad hoc workarounds that undermine policy and auditing
The result is a familiar trade-off: convenience and personalisation vs control and compliance. In practice, this trade-off is not always explicit it shows up as inconsistent room behaviours and increased support burden.
3) The specialist trap: when “one-touch join” isn’t enough
Platform-first rooms often promise simplicity: one touch and you’re in. When the scenario matches expectations, that can be true. The problem is what happens when it doesn’t.
If a meeting doesn’t match the room’s optimised platform, or if a join path fails, the room can quickly become dependent on a specialist:
the one person in the team who “knows how this room works”
an AV technician
the IT helpdesk
This pattern is commercially important. A meeting room that requires a specialist to succeed is not a self-service asset; it is a support liability. It is also one reason some employees avoid meeting rooms entirely if they lack confidence in the technology. A Zoom-compiled set of 2025 meeting statistics reports 30% of employees are hesitant to take meetings from meeting rooms due to discomfort with meeting room technology.
Across a large estate, these small moments add up: delayed starts, reduced confidence, increased tickets, and lower adoption even if the underlying platform is strong.
A people-first alternative: agnostic by design.
A people-first approach starts with a different assumption:
The user is the constant. The platform is the variable.
Rather than asking the user to adapt to the room, the room adapts to the user providing a consistent workflow for starting meetings, sharing content, and collaborating, regardless of which UC platform is in play.
This does not require rejecting platform ecosystems. It reframes their role. Platforms remain strategically important but the “front door” of the meeting room experience is designed around:
consistent usability across platforms
clear, repeatable workflows
personalisation that is temporary and secure
reduced cognitive load for users
standardisation that lowers support burden
From a channel perspective, the distinction is meaningful. A platform-first approach tends to be sold as a specification decision. A people-first approach tends to be sold as a workflow and outcomes decision: reliability, adoption, lower cost-to-serve, and improved user experience at scale.
What people-first looks like in practice: three outcomes.
The people-first idea can remain abstract unless it’s tied to specific outcomes. Here I point to three outcomes that are highly recognisable in enterprise and education estates.
1) Removing the “first five minutes” friction
Many meeting disruptions occur at the start: joining, finding the right link, figuring out which system the room expects, switching devices, or asking someone else for help.
A people-first room experience aims to remove that early friction by presenting a consistent interface that feels familiar and self-service closer to how people interact with personal devices. The objective is not novelty; it is predictable behaviour: users know what to do, regardless of room, campus, or site.
For channel partners, this matters because predictability reduces support tickets and makes deployments more repeatable across different environments.
2) Personalisation without persistent risk
A people-first approach typically aims to deliver “just enough” identity to be useful without turning the room into a persistent identity container.
One model is mobile-based sign-in: users authenticate via their phone to access the resources they need (calendar, files, meeting links) temporarily, while the room remains locked down from an admin perspective. The governance objective is straightforward:
the user experience becomes personal and fast
the room remains secure and consistent
data does not persist beyond the session
This is the practical bridge between convenience and security that many estates need especially where shared spaces are used by diverse groups and varying levels of technical confidence.
3) Future-proofing the workflow partner model
A recurring challenge in the channel is balancing capex-led room refresh cycles with the growing expectation for software-led value: analytics, manageability, standardised workflows, and continual improvement.
People-first models can support this shift by being hardware-agnostic in principle: working with existing displays and PCs where appropriate, extending the life of investments, and moving value into a software and services layer. In channel terms, this enables a different commercial conversation:
not only “what kit are we installing?”
but “what workflow outcomes are we standardising, supporting, and improving over time?”
At this year’s ISE, AI will undoubtedly cast a big shadow, reflecting the broader trend of software and intelligence layers becoming more central to workplace technology. A people-first workflow approach can be seen as compatible with that direction: the room experience becomes an adaptable, managed layer rather than a static endpoint.
What this means for the channel: from AV specialist to workflow partner.
The channel value proposition is often strongest when it is consultative: understanding the customer’s environment, constraints, and workflows then designing a solution that works reliably over time.
A people-first benchmark supports that consultative role, particularly as meeting spaces become part of broader workplace experience and IT governance conversations. It can also help address a commercial reality: if hardware becomes increasingly substitutable, the channel’s differentiation often shifts towards outcomes, supportability, and services.
A practical way to describe the transition is as three stages:
Kit-led rooms (capex-led)
The room is primarily a hardware specification. Value is delivered at install. The long-term experience varies room-to-room.Platform-led rooms (ecosystem-led)
Standardisation improves. Rooms align to an ecosystem. The user experience is strong when scenarios match the ecosystem, but friction appears at the edges.Workflow-led estates (people-first)
The focus is on consistent, self-service workflows across platforms and room types. The channel sells standardisation, adoption, and governability and can attach services that sustain outcomes.
This framing gives channel partners a clear narrative ahead of ISE: the opportunity is not to “reject platforms”, but to push beyond platform-first assumptions and deliver estates optimised for how people actually work.
Platform-first vs people-first: a practical comparison.
FeaturePlatform-first rooms (typical)People-first workflow approach (typical)FlexibilityOptimised for one ecosystem; cross-platform scenarios can be awkwardDesigned for mixed-platform reality; consistent entry pointUser identityOften tied to room accounts or shared loginsTied to the user, temporarily, with governance controlsHardwareMay encourage certified “kits” and prescriptive specificationsCan be more tolerant of existing estate hardware (where suitable)IT burdenInterop exceptions can increase tickets and escalationsStandardised workflows can reduce support variabilityPhilosophyServe the ecosystemEmpower the human and the workflow
This table should be read as patterns, not absolutes. Many organisations will fall somewhere between the two columns. The relevance is the direction of travel: estates increasingly require room experiences that handle messy reality without specialist intervention.
A pragmatic benchmark for 2026.
The shift towards people-first shared workspaces is not only about user experience. It is also about operational efficiency and commercial clarity.
When platform-first room designs struggle with interop, identity friction, or specialist dependency, the costs tend to show up in the places organisations care about most:
lost time
increased IT burden
lower adoption
reduced confidence in meeting spaces as an estate standard
The people-first benchmark can be summarised as a simple goal: a meeting room that supports choice, reduces friction, and remains governable regardless of who is inviting, which platform is being used, or which room a user walks into.
For channel partners this creates a constructive conversation: moving beyond platform-led specifications towards workflow-led estates where value is delivered not just at install, but across the lifecycle through standardisation, supportability, and outcomes.