Great book. Lots of practical tips, useful concepts and metaphors, as well as interesting stories. This is a roadmap for managers looking to the next
Great book. Lots of practical tips, useful concepts and metaphors, as well as interesting stories. This is a roadmap for managers looking to the next big thing in how to design &run companies Really enjoyed it...more
I recently read Helping: How to Offer, Give, and Receive Help by Edgar Schein (actually I listened to it on Audible and then read it again on kindle tI recently read Helping: How to Offer, Give, and Receive Help by Edgar Schein (actually I listened to it on Audible and then read it again on kindle to better process/digest). I can highly recommend it if you are interested in ways to become a more helpful consultant, manager, person - one who is able to actually help people/organizations rather than just dispense advice/suggestions. I'm not doing a full review of the book here but there are a couple of points I found very interesting in the relation between the Helping approach and the Kanban Method, which I wanted to put out there.
The key theme in the book is that in order to provide helpful help you need to be build the helping relationship - not jumping to the expert/doctor role of dispensing advise/diagnosing but first listening, understanding, working through what Schein calls Humble Inquiry which starts with Pure inquiry - understanding what is happening without trying to influence the client in any way. Only then moving to Diagnostic Inquiry which directs attention to other aspects in the story and Confrontational Inquiry which asks what-if questions thereby hinting at suggestions (which is close to the Doctor/Expert role).
"This kind of inquiry can best be described as accessing your ignorance and, because it is genuine inquiry, it is appropriate to call it humble. The helper becomes open to what may be learned through observation and careful listening. The helper’s expectations may be incorrect, and it is the helper’s willingness to accept new information that elicits trust and makes the client feel better about having a problem"
If we look at what we are trying to do with Kanban - it is quite similar. We start with understanding the system by visualizing it. Not trying to diagnose/probe too deeply before we understand - actually before the client/clients understand. Accessing our ignorance - we don't know HOW the system is working, we don't know how it SHOULD be working. Which is exactly what Schein is trying to do with process consulting - to build the understanding together, not be in a position to understand FOR the client but WITH the client. In Schein's perspective this not only minimizes the chance we will dispense generic advise based on our experience of similar events but will help to equilibarate the relationship between helper and helped - listening and respecting the situation helps the client/helped gain back "face" that he lost by asking for help. If we don't "bring the helped up" by doing this there is a chance he will "bring us down" by trying to be very critic and unaccepting of our suggestions by the way.
"Starting out in the process consultant role is the most likely to facilitate status equilibration and to reveal the information necessary to decide on what kind of help is needed and how best to provide it. Only when some level of trust has been established is it possible to get accurate information that allows the shift to the expert or doctor role. As the helping process proceeds, the helper may shift among all three roles many times as the situation demands."
This humble inquiry approach is also aligned with our approach towards management workshops in AgileSparks. Our instincts over the years pointed us away from diagnosing and presenting solutions and towards a more humble exploration of the system/context in parallel to presenting some useful patterns like Kanban, Scrum, ATDD. I try to emphasize the diagnostic role of these patterns/frameworks and the fact that even when we go out of the room with a decision to do something, it is basically a continuation of this "humble inquiry" (I didn't use the term until today obviously...). We are obviously shifting roles from process consultant to doctor and expert and one of my main takeaways is to be more conscious about the role I'm playing and whether it is the effective/helpful one at the moment. I'm definitely jumping to the doctor/expert one faster than I should - and I will try to work on that using some tips and tricks from the book.
To summarize - and as I answered Bob (Marshall) yesterday - this book leaves me: startled (discovering new perspectives of how I'm doing things), a bit ashamed (for being more of a Doctor/Expert), alert (to the potential of being more helpful using this approach) , curious (about whether I can actually leverage it and what will happen if I do), rejuvenated (by getting a fresh perspective to something so core to my work). So bottom line the Helping book was quite helpful....more