Do-ocracy: Has anyone looked this is awhile? It’s on our New Members 411 wiki page (New Member 411 - Dallas Makerspace)
It links to a community wiki page (CommunityWiki: Do Ocracy) that has two examples.
One: Mary inquires about food arrangements at a large group outing, asks for help, gets little to none, takes on the load and this pops up: “Jeez, why does Mary get to decide what everyone eats and when they work? Who put her in charge?”
Two: A corporate IT group replies to requests for applications in arrogant, condescending ways and takes forever to do anything. IT customers teach themselves how to do something IT can’t be bothered with, do it quickly and successfully. IT strikes back by issuing an edict that “pirate” software “will not be supported” by IT helpdesk staff and is an improper use of company property (the network). In the end IT loses the job for development and is limited to maintenance and support activity.
Hmmm, the complainer about Mary and the staffers who can’t evolve to get things done sooner than later are not strangers at DMS. Once you get past all the fantastic creativity and problem solving done by Makers in the business of Making what you have left is a Don’t-ocracy.
Start a sentence like “What if we did _______ to solve an issue or create an opportunity at DMS …
Some popular responses are (in no particular order)
- It’s not a problem to me (or my committee), so by definition … it’s not a problem
- We did something like that and it didn’t work
- “They” would never agree to that
- We have never done things like that
- It’ll take changing the rules/by-laws, etc. ie: better keep the problem and avoid a solution
- The BoD will never agree
- The membership will need to explore ever option in public debate (until everyone loses interest)
- Here’s just the top 10 reasons that is a bad idea
- It won’t work because you haven’t explored every possible detail before you raised the thought
- That’s a political hot potato …. should not go there.
- That committee would never agree
- It’s OK as long as my committee can opt out.
- Everybody thinks such and such
- Nobody thinks such and such
- Somebody will try to cheat the system (compared to cheating with no system)
- It could be worse, we are at least as good at this as such and such example.
- Or a personal favorite … only if we can make it really complicated with a bunch of gadgetry, coding, tracking and identify/gotcha members who might do something wrong.
I’m sure I missed some too.
What do you not hear enough: “Well, there will probably be some challenges to overcome, but let’s think about how we could approach this and get the desired result(s)” or anything remotely related to “let’s figure out how we could do it” instead of regurgitate all the reasons why we can’t.
And lastly, I would really like to see DMS develop a willingness to pilot ideas, run experiments that sunset if results aren’t what’s desired … basically the same thing makers do when they try a new concept and keep tweaking it until they decide it either works or it doesn’t. When it doesn’t work … it’s not a failure, it’s something learned.
