Using Lean Thinking to Improve Knowledge Work

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, July 4, 2009

Systems Thinking: Why Analysis Can't Answer Critical Questions About Systems

Here, Dr. Ackoff:

  • distinguishes between gaining knowledge vs. understanding
  • compares and contrasts 3 steps of "synthetic thinking" with "analytical thinking" (analysis)
  • states that an "essential property of a system is that it cannot be divided into independent parts"
A key takeaway is that a system is not (equal to) the sum of its parts, but a product of the interactions (of the parts).

I'll create a summary comparison table of the 3 steps.
Bookmark and Share
Posted by Robert Damelio at 1:36 PM
Labels: , , , , , , ,

2 comments:

b_flat said...

Hi Robert -

I love the nuggets you're posting on "Systems Thinking" - more, please, especially the table you mentioned.

I especially like the material on analysis vs. synthesis. About 20 years ago, I was on a crusade to have the job title "Business Analyst" changed to "Business Synthesist," because it's in the synthesis of details into a new or a previously unseen whole that a BA really adds value. Obviously, I didn't succeed, but it's great to see synthesis being discussed. Thanks! :-)

Your post reminded me that around the time of that crusade I did a presentation on the essential facets of being a business analyst (or whatever you want to call it.) I dug out the pres, and found the slide where I depicted those facets, drawn like the points of a compass:
- up or north was synthesis
- down or south was analysis (division into more granular details)
- left or west was representation (showing the same subject in different ways, primarily graphic, narrative, and scenario/example, to appeal to visual, auditory, and kinesthetic learners.)
- right or east was analogy (illustrating the concept via an analogy to something well-understood.)

Really interesting stuff, as usual in your blog - like I said, I'm looking forward to more.

Cheers,
Alec

July 11, 2009 8:46 PM
Alec Sharp said...

Thanks, Robert, for the posts on synthesis vs. analysis. This is a topic that's been near and dear to my heart for about 20 years, but I don't think (astoundingly) that I'd ever seen anything written about it. So many of the problems what people have with Business Analysis have to do with the focus (not surprisingly) on analysis. The result is useless requirements documents that are the product of traditional analysis - breaking things down finer and finer and finer until they are discrete and trackable, but devoid of context. The real value, of course, is when these details are synthesised into a view that didn't exist before. Hmmm - I seem to have climbed onto a soapbox, so I'll climb down now.
I just wanted to let you know how much I appreciate the posts you've put up on this subject. I look forward to more.

Thanks,
Alec

July 15, 2009 11:12 PM

Post a Comment

Subscribe to: Post Comments (Atom)