Move fast.
I'm often struck by the desire to move fast with the assumption that a correct or good solution is inevitable regardless of the process used to derive that solution.
I've never seen the command, "we need to go fast," accompanied by the proportional increase in resources or the necessary scaling of scope to meet such a timeframe. Instead what usually accompanies the command for speed is the notice that it must be done with limited resources and the scope of the effort will not be negotiated.
Imagine yourself sitting in the doctor's office with an unknown ailment necessitating treatment and you are there for the physician to diagnose and treat this illness. Of course you want it fast; you want to be on the road to recovery. Now ask yourself if you are willing to sacrifice a physical examination, needed lab tests, and any other diagnostic interventions necessary to correctly identify the illness, its causes, and the treatments to put you on that road to recovery. Imagine: would you ever hope the doctor would burst through that door with a syringe of medicine (don't worry, we know it's worked on several other patients!) that is immediately injected in you, then to have that physician ask for thanks as they walk out the door?
Just as you would never allow yourself to be treated in such a manner, neither should you allow for your organization to inflict 'known solutions' onto your business without understanding the problem at hand. Even in a code blue situation necessitating rapid assessment and treatment, care providers still assess.
Remember to take the time to define the problem at hand, to understand the reality of the current situation, to truly surface the root causes of the problems that exist, and that any solutions proposed address the root cause(s). Otherwise you're stabbing the organization with a syringe of unknown contents, and that's just assault.
APN/PA Clinical Practice Manager at Kaiser Permanente, CO
5 年Hmmm. Sounds like instruction to 1) make a problem statement/define problem, 2) gather some data to understand how your system is operating currently, 3) make a cause/effect diagram to find sources or error/problem, 4) construct a driver diagram so everyone knows how it affects the org, 5) identify and try some PDSAs from step 3 above with input from those working at Gemba, 6) watch data for result of PDSAs, 7) create standard work and adopt PDSAs that are proven and 8) create a sustainability plan in place so this change can spread for more improvement. Anything I’m missing?
APN/PA Clinical Practice Manager at Kaiser Permanente, CO
5 年What if the syringe of medical treatment was from a PA or NP?........just sayin!??
APN/PA Clinical Practice Manager at Kaiser Permanente, CO
5 年Well said Friend. Acting in this manner is a real Achilles heel!
Healthcare Learning & Development - RETIRED
6 年Goll-LEE, I miss working with you.
GME Generalist at SCL Health
6 年Miss you Michael!? I hope you and your family are doing well!