Send us a text

How to Build a Problem Prevention Culture (AWS Well-Architected Explained)
Stop firefighting — start preventing problems.
In this episode of Serverless Craic, Dave Anderson, Mark McCann, and Michael O’Reilly explore how engineering teams can create a problem prevention culture using the AWS Well-Architected Framework.

They unpack lessons from Chapter 17 of The Value Flywheel Effect, showing how high-performing cloud teams use SCORP reviews (Security, Cost, Operational Resilience, Performance) to operationalise engineering excellence.
Learn how to:
✅ Shift from reactive to proactive problem solving
✅ Build dashboards that actually drive team learning
✅ Scale architecture reviews across hundreds of teams
✅ Foster psychological safety and positive peer pressure
✅ Future-proof your organisation for the AI-driven cloud era

⏱️ Chapters

00:00 – Intro and setup
00:40 – What is a problem prevention culture?
02:20 – Recognising unseen engineering work
04:30 – Balancing delivery and engineering excellence
05:40 – Defining “good architecture”
07:00 – The AWS Well-Architected Framework
08:40 – From theory to practice: SCORP sessions
10:30 – Scaling Well-Architected reviews
13:50 – Using dashboards for insight and improvement
15:00 – Building trust and psychological safety
17:00 – Peer learning and positive pressure
19:00 – Continuous improvement in real teams
21:00 – Measuring long-term maturity
22:30 – Looking forward to AI-driven cloud operations
25:00 – Outro and what’s next

🔗 Resources

📘 The Value Flywheel Effect → https://theserverlessedge.com/the-value-flywheel-effect

🧭 AWS Well-Architected Framework → https://aws.amazon.com/architecture/well-architected

🧩 SCORP Process & Templates → https://theserverlessedge.com/scorp-process-cycle

🎙️ Serverless Craic Podcast → https://theserverlessedge.com/podcast

💡 Follow The Serverless Edge on LinkedIn and YouTube

Serverless Craic from The Serverless Edge
Check out our book The Value Flywheel Effect
Follow us on X @ServerlessEdge
Follow us on LinkedIn
Subscribe on YouTube

Send us a text

In this episode of Serverless Craic, Dave Anderson, Mark McCann, and Michael O’Reilly share key takeaways from two major events — AWS Community Summit Manchester 2025 and AWS Cloud Day Dublin 2025.

From psychological safety in engineering teams to serverless adoption patterns, event-driven architecture, and the rise of AI agents with Amazon Bedrock AgentCore, the discussion highlights what’s shaping cloud-native development today.

If you’re a software engineer, cloud architect, or tech leader interested in modernisation, AI in the enterprise, serverless-first strategies, and community-led learning, this episode is for you.

⏱ Chapters
00:00 – Intro & catching up
00:55 – AWS Community Summit Manchester highlights
02:10 – Psychological safety in engineering teams
05:30 – AI hype, misuses & team impact
07:10 – Women in Tech track & allyship
08:30 – Event-driven architecture & domain-driven design
10:45 – Modernisation talks & API boundaries
12:00 – The reality of AI adoption in enterprises
14:55 – Serverless adoption patterns & challenges
15:53 – AWS Cloud Day Dublin highlights
17:45 – AI agents and Amazon Bedrock AgentCore
19:14 – Challenges of agentic user experiences
20:15 – Securing and testing AI systems (OWASP LLM Top 10)
21:00 – Well-Architected Framework (SCORP) talk
21:39 – Power of community learning
22:22 – Wrap up & next episode preview

🔗 Resources & Mentions

The Serverless Edge Website: https://theserverlessedge.com

Follow us on LinkedIn: https://www.linkedin.com/company/the-serverless-edge/

The Serverless Edge GitHub – SCORP: https://github.com/ServerlessEdge/SCORP

Amazon Bedrock & AgentCore: https://aws.amazon.com/bedrock/

Event Catalogue: https://eventcatalog.dev/

Serverless Craic from The Serverless Edge
Check out our book The Value Flywheel Effect
Follow us on X @ServerlessEdge
Follow us on LinkedIn
Subscribe on YouTube

Send us a text

In this episode Dave Anderson, Mark McCann, and Michael O’Reilly revisit their time at Liberty Mutual, exploring how one of the world’s largest insurers transformed from legacy systems and SOA to cloud-native architectures and serverless-first strategies.

Discover how Wardley Mapping, empowered engineering teams, and a strong cultural foundation enabled Liberty Mutual to modernise at scale and deliver business value faster.

We cover:

Moving from mainframes and monoliths to microservices and serverless

Building agile, product-led teams that own security, testing, and operations

Using Wardley Mapping to make strategic technology bets

Lessons on cloud adoption, change management, and leadership in a Fortune 100 enterprise

👉 If you’re a CTO, software architect, or engineering leader, this case study is packed with insights on modernisation and enterprise cloud transformation.

⏱️ Chapter Markers

