by Ted Eytan, on 28 Feb 2007 05:01 am
The Journey
Problem(s) solved
Lasting change does happen, and several examples arrived in my InBox this week:
First, from a message I received from a colleague about changes they made to our information systems, based on standard work we created for them, to support our doctors use of evidence-based guidelines:
The long and short of it was that all the work got done (there had been quite a bit of pre-work) so that we could put together all the materials necessary for implementation … and sync everything up according to our [health care] system needs so that will be able to present all changes, all materials…within a very reasonable timeframe, something that historically would have taken months.
Lots and lots of very positive feedback from the whole team about how much was accomplished in a relatively short time.
Second, I participated in a rapid process improvement last week with colleagues (and led by one of this blog’s readers…) where we specified new configurations and several pieces of code, tested them, slotted them for production use, and found them loaded into our system using a standard process just two days later.
Prior to our transformation, I clocked similar changes taking 30 days each.
It isn’t so much that I notice the difference, though. It’s that the people serving our members who do the innovation notice the difference. And the difference is not just the speed at which they can create change, but that they get to lead change and see the impact.