There’s one striking trait the truly successful tech teams have in common: they don’t run from their problems, they go looking for them. Where others see a roadblock to work around, they see a signal: the visible trace of a weakness in their product, their organization, or their technical approach. This shift in perspective, simple as it looks, changes everything. Because a problem you allow yourself to see is a problem you can solve, and every resolution makes the team a little stronger than it was the day before.
This is exactly the heart of the Lean mindset: treating every problem not as a fate to endure, but as an opportunity.
Every problem is an opportunity
Adopting this view means accepting that an obstacle carries more value than it costs. Concretely, a well-handled problem delivers three things:
- Improving quality and productivity. By tracing a malfunction back to its source, you don’t just fix a one-off symptom: you remove a cause that would otherwise have kept holding the team back, silently.
- Generating collective learning. A problem solved together becomes shared knowledge. A team doesn’t grow through the sum of individual skills, but through what it learns collectively with every obstacle it clears.
- Practicing continuous improvement on every front. Product, management, technical: none of these escapes this dynamic. Every difficulty is a chance to adjust, refine, and progress.
To make this tangible, let’s take a concrete and demanding goal that many teams pursue: reaching Continuous Delivery.
The Continuous Delivery example
A team aspiring to Continuous Delivery is aiming at a precise target. To get there, it will need to simultaneously:
- Increase deployment frequency: ship more often, in small increments, rather than concentrating risk into a few massive releases.
- Improve its Lead Time: reduce the delay between the moment an idea is ready to be coded and the moment it actually reaches production.
- Preserve (or improve) quality: without introducing regressions or bugs, because deploying faster must never mean deploying worse.
This path, rightly, is never without obstacles. And that’s good news: those obstacles are so many indicators of what needs to improve.
The problems that show up along the way
As it makes progress toward this goal, the team will inevitably run into very real difficulties. Among the most common:
- Insufficient code or test quality, which makes every deployment nerve-wracking.
- A CI/CD pipeline that’s too slow or too complex, which lengthens the feedback loop.
- Time-consuming technical reviews, or validation steps that multiply the back-and-forth.
- A lack of monitoring to track the state of production in real time.
- Dependencies between teams that slow the pace and create bottlenecks.
The list could go on. Each of these points is a concrete drag on the target, but also, and this is the whole point, a precise indication of where to direct the effort.
Two attitudes in the face of a problem
At this stage, the team faces a choice that shapes its trajectory.
The first attitude is to accept the situation as inevitable. You keep enduring the blockers, you introduce workarounds, those famous workarounds that bring relief in the moment but, once they pile up, only weigh the system down and slow progress a little more. This is the path of resignation: comfortable in the short term, costly in the long run.
The second attitude is to challenge the status quo. Instead of working around, you identify the real problems and solve them, one by one. It’s more demanding in the moment, but it’s the only road that leads to lasting improvement. Every problem eliminated is one less drag, for good.
The difference between these two stances isn’t a matter of talent or resources: it’s a matter of mindset. And that’s precisely where Lean brings a method.
Adopting a Lean mindset
Choosing to challenge the status quo doesn’t mean exhausting yourself solving problems at random. It means adopting a simple but rigorous discipline that transforms the way the team moves forward:
- Ask the right questions and analyze root causes. A visible problem is almost never the true cause. Tracing it back to the root (for instance by practicing the “5 whys”) keeps you from treating symptoms on a loop and watching the same problem resurface in another form.
- Collaborate and turn every obstacle into learning. Problem-solving isn’t an individual affair. It’s by mobilizing collective intelligence that an obstacle becomes an opportunity for shared improvement, one the whole team comes out of stronger.
- Experiment and adjust as needed. Every solution is a hypothesis. You test it, observe the results, correct if necessary, then start again. Rinse and repeat. It’s this iterative cycle that embeds continuous improvement into everyday work.
Adopt this mindset, and you’ll see your team’s progress accelerate dramatically. Not through some grand gesture, but through the cumulative effect of hundreds of small problems solved, methodically, one after another.
Conclusion
Successful teams aren’t the ones that run into fewer problems: they’re the ones that have learned to see them, name them, and solve them. Where resignation turns every obstacle into a glass ceiling, the Lean mindset turns it into a stepping stone.
The Continuous Delivery goal was only a pretext here: the reasoning holds for any ambitious target. What matters is the stance. Refusing to accept fate, challenging the status quo, tracing problems back to their root causes, and experimenting as a team: that’s what separates a team that endures from a team that progresses.
So, in your team, how do you face your problems?