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
Most companies still get Product Ownership wrong
Many organisations misunderstand Product Ownership, treating it as simple backlog management instead of a strategic, accountable role …
The market isn’t slowing down for anyone
Explores why organisational responsiveness and real-time decision-making are crucial for staying competitive, highlighting the risks of …
Hiring a Product Owner? Avoid copying job specs from the internet
Learn what makes an effective Product Owner, why generic job specs fall short, and which key responsibilities and skills are essential for …
Building the wrong thing is worse than fixing a bug
Most features don’t deliver value. Short feedback loops and real user input help teams avoid wasted effort by ensuring they build what users …
A great Product Owner drives product strategy, not just manages the backlog
Explains how effective Product Owners shape product strategy using accountability, awareness, acceptance, access, and adaptability, not just …
Navigating the Legacy System Labyrinth: Strategies for Modernisation Success
Explore practical strategies for overcoming legacy system challenges, addressing technical debt, compliance, integration, and guiding …
Executives want predictability
Lack of a clear, enforced Definition of Done leads to hidden risks, unreliable forecasts, and eroded trust in delivery, undermining …
Your Evolving Definition of Done
Explains how the Definition of Done evolves in Scrum, aligning team practices with organisational standards to ensure consistent quality, …
Why Scrum Masters Need Technical Expertise to Guide Teams
Scrum Masters need technical expertise to effectively support teams, understand best practices, and bridge gaps between process and …
Why Most Companies Fail at Adopting Agility Beyond IT
Most companies struggle with agility due to rigid structures, outdated processes, and cultural barriers, not technical issues. True agility …
The True Role of a Scrum Master Beyond Facilitation
Explains how a Scrum Master drives team improvement, removes obstacles, and leads organisational change, going far beyond basic facilitation …
Great Scrum Masters Need Technical, Business, and Organisational Mastery
Scrum Masters are most effective when they combine leadership skills with technical, business, and organisational mastery to support teams, …
Great Scrum Masters and Product Owners don’t micromanage
Effective Scrum Masters and Product Owners empower teams with clear goals and autonomy, balancing structure and flexibility to promote …
Overcoming Project Blockers and Challenging Organisational Inertia
Explores how lack of authority hinders teams from removing project blockers and overcoming organisational inertia, stressing the need for …
“Teams are self-managing
Explains how self-managing teams in Scrum need structure and leadership, clarifying the Scrum Master's role in maintaining clarity, …
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 …