The conversion of a VR sceptic

May 11, 2022

By Stefan Kosnik, Product Owner


As a product owner, I’m very tied to my computer to get work done. So when the idea of working in virtual reality was floated, I was sceptical that it would add any business value. 


We already spend so much of our working day in meetings, so I wanted to know whether I be able to get any real work done in VR without my computer.


My general sense was that we’re just not ready for VR, that the technology is too immature to use at work and maybe we, even with all the changes the pandemic has brought, just aren’t ready either. 


So, I raised these concerns with our Developer Custodian (and VR enthusiast) Paul Seymour. 


His response? That trialling VR was exactly about finding an answer to these questions. 


Working at Patient Zero, this approach is not uncommon. We apply our Way of Working to just about everything - which means that testing, iterating and learning isn’t just part of our development process, it’s part of our culture. 


To be honest, I also wasn’t entirely disappointed about the idea of at least having a play with the latest Oculus gear either. 


After our first sprint working in VR, I have to say I’m pleasantly surprised at the results. After getting over the initial ‘Wow’ factor of being in the metaverse, using the tools in Horizon Workrooms very quickly becomes second nature.

I am able to partially bring my hardware into VR, remote desktop (one screen only) via the Oculus app and my mouse, but there are limitations at present to which keyboards can be scanned in. This means all agenda items need to be pre-prepared on the one screen.


Collaboration is much easier and more engaging than existing meeting platforms (Zoom, WhereBy, Teams, etc.) - directional audio means that when someone turns away from you, they are muffled. It actually feels like you are in room together. We also end all of our meetings with the ‘High Five’ feature, it’s pretty cool!


What’s holding it back?


Resolution. The headset hurts your eyes after a while, because the resolution just isn’t high enough to be comfortable. It’s not high enough to showcase User Interfaces in VR either, nor to be able to peer program, so you need to switch back to video conferencing for these kind of tasks. 


The other big ticket on my wishlist now is to set up a VR room at home. Drawing in the air is really, really difficult. So when using the whiteboard you need to have a solid surface to write against, you also need to have a keyboard and set up that works with the physical prompts in your virtual reality.


But almost all of the drawbacks of VR for work are technology issues that will inevitably be solved by the march of technology. The headset will get lighter, the resolution higher, the controllers more tactile in their response. 


So call me a convert? Maybe.


I’m more excited about the promise of VR than I was before, and I’m enjoying using it. There is a definite business use for this technology now, but is it at the point where everyone should have a VR headset on their desk? 


We’re still trialling it at Patient Zero so you’ll have to wait for our answer on that. But personally?


We might not all need a VR headset on our desk, but in a few years? Absolutely.

Share This Post

Get In Touch

Recent Posts

May 20, 2025
We’re proud to announce that Hanieh Madad has been named the winner of the Technical Award at the prestigious 2025 ARN Women in ICT Awards.
Copies of the book DesignedUp are stacked on top of each other on a pink background
By Lennah kuskoff May 5, 2025
At PZ, we’re always exploring how design and technology can better complement each other. We recently hosted a Lunch & Learn featuring Emma Carter, Experience Design Leader and author of DesignedUp, whose talk was a candid, experience-rich exploration of what it takes to create great products, and even better collaboration between disciplines.
By Joe Cooney May 5, 2025
A friend and former colleague reached out to me recently to ask if I could help him fix a couple of bugs in a small project he’d been working on. He was not a developer, but had worked in and around developers for his whole 20+ year career as a business analyst, product owner and program manager. With the advent of tools like Cursor and Lovable his lack of coding ability was (maybe) no longer a barrier to getting some ideas he’d been incubating in his mind for a while, out into the world. With credit card in hand, he dived headfirst into the world of “vibe” coding. We met for coffee, and he showed me the prototype he’d built. I was quite impressed with what he showed me (running on his laptop…deploying it anywhere was a bridge he had not crossed yet) – a capable working prototype that demonstrated the ideas he was trying to prove out. I asked him about the “development experience” and he said it had been great at first, and he’d been able to make a lot of progress quickly, but at some point he hit a bit of a wall where each change he tried to make introduced more issues, and he felt like it was pointless to continue. He’d switched between a few different AI coding tools in an effort to see if the problems he encountered were specific to the tool he’d started with, but without success. The vibes had run out.
By Joe Cooney April 3, 2025
Making cybersecurity fun and engaging with capture-the-flag (CTF) events—boost team collaboration, enhance security skills, and turn dry security practices into an exciting challenge!
More Posts