Case study · Facilitation
A 2-hour workshop I designed and ran for two cohorts of new junior hires, to help them see the big picture of a product and think like problem-solvers.
Role
Workshop designer and facilitator
Audience
Junior hires, many from computer science and software engineering
Format
2-hour workshop, two cohorts
Follow-up
Prototype pitch session (second cohort)
Add image: Hero: a photo from the workshop
Why I ran it
A new batch of junior hires had joined, many with computer science and software engineering backgrounds. I wanted them to see the big picture of a product and think like problem-solvers, so they would understand how their own work affects the whole project. It also got them ready for the team project that was coming up.
Two ideas I wanted them to remember
Every good product sits at the intersection of desirability, viability and feasibility. And every Jira ticket is more than a single task: it’s a step toward the value of the whole product.
Add image: The desirability, viability and feasibility diagram
I kept it hands-on and team-based. Brainstorming and role-playing kept everyone engaged, and just enough structure kept teams focused.
Step 1 · Opening
I opened with a product everyone knows. I asked who uses Uber, then explained what happens behind the scenes: how rides are priced and matched, and how the company makes money. It showed that apps don’t just happen. Designers plan every step with intention.
Step 2 · Framework
I asked everyone to name a favourite product and why they like it. Then I introduced desirability (people want it), feasibility (it can be built) and viability (it makes business sense). Miss one, and the product won’t work.
Step 3 · 10 minutes
Each team member took a role: CEO, CPO, CTO, CMO or, in later sessions, CAIO (Chief AI Officer). In the first session, 12 participants formed three teams of four. The roles made the activity playful and made sure teams looked at the product from every angle.
Step 4 · 10 minutes
Teams wrote a clear problem statement and nothing else. No solutions yet. Articulating the problem before jumping to solutions was new for many of them, and it is critical.
Step 5 · 40 minutes
Teams brainstormed on sticky notes, with their role in mind but not limited by it: a CEO could suggest a technical solution too. I walked between teams, asked questions and joined discussions when needed. I gave them two simple tools: “How might we?” to frame the problem, and a prioritization matrix (impact against effort) to pick the ideas that bring the most value in the least time.
Step 6 · 50 minutes
Each team presented its product, with up to 10 minutes to pitch and 15 for feedback, and answered challenging questions from a senior colleague who joined the session. In the first session we ran out of time for detailed feedback, so I built that time into the plan.
Add image: Teams working with sticky notes
Add image: Roles and presentation prompts on screen
I put eight questions on screen so each pitch covered the whole product, not just the idea.
What type of product is this?
Website, mobile app, desktop software and so on.
What problem does it solve?
The specific need or pain point.
Who are your users?
The target audience and why they need it.
How will you make money?
The revenue model.
What technology do you need?
Platform and technical requirements.
How could AI or agentic AI be part of it?
Only where it solves a real user problem.
How will people find out about it?
Marketing and user acquisition.
How will you test it?
How you make sure it actually solves users’ needs.
For the second cohort I added a follow-up session two days later. Teams came back with prototypes, pitched their solutions and got feedback again.
I encouraged them to explore AI and agentic AI to build their prototypes, but only where it solved a real user problem. I also introduced the MVP idea: the simplest version of a product that still solves the user’s main problem.
Add image: A team demoing its AI-built prototype
The teams were engaged from start to finish. They discussed every part of their product, faced the challenges and solved them together. Their final pitches were far more mature than their first presentations, and it all happened in just a few days.
Challenge
In the first session we ran out of time for detailed feedback after the pitches.
Value
A second session gave teams another round of pitching and feedback, and the difference showed in how mature their final pitches were.
I never expected facilitation to become one of my favourite parts of my work. I look forward to running more sessions like this and becoming a better facilitator.