Product design question
How would you design a metaverse solution for office management and collaboration?
- Atlassian
- Product design
- Medium
Practice this question out loud. An AI interviewer asks it, follows up like a real interviewer would, and scores your answer. Type or speak.
Start a mock interview on this question · Mock interview from a job description
What this question tests
Tests product design for an unproven, high-hype technology applied to a concrete B2B use case: can you ground a metaverse concept in real collaboration pain points instead of novelty.
How to approach it
- Clarify the user: distributed teams at Atlassian's customers who struggle with the limits of video calls and flat documents for spatial or brainstorming-heavy work.
- Identify the specific pain point a metaverse solves better than existing tools: persistent virtual whiteboards and spatial audio for brainstorming sessions, where flat video calls lose the feel of standing at a shared whiteboard.
- Prioritize a narrow use case first, virtual workshop and retro sessions with persistent 3D sticky-note boards, rather than a full always-on virtual office, since adoption of immersive tools is still low.
- Design for low-friction access: browser-based or lightweight VR entry so most users are not forced to own a headset, since headset penetration in enterprise is still small.
- Integrate with existing Atlassian tools (Jira, Confluence) so outputs from a session sync directly into real workflows, rather than the metaverse session being a disconnected novelty.
- Define success as session-to-action conversion (percentage of ideas from a session that become tracked Jira tickets) and repeat usage, not headset sign-ups alone.
What a strong answer includes
- Scopes the metaverse idea narrowly to workshops and retros, a bounded, high-value use case, rather than an ambitious always-on virtual office that is unlikely to get adoption yet.
- Explicitly addresses the hardware adoption barrier by defaulting to browser access, showing realism about current headset penetration.
- Ties the feature back into Atlassian's actual product suite (Jira, Confluence), avoiding a disconnected gimmick.
- Uses a concrete conversion metric, ideas becoming tracked tickets, that ties novelty usage to real business value.
Common mistakes
- Designing an ambitious always-on virtual office without addressing headset adoption or realistic near-term usage.
- Treating this as a standalone novelty with no integration into existing collaboration tools teams already use.
- No metric beyond usage or sign-ups, missing whether the experience produces real work output.
Likely follow-up questions
- How would you validate demand for this before investing in a VR-specific build?
- How would you measure success for users without VR headsets using the browser version?
- What would make you kill this project after a pilot?
More product design questions
- You are a new PM at Facebook. Design an app to help people save money.Atlassian · Product design · Medium
- Design a mobile application to assist hobby gardeners.Atlassian · Product design · Easy
- Tell me about a product that can be sold at vending machines beyond classic snacks and drinks.Atlassian · Product design · Easy
- What is that one product feature that would change the landscape of Devops/GitOps?Google · Product design · Hard
- Imagine an ideal kitchen. How would you design it?Atlassian · Product design · Easy
- How would you improve Outlook for the use case when people get overwhelmed by number of emails received after returning from a vacation?Microsoft · Product design · Medium
More questions from Atlassian
Learn the skill behind it
Chapters of the AI PM course that teach what this question tests.
- Chapter 4: Discovery and strategy for AI products
- Chapter 7: AI UX and human oversight: design for a system that is wrong sometimes
- Chapter 14: Get the job: the AI PM interview loop