Urgent.News

What's breaking now, across thousands of outlets.

Tech

Most businesses are still not getting their tech and IT working right - and it's causing disruption across the entire workforce

Logitech report claims that if IT teams were involved earlier on in office space planning, productivity wouldn't take such a hit.

Most businesses are still not getting their tech and IT working right - and it's causing disruption across the entire workforce

A recent Logitech report reveals that only a small fraction of businesses engage their IT and Audio-Visual teams early in the planning process, leading to suboptimal technology setups and potential productivity losses. In the UK, fewer than a third (31%) of workplaces involve these teams before space planning begins, forcing tech decision-makers to scramble for solutions in already designed spaces.

The report highlights that poor IT team involvement results in failed audio, dropped connections, and a median productivity loss of 12.2 minutes per person per poor meeting. Despite the acknowledgment of a strong link between workplace experience, productivity (86%) and collaboration (90%), only half (56%) of business leaders feel confident in justifying tech investments with ROI data, and only 29% treat it as a core business strategy.

Logitech proposes a solution of closer alignment between IT, HR, and Real Estate teams from the outset, as planning rooms as a coordinated team could reduce long-term costs associated with upgrading outdated hardware. To strengthen ROI justification, the report suggests using tech downtime as a metric, with productivity impact serving as sufficient proof that office spaces need improvement.

Written by urgent.news from TechRadar's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.

Read the original at techradar.com →

More in Tech

Mobile App Testing: 11 Practical Ways to Find Bugs Before Users Do

Mobile App Testing: 11 Practical Ways to Find Bugs Before Users Do A mobile app can work perfectly during development and still fail when real users start using it. Why?

  • Test unexpected user inputs like empty fields, special characters, and long inputs
  • Simulate poor network conditions to test app resilience during API requests
  • Check how the app handles background reopening and state preservation

More from Monday 21 September →