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
Engineering as a Leadership System: Moving Beyond Frameworks
Delivery outcomes are shaped less by frameworks and practices than by the operating model leaders have designed. How an organisation's …
Why Most Companies Operating Models Fail in Dynamic Markets
A concise comparison of Predictive and Adaptive Operating Models, explaining why traditional structures fail in dynamic markets and how …
Engineering as a Leadership System
Session recording from The Future of Work in Scotland. Why the frameworks your teams adopt cannot overcome the operating model your …
AI Agents Lie About Being Done
My agent reported every task complete when half the tests were missing. Call that a lie if you like. The engineering problem is that the …
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 …
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 …
How to Build for Business Resilience and Continuity
Learn key strategies for building business resilience and continuity, including observability, system decoupling, routine deployments, team …
Rethinking Capacity Planning
Explores how effective capacity planning shifts focus from individual hours to system-level flow, using Lean and Agile principles to improve …
How Lack of Agency is Killing Your DevOps Initiatives
Explores how lacking developer control over production, telemetry, and deployments undermines DevOps, leading to fragile automation and …
Engineering as a Leadership System: Moving Beyond Frameworks
Delivery outcomes are shaped less by frameworks and practices than by the operating model leaders have designed. How an organisation's …
Why Most Companies Operating Models Fail in Dynamic Markets
A concise comparison of Predictive and Adaptive Operating Models, explaining why traditional structures fail in dynamic markets and how …
AI Agents Lie About Being Done
My agent reported every task complete when half the tests were missing. Call that a lie if you like. The engineering problem is that the …
Who Owns the Code?
AI-generated code and copyright. Why "who typed it" is the wrong test, where the real legal uncertainty sits for agentic development, and …
How My Father's Business Reverted to the Mean
My father died eight years ago today. In 1980 a leadership team's golf retreat left him holding a ten-year lease on a Glasgow shopfront, so …
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 …
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 …
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 …
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 …
Engineering as a Leadership System
Session recording from The Future of Work in Scotland. Why the frameworks your teams adopt cannot overcome the operating model your …
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 …
Engineering Excellence Isn’t Perfection: How Continuous Improvement and Fast Feedback Drive Real Agile and DevOps Success
Engineering excellence isn’t perfection, it’s continuous improvement, clean code, and fast feedback. Unlock true agility with modern Agile …
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 …
Stop Testing Quality In: How Shifting Left Builds Better Software, Faster
Stop testing quality in, start building it in. Learn how shifting left, automation, and fast feedback loops drive engineering excellence in …
Why Your Definition of Done Is the Secret Weapon Your Team Needs to Win
Unlock your team's true potential, discover why a powerful definition of done drives real business impact, customer value, and lasting …
Legacy Systems Aren’t the Enemy, Friction Is: How to Unblock Innovation and Accelerate Agile Delivery
Is legacy tech slowing your team? Discover how removing friction unlocks agility, innovation, and faster delivery in your organisation.
Stop Chasing Tech Hype: How Evidence-Based Decisions Empower Real Leadership
Stop chasing tech trends. Learn how evidence, visibility, and clarity empower tech leaders to make confident, strategic decisions, beyond …
How to Evolve Your Definition of Done: Start Small, Grow Smarter, and Build Lasting Momentum
Unlock a smarter Definition of Done, start small, evolve standards, and build team momentum without overwhelm. Discover how progress drives …
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, …
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 …
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 …
Evidence-Based Portfolio Management
Explains how evidence-based portfolio management helps organisations extend agile practices beyond teams, enabling greater responsiveness …
OKR Guide - A Social Discipline for Shared Focus, Measurable Contribution, and Strategic Learning
Comprehensive guide to using OKRs for shared focus, measurable outcomes, and strategic learning, including roles, events, best practices, …
AI Adoption Guide - Engineer Your System of Work That AI Reveals
NKD Agility's problem-first guide to AI adoption, built on the Kendall Framework and written from engineering - start with a validated …
487 resources, newest first
Scrum Masters: Why Influence Alone May Not Be Enough
Explores why Scrum Masters need authority, not just influence, to enforce Agile practices, remove blockers, and ensure teams follow Scrum …
No one questions a Product Owner authority
Explores why Product Owners’ authority is accepted while Scrum Masters’ is questioned, highlighting the need for clear authority to ensure …
Why Teams Claim Self-Management to Avoid Alignment Discussions
Explores how teams misuse self-management to dodge alignment, clarifying that true autonomy requires accountability, shared goals, and …
Everyone loves the idea of self-managing teams
Explains how self-managing teams thrive with autonomy balanced by structure, highlighting the need for clear goals, accountability, and …
Scrum Masters and Product Owners are held accountable for results
Explores the gap between accountability and authority for Scrum Masters and Product Owners, highlighting the need to empower roles …
Balance of Leadership and Control in Scrum
Explores how Scrum Masters and Product Owners balance leadership, authority, and team autonomy to ensure accountability, effective …
Lack of Authority Blocks Progress on Critical Projects
Scrum Masters need authority to remove obstacles and drive project success. Without empowerment, they can't fulfil their role or be held …
Why Measuring Individual Cycle Time Fails to Help Teams
Measuring individual cycle time overlooks team performance and system bottlenecks. Focus on lead time, throughput, and process efficiency to …
Technical debt isn’t just messy code
Technical debt includes slow feedback, fragile systems, and manual processes that hinder progress. Addressing it early with automation and …
Why Tracking Individual Cycle Time Distorts Team Behaviour
Tracking individual cycle time can harm team performance by encouraging task cherry-picking, reduced collaboration, and lower quality, …
Velocity isn’t how many story points a team burns down
Velocity measures how quickly teams turn ideas into value, using build, test, deploy, and feedback times, not just story points, to track …
Scrum Masters are not glorified meeting schedulers
Scrum Masters must have technical and business expertise to guide teams, improve code quality, and drive real agility, not just schedule …
Agile Is Not Easier Than Traditional Methods: Common Misconceptions
Explains why Agile methods are often more challenging than traditional ones, highlighting common misconceptions, required discipline, and …
Scrum Masters: Enabling Teams, Fostering Agility, Removing Blockers
Explains the Scrum Master's role in ensuring team delivery by fostering agility, removing blockers, and being accountable for improving team …
Understanding Blocked Columns and Stalled Work in Project Boards
Explains why using blocked columns for stalled tasks on project boards harms workflow, and suggests better ways to highlight and address …
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, …
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 …
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; …
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 …
Testing in Production Maximises Quality and Value
Explains how audience-based deployment and testing in production enable faster feedback, safer rollouts, and higher software quality by …
Every delay increases the risk of failure
Delaying software releases increases failure risk. Frequent, small releases improve success rates, adaptability, and recovery, as shown by …
Navigating the Balance: How Lean Governance Can Boost Agility and Innovation in Your Organisation
Explores how lean governance reduces unnecessary processes, enabling organisations to stay agile, meet compliance, and foster innovation …
Branch promotion is a relic of slow, manual software delivery
Explains why modern software teams avoid branch promotion, using continuous integration, feature flags, and production-like testing to …
Frequent releases are not just a technical strategy
Frequent software releases reduce risk, enable faster feedback, and help teams adapt to user needs, preventing costly mistakes and improving …
Transforming Agility: How Azure DevOps Went from Two-Year Releases to 880,000 Deployments
Explores how Azure DevOps shifted from slow, two-year releases to rapid, continuous delivery, highlighting the benefits of fast feedback, …
Too many teams overcomplicate their branching strategies
Learn why simple branching strategies like GitHub Flow and Release Flow help teams deliver faster, reduce risk, and avoid the pitfalls of …
Every unreleased feature is a cost
Unreleased features create hidden costs and risks. Regular software delivery reduces failure rates, rework, and missed opportunities, …