6D root cause analysis of flow in knowledge work

I have been working on a little framework for analyzing why work is, or is not, flowing. The result can be seen below. It takes the form of an Ishikawa, or fishbone, diagram.

Screen Shot 2013-11-17 at 15.41.41

The purpose is to look at a situation and use the framework to identify causes of why work is not flowing.

The Ishikawa diagram above, nicely complements the 4L root cause analysis that I posted before. The 6D framework can be used at the team level; the 4L framework at the value stream level.

I am putting it on the blog mainly to get feedback. Do you find it useful? How do you find the categories? Let me know.

This entry was posted in Uncategorized and tagged , , , , , . Bookmark the permalink.

1 Response to 6D root cause analysis of flow in knowledge work

  1. Carolyn says:

    This would be a great tool to give the team a fresh way to approach the retrospective. Would you consider elaborating on the 6Ds as you did in the 4L blog? Some of my questions are: How do you differentiate between demand that is disruptive/speculative versus ambiguous/variable? If there were impediments because the team was waiting on a service from an outside group, would that fall in the Availability category? And finally, could you give some examples of delayed or dis-engagement? Thank you!

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s