Every once in a while, we're in a meeting or workgroup and it appears that the workgroup is focused on making things perfect before taking the next step...I'll hear comments like the 'administrators will need this'....'the teachers will say this...' 'they need to know ___, ____, and ____ before we get started.' etc, etc...to the point where rather than understanding that the outcome or the next steps will make our schools better even if the system of implementation is not perfect.
In some ways, isn't that better? Doesn't it show a sense of risk-taking to those around us? Doesn't allowing risk create trust? Doesn't it allow us to engage folks in doing the work rather than just talking about the work? I'm pretty sure it's akin to what Rick DuFour states in his writing that we 'Learn by Doing'...not by talking about what we're doing. It's very similar to a 1st generation model or taking something to the 'beta' stage. This is different than a pilot in my mind. (see future blog on Pilot v Beta). Please don't misunderstand me and think that we should half-a__ things just to get them out there...but there's a point in a work group where you begin to overthink every detail before really finding out all the details. This is all beginning to remind me of the concept of 'perfection paralysis'...a debilitating organizational disease. But, how do we break through or out of paralysis? How do we get others to break out of perfection paralysis? When is the right time to 'move-on'?
Compounding this situation is the fact that our the stakes are too high for our kids to wait until 'we' have it perfect. Our kids need better NOW...not in a month not in a year...not until the 'experts' think we have it perfect...they need better NOW!
Opponents to this concept or those that are conservative will say that the stakes are too high for us to take that risk and will filibuster a committee for months and years. It's easy to be conservative in these situations...it's not easy to take risks. (Another blog for another time).
I don't have the answers...just lots of questions on this topic. But, I think we need to reflect on this as we are working together as an organization or work group. So, what if we just sent it out there knowing it's not perfect and letting other know that it's not perfect...then say let's work out the kinks to make it better. What's the worst that can happen? It's a colossal 'failure'? Doubtful...If it's a good idea and has a researched background, then that minimizes the chances of 'failure'. Also, if we know we're going to use it as a launching point and not the ending point, then doesn't that create some level of buy-in?
In some ways, isn't that better? Doesn't it show a sense of risk-taking to those around us? Doesn't allowing risk create trust? Doesn't it allow us to engage folks in doing the work rather than just talking about the work? I'm pretty sure it's akin to what Rick DuFour states in his writing that we 'Learn by Doing'...not by talking about what we're doing. It's very similar to a 1st generation model or taking something to the 'beta' stage. This is different than a pilot in my mind. (see future blog on Pilot v Beta). Please don't misunderstand me and think that we should half-a__ things just to get them out there...but there's a point in a work group where you begin to overthink every detail before really finding out all the details. This is all beginning to remind me of the concept of 'perfection paralysis'...a debilitating organizational disease. But, how do we break through or out of paralysis? How do we get others to break out of perfection paralysis? When is the right time to 'move-on'?
Compounding this situation is the fact that our the stakes are too high for our kids to wait until 'we' have it perfect. Our kids need better NOW...not in a month not in a year...not until the 'experts' think we have it perfect...they need better NOW!
Opponents to this concept or those that are conservative will say that the stakes are too high for us to take that risk and will filibuster a committee for months and years. It's easy to be conservative in these situations...it's not easy to take risks. (Another blog for another time).
I don't have the answers...just lots of questions on this topic. But, I think we need to reflect on this as we are working together as an organization or work group. So, what if we just sent it out there knowing it's not perfect and letting other know that it's not perfect...then say let's work out the kinks to make it better. What's the worst that can happen? It's a colossal 'failure'? Doubtful...If it's a good idea and has a researched background, then that minimizes the chances of 'failure'. Also, if we know we're going to use it as a launching point and not the ending point, then doesn't that create some level of buy-in?
Ironically, there are many times that I suffer from this as a writer and am making a conscious choice today to 'move-on' and leave this blog as is...and also think about some of my other blogs. They are not perfect...they need to be refined, but rather than wait to make them perfect, I'm going to let them all go to 'beta'...isn't that the beauty of a blog anyway that it can always be revisited and refined? Maybe, that's my New Year's Resolution for blogging...just get some words down...hit 'Save' and then come back later and make it better.
Thanks for taking the time to read this blog today...I hope to make it better soon!