Skip to content

Instantly share code, notes, and snippets.

What would you like to do?
Talk resources


Favourite things to read/talk about:


Time for What's Next

10 Min Slides Here
30 Min Slides Here

Key points:

Most team effort/growth/transformation is doomed because companies lack visibility into how it improves the business

  • lack buy in/alignment
  • arbitrary focal points based on industry
  • arbitrary roadmaps unlinked to reality

Most teams focus on micro optimization instead of starting with a holistic view

  • mistakenly focus on tools
  • try to buy a technical solution to a people/process problem
  • not looking at the big picture

By improving your existing processes, you can regain time to improve

  • stream mapping reveals issues/opportunities
  • helps alignment, communication and understanding
  • serves as a roadmap for improvement

I call this process Flow Engineering.

Remember the current system and process exist because of many actions and events, and blame for the current state isn't going to move you forward. Every step forward is a cause for shared celebration and since we can measure every iteration, there's data to account for every improvement! Sharing your progress is an excellent way to spread learning, good practices and scale the momentum to other teams.

Don't worry so much about the detail of Value Stream Mapping (VSM) - 80% of the value comes from 20% of the parts - focus on the Goal, Steps and Lag time. The main benefit is in creating a visual asset so separate groups (Dev,Ops,Support,QA,etc) can all have a common understanding and point of reference



Principles of Product Development Flow
Value Stream Mapping
Learning to see
Toyota Kata
The Goal
Project to Product
Visual leadership


DevOps Traction






The DevOps Pipeline




Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.