0:00 – Introduction
0:34 – Liberty Mutual in Belfast: tackling hard problems
2:21 – Strategic mindset of a mutual insurance company
3:49 – Early SOA systems and first encounters with cloud
4:49 – Microservices before it was mainstream
6:14 – Enter serverless: below the line vs above the line
8:38 – Technology manifesto and cultural change
10:25 – Learning from world-class infrastructure engineers
13:53 – Wardley Mapping and spotting key enablers
16:08 – CDK, BDD, and shifting left
18:20 – Security, threat modelling, and shifting responsibilities
19:58 – Product thinking and “next best action”
21:31 – Working with auditors and external stakeholders
22:18 – Upskilling, conferences, and internal evangelism
24:08 – Business impact and scaling during COVID
25:39 – Change management: it takes a village
26:45 – External evangelism and organisational support
27:22 – Next episode teaser: Problem Prevention Culture

📚 Resources & Links

🌐 The Serverless Edge https://theserverlessedge.com
– Thought leadership on modern cloud

🎧 Podcast on Spotify

🎥 More episodes on YouTube

📖 The Value Flywheel Effect – by David Anderson, Mark McCann & Michael O’Reilly https://thevalueflywheeleffect.com

Serverless Craic from The Serverless Edge
Check out our book The Value Flywheel Effect
Follow us on X @ServerlessEdge
Follow us on LinkedIn
Subscribe on YouTube

Send us a text

In this episode of Serverless Craic, Dave Anderson, Mark McCann, and Michael O’Reilly explore Chapter 15 of The Value Flywheel Effect — Map Your Solution. They discuss how Wardley Mapping and tech stack mapping create situational awareness, reduce friction between teams, and guide better architectural decisions.

If you’re a software engineer, architect, or tech leader aiming to evolve your systems with serverless and cloud-native thinking, this conversation shows practical techniques to uncover bottlenecks, reduce technical debt, and align teams on strategic improvements.

⏱️ Chapters

00:00 – Intro: jumping from summer to winter
01:00 – Mapping your solution: why it matters
02:20 – Tech stack mapping in practice
03:50 – Situational awareness and collaboration
05:50 – Funding priorities and bottlenecks
07:20 – Cloud services, serverless options, and evolution paths
09:30 – Custom build vs buy vs adopt cloud-native
11:00 – Organisational insights from mapping
12:00 – Duplication and domain-driven design issues
13:00 – Team Topologies and independent service heuristic
14:20 – Total cost of ownership and well-architected lens
15:50 – Target architecture and business impact
16:50 – Using mapping for strategy and incentives
17:40 – Context switching and leadership effectiveness
18:10 – Takeaways: evolutionary architecture

🔗 Resources

📖 The Value Flywheel Effect Book – https://thevalueflywheeleffect.com

🎥 Wardley Mapping 101 – https://www.youtube.com/watch?v=uP9Rl26Xeag

🎧 Podcast: Wardley Mapping is a Game-Changer – https://open.spotify.com/episode/5cUQgQFBeIkOBWUe35rDRU

Serverless Craic from The Serverless Edge
Check out our book The Value Flywheel Effect
Follow us on X @ServerlessEdge
Follow us on LinkedIn
Subscribe on YouTube

Send us a text

In this episode, Dave Anderson, Mark McCann, and Michael O’Reilly dive deep into The Value Flywheel Effect (Chapter 14) — discussing frictionless developer experience, sense checking, feedback culture, AI in software engineering, DevOps, platform engineering, and marginal gain.

We explore how AI and LLMs are shaping engineering practices, the importance of psychological safety, continuous improvement, and why code is always a liability. If you’re interested in serverless, DevOps, or building resilient modern software teams, this conversation is packed with insights.

Chapters
00:00 – Introduction & Belfast heatwave 🌞
00:18 – Revisiting *The Value Flywheel Effect* (Chapter 14)
01:11 – Sense checking & psychological safety in teams
02:37 – Leadership, listening, and feedback loops
04:12 – RFCs, well-architected reviews & threat modelling
05:14 – Trusting AI feedback vs human feedback
07:59 – Documenting engineering standards for AI
09:33 – Human in the loop & cadence of reviews
11:42 – Traceability, accountability & marginal gains
13:56 – Scaling teams & expanding the “full stack”
14:29 – Infrastructure as code, DevOps origins & AI parallels
17:13 – Deployment pipelines & frictionless production
18:01 – Platform engineering & hardened building blocks
19:40 – Code as liability & avoiding bloat
20:20 – Well-architected standards & AI context
21:32 – Shifting security left & automated governance
22:33 – Isolation, zero trust & resilience
23:18 – Platforms as standards & consolidation
25:23 – Less code, better docs, and evolving patterns
27:06 – Avoiding command & control in engineering culture
28:22 – Empowerment, enabling environments & AI’s role
28:50 – Developer experience & future of AI in software

Serverless Craic from The Serverless Edge
Check out our book The Value Flywheel Effect
Follow us on X @ServerlessEdge
Follow us on LinkedIn
Subscribe on YouTube

Send us a text

In this episode Dave Anderson, Mark McCann, and Michael O’Reilly continue their deep dive tackling Chapter 14: The Frictionless Developer Experience.

