Most of the work we do is knowledge work. What does that really mean? Are there characteristics to knowledge work that we should consciously address when we seek to do this type of work faster, more cheaply, or better? Though I've spent more than 25 yrs working to improve knowledge work, I still consider myself a student. In this blog, I hope we can learn from each other. I can get us started-where we go from there is up to all of you. Thanks for taking the time to read and participate.

Saturday, September 20, 2008

2009 ASQ Lean Six Sigma Conference Presentation

I know it is early to think about what you are doing next March. I'll probably forget about this myself. But, right now I want to let you know that I'll be speaking on "Organizing Around Flow" at the 2009 ASQ Lean Six Sigma Conference.

Click on the title of the post and it will take you to the Conference website for more information.

Here is a preview of what to expect from this session:

"One of the central foundations of lean thinking is the focus on the flow of the work. In this session, you’ll get a chance to explore and clarify some of the key characteristics of workflow in knowledge-intensive work. This will help you more quickly recognize some of the situations you’ll likely face, and it will help prepare you to address those situations as well.
"

Here is what we'll discuss:

Objectives:

  • What is “flow,” anyway?
  • What are some key considerations of flow in knowledge-intensive work?
    • Jobs vs. flow
    • Assets vs. flow
    • Boundaries of the flow
    • Ownership of the flow
    • Determining customer demand
    • Scheduling and prioritization
    • Inputs vs. triggers
    • Output criteria and standards
  • What does it mean to “organize” around flow?
  • What does it mean to “manage” the flow?
  • Recognize typical challenges associated with organizing around flow
  • Discuss selected approaches to help you organize around flow
I look forward to seeing you there.

PS. Organizing Around Flow is one of the 7 Principles for Improving Workflow.

0 comments: