Oh, That's How I Help The Team?
A sustainable mobility start-up discovers how their tester can evolve from hands-on automation to quality-driving force.

A sustainable mobility start-up was growing fast. Really fast. Hockey-stick growth.
They organised workshops to get their expanding team aligned as complexity increased.
When they called me in for a RiskStorming session, they already knew what mattered and which risks were looming.
What they didn't have: a plan for actually implementing the structures needed to monitor and control things.
The problem with action points
I see this pattern often in teams running Scrum or similar practices. Retrospectives generate action points.
But there's a difference between simple action points, meatier initiatives that need planning, and things that should start as a Proof of Concept. That distinction isn't always obvious.
This team had fallen into a familiar trap. Improvement initiatives start small and actionable. Then they grow. They become complex. And they die.
A role that changed
The biggest takeaway from the session? Their tester suddenly understood his job differently.
Before: most of his time went to automated testing. Working hands-on. Mostly separate from the team.
During the workshop, the team effectively gave him a new mandate. "You need to steer us to deliver better quality software."
They told him: set a minimum quality level and guard it.
That's a powerful starting point for quality coaching or engineering leadership.
His role shifted from being hands-on and isolated to being a quality-driving force that touches multiple disciplines.

