From delivery friction to sustainable fast flow – restoring pace and predictability under pressure.
I help scale-ups make delivery predictable again when growth starts to outpace their systems – stabilising delivery, unblocking decision flow, and embedding sustainable capability between product and engineering.
This talk explores three practical strategies to reduce bugs and improve software delivery, without blaming people or just trying harder. It was presented at LDX3 2025 and Agile on the Beach 2025 .
Beyond Just Try Harder was delivered at LDX3 2025 and Agile on the Beach 2025. It explores how teams can tackle bugs more effectively by fixing the system, not blaming the people.
We’ve all been there: bugs escape, estimates slip, releases break – and someone says, just try harder next time. But pressure and process rarely fix the root cause. This talk outlines a more sustainable approach, built on what research and real-world teams actually show works.
“Just try harder” isn’t a strategy. Learn three proven approaches – monitoring bugs, managing legacy systems, and optimizing feedback loops – that empower teams to deliver better software.
→ Read more
We've all been there. Developers are told to "just try harder" not to create bugs, and testers are expected to "just try harder" to catch bugs before they reach production. However, this age-old strategy doesn't address the root causes of software bugs and can even be counterproductive.
→ Read moreView the slide deck: LDX3 10-minute ligntning
talk
View the slide deck: AOTB 45-minute full
talk
You’ll discover three proven strategies:
Get Feedback in the Time It Takes to Make a Cup of Tea
Our test suite took 30+ minutes. Developers avoided it, bugs slipped through, and delivery slowed down. We cut feedback time to under five minutes by prioritising key tests, optimising pipelines, and parallelising execution, boosting flow, reducing context switching, and reclaiming dev hours.
You Can’t Inspect a Fourth Leg onto a Three-Legged Table
Even with fast feedback, our legacy system made every change feel risky. We used the strangler fig pattern to migrate safely, automate delivery, and reduce batch size. The result? A shift from chaotic fortnightly releases to confident daily deployments.
Find Bugs Before Your Customers Do
Shipping fast isn’t enough – you need to ship safely. For a critical HealthTech platform, we used feature flags, real-time monitoring, and parallel legacy operation to catch bugs before users did. This gave us trust, safety, and true continuous delivery.
Go beyond Just Try Harder
You don’t need heroic effort. You need a system that supports fast feedback, safe changes, and controlled delivery.
Explore the research, techniques, and practices behind the talk.
Reduce overhead, tighten loops, and catch issues early
DORA is a long running research program that seeks to understand the capabilities that drive software delivery and operations performance. DORA helps teams apply those capabilities, leading to better organizational performance.
→ Read more
Testing is a Good Thing, right? Especially automated testing. But "Good things come to those who wait" is not something that's going to appeal to the busy developer. You want results, and you want them now. You're in The Zone working on a problem, and the last thing you want is to break your flow wrestling with your testing framework or waiting for the tests to finish running.
→ Read more
Nicole has authored two books on DevOps that have become industry guidebooks on using technology to drive business value, resulting in success.
→ Read more
The DORA State of AI-Assisted Software Development report dives deep into how AI is impacting technology-driven teams.
→ Read moreShrink batch size, reduce complexity, lower risk
Inspired by the strangler figs in Australia, a strangler fig application gradually draws behavior out of its host legacy application
→ Read more
a bliki entry for Parallel Change
→ Read more
A portal on this practice
→ Read more
I have a new book out. It’s called “Modern Software Engineering” and I have been working on it for the past few years.
→ Read moreControl exposure, learn safely, and observe failures early
Feature Flags can be categorized into several buckets; manage each appropriately. Smart implementation can help constrain complexity.
→ Read more
Execute back-end code but don’t show results, in order to assess impact on back-end systems
→ Read more
Learn the key aspects of observability that Honeycomb thinks everyone should know.
→ Read more
Testing in production is a superpower. It’s our inability to acknowledge it that’s the trouble.
→ Read moreAll illustrations in this talk were generated using ChatGPT + DALL·E, based on a custom system prompt and detailed slide-by-slide prompts.
The illustrations use cartoon-style green bugs as metaphors for complexity, fragility, and poor system design – with a consistent visual style to reinforce the talk’s themes in a playful but professional way.
View the full prompt and slide descriptions
These articles explore the ideas and real-world experiences that shaped the talk, from reducing bugs with observability and automation to lessons learned from leading change in a growing HealthTech team.
Three system-level strategies to tackle bugs in software delivery – monitoring, streamlined approvals, and automation – without burning out teams.
→ Read more
What I learned about credibility, pace, and patience when I took on my first technical leadership role.
→ Read moreThese strategies reflect the principles I bring to software delivery consulting, helping teams modernise systems, improve flow, and build software that works in the real world.
If this talk resonated with you and you’d like support with similar challenges, I’d love to hear from you.
Book a 20-minute discovery call