Pragmatic Thinking is the application of practical, experience-based problem-solving in complex environments, enabling teams to navigate challenges effectively. This approach prioritises actionable insights over theoretical constructs, fostering a mindset that values real-world applicability. By focusing on what works in practice, teams can adapt their strategies to deliver value predictably and sustainably.
This concept is crucial in environments characterised by uncertainty and rapid change, as it encourages a culture of experimentation and learning. Teams employing Pragmatic Thinking are better equipped to identify and implement solutions that resonate with their specific context, rather than relying solely on prescribed methodologies. This adaptability not only enhances responsiveness to customer needs but also promotes resilience in the face of evolving market dynamics.
Pragmatic Thinking supports long-term systemic improvements by embedding a continuous learning ethos within the organisation. It empowers teams to reflect on their experiences, iterate on their processes, and refine their approaches, ultimately leading to enhanced performance and value delivery. By integrating this mindset into daily practices, organisations can cultivate a robust framework for sustained innovation and effective problem-solving, ensuring they remain competitive and relevant in their respective fields.
The strongest work on Pragmatic Thinking — ranked by substance, not recency. How this is ranked
Stop Building Silos. Start Building Systems
Explains how fragmented automation and tool silos harm software delivery, and advocates for unified engineering systems and platform …
Don’t Manage Dependencies, Remove Them
Explains why dependencies are a sign of poor system design and outlines steps to eliminate them by aligning teams, clarifying ownership, and …
Flow of Value vs Flow of Work – Misnomer or Useful Shorthand?
Compares “flow of value” and “flow of work” in Kanban, explaining why only validated outcomes count as value and stressing the need for …
Is Agile Really Just a Mindset?
Explores Agile as a disciplined system of delivery, emphasizing engineering excellence, CI/CD, observability, and system design over mindset …
Rethinking Capacity Planning
Explores how effective capacity planning shifts focus from individual hours to system-level flow, using Lean and Agile principles to improve …
Why Topic Branches Drive High-Quality Delivery
Explains how short-lived topic branches in source control improve software quality, enable modularity, speed up integration, and support …
Why a Shared Definition of Done Is the Secret to Consistent, Predictable Quality in Agile Teams
Struggling with inconsistent delivery? Discover why a shared definition of done is key to predictable, high-quality results your teams, and …
Why Outsourcing DevOps Fails, and How Real Engineering Excellence Starts With Your Team
Avoid DevOps vendor lock-in, discover how true engineering excellence starts with partnership, not outsourcing. Ready to transform your …
The Estimation Trap: How Tracking Accuracy Undermines Trust, Flow, and Value in Software Delivery
Tracking estimation accuracy in software delivery leads to mistrust, fear, and distorted behaviours. Focus on customer value, flow, and …
Stop Building Silos. Start Building Systems
Explains how fragmented automation and tool silos harm software delivery, and advocates for unified engineering systems and platform …
Don’t Manage Dependencies, Remove Them
Explains why dependencies are a sign of poor system design and outlines steps to eliminate them by aligning teams, clarifying ownership, and …
Flow of Value vs Flow of Work – Misnomer or Useful Shorthand?
Compares “flow of value” and “flow of work” in Kanban, explaining why only validated outcomes count as value and stressing the need for …
The Estimation Trap: How Tracking Accuracy Undermines Trust, Flow, and Value in Software Delivery
Tracking estimation accuracy in software delivery leads to mistrust, fear, and distorted behaviours. Focus on customer value, flow, and …
Estimating Better in an Overloaded System Is a Poor Man’s Strategy
High work in progress (WIP) causes delays and unpredictability; improving estimates won’t help. Limiting WIP and focusing on flow is key to …
Are We Still Pretending Coding Was the Bottleneck?
AI exposes that coding was never the main bottleneck in software delivery; real constraints are in system flow, team practices, and …
Should You Use One Project to Rule Them All in Azure DevOps?
Explores when to use a single Azure DevOps project versus multiple projects, detailing impacts on flow, visibility, governance, and team …
Getting Started with Objectives & Key Results
Learn how to successfully implement OKRs by aligning clear strategy, fostering transparency, empowering teams, focusing on outcomes, and …
Is Agile Really Just a Mindset?
Explores Agile as a disciplined system of delivery, emphasizing engineering excellence, CI/CD, observability, and system design over mindset …
Why a Shared Definition of Done Is the Secret to Consistent, Predictable Quality in Agile Teams
Struggling with inconsistent delivery? Discover why a shared definition of done is key to predictable, high-quality results your teams, and …
Why Outsourcing DevOps Fails, and How Real Engineering Excellence Starts With Your Team
Avoid DevOps vendor lock-in, discover how true engineering excellence starts with partnership, not outsourcing. Ready to transform your …
How to Tackle Technical Debt Without Halting Progress: Smarter Ways to Keep Your Team Moving Forward
Struggling with technical debt? Discover practical ways to tackle legacy systems, boost team morale, and deliver value, without grinding to …
Why Big Bang Rewrites Fail: How Sustainable Change and Engineering Excellence Transform Legacy Systems
Ditch the Big Bang rewrite. Discover why sustainable, in-place change drives true engineering excellence and lasting transformation in your …
Why Azure DevOps Wins for Governance, Security, and Scale, Right Out of the Box
Unlock seamless governance, security, and scale with Azure DevOps, integrated tooling that lets you deliver value, not just manage …
Stop Guessing: How to Make Work Visible and Drive Real Improvement with Azure DevOps Flow Metrics
Stop guessing, start making data-driven decisions in Azure DevOps. Discover tools, tips, and insights to make your work visible and your …
Still Deploying Manually? Why Automation Is the Bare Minimum for Modern Engineering (and Your Business Survival)
Still deploying manually? Discover why automation isn’t optional, protect your business, avoid disaster, and deliver value with modern …
From Legacy Pain to Modern DevOps: My Proven Roadmap for Real Engineering Transformation
Transform legacy engineering with a proven, step-by-step approach, learn how to automate, adapt, and build a resilient, modern DevOps …
Unlocking Engineering Excellence: How Azure DevOps Transforms Traceability, Transparency, and the Developer Experience
Unlock engineering excellence with Azure DevOps, boost traceability, transparency, and developer experience for agile, high-performing …
Building a Resilient Token Server: Engineering for Flow, Fault Tolerance, and Speed
Explains how to engineer a robust, fault-tolerant token counting server using FastAPI and PowerShell, covering error handling, retries, …
Convert Legacy Projects and ASP.NET MVC Apps to SDK-Style with Confidence
Learn how to upgrade legacy .NET and ASP.NET MVC projects to SDK-style for easier builds, modern tooling, and future readiness, including …
How I Used Generative AI to Transform Site Tagging and Categories
Explains how generative AI and PowerShell scripts automate and improve blog post tagging and categorisation in Hugo, with human oversight …
Kendall Guide - A System of Work for AI Adoption
Evidence-Based Portfolio Management
OKR Guide - A Social Discipline for Shared Focus, Measurable Contribution, and Strategic Learning
496 resources, newest first
Engineering can fix technical debt, but leadership has to invest in it
Technical debt requires leadership investment to resolve; without support for automation and quality improvements, continuous delivery is …
At the end of the day, Kanban is about improving flow
Kanban focuses on improving workflow by removing bottlenecks and constraints, reducing work in progress, and increasing process efficiency, …
Why Measuring Individual Cycle Time is Killing Your Flow (And What to Do Instead)
Measuring individual cycle time in Kanban misleads teams, hides real bottlenecks, and harms flow. Focus on system-wide metrics like PCE, …
If software is not delivered, it is not valuable
Undelivered software provides no value. Frequent, iterative releases reduce risk, cost, and failure, enabling faster learning and real user …
Staging Environments Do Not Prevent Production Failures
Staging environments can’t fully replicate production, often leading to false confidence. Real risk reduction comes from safe, incremental …
A two-day Scrum Master certification doesn’t make you a Scrum Master
Practical experience is essential for effective Scrum Masters; certification alone is insufficient. True expertise comes from guiding teams, …
Embrace Simplicity: How to Transform Complexity into Continuous Delivery Success
Explains how simplifying complex software and committing to change enables continuous delivery, highlighting the need for cultural shift, …
Do More Staging Environments Really Reduce Deployment Risk
Adding more staging environments does not reduce deployment risk; true safety comes from automated testing, continuous integration, and …
Mastering the Art of Scaling Agile: Strategies to Maintain Agility Across Multiple Teams
Learn effective strategies for scaling agile across multiple teams, managing dependencies, avoiding common pitfalls, and maintaining agility …
Scaling Smart: How to Tackle Technical Debt for Sustainable Growth
Learn how unmanaged technical debt can hinder growth, and discover strategies like sustainable architecture, DevOps, and automation to scale …
Scrum is built on empiricism, transparency, inspection, and adaptation
Explains why consistent delivery of usable increments is essential in Scrum, highlighting the Scrum Master's accountability for ensuring …
Why Organisations Believe Their Software Is Too Complex for CD
Many organisations cite software complexity as a barrier to continuous delivery, but real obstacles are technical debt and lack of …
Stop Hiding Behind Complexity and Start Delivering Continuously
Continuous delivery is achievable for any software, regardless of complexity. Success depends on investment in automation, quality, and …
Why the Concept of a "Junior Scrum Master" is a Misguided Myth
Explains why the Scrum Master role requires experience and competence, debunking the myth of a "junior" Scrum Master and highlighting the …
What Makes an Effective Scrum Master Beyond Meeting Facilitation
Explores key qualities of an effective Scrum Master, focusing on team empowerment, backlog management, collaboration, and removing …
Deploying Windows OS Directly to Production: Then vs Now
Explains how Windows OS updates shifted from infrequent, risky releases to safe, staged rollouts using ring-based deployment and real-time …
Rethinking Dev-Test-Staging-Production Pipelines for Safety
Explores why traditional Dev-Test-Staging-Production pipelines fall short and highlights audience-based deployment for safer, faster …
Why Using a Blocked Column in Azure DevOps Is a Mistake
Explains why a “Blocked” column in Azure DevOps hinders workflow, and suggests using tags and tracking to manage blocked work more …
How Top Scrum Masters Are Selected by Their Teams
Explains how Scrum Masters are naturally chosen by teams based on trust, experience, and leadership, highlighting the importance of peer …
Scaling Smart: How to Build Sustainable Growth Without the Chaos
Learn how to achieve sustainable, resilient organisational growth by focusing on simplification, value delivery, and effective agile …
Key Skills Scrum Masters Need: Technical, Business, Organisational
Scrum Masters need technical, business, and organisational skills to guide teams, remove obstacles, drive value, and lead effective agile …
Mastering the Art of Scaling Product Development: Why Adding More Developers Isn't the Answer
Explores why scaling product development requires system improvements, not just more developers. Covers alignment, technical debt, and …
The fastest way to cripple a Scrum Team? Hire the wrong Scrum Master
Hiring an unqualified Scrum Master limits team growth, reduces agility, and hinders value delivery. Effective Scrum Masters drive change, …
Would you hire a Junior CISO? A Junior Financial Director
Scrum Masters require proven expertise, not entry-level skills. Hiring juniors in this role risks team performance and agile success; …
There Is No Such Thing as a "Junior" Scrum Master
Argues that the Scrum Master role requires proven mastery and real-world experience, not entry-level skills or certifications, and should be …
Hiring a Scrum Master is hard
Finding a skilled Scrum Master is challenging; true effectiveness requires deep Scrum knowledge, coaching ability, and alignment with your …
Not all delays are the same
Explains the difference between waiting and blocked tasks, why clear distinction matters in workflows, and how to track and address sources …
Why Engineering Teams Use Staging Environments for Risk Reduction
Explores how staging environments aim to reduce risk in software development, their hidden costs, and modern alternatives like feature flags …
Challenging Misconceptions About Behaviour in Agile Teams
Explores common misconceptions about Agile teams, clarifying that true agility demands discipline, planning, and professionalism, not chaos …
There a common belief that rollback is the ultimate safety net
Rollback is often riskier than rolling forward, especially for stateful apps. Safer deployment relies on progressive delivery and …