Feb 13, 2020

Workshops can be more efficient than meetings

Avoid endless discussion and get things done with workshops

Say, your team gets a new project with a challenge to “Design better wayfinding for hospital X”. Things are very abstract and everyone has different opinions. At this point, meetings most likely will be less effective because you’ll need hours of discussion to get alignment.

The biggest contrast between meetings and workshops is the discussion structure. Meetings require a linear discussion; which means, one person talks, then the other person talks, and so on. Workshops, on the other hand, will be much effective because it allows parallel discussion.

Benefits of workshops

Parallel discussion

Give everyone post-it and sharpie. Everyone can start writing their opinions or ideas, at the same time. You’ll get very diverse ideas for less than 5 minutes, that otherwise will take more than 30 minutes to discuss all of them in a meeting.

Everyone has an equal voice

No matter what your title or position in the company, the workshop equalizes the voice level because everyone’s voices represented in the post-it. It’s a great way to avoid the loudest voice in the room to win. Also, give a voice to the silent one.

Collaborative and real-time alignment

Workshops allow everyone to contribute their perspective; questions, ideas, or insights. Imagine, if a designer in your team explores ideas for 2 days alone. Chances are, the exploration can’t be very diverse. Then, your team will hold a meeting to review the designer’s work just to find out the work is not aligned with the product vision.

What if, instead, everyone in the team spends 2 hours doing a brainstorming session? Not only the idea become more diverse. It also allows real-time alignment because everyone agrees and makes a decision together. As a result, your project can move forward faster.

Guided conversation

Unlike meetings, in workshops, there is a formal facilitator to facilitate the activity. Needless to say, this is beneficial because there’s somebody who really manages the discussion, helps the team understand the agenda, and move the team along until producing the expected output.

Feedback from real people

Last month, In Bukalapak, we started to encourage people to consider workshop format instead of meetings. Here are a few words from people who tried the workshop format:

“I love we have a rich perspective to solve one big challenge together.” Product Manager

“From this activity, I started to understand what concerns that PM and Designer have. It gives me an opportunity to help and contribute more.” Data Scientist

“I wouldn’t imagine if we can come up with all of these ideas. I’m excited to keep doing this in next projects” Researcher

Closing note

Challenge: Workshops require a facilitator Althought workshops can be useful, it has a specific challenge too. It requires someone to facilitate the conversation and have some level of proficiency in a few methods to direct the project. It’s also important that the facilitator come prepared with the agenda to make sure the workshop is effective and achieve the goal. That being said, the workshop can be efficient but it centered on how well the facilitator manages the workshop.

Nothing wrong with meetings There’s nothing wrong with meetings. Meetings can be a good format when you need to report, monitor the project, or do some work review. But, for some instances when your team needs to make a decision and get things done, the workshop can be a better alternative.

The last thing you want is to sit down for 1-2 hours and end up with nothing other than debates or endless discussion. Share this with your team and start trying 30 minutes or a 1-hour workshop to get things done.

So, what do you think? Are you ready to have an efficient way to collaborate through the workshop?

ask me question illustration

Book a 50 minutes chat

Get career advice or portfolio review. We'll work together on your career challenge. More details. →

ask me question illustration

Ask a question

Send your question about the most recent post. If I can, I'll answer it on the blog. (This will open your email client)

ask me question illustration

Subscribe to newsletter

Get the post right into your inbox every time a new post is published or get a weekly email, you choose.

2021

