> Markdown version of [/videos/855-fast-flow-not-fast-fluff-embracing-an-eclectic-devops-coaching-approach?t=2295](https://www.wearedevelopers.com/videos/855-fast-flow-not-fast-fluff-embracing-an-eclectic-devops-coaching-approach?t=2295). Every page supports `.md` or `Accept: text/markdown`. Links point to the HTML versions so they work for humans too. Agent guide: [/agents.md](https://www.wearedevelopers.com/agents.md).

---

# Fast Flow, Not Fast Fluff: Embracing an Eclectic DevOps Coaching Approach

Are your teams shipping the wrong things quickly? Learn how an eclectic DevOps coaching approach eliminates systemic friction, shifting organizations from reactive fast fluff to sustainable fast flow.

- **Speakers:** Jacob Duijzer
- **Event:** WeAreDevelopers LIVE
- **Published:** February 12, 2024
- **Duration:** 57:53
- **URL:** https://www.wearedevelopers.com/videos/855-fast-flow-not-fast-fluff-embracing-an-eclectic-devops-coaching-approach

## Summary

Organizations frequently struggle with sluggish delivery and unhappy engineering cultures because they rely on rigid workflows rather than diagnosing underlying systemic friction. By adopting an eclectic coaching approach—drawing from lean manufacturing, agile principles, and modern platform engineering—teams can escape "fast fluff" (shipping the wrong things quickly) and achieve sustainable fast flow. The core methodology centers on three distinct phases: amplification, slowification, and simplification, which collectively diagnose bottlenecks, carve out time for deep problem-solving, and reduce cognitive friction.<br><br>Effective transformation begins with amplification, signaling a shift toward generative cultures that actively reward psychological safety. Pulling the proverbial "Andon cord" when things break shouldn't trigger an urge to blame, but should instead act as a catalyst for immediate retrospectives to error-proof systems. Techniques like Gemba walks and the Spotify Squad Health Check help surface these hidden issues without intimidation. Once problems are visible, teams must embrace slowification, which involves shifting from reactive heuristic responses to deliberate System 2 planning. Applying hard limits on work-in-progress (WIP) forces necessary conversations about systemic bottlenecks rather than allowing developers to quietly start new tasks. Using frameworks like Cynefin to map out complex domains or leveraging liberating structures empowers teams to collectively navigate ambiguity rather than falling back on flawed muscle-memory.<br><br>Finally, simplifying the developer experience requires active management of engineering cognitive load. Implementing structural patterns from Team Topologies—such as utilizing self-service platform engineering and dedicated enabling teams—decouples dependencies and significantly cuts the extraneous workload that bogs down stream-aligned teams. Success in this environment is measured by hard flow analytics, favoring DORA deployment frequencies and aligned OKRs over subjective story points. Ultimately, true DevOps maturity means bridging the gap between business value and technical velocity, ensuring that output directly solves strategic problems instead of simply moving code forward.

**Keywords:** devops coaching methodologies, team topologies patterns, engineering cognitive load, cynefin framework applications, WIP limit optimization, gemba walk implementation, andon cord principles, engineering psychological safety, DORA metrics tracking, system 2 software planning, fast flow organizational design, liberating structures facilitation, generative culture development, evidence-based management tracking, OKR alignment strategies

## Chapters

1. **Understanding fast flow versus fast fluff in organizations** (00:00) — Recognizing the difference between a constant stream of updates and releasing unused features.
1. **Using the agile coaching wheel for situational leadership** (01:43) — Applying different coaching stances like serving or facilitating based on the specific team challenge.
1. **The eclectic approach of wiring the winning organization** (03:27) — Leveraging amplification, slowification, and simplification to structure problem solving without dogmatism.
1. **Analyzing the three layers of sociotechnical organizational design** (04:55) — Separating domain experts, platform resources, and social circuitry clarifies where leadership interventions are needed.
1. **Promoting psychological safety through the Westrum organizational model** (06:21) — Shifting from pathological fear-based environments to generative cultures improves defect visibility and learning.
1. **Executing gemba walks to uncover actual workplace constraints** (09:25) — Engaging directly with continuous delivery teams identifies realistic process friction without assigning blame.
1. **Empowering continuous improvement by pulling the andon cord** (11:27) — Treating production incidents as actionable feedback enables systemic reliability upgrades instead of individual punishment.
1. **Tracking team health with Spotify checks and DORA** (13:55) — Measuring job satisfaction alongside key technical capabilities provides an accurate barometer of workplace culture.
1. **Implementing slowification to transition from system one thinking** (16:55) — Deliberately pausing to plan structurally reduces biased reactions and separates novel unknown problems.
1. **Navigating complex unknowns using the Cynefin sensemaking framework** (19:56) — Classifying operational environments into simple, complicated, complex, or chaotic domains dictates the appropriate management strategy.
1. **Measuring deployment efficiency without standardizing local technical optimizations** (21:43) — Balancing DORA delivery flow metrics ensures rapid delivery translates efficiently into actual business value.
1. **Aligning strategic intent with immediate goals and OKRs** (23:16) — Defining clear immediate outcomes guarantees daily technical output drives overarching organizational objectives.
1. **Eliminating workflow bottlenecks using work in progress limits** (25:34) — Forcing synchronous collaboration when limits are reached highlights integration delays and refines process efficiency.
1. **Cultivating dedicated learning structures for technical mastery** (27:43) — Utilizing code dojos, mob programming, and dedicated innovation weeks builds proactive problem-solving capabilities outside daily tasks.
1. **Decreasing extraneous cognitive load to simplify complex systems** (31:11) — Reducing distractions and clarifying operational responsibilities allows engineering resources to focus effectively on germane execution.
1. **Optimizing workflows by applying Team Topologies architectural models** (34:11) — Distributing work across specific team topologies decouples dependencies and encourages autonomous platform utilization.
1. **Integrating an eclectic toolkit for optimizing software flow** (38:15) — Combining agile, lean, and sociotechnical tools creates a unified strategy for solving diverse engineering bottlenecks.
1. **Overcoming cultural friction and scaling DevOps team practices** (39:57) — Aligning delivery metrics and addressing foundational security priorities handles resistance during broader agile transformations.

## Related Moments

- [Unifying core software principles for better team performance](https://www.wearedevelopers.com/videos/721-the-quest-for-better-software) (from "The QUEST for Better Software")
- [Navigating and mitigating the impacts of broken engineering cultures](https://www.wearedevelopers.com/videos/1998-from-code-to-culture-why-leadership-determines-software-quality) (from "From Code to Culture: Why Leadership Determines Software Quality")
- [Using Scrum, stoicism, and systems thinking for engineering](https://www.wearedevelopers.com/videos/2103-systems-thinking-for-performance-how-to-diagnose-and-fix-slow-systems-without-guessing) (from "Systems Thinking for Performance: How to Diagnose and Fix Slow Systems without Guessing")
- [Defining the core pillars of modern DevOps practices](https://www.wearedevelopers.com/videos/1759-ai-killed-devops-what-now-lee-faus) (from "AI Killed DevOps... What Now? - Lee Faus")
- [Optimizing developer flow state and removing tooling constraints](https://www.wearedevelopers.com/videos/320-building-better-with-nuxt-3) (from "Building Better with Nuxt 3")
- [Transitioning to agile methodologies for faster software delivery](https://www.wearedevelopers.com/videos/611-from-punch-cards-to-ai-assisted-development) (from "From Punch Cards to AI-assisted Development")

## Related Articles

- [Now is the time for industrialized software development](https://www.wearedevelopers.com/magazine/601-now-is-the-time-for-industrialized-software-development)
- [Get Old, go Slow, Write Code!](https://www.wearedevelopers.com/magazine/81-get-old-go-slow-write-code)
- [Why Event-Driven Architecture Isn’t About Speed (and When You Actually Need It)](https://www.wearedevelopers.com/magazine/745-why-event-driven-architecture-isn-t-about-speed-and-when-you-actually-need-it)
- [MLops – Deploying, Maintaining And Evolving Machine Learning Models in Production](https://www.wearedevelopers.com/magazine/115-mlops-deploying-maintaining-and-evolving-machine-learning-models-in-production)

## Related Jobs

- [Tribe Lead - ( Software) Engineering Centre of Excllence](https://www.wearedevelopers.com/jobs/ext/1475530-tribe-lead-software-engineering-centre-of-excllence) at **SD Worx**
- [Lead Software Engineer - Data Engineering](https://www.wearedevelopers.com/jobs/ext/2000968-lead-software-engineer-data-engineering) at **Dynatrace**
- [Senior Software Engineer, Enterprise Products](https://www.wearedevelopers.com/jobs/ext/1841248-senior-software-engineer-enterprise-products) at **GitHub**
- [Senior Software Engineer](https://www.wearedevelopers.com/jobs/ext/15942-senior-software-engineer) at **GitHub**
- [Cloud Foundations Team](https://www.wearedevelopers.com/jobs/ext/1483289-cloud-foundations-team) at **GitHub**
- [Staff Software Engineer, Copilot Experiences](https://www.wearedevelopers.com/jobs/ext/164361-staff-software-engineer-copilot-experiences) at **GitHub**