Pearls Of Wisdom (or not)

Following a discussion about management in a LinkedIn forum, I got an email with a thank you note, and a very good question:
You have sent me on a quest and given me a useful map, but this journey is going to take some time and have to be scheduled. Are you willing to pass on any pearls of wisdom from your journey?
I do not have a very good answer, I am afraid, but I did my very best. Here is what I wrote:

The following works for me. The important thing is not to do the same things, but to do what works for you:
  • Here is what I am doing right now: I study Hoshin Kanri, Lean policy deployment. Toyota is one of very few companies able to execute a strategy well. It is my opinion that Hoshin Kanri and Lean Accounting (or similar practices) are critical success factors when implementing Lean. Also very useful insights if one is interested in Strategic Navigation, or anything else which involves deploying policy.
  • When you read a good book, check the references at the back for interesting reading.
  • Don't be afraid to ask about things. I sometimes contact authors of books I've read if there is something I cannot get my head around. Most have been very helpful. When I began writing my own book, Tempo!, I contacted some very, very smart people and asked if they would proofread parts of the book. So far, everyone I contacted wanted to help out. The book is better for it, and I have learned a lot that I would never have figured out on my own.
  • Find some interesting newsgroups and join. It is amazing what one can learn. Pay close attention when people discuss books they've read. I have got a lot of good tips. (I ruin myself by buying too many books, and I measure my reading backlog with a carpenter's rule, not the number of books. Nothing comes without a price.)
  • Cherish the people who disagree with you, because they are the ones who just might teach you something.
  • Make notes while you read. My books are full of scribbled margin notes. I don't just mark interesting passages, I write keywords in the margin, and make references to related material in other books.
  • Use a mind-mapping tool, FreeMind, to track interesting ideas. (I will admit that my own FreeMind database is always a few steps behind. It is still very useful.)
  • I don't drive, ever. I take the bus. Gives me more time to read.
  • When you find an idea you like, try to find a book by an author who disagrees, or promotes a different idea. For example, in order to understand The Logical Thinking Process from TOC, I also study general systems thinking, system dynamics, and some interesting approaches that are not based on the idea of systems, but more on patterns and pattern recognition.
  • Practice! Apply your knowledge to everyday problems.
  • Observe the systems around you. I am fascinated by such things as queues in restaurants. Could the flow be improved if the forks and knives were moved a bit to the left? Can the flow at the salad bar be improved?
  • Experiment! I have done the statistical experiment in Goldratt's The Goal, the funnel experiment from Deming's Out Of the Crisis. I sometimes device my own small experiments, including behavioral experiments. You will learn a lot from this. (Be careful with the behavioral experiments. Use willing subjects, or be very, very subtle.)
  • Write about what you learn. The act of writing it down makes it stick. If you write a blog, or a book, the feedback will teach you a lot.
  • Work only with stuff you are passionate about. This will cost you, but it is also immensely rewarding.
  • When you are with your family, really be there! I have a three year old son, and I really want to be present in his life when he grows up. (And he teaches me a lot about human behavior. I use ideas from systems thinking and behavioral science to bring him up. Seems to work.)
  • Don't fear failure. It is nature's way of teaching us things.
  • Learn from other peoples failures when you can. It is cheaper, more comfortable, and more fun than making your own.
  • Make a conscious decision about whether you subscribe to Theory X or Theory Y. Your views of other people have a strong impact on how you interpret information, and manage relationships. Therefore it should be a conscious decision.
I don't know if there are any pearls of wisdom in the list above. It is how I approach learning, but I do not lay claim to having any great wisdom or insights. I do have a lot of fun!

Comments

Michael Nilsson said…
very intresting thing, how we learn.
I think you would like this audiobook: http://www.amazon.com/gp/product/0671536842/

I do allot of things the same as you but i will for sure add listening on audiobook wile walking, training or if you have to drive a car.
April 21, 2009 8:30 PM
Post a Comment

Popular posts from this blog

Waterfall vs. Agile: Battle of the Dunces or A Race to the Bottom?

Image
The major software methodology wars since the mid 1950’s. Someone was wrong on the Internet, so here we go… In a recent HBR article, It’s Time to End the Battle Between Waterfall and Agile , the author sets up a false premise: There is a war between Waterfall methodology and Agile. The war must end. And finally, you can combine the approaches to get the best of both worlds. This sounds good, but the article is based on a misunderstanding of both Waterfall and Agile. Also, there is no war between Waterfall methodology and Agile. There can’t be, because Waterfall methodology does not exist! Waterfall is a name for large projects that failed in the 1960’s. Waterfall was never a methodology, but a failure to apply the methodologies that existed back then. As I will show towards the end of this article, at least one of the “successful” Waterfall projects mentioned in the HBR article was neither successful, nor a Waterfall project. I got invaluable help from Alistair Cockburn. He fact che
Read more

Performance Evaluations, Business Strategy, and Agile Methodologies

Image
It is performance evaluation time in many companies. This can be stressful, both to the people being evaluated, and the people doing the evaluation. In companies adopting agile software development methods, the tension can be extraordinary. Individual performance evaluations run counter to agile philosophy, which emphasizes team performance over individual performance. However, managers and corporate leaders need to take a few steps back, and consider the impact performance evaluations have on the organization as a whole. Especially now, in the midst of a recession, it is important to look at a companies current policies to see if they can be improved, or if they are actually holding the company back. So, how can a manager evaluate policy? Performance evaluation policies can serve as an excellent example. I'll confine myself to discussing the so-called ‘rank and yank’ methods. These are performance reviews were employees are ranked using a forced ranking system. It usually looks so
Read more

Agile Requirements Structures, Part 1

Image
If you have worked in large Agile projects or programs, you may have noticed that there is often quite a bit of confusion about requirements, what the requirement types are, their purpose, how to write them, how to use them, and above all, what not to do with them. There are many causes for this confusion. Here are some of the more common I have seen: Nobody in the organization has read up on the requirements model it is using, so everyone makes their own interpretation. The organization deviates from a standard requirements model, but nobody knows which standard model the organization is deviating from, and/or there is no agreement about how they deviate from it. The organization has not documented its own requirements model very well. The organization mixes two or more different requirements models, often without realizing it. The organization has documented its requirements model, but finding the documentation is an epic project in itself, on par with when Henry Sta
Read more