Mar 01 Product design leadership — Setting direction
Feb 26 Friday diary 02: On GUI history, learning, and explain features.
Feb 25 Product design leadership — Create changes
Feb 24 Product Design Leadership series
Feb 22 Documenting is a good team’s habit
Feb 18 Have a hard time getting design feedback?
Feb 18 I'm writing a book.
Feb 16 A manager cried in front of me.
Feb 15 Should I move to the managerial role?
Feb 12 Friday diary 01: On personal development, being senior, and breaking small task.
Feb 11 Evangelizing the human-centered practice
Feb 09 Human-centered team vs. Feature-centered team – Strategic insight
Feb 08 Human-centered team vs. Feature-centered team – Strategic relationship
Feb 08 Human-centered team vs. Feature-centered team – Overview
Feb 05 Dealing with top down request
Feb 03 Every team has its unique challenges.
Feb 02 Business aware designer – Recognize your competitors
Jan 29 Business aware designer – Job to be done
Jan 27 Business aware designer – Value proposition
Jan 26 Business-aware designer - overview
Jan 25 What do product designers do?
Jan 22 Announcement for mentorship program
Jan 21 Community story: impostor syndrome
Jan 20 Should startups build a design system?
Jan 18 How I overcame my impostor syndrome
Jan 17 User metrics - Signals and Metrics
Jan 15 User metrics - Vision
Jan 14 User metrics - Overview
Jan 13 Give back to the community
Jan 12 4P: framework for choosing job
Jan 11 Take things with a grain of salt
Jan 09 Principles of good portfolio design
Jan 07 An effective product design portfolio – Constraint
Jan 06 An effective product design portfolio – Structure
Jan 05 Connect user and business with AARRR framework
Jan 05 My blog in 2021
Jan 03 Should I build the feature request from customers?

2020

Dec 30 Feature requests are stupid business activity
Dec 21 The benefit of creating a design portfolio
Nov 24 About self-doubt
Nov 11 Don't confuse design with artifacts
Nov 06 What if you need to find another job tomorrow?
Oct 26 Making sense of your design project by writing
Sep 30 When was the last time you reflect?
Sep 29 Methods are tools
Sep 24 How can I get a bigger project?
Sep 23 Entering product design – Chapter 7: Craft and analysis
Sep 22 Entering product design – Chapter 6: Narrow collaborator
Sep 21 Entering product design – Chapter 5: Soloist product designers
Sep 17 Entering product design – Chapter 4: Product designer key skill areas
Sep 14 Entering product design – Chapter 3: Misunderstanding of business
Sep 11 Entering product design – Chapter 2: Principles over steps
Sep 10 Entering product design – Chapter 1: Silver bullet
Sep 10 Entering product design – Overview
Sep 04 SAR: A framework for concise storytelling
Aug 27 Start your design with outcome
Aug 24 New medium post: Collaboration ground for design systems
Aug 17 Action points
Aug 13 Pulse check: Listen to your team
Aug 11 You should actively apply for a new job
Aug 10 Design systems' area of influence: Service (3/3)
Aug 04 Design systems' area of influence: Offering (2/3)
Aug 03 Design systems' area of influence: Identity (1/3)
Aug 01 My mom ran me to the hospital
Jul 29 Reader question: Do we need to build MVP for every product?
Jul 27 Reader question: Do I need formal design education?
Jul 24 Recognize assumptions
Jul 21 Sandbox for your personal growth
Jul 20 Start your week with questions
Jul 17 Specificity in feedback
Jul 15 Don't sell the design. Sell the business impact
Jul 14 Overwhelming inspiration
Jul 13 The framing trap
Jul 10 Everyone vs. Specific
Jul 09 The blind horse designer
Jul 08 Set the context in your meeting
Jul 07 Let's just try and see what happens
Jul 06 Managing expectation
Jul 05 Low UX maturity company
Jun 17 A simple exercise for career reflection
May 31 The “Coach sheet” – A paper-based system for people management
May 26 Bring calm to your remote team
Feb 13 Workshops can be more efficient than meetings
Feb 07 3 questions designers should be asking
Feb 06 Walking 1on1: A refreshing way to connect

2019

Nov 21 My hope for stubborn 'Innovators'
Jul 18 Five simple actions to help you gain more time
Apr 23 Evolving Product Experience Principles at Bukalapak
Mar 09 A framework to give better design feedback: Analyze, Discuss, Suggest
Jan 28 Making a decision is hard, here's my rule of thumb

2018

Dec 04 Essential skills for Product Designers
Nov 16 Quick life update
Nov 06 Things I learned from working at Shopify
Oct 15 About design critique
Sep 17 Common icon design problems you should avoid
Sep 06 Preface: Welcome to yellowstroke.com