The Most Expensive AV Problem Might Be the One Nobody Owns
Why workplace technology needs clear ownership, not just good equipment
There is a meeting room somewhere that nobody particularly likes using.
The equipment works. The installation was completed properly, the system passed its commissioning tests and the project was signed off. The IT department can see the devices on the network, Facilities is satisfied that the room is finished and Finance has paid the invoice.
By almost every conventional measure, the project was successful.
Yet six months later, people are avoiding the room.
Perhaps meetings regularly start late because the technology doesn't behave quite as people expect. Perhaps the room is being used differently from the way it was originally designed. Or perhaps employees have simply discovered that another space is easier, so they book that instead.
Nothing is sufficiently broken to trigger a major investigation. The technology is operational, the room looks impressive and nobody has formally complained.
But the business isn't receiving the value it expected from its investment.
So whose problem is it?
That question is more difficult than it first appears, and I suspect it reveals something important about the way organisations manage workplace technology.
For years, we've concentrated on making sure every part of a technology project has someone responsible for delivering it. We have project managers, technical specialists, installation teams, IT administrators and support providers. Responsibilities are documented, milestones are agreed and the work is divided into manageable areas.
All of that is necessary.
But somewhere between defining who is responsible for the individual components and delivering the finished environment, we can lose sight of a more fundamental question.
Who is responsible for making sure the whole thing actually delivers what the business needs?
When everybody has a responsibility, but nobody owns the outcome
Modern workplace technology has become remarkably difficult to place within a traditional organisational structure.
Consider a typical office. The meeting-room technology depends on the corporate network and collaboration platform, both of which naturally sit within IT. The room itself belongs to the physical workplace, making Facilities an obvious stakeholder. The way employees use that room affects productivity, communication and the broader employee experience.
Finance has an interest in the investment, while senior management expects the environment to support the organisation's wider objectives.
None of these perspectives is wrong.
The difficulty is that each function can be doing its job perfectly well without anybody being accountable for the experience created by all of them together.
An IT team may quite reasonably judge a meeting room by whether its devices are connected, secure and functioning. Facilities may be concerned with the condition, availability and suitability of the physical space. The AV integrator may have delivered precisely what was specified and demonstrated that it operates as designed.
Yet employees don't experience those responsibilities separately.
They experience the room.
They don't care which department owns the camera or whether a particular fault belongs to the network, the collaboration platform or the AV system. They simply expect to walk into a space and do what they came there to do.
This is where the distinction between responsibility and ownership becomes important.
Responsibility can be divided. Ownership of the outcome needs to remain clear.
We've previously explored the relationship between AV integrators and internal IT teams, particularly the importance of bringing their complementary expertise together. That remains essential, but the ownership question goes further. It isn't simply about deciding who installs, configures or supports different parts of a system. It's about deciding who will notice when a technically functioning system is no longer delivering the intended business result.
That is a very different responsibility.
And it doesn't end when the installation is completed.
In fact, it may only become meaningful once people start using the technology in their normal working lives.
A room that looked ideal during the design process may turn out to be used for different kinds of meetings. An internal communications display may be installed in exactly the right location, but the content eventually becomes irrelevant because nobody has taken responsibility for keeping it useful. A workplace may have invested heavily in technology to support collaboration, yet employees continue working around it because the experience doesn't fit the way they actually operate.
These aren't necessarily equipment failures.
They are failures of continuity between the original intention and the ongoing reality.
And they can remain largely invisible when every department is measuring only the part of the environment it directly controls.
They don't care which department owns the camera or whether a particular fault belongs to the network, the collaboration platform or the AV system. They simply expect to walk into a space and do what they came there to do.
This is where the distinction between responsibility and ownership becomes important.
Responsibility can be divided. Ownership of the outcome needs to remain clear.
We've previously explored the relationship between AV integrators and internal IT teams, particularly the importance of bringing their complementary expertise together. That remains essential, but the ownership question goes further. It isn't simply about deciding who installs, configures or supports different parts of a system. It's about deciding who will notice when a technically functioning system is no longer delivering the intended business result.
That is a very different responsibility.
And it doesn't end when the installation is completed.
In fact, it may only become meaningful once people start using the technology in their normal working lives.
A room that looked ideal during the design process may turn out to be used for different kinds of meetings. An internal communications display may be installed in exactly the right location, but the content eventually becomes irrelevant because nobody has taken responsibility for keeping it useful. A workplace may have invested heavily in technology to support collaboration, yet employees continue working around it because the experience doesn't fit the way they actually operate.
These aren't necessarily equipment failures.
They are failures of continuity between the original intention and the ongoing reality.
And they can remain largely invisible when every department is measuring only the part of the environment it directly controls.
The cost of problems that never become faults
The obvious cost of poorly managed workplace technology is downtime. When a system stops working, people notice, support tickets are raised and somebody is expected to resolve the problem.
But I wonder whether some of the more expensive problems are the ones that never become faults at all.
A meeting room that takes a little longer to use than it should. A display that nobody pays much attention to. A collaboration space that is consistently underused. Technology that works well enough to avoid a complaint but not well enough to deliver the improvement that originally justified the investment.
Individually, these things may seem insignificant.
Across an organisation, they can represent a substantial amount of unrealised value.
The difficulty is that conventional technology management is often much better at detecting failure than recognising disappointment.
We know when a device goes offline. We can establish whether a warranty remains valid, whether a system is receiving updates and whether an engineer has resolved a reported fault. Those are important measures, and organisations should absolutely have them.
But they don't necessarily tell us whether the technology is making the workplace better.
That requires a different kind of conversation.
When a business invests in a new meeting environment, the original justification is rarely that it wants more hardware. The objective is usually to make communication easier, improve collaboration or support a change in the way people work.
The equipment is the means of achieving that objective.
Yet after installation, the original business ambition can quietly disappear from the way the system is managed. Success becomes defined by whether the technology is operational rather than whether it continues to deliver the improvement everyone expected.
We touched on this distinction in Stop Buying AV. Start Designing Experiences, where we argued that workplace technology should be judged by what it enables people to achieve rather than simply by the products installed.
There is a natural extension to that argument.
If we believe technology should be designed around outcomes, somebody must remain interested in those outcomes after the project has finished.
Otherwise, we risk investing considerable time in understanding the business requirement at the beginning, only to manage the result as a collection of technical assets afterwards.
And this becomes more significant as workplace technology expands beyond traditional meeting rooms.
Digital signage is a particularly interesting example because the distinction between technical operation and business effectiveness is so obvious. A display can remain switched on, connected and fully functional while showing information that is no longer relevant. From a technical perspective, everything is fine. From a communication perspective, the investment may be achieving very little.
The person responsible for maintaining the display may have no authority over the content.
The person responsible for the content may not know whether employees are engaging with it. The person who originally approved the investment may assume somebody else is managing its effectiveness.
The result is technology that belongs to everybody in some respects, but nobody in the way that matters most.
As AI and connected workplace systems make it easier to distribute information across physical environments, this question of ownership will become even more important. Technology will increasingly be capable of delivering information automatically, but automation doesn't remove the need for someone to decide whether that information is useful, appropriate or achieving its intended purpose.
In some ways, it makes that responsibility more important.
Perhaps ownership should follow the experience
I don't think the answer is to create another department or invent a new job title for every piece of workplace technology.
Most organisations already have the expertise they need. The challenge is often how that expertise is connected and where accountability sits.
In a smaller business, the same person may be responsible for IT, workplace operations and much of the technology strategy. In a larger organisation, those responsibilities may be spread across several specialist teams.
Neither arrangement is inherently better.
What matters is whether somebody has sufficient visibility and authority to recognise when the overall experience is falling short, and whether there is a practical way to bring the relevant people together to improve it.
That may sound more like a management issue than an AV issue.
Perhaps it is.
But I think this is exactly where the conversation around AV integration needs to mature.
For a long time, integration has been understood primarily as a technical discipline. We connect devices, configure systems and make different technologies operate together.
Good integration requires genuine engineering expertise, and none of that becomes less important.
The question is whether the same joined-up thinking should extend beyond the technology itself.
A system can be technically integrated while the people responsible for its success remain organisationally disconnected.
The network is managed by one team, the physical space by another and the user experience is left to emerge from the combination.
Sometimes that works extremely well.
But when it doesn't, the absence of clear ownership can make improvement unnecessarily difficult.
A more useful approach is to establish, from the beginning, not just who is responsible for delivering the technology but who will remain accountable for the result. That means the business objective needs to survive the transition from project to operation.
If a new workplace environment was designed to improve collaboration, somebody should be interested in whether collaboration has actually improved. If a digital signage system was introduced to make internal communication more effective, its ongoing success cannot be measured solely by whether the displays remain online.
This doesn't mean every business needs elaborate reporting or a new layer of administration. In many cases, a relatively simple conversation between the people responsible for technology and the people using it will reveal far more than another technical dashboard.
The important thing is that the conversation continues.
This is also where ongoing support should become more than an arrangement for responding when something breaks.
A good support relationship provides the opportunity to understand how technology is performing in the real world, whether requirements have changed and whether small improvements could make a meaningful difference.
Sometimes the answer will be technical. Sometimes it will involve changing the way a system is configured or helping employees understand how to use it more effectively. Occasionally, the technology itself may be entirely appropriate and the issue lies somewhere else in the organisation.
The value comes from being willing to understand the whole problem rather than concentrating only on the part that happens to fall within a particular technical responsibility.
And that requires a degree of honesty from everyone involved.
An integrator cannot reasonably take responsibility for every business outcome that depends on a workplace environment. Equally, an organisation cannot assume that installing a well-designed system automatically guarantees the benefits it originally hoped to achieve.
Successful ownership is a partnership.
The customer needs to remain clear about what it wants the technology to accomplish. The integrator needs to understand that objective and help translate it into a practical, supportable solution. And both need to recognise that the relationship between technology and business requirements will continue changing long after the initial installation.
The project ends. The responsibility doesn't.
At Collab AV, this is an important part of how we believe workplace technology should be approached.
Our role isn't simply to deliver a system that meets a specification and then move on. We want to understand why the investment is being made, how people are expected to use the environment and what success should look like once the technology becomes part of everyday working life.
That means working with the people responsible for both the technology and the workplace around it. It also means recognising that the right solution isn't always the most technically sophisticated one, and that the job doesn't necessarily finish when the equipment is installed and commissioned.
Through planning, design, implementation and ongoing support, our aim is to help customers maintain the connection between the technology they've invested in and the outcomes they want it to deliver.
We can't own every aspect of a customer's workplace experience, and nor should we. But
we can help make sure the technical responsibilities are clear, the right people are involved and there is continuity between the original business requirement and the environment that is ultimately delivered.
For me, that is an increasingly important part of what good AV integration should mean.
Because the real value of workplace technology isn't established on the day the project is signed off.
It's established in the months and years that follow, when people use it, depend on it and expect it to make their working lives easier.
A successful installation is important. A reliable support arrangement is important too. But neither automatically guarantees that the organisation is receiving the value it expected.
That requires somebody to keep asking whether the technology is doing what it was supposed to do in the first place.
And perhaps that's the question we should be asking before the next workplace technology project begins.
Not simply who is buying it, who is installing it or who will fix it when it breaks.
Who is going to own the outcome?
Because the most expensive AV problem might not be the system that stops working.
It might be the one that keeps working perfectly, long after it has stopped delivering any real value.
Comments