“Blink” Program Development
Discuss, propose, discuss, test, discuss, propose again, tell everyone about it so they know it is coming, implement.
Seems cumbersome.
How about the following? Discuss and implement. Partner, discuss and adapt as we go along.
In several of our clients we are trying the "Blink" method of program development. It has been most successful with a group we are working on building coaching skills. We got together, decided we didn't want to do a training course, and together we came up with a format. IMPACT helped launch it. The client has run with it. We get connected periodically, refine and keep going. It has been quite a success.
Another story has been a little more difficult. Similar to the group above, we agreed we had a problem to solve -- help people be more successful at work. The challenges with this story have come with the partnering piece. It is important to ask for and accept regular feedback and then adjust and move forward. What has broken down? Probably time and focus. We get the feedback and we have not dedicated enough time to the adjustment phase. We have not been ok with the negative feedback. The important assumptions in these kind of "blink" implementations is openness to imperfection and building it as we go.
What do you need to make this work?
- courage to not be perfect and try some new things
- open communication: consultant, client and participants need to be able to say "this isn't working" let's change
- participants in the program need to be able to provide regular feedback
- the time to make the adjustments
- stamina: the ability to maintain focus on your objectives while changing your approach or the details. Not throwing the "baby out with the bath water".
