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

What if slowing down is the secret to delivering value faster? Learn a practical framework to separate fast flow from fast fluff.

#1about 3 minutes

Defining fast flow versus fast fluff in organizations

Differentiating between a continuous stream of value (fast flow) and wasteful activities like unused projects or wrong features (fast fluff).

#2about 3 minutes

Using a three-part model for organizational change

The talk is structured around the eclectic model of amplification, slowification, and simplification from the book "Wiring the Winning Organization."

#3about 5 minutes

Making problems visible with psychological safety and Gemba walks

Improving organizational feedback loops requires fostering psychological safety and using tools like Gemba walks for leadership to observe and understand real work.

#4about 5 minutes

Using tools like the Andon Cord and health checks

Practical tools like the Andon Cord, Spotify Squad Health Checks, and retrospectives help teams surface issues and continuously improve their processes and wellbeing.

#5about 5 minutes

Slowing down to solve complex problems effectively

Adopting "slow thinking" and using frameworks like Cynefin helps teams differentiate between simple, complicated, and complex problems to choose the right approach.

#6about 6 minutes

Aligning teams with goals and WIP limits

Using goal-setting frameworks like OKRs and implementing Work in Progress (WIP) limits helps teams focus on delivering value and quickly identify workflow bottlenecks.

#7about 3 minutes

Building a continuous learning culture in teams

Creating dedicated time and space for learning through practices like coding dojos, code retreats, and liberating structures improves team capability and problem-solving skills.

#8about 5 minutes

Simplifying work by managing team cognitive load

Understanding and managing the three types of cognitive load—intrinsic, extraneous, and germane—is crucial for preventing team burnout and improving focus.

#9about 4 minutes

Designing teams for fast flow with Team Topologies

Structuring the organization around four fundamental team types and three interaction modes reduces dependencies and optimizes for flow.

#10about 18 minutes

Q&A on Team Topologies, security, and cultural change

Answering audience questions on implementing Team Topologies, balancing speed with security, handling cultural resistance, and applying DevOps principles in various team sizes.