—
“The future of work is remote. The future of leadership is empowerment.” — Bill Gates
1
My Role: Head of Product & Design
When I joined Kumospace in early 2022, we were beginning an exciting pivot. We'd moved from virtual events—online conferences and parties—to virtual offices for remote teams. The market opportunity felt huge, and we started with a beta program with 10 teams to test our assumptions as we built towards “the future of remote work”.
I led both product strategy and design for this platform transformation, managing a product manager, two product designers, a 3D artist, and a product marketing manager, while working closely with 10 engineers split across mobile and desktop platforms.
1.1
Product Leadership
I defined quarterly product strategy that balanced the technical challenge of platform transformation with evolving user needs and competitive positioning. This included deciding which legacy event features to preserve, how to sequence new office capabilities, and when to shift priorities based on user insights. I managed feature prioritization across competing demands from different user segments while ensuring engineering bandwidth aligned with business impact.
1.2
Design Leadership
I drove the design strategy for the transformation, writing PRDs to align the team on problems and requirements. I guided designers through review sessions to ensure we stay consistent within our own design system and standard UX patterns while giving them creative ownership within clear problem definitions. When the company laid off designers in late 2023, I transitioned to hands-on design work, creating wireframes and final design hand-offs myself.
1.3
Cross-Functional Collaboration
I worked with the data team to design A/B tests, analyze feature usage patterns, and define success metrics for our features and workflows. I partnered closely with customer success to identify what was working and what wasn't, using their frontline feedback to inform our product decisions and feature iterations.
I worked with engineers closely from kick-offs to feature testing. When technical constraints conflicted with UX goals, we'd first investigate whether issues were user confusion or technical problems. For UX issues, we'd iterate designs. For technical issues, engineers would investigate solutions, and if the ideal technical solution wasn't viable, we'd design UX workarounds.
1.4
Project Management
The most challenging aspect was managing features at different stages simultaneously - researching and working with designers on future features, tracking current development (including scope adjustments and issue resolution), and analyzing results from shipped features to inform next plans. The entire integration took about a year, rolled out in phases.
2
The Challenge: Events vs Offices
The original Kumospace product was virtual event spaces. This example of a virtual cocktail lounge gathered people together to hang out, play board games, mingle, and listen to music.
The pivot required rethinking our platform's core mechanics. We couldn't start from scratch—we had an existing spatial platform with users who loved it for events. The challenge was transforming these core features to work for offices without losing what made them valuable in the first place.
2.1
What made our event platform successful
One shared space Everyone could see and talk to everyone, creating energy and spontaneous mingling
Always-visible video presence Seeing all attendees made the space feel alive and encouraged participation
Frictionless walk-ups Anyone could approach anyone instantly, just like a physical party
Ephemeral nature Conversations existed only for that event's duration with no need for history or persistence
2.2
Why those same features became problems for offices
One shared audio space No way to have private client calls or confidential team discussions
Always-visible video presence Unsustainable camera fatigue when people needed to be "there" for 8 hours daily
Frictionless walk-ups Constant interruptions that destroyed focus time and deep work
Ephemeral nature Conversations and context disappeared, no way to reference past decisions or maintain project continuity
3
Remote Work Reality We Were Solving
As we researched our new market through intake interviews and reviewing remote work stats, we discovered remote teams were struggling with fundamental workflow problems:
3.1
invisible Colleagues
Unlike physical offices where you can see if someone's at their desk, in a meeting, or grabbing coffee, remote workers had no ambient awareness of their teammates. This led to awkward interruptions or missed opportunities for collaboration.
3.2
Lost of Spontaneous Collaborations
The natural “Can I grab you for a minute?” moments that drive innovation were nearly impossible remotely. Everything had to be scheduled, losing serendipitous problem-solving.
3.3
Meeting Friction
Even simple conversations required the overhead of “Let me send you a calendar invite” - creating barriers to the quick syncs that keep teams aligned. Sometimes sending a Slack message took hours to get a reply, making real-time collaboration nearly impossible.
3.4
Tool Fatigue & Context Switching
Teams were constantly jumping between Slack for chat, Zoom for video calls, Google Calendar for scheduling, and email for follow-ups. Each switch broke focus and made it cumbersome to maintain conversational flow.
3.5
Lost Context & Scattered Conversations
Important discussions were split across platforms - quick decisions in Slack, detailed planning in video calls, follow-ups via email. Teams lost track of why decisions were made and couldn't easily reference past conversations.
Kumospace's spatial awareness platform already provided a foundation for solving some of these problems - users could see colleagues in the virtual space and approach them naturally for quick conversations. But adapting these event-focused interactions for professional workflows required changes to privacy, content persistence, and collaboration features.
4
Privacy and Boundaries
Kumospace office has personal offices, team areas, conference rooms, and open areas to facilitate multiple conversations and support the needs of private conversations.
The pivot from virtual events to virtual offices created a fundamental design challenge around three competing needs:
Virtual offices require all three simultaneously:
Spontaneity The "Can I grab you for a minute?" moments that drive collaboration
Privacy Confidential calls, sensitive discussions, focus time for deep work
Presence Being available and visible to your team throughout the day
But these forces pull against each other. Maximum spontaneity (everyone can approach anyone) destroys privacy and makes presence exhausting. Maximum privacy (locked away) kills spontaneity and defeats the purpose of presence. The challenge was designing a system that balanced all three.
4.1
Approach
4.1.1
Internal Discovery
Using Kumospace as our own virtual office, we immediately realized that we wanted to see everyone in the office simultaneously while maintaining privacy options. Initially, rooms were in separate views, forcing users to leave their room and return to the “lobby” to see where teammates were located - breaking the natural awareness that makes offices effective.
4.1.2
Office Design Research
We researched physical office design layouts to understand the needs of an office besides conference rooms and offices. When do offices use pods vs personal offices vs cubicles? How are offices designed to enhance collaboration but also allow for deep focused work? And how does one design for flow to encourage the serendipitous meetings “water cooler” moments.
4.1.3
Maintaining Interaction Model
Since Kumospace already had an established spatial visual language where users move their avatar around with a mouse and interact with objects, we wanted to keep that interaction model consistent. Adding doors extended this existing language naturally - users could approach and interact with doors just like other objects in the space, maintaining the intuitive spatial metaphor while providing clear visual privacy cues.
4.1.4
Beta User Testing
We started our learning with the goal of getting 10 beta remote teams on board to use Kumospace as their virtual office. We tested office layouts internally and with beta teams to find virtual office layouts optimized for collaboration, focused work, and crossing paths. We experimented with pods, personal offices, cubicles, and even the controversial Munger Hall design by Charlie Munger for University of California, Santa Barbara.
4.2
Solution: Zone-Based Audio Architecture
4.2.1
Separate Audio Spaces
Rather than having everyone in one big audio space (like events), we built rooms that created distinct audio boundaries. When you entered a room, you only heard people in that room, enabling private conversations while others continued working in different spaces.
4.2.2
Room Types and Ownership
Room types accommodated various office activities and meetings that may require different levels of privacy and offered offices the flexibility to design their own working model.
Personal Offices Spaces that could be decorated and personalized by their owners
Conference rooms Bookable spaces with integrated calendars for formal scheduling
Open zones Collaborative areas for spontaneous interaction
4.2.3
Visual Privacy Language
We established doors as the universal privacy signal. Public collaboration spaces remained doorless and open, encouraging spontaneous interaction. Offices and conference rooms featured doors that occupants could control, creating clear visual cues about accessibility.
When doors were closed, outsiders couldn't see the videos or screen sharing happening inside the room. But when doors were open, people could see the video feeds and what was being shared - just like walking by a conference room or public area in a physical office. This allowed for more transparency and awareness of ongoing work, while still providing privacy for confidential meetings.
4.2.4
Access Control System
Users inside rooms could open and close doors at will. When doors were closed, anyone outside had to “knock” - sending an audio alert to everyone inside the room. Any occupant could then choose to open the door, replicating natural office etiquette.
4.2.5
Smart Muting and Performance
Rooms could be configured to auto-mute newcomers, serving dual purposes. For large presentations, most attendees joined to listen rather than speak. For intimate meetings, everyone expected to participate. This also solved a technical challenge - reducing camera and microphone load when many people joined.
4.3
The Impact
“The rooms was the game changer —that's when everyone was like, ‘OK we're on board.’”
Moving from one shared audio space to room-based audio was fundamental to the events-to-office transformation, enabling multiple simultaneous conversations and professional privacy.
5
Availability Awareness
Interview transcriptions and data organization
Avatar states
Profile card with calendar
In physical offices, you can glance over to see if a colleague is deep in focus, on a call, or available for a quick question. Remote work eliminated this ambient awareness, forcing teams to choose between awkward interruptions or the friction of switching to calendar apps to check availability. How do you enable the natural "is now a good time?" assessment without breaking workflow?
5.1
Approach
5.1.1
Beta Team Reasearch
After few weeks of office usage, we would check in with the beta teams. We send everyone on the team a survey and interviewed a few team members. Insights emerged:
This feedback led us to build availability features iteratively, starting with what we already had and adding layers based on user needs.
5.1.2
Track Adoption and Feedback
We tracked feature usage and user feedback for the availability features.
5.2
Solution: Iterative Availability Features
5.2.1
Build on Existing Spatial Awareness
We already had spatial awareness - users could see where teammates were located in meeting rooms, shared workspaces, or private offices, providing context about their current activity and likelihood of being interruptible.
5.2.2
Add Status Indicators
We built status indicators (available, focusing, away) so users could communicate their work mode and give teammates clear signals about their availability. We combined status indicators with audio and mic management, into a toggle—instead of clicking on mic, audio, and status buttons separately.
Focusing = audio and mic off
Available = audio and mic on
Colleagues could still “nudge” them for urgent communication, sending a chime and notification
This balanced respect for focus time with the ability to reach someone when truly necessary.
5.2.3
Calendar Integration
Finally, we added calendar into the profile card. To see when someone would be free, users could hover over a teammate's avatar to see their current status and upcoming schedule - whether they were free immediately, busy for a few more minutes, or had back-to-back meetings. The hover interaction revealed schedule gaps, letting people make informed decisions about when to approach colleagues and coordinate timing without leaving the platform.
5.3
The Impact
Status indicators became one of the top features, used on average 5.5x times a day by people who use it. Teams could respect each other's focus time while maintaining spontaneous collaboration opportunities. The friction of “let me check when you're free” was eliminated, enabling more natural communication patterns that balanced productivity with accessibility.
6
Conversation Continuity
User survey results: External application usage
Solution: Persistent chat with channels, group DM, search, tags, reactions, threads, and editing
Solution: Full featured chat with file sharing
Solution: Meeting recordings saved in the left panel
Remote teams were losing context as conversations scattered across platforms. Quick decisions happened in Slack, detailed planning occurred in video calls, and follow-ups lived in email. Teams lost track of why decisions were made and couldn't easily reference past conversations, creating knowledge gaps and repeated conversations.
6.1
Approach
6.1.1
Customer Development & Business Strategy
As we worked to convert trial users to paying customers, we consistently heard that teams didn't want to pay for separate services - Zoom for video, Slack for chat, Google or Notion for file management. This feedback revealed that conversation continuity wasn't just a UX problem, it was a business opportunity.
6.1.2
User Survey & Feature Gap analysis
We sent out a survey to all our users asking if they were still using other chat or video conferencing apps alongside Kumospace. The results were eye-opening: 84% were still using other video conferencing apps and 80% were using other chat apps. The top reasons were that other teams in their company were using these tools and stability concerns.
6.1.3
Feature Prioritization
Through sales intake conversations and our user survey, we identified the essential features needed to replace Slack and Zoom. Meeting recordings was a top requested feature and structured chat features like searchable chat history, threads, channels, and groups were at the top of the list.
6.1.4
Competitive Analysis & Feature Strategy
We researched Slack, Microsoft Teams, Zoom, and Google Workspace to understand how they manage chat, video, and files. All these applications were fully featured, and for us to catch up would take years. Instead of trying to build all features to compete, we decided to offer the core features teams actually use as a bundle for a cheaper price, allowing teams to save money by replacing multiple tools.
6.1.5
Internal Testing
We tested our approach internally first, replacing our own company Slack to validate that our feature set could actually support daily team operations before rolling it out to customers.
6.2
Solution: Integrated Communication History
6.2.1
Persistent Chat Architecture
We built structured channels that maintained conversation history across all team interactions. Unlike temporary event chat, these channels preserved context over weeks and months, allowing teams to reference past decisions and maintain project continuity.
6.2.2
Meeting Recording Access
The ability to record conversations and access them later was available through the “recordings” section in the panel, so teams could reference important discussions when needed.
6.2.3
Chat Search
Users could search through all chat messages within the platform, making it easy to find past conversations and decisions without jumping between tools.
6.2.4
Seamless Communication Flow
Teams could start conversations in any mode - quick spatial chat while working, move to focused video discussion, then continue in structured chat channels - all within the same platform. Users never lost access to ongoing conversations and could search chat history and reference recordings later on.
6.3
The Impact
By housing all communications and discussions in one place, teams experienced more seamless collaboration and could easily find information without switching between tools. This also delivered cost savings - teams no longer needed to pay for separate chat and video applications.
7
Enable Real-Time Collaboration
Solution: Shared pointer for collaboration
Solution: Collaborative whiteboarding
When people work together side by side, they can naturally point to each other's screens, gesture to specific elements, and use body language to show engagement or direct attention. Remote work strips away these essential collaborative gestures, making it difficult for teams to work together effectively on shared tasks or provide real-time feedback during screen sharing sessions.
7.1
Approach
7.1.1
Identify the Missing Piece
From our user survey, we learned that the most requested feature for video conferencing was annotation - the ability to mark up and point to specific elements during screen sharing work sessions.
7.1.2
Iterating for Speed
Rather than building a robust annotation tool, we built this feature incrementally so we could release it faster. First we added the ability to share your pointer so people could see what you were pointing to. Then we added the ability to draw. Adding emoji drawing was easy, so we added that and people enjoyed it.
7.1.3
Cross-Modal Consistency
These collaboration features had to work seamlessly whether users were in map mode (seeing multiple screens) or gallery view (focused on one presentation)—allowing users to seamlessly switch back and forth while maintaining the interactive capabilities across different viewing contexts.
7.1.4
Track Adoption and Feedback
We tracked feature usage (screen annotation and screen sharing) and user feedback for the screen annotation features.
7.2
Solution: Interactive Visual Collaboration
7.2.1
Shared Pointer & Drawing Tools
We added the ability for users to toggle on their pointers so other users could see their pointer during screen sharing sessions, along with real-time drawing capabilities. Team members could circle important elements, draw arrows to highlight connections, or sketch out ideas directly on the shared screen - all visible to everyone in real-time.
7.2.2
Emoji Reactions
Users could stamp emojis directly onto the screen to react to specific content, providing immediate feedback and engagement without interrupting the flow of presentation.
7.2.3
Side-by-side Screen Sharing
In map mode, users could see multiple screens being shared side-by-side simultaneously - essential for live collaborative work where team members needed to share their screens to work together on the same project in real-time.
7.3
The Impact
After launching the shared pointer feature, screen sharing usage increased by 2% within two weeks. The annotation tools transformed how teams collaborated - members could point to specific details, react with emojis, and work together in real-time when multiple people shared screens side-by-side. This shifted remote work sessions from passive viewing to active collaboration, enabling the kind of detailed visual discussions that drive better decisions. The side-by-side capability provided collaborative workflows that traditional video platforms couldn't support.
8
Unified Interface
Original window-based UI system for ephemeral chat
Solution: Panel UI system for housing chat, calendar, and recordings
How do you house a complete communication suite - spatial map, video calls, structured chat channels, group DMs, calendar integration - in one interface without overwhelming users? The core UX challenge was creating space for all these features while maintaining the primary goal: seamless communication and collaboration.
8.1
Approach
8.1.1
Design Considerations
From our user survey, we learned that the most requested feature for video conferencing was annotation - the ability to mark up and point to specific elements during screen sharing work sessions.
8.1.2
Feature Grouping
Rather than building a robust annotation tool, we built this feature incrementally so we could release it faster. First we added the ability to share your pointer so people could see what you were pointing to. Then we added the ability to draw. Adding emoji drawing was easy, so we added that and people enjoyed it.
8.1.3
Reconsider the UI System
These collaboration features had to work seamlessly whether users were in map mode (seeing multiple screens) or gallery view (focused on one presentation)—allowing users to seamlessly switch back and forth while maintaining the interactive capabilities across different viewing contexts.
8.1.4
Incremental Rollout & Testing
We tracked feature usage (screen annotation and screen sharing) and user feedback for the screen annotation features.
8.2
The Evolution: From Windows to Panels
As we layered on features for virtual offices, our original window-based chat system became unworkable. Users ended up with multiple chat windows cluttering their view and blocking spatial navigation.
To support a complete chat system with searchable channels and group DMs, we redesigned the entire communication experience into a unified panel system.
The panel system created dedicated space for:
Structured chat channels for organized team conversations
Group DMs for quick coordination
Search functionality across all conversations
Calendar integration for scheduling and availability
This allowed users to access the full communication suite while maintaining their primary view options. Users could seamlessly switch between two primary modes while keeping panel access:
Map mode Full spatial awareness of the virtual office
Gallery view Focused video conferencing (like Google Meet/Zoom)
8.3
The Impact
We decided to roll out the change from a window system to a panel system since the impact was neutral.
Initially, we made panels persistent to encourage feature discovery, but anticipated users would want to hide them for a bigger office view. We tested this directly - users did complain - and since we had a backup design ready, implementing the show/hide functionality was an easy change.
9
Results and What I Learned
We successfully transformed the platform from virtual events to virtual offices, with the company hitting $1M ARR within one year. Although we built a lot and learned a lot, we also realized that the market was not as big as we thought. Eventually, leadership decided to pivot the company based on these market realities.
Transforming a platform from one use case to another requires more than just adding features - it means fundamentally rethinking user workflows and behaviors. The challenge wasn't technical complexity but understanding how to preserve what made the original platform valuable while solving entirely different user needs. This taught me that successful platform evolution requires deep user research and systematic testing at every step.
This project expanded my leadership scope from design collaboration to full product strategy coordination across engineering, marketing, sales, customer success, and data teams. I learned that translating user insights into aligned organizational action requires understanding how each function operates and ensuring everyone understands not just what we're building, but why. Design thinking provided a systematic foundation, but I had to develop new skills in business strategy and operational coordination to drive complex product decisions forward.