Sunday, June 19, 2011

Reflections on the passing of Eli Goldratt

Eli Goldratt, creator of the Theory of Constraints, author of many books including the best selling and seminal, “The Goal”, passed away last weekend. I had the pleasure of meeting Eli twice and interacting with him via email a few more times. Eli’s work strongly influenced and inspired my own and I’d like to share my thoughts on the sad occasion of his death.

I first encountered Eli’s work when my boss at the time, John Yuzdepski, gave me and my colleagues copies of The Goal in March 2001.I read it on a flight from Dallas to Tokyo. About 2/3rds of the way through I had the epiphany that I could equate Features in Feature-Driven Development to inventory in Eli’s Drum-Buffer-Rope system. I spent the remainder of the flight vigorously marking up notes in the margins throughout the book. What evolved from that was my 2003 book, Agile Management for Software Engineering

Eli was kind enough to respond positively when he heard from me out-of-the-blue asking him to review my manuscript and write the foreword. He referred me to his friend and colleague Eli Schragenheim who provided the foreword. Goldratt was polite, patient and welcoming to a newcomer to his community. I had not taken the classes, passed the exams or become a “Jonah”. I was just some guy who’d read 7 books mostly written by Goldratt and figured some stuff out for myself. I came to realize later that Goldratt’s kindness extended to the professional courtesy that my use of his ideas was probably ill-founded. He knew the underlying assumptions behind his own work and his choices to focus on physical goods businesses was not an accident. He almost certainly knew that the assumptions his work was founded upon were not true in knowledge work problems like software development. He was kind enough not to shoot my work down given that I’d spent a year writing a 300 page book about it.

I believe that Eli was incredibly tolerant of failure and of early innovation that wasn’t fully baked or thoroughly thought through. We saw this with his tolerance of the early failures pitching “viable visions” and with his grace to hand off my manuscript to Schragenheim who concluded that the mapping of requirements to inventory was ingenious and enabled a major step forward in managing software development. This was particularly poignant as both he and Goldratt had owned and run software companies and the use of DBR had never occurred to them.

I was invited to the 2004 TOCICO conference in Miami where I was to meet Eli for the first time. During the conference I learned that my own father had died. Eli was very warm and compassionate, surprising to me as I was a total stranger to him. I was unable to get a flight back to Seattle to collect my passport and actually stayed through the end of the conference returning home on my scheduled flight, only to turn around and fly to Glasgow immediately afterward.

The following year I was invited again to TOCICO where I presented the XIT case study as a DBR implementation. This was the foundation of what we now refer to as Kanban (for software development) and it had evolved directly from my experience writing my first book. I was inspired by Eli’s “5 Focusing Steps” and the incremental evolutionary approach to change inherent in TOC. Once again I found Eli warm and welcoming of an outsider presenting ideas and experience from a different field. It was evident that he was fiercely loyal to his people as well as affectionate in a fatherly sort of way. Everything he gave he got back tend fold from his loyal following.

I will primarily remember Eli Goldrat as a warm, affectionate, kind, loyal, trusting and respectful man who just happened to care deeply about how people worked together while holding a passion for effective performance of businesses. Eli never approved of an improvement that was achieved at the expense of the workers. He could be viewed as a very social capitalist. I believe his leadership in this respect is exemplary and will in future be recognized as visionary and ahead of its time.

I have the greatest respect for Eli the man and the intellectual and his work continues to inspire me even if my focus has changed and I’ve come to see the limitations of applying TOC to knowledge work problems. To recognize limitations isn’t to criticize. Today we’re solving a different set of problems from the ones Eli tackled. Eli’s work will continue to be a core foundation of how we think about improving the effectiveness of the knowledge workplace. Eli’s leadership and example will continue to inspire us as we seek the intersection of performance that is a better economic outcome together with a better sociological outcome for everyone involved.

Eli Goldratt may you rest in peace. My deepest condolences to your family and everyone at Goldratt Consulting.

Posted by David on 06/19 at 06:42 AM
Page 1 of 1 pages

David,

Touching story around how you met Eli.

I think Eli was wise not to shoot down you earlier work, likely he saw the innovation for what it was, and very likely he saw the passion behind the person who wrote it, deep passion always commands respect.

Jeff

Posted by Jeff Anderson  on  06/19  at  02:06 PM

Hi, David

Very nice tribute. I recall meeting you the first time at that TOC conference and the sad news you had to deal with then.

I have been meaning to write you to congratulate your work with your new Kanban approach. It complements what I do with Critical Chain Project Management (CCPM) perfectly.

While I can agree that Kanban alone can form a complete solution for the domain you work in I read your 2009 comments on critical chain and have to disagree with some of your assertions there and the implications about Goldratt’s work not applying to knowledge work in your most recent post.

CCPM focused on reducing WIP from the beginning. We just didn’t call it that till about five years ago. It did it for single projects by assigning resources fully to tasks and leveling the demand for resources before selecting the critical chain. It did it for portfolios of projects by Pipelining…including a capacity buffer. In the last five years there has been much explicit focus on reducing WIP and some have even used WIP control more directly as the project release mechanism.

CCPM has also employed Pull for a long time. Again many haven’t called it that till recently. The innovation of the Task Manager (read SCRUM Master or Kanban Team leader prioritized task list supports this behavior. All the other team behaviors you describe in your book have been recommended Task Manager and team behaviors within CCPM by most practicioners for going on ten years.

I believe your Kanban method is in no way limited to IT work. I believe it applies to all work; both knowledge and physical. I am employing it in both domains and mixed domains.

I also find Kanban integrates beautifully with CCPM. A task on a work group’s Kanban board can be a project schedule task. It simplifies the project schedules by not needing the Kanban columns as discrete tasks. It helps integrate non-project work with project work whilst maintaining work group WIP.

The beauty of CCPM and Kanban combined is that it works for any kind of project of any size. You might think of CCPM as providing the mapping across Kanban boards and overall buffering so that buffers aren’t needed in each Kanban.

I have a presentation that I have been giving on this and have a couple of customers actively piloting the combination. I am adding the audio to the presentation and will have it on my WEB site soon. I’ll let you know when that is.

So please keep on with your good work but also please describe CCPM and Eli G’s work more accurately in the future.

Regards,
Larry Leach, PMP

Posted by Larry Leach  on  07/10  at  09:58 AM

Larry,

Thanks for your note. It’s not particularly appropriate to have a discussion of theory under this particular post marking such a sad occasion.

I did find your response curious as Kanban has neither time buffers nor does it track tasks on the board, so I am unclear how to respond to you. Perhaps you’d like to take it up on the Kanbandev discussion list on Yahoo!?

Regards,
David

Posted by David Anderson  on  07/10  at  07:29 PM
Page 1 of 1 pages
Commenting is not available in this weblog entry.

<< Back to main