Teams waste time in problem-solving workshops when they brainstorm without constraints, then avoid the hard pick—so nothing changes and customer trust keeps leaking. In this article, Jef Menguin shares how to use customer stories to drive disciplined action, not a brainstorming party. Apply the board, end with “Who owns this?” and “When will customers feel the difference?”, then share it at work so your workshops produce movement, not just motion.
You’ve probably facilitated a session where everyone contributed, the whiteboard filled up, and the energy felt productive. People shared ideas. People nodded. Someone even said, “Ang dami nating napag-usapan.”
Then Monday came.
And the same customer pain showed up again.
That’s the frustration with many problem-solving workshops. They create motion, but not movement. They generate ideas, but not decisions. They make people feel involved, but not accountable.
Customers don’t benefit from your workshop.
Customers benefit from what your workshop changes.
Why customer stories belong at the center of problem solving
If you want a workshop that produces real action, start with a customer story that has friction and stakes. A real moment where a customer struggled, waited, got confused, or lost trust. Because when the “problem” is abstract, teams stay abstract too.
Customer stories make problems concrete. They give you a scene, not a slogan. And a scene forces a different kind of thinking—less opinion, more empathy; less guesswork, more evidence.
If you want a clean handoff from analysis to action, the previous post on case studies helps. It shows how to use customer stories to train better decisions before you try to solve anything. Here it is: Use Customer Stories in Case Study Analysis to Train Better Decisions.
Now we go one level deeper.
We stop discussing the story.
We start fixing what the story reveals.
From “ideas” to “solutions under constraints”
A workshop becomes powerful when it faces constraints honestly.
Because customer problems don’t happen in a perfect world. They happen when people are busy, information is incomplete, policies exist, systems break, and emotions are high. If your solutions ignore those realities, your solutions won’t survive contact with Monday.
So the shift in a real problem-solving workshop is simple:
Stop hunting for “best ideas.”
Start designing the best move given the constraints.
That mindset changes everything. It prevents the usual trap of proposing what sounds great but never gets implemented.
The tool: Pain → Cause → Option → Tradeoff → Pick
This is your workshop board.
It’s not fancy, but it keeps teams honest. It turns emotional storytelling into disciplined action.
1) Pain — What did the customer experience?
State it plainly, from the customer’s side.
Not “delay in processing.”
But “customer waited three days without an update.”
2) Cause — Why did it happen in our system?
Don’t blame people. Find the pattern.
Is it unclear ownership? Slow approvals? Missing templates? Fear of overpromising? Broken handoffs?
3) Options — What could we do next time?
Generate 3–5 options quickly. Don’t evaluate yet. Just list.
4) Tradeoff — What do we give up with each option?
Every option has a cost.
Faster responses might mean less certainty. More ownership might mean more workload. Automation might mean less personalization. Name it.
5) Pick — What will we actually do?
Choose one option to implement. Assign an owner. Set a deadline. Define what “done” looks like.
That last part is the workshop.
Everything else is warm-up.
A customer story you can use as your workshop starter
A customer asks for an update. The team has partial information, but not the final answer. Nobody replies because people don’t want to overpromise, and they don’t want to step on anyone’s toes internally. The customer follows up again. Still quiet. When the reply finally comes, the customer sounds different—less engaged, less trusting.
Now put that story on the board.
Pain: “Customer waited too long and felt ignored.” Cause: “No clear owner + fear of responding without full info.” Options:
- Reply within 2 hours with partial clarity and a next update time
- Assign a single point person for customer updates
- Create a simple update template for incomplete info
- Escalate internally after 1 hour of no response Tradeoffs: Speed vs certainty. Ownership vs workload. Pick: Choose one and commit.
Then ask the question that makes it real:
What would we do if this customer was our most important account?
Let them answer. Even silently. Especially silently.
How to facilitate this without turning it into a brainstorming party
Keep the pace.
Start by reading the customer story out loud. Then give one minute of quiet writing: “Write the pain in the customer’s words.” That short silence changes the room. It makes the problem feel human.
Next, limit causes to patterns, not personalities. If someone says a name, redirect: “What in our system made that likely?” You’re building a culture where people solve, not blame.
Finally, force a pick.
Workshops fail when teams refuse to choose. They hide behind “We need more data.” Sometimes you do. But many times, you already know enough to make a better default and test it.
You don’t need perfection. You need motion.
What changes when workshops end with a real pick
When you run workshops this way, teams stop treating customer pain as background noise. They start treating it as design input. Leaders stop collecting ideas and start making calls. People leave with a decision they can implement, not a list they’ll forget.
And customers feel the difference.
They experience faster updates. Cleaner handoffs. Fewer repeated explanations. More ownership. Less waiting in the dark.
That’s the transformation.
Not a workshop that “went well.” A workshop that changes what customers experience.
Try this in your next workshop
Pick one customer story from the last 30 days that still annoys you a little. The ones that sting are usually the ones worth fixing. Put it on the Pain → Cause → Option → Tradeoff → Pick board.
Then end with two lines:
Who owns this? When will customers feel the difference?
Write the answers where everyone can see them.
That’s how you turn a customer story into action.