The crew explore whether the principles of engineering excellence, developer enablement, and team topologies still stand strong in a world increasingly powered by AI and agentic systems. From **managing cognitive load** to **code as a liability**, they unpack how AI changes (and doesn’t change) the fundamentals of building high-quality software.

📌 Topics include:

Does AI really make development frictionless?
Maintaining engineering excellence in an AI-driven world
Enabling constraints and team autonomy
Revisiting the four team types in *Team Topologies*
The enduring importance of DORA metrics and stability
Why code is a liability—and how AI impacts this
The rise of specifications, contracts, and stronger test practices

⏱ Chapters
00:00 – Intro & recent travels
01:20 – Go To Service Bangalore & serverless momentum
02:40 – Frictionless developer experience in an AI world
04:50 – Cognitive load & enabling constraints
06:20 – Engineering excellence: still relevant?
08:10 – Three characteristics of great software creation
10:25 – Principles, context, and best practices in the AI era
12:40 – Goal-driven frameworks & outcome-based leadership
14:00 – Challenging teams with the right questions
15:35 – AI as an enabler for strong engineers
17:20 – Democratising knowledge & rapid learning
18:40 – Team Topologies in the AI landscape
20:45 – Socio-technical changes & enabling teams
22:15 – Will teams be smaller or just better?
23:30 – Autonomy, mastery, and purpose
25:05 – Engineers’ mastery in the age of AI
26:00 – DORA metrics: throughput & stability
28:00 – Code as a liability & maintainability concerns
29:20 – Specifications, contracts, and test-driven approaches
31:00 – Shared outcomes & embracing AI in delivery

🔗 Resources & Links

📚 Team Topologies: https://teamtopologies.com by Matthew Skelton & Manuel Pais
📖 Accelerate by Nicole Forsgren, Jez Humble & Gene Kim
🌐 The Serverless Edge https://theserverlessedge.com)– Blog & resources

Serverless Craic from The Serverless Edge
Check out our book The Value Flywheel Effect
Follow us on X @ServerlessEdge
Follow us on LinkedIn
Subscribe on YouTube

Send us a text

Serverless myths debunked for modern cloud teams: In this episode, we dive into the second part of Chapter 13 The Serverless First Edge from The Value Flywheel Effect book. We explore common serverless myths, how relevant they still are in 2025, and what’s changed since the early days of serverless adoption.

From cold starts and testing challenges to cloud lock-in and the rise of AI, we reflect on the evolution of the landscape — and the mindset shifts still needed across engineering and leadership teams.

💥 Packed with practical insights and real-world experiences, this is a must-watch for anyone navigating modern cloud architecture, serverless patterns, or leading engineering teams in the age of AI.

⏱ Chapters:

00:00 - Intro & weather chat
00:34 - Chapter 13 overview: "The Serverless First Age"
01:17 - Cold start problems: Still a myth?
05:11 - Serverless is hard to test? Solved with cloud-native testing
09:34 - Observability: You can't see what's happening?
12:48 - Serverless isn’t the next big thing? The AI distraction
16:23 - Vendor lock-in fears & multi-cloud myths
20:00 - “We’re different” & custom standards fallacy
23:02 - Serverless is more expensive?
25:26 - Engineers won’t do what I tell them
26:23 - Engineers are disconnected from the business
27:24 - “This worked last time, let’s use it again”
28:02 - “We only work on the cool stuff”
28:27 - Organisational myths: “We’re under capacity”
29:54 - Security is blocking serverless?
30:41 - Finance myths: OPEX model resistance
30:54 - Sunk cost fallacy in cloud transformation
31:37 - Outsourcing strategy to consultancies
32:47 - Wrap-up & what’s still relevant

🔗 Links & Mentions:
The Value Flywheel Effect book
ServerlessDays Belfast
Talks by Jeremy Daly, Yan Cui , Adrian Cockcroft
BizTech Evolution by Ivan Krnić

Serverless Craic from The Serverless Edge
Check out our book The Value Flywheel Effect
Follow us on X @ServerlessEdge
Follow us on LinkedIn
Subscribe on YouTube

Send us a text

Serverless First: Focus, Not Functionality

In this episode, Dave Anderson, Mark McCann and Michael O’Reilly dive into Chapter 13 of the Value Flywheel Effect—focusing on the concept of “Serverless First” and what it really means for engineering teams and product leaders today.

🔍 Topics include:
Why code is a liability and how to identify what to build—and more importantly, what not to.
Embracing a frictionless developer experience to enable speed and innovation.
The shift from legacy cloud to modern cloud and the pitfalls of lift-and-shift thinking.
Understanding core vs. supporting domains through DDD and how that informs what to offload.
The enduring value of good architecture*and how modern cloud constraints can be enabling.
A powerful reminder that the point of serverless isn’t tech—it’s focus.

🚀 Whether you're navigating cloud migration, modernising your stack, or wondering how to leverage AI without drowning in infrastructure, this conversation will help you elevate your thinking.

Serverless Craic from The Serverless Edge
Check out our book The Value Flywheel Effect
Follow us on X @ServerlessEdge
Follow us on LinkedIn
Subscribe on YouTube