WorkshopX
A case study of why and how I designed a web-based workshop platform during the pandemic. From a simple “click and go” idea, the project evolved into a full design journey — rapid prototyping, user testing, and public iteration — exploring how simplicity, privacy, and constraints shape meaningful collaboration.
Proof of concept
To validate the core assumptions - zero friction, simple join flow, and workshop-style collaboration - We built a lightweight proof-of-concept.
The POC focused strictly on the experience: no signups, one-click entry, high-quality audio/video streaming.
The goal was to prove the product hypothesis quickly: people will prefer a low-barrier, privacy-focused meeting flow for creative sessions.
We decided to open up to 7 participants to join a workshop simultaneously. We picked the magic number of 7 according for our initial performance testing, and also because it is a good team size which could be fed with two-pizzas.
Once we have done the initial testing with our friends, it was time to introduce it to the world. We made an intro video and released it on Product Hunt.
Power-up with the tools we already love.
We kept the momentum and kept polishing the user interface, in the meantime also added more productivity features as we test and use it ourselves.
A team workspace was built up for more collabration possibilities.
A whiteboard is always important for quickly sketching out the ideas and keep the team on the same page.
The textpad is the developer's way of sketching out their thoughts and ideas.
For designers they could look at the same Figma design and discuss on how to polish the details.
For casual users, they could also invite friends and watch the same youtube video together.
Reflection & learnings
Looking back, WorkshopX was less about creating a polished product and more about practicing a complete design cycle end to end — from framing a problem, to rapidly prototyping, testing with real users, and iterating in public.
Start small, validate early.
Building a proof of concept with only the core assumptions made it easier to test ideas quickly and avoid over-investing in features that might not matter.
Show, don’t just tell.
A live POC and short demo video communicated the concept far better than documentation alone, helping peers and testers engage with the idea immediately.
Feedback loops matter more than polish.
Even rough prototypes generated meaningful insights. Early feedback revealed blind spots in copy, flows, and technical stability that I would not have anticipated alone.
Constraints shape creativity.
Limiting sessions to small groups and choosing only a handful of collaboration tools kept the design focused, and helped me practice prioritization and scope control.
Designing for practice vs. designing for scale are different mindsets.
In this project, the emphasis was on learning through making rather than optimizing for growth. This reframing freed me to experiment more openly.