How we make decisions
How do we make decisions in a decentralized organized with no managers?
Note – for allocation of consultants to client engagements we have a specific protocol for that – the bun protocol. Similar for recruitment decisions.
Why don’t we have a well defined decision-making process?
We make lots of decisions all the time. Which type of coffee machine to buy? Should our internal fees be raised? Where & when is our next verseworks team meeting? Which associates and friends should we invite?
Different types of decisions need a different process. It would be crazy to involve the whole team in decisions like which type of whiteboard pens to buy. And it would be crazy to NOT involve the whole team if we needed to move our office to a new location.
So it’s not a good idea to have one single well-defined decision process for everything. And it’s not a good idea to try to list all potential decision types and create a well-defined process for each type, the list would be too long and complex, and there would be too many gray zones.
Well, how do we make decisions then?
You don’t need a well-defined decision process in order to make decisions. If that was the case, the world would stand still :)
Instead, we follow these principles/guidelines:
- The person driving an issue owns the decision process.
- A decision is only a decision if there is a “puller” who follows up on the execution. (we use the term “driver” and “puller” interchangeably)
- Important decisions should be documented in our decision log and emailed to everyone
- Some decisions lead to funded “projects”, like a new website.
Example: If I want verseworks to collaborate with company X, then I’m the one driving that question and I pick the decision process.
How do I pick a decision process?
Here are some examples of different decisions processes on a scale from “fast” to “well-anchored”.
- Own decision. Decide yourself without talking to anyone.
- Own decision with team input. Ask for input from the team, but then make the decision yourself.
- Own decision with team-anchoring. Ask for input from the team, suggest a decision, check if the team is OK with it before closing the decision.
- Team decision. Facilitate a decision from the whole team (using consensus, with majority vote as fallback if we can’t reach consensus).
The term “team” in this case really means “those who are affected by the decision”. Sometimes the whole team, sometimes just a few individuals.
These decisions processes can be combined. For example, start by getting input from the whole team, then suggest a decision and anchor with those people who are most directly affected.
For simple decisions, this communication can happen via email, an online poll or Slack. For more complex or sensitive decisions, face-to-face conversation is better. We usually do those at our team meetings or ad-hoc in the pub.
Some things to consider when choosing a decisions process:
- Who is affected? Only you? You and a few others? The whole team?
- How important is this question to you? How important is it to those who are affected? Is it a critical decision or trivial one?
- Is the decision reversible? Most decisions are. What is the consequence of making the “wrong” decision, and who is affected by that?
- How easy or hard is the decision? How easy is it to reach consensus with all people affected?
- How urgent is the decision? What is the consequence of delaying the decision, or not making a decision at all?
- Who are you? The decision process may vary depending on your perspective – consultant, board member, office admin, etc. May also depend on how long you’ve been at verseworks (if you are new and unsure you might need to seek more anchoring from people).
- Are there legal consequences? We need to make sure that decisions we make are within the law, and reflect our values.
- “Should I arrange a free seminar with Lyssa Adkins” => Own decision. Just do it.
- “Which colour should we have on the verseworks cup?” => Own decision with team input.
- “How often should we do unconferences?” => Own decision with team anchoring.
- “Should we divide the company into two business units?” => Team decision.
At the end of the day it’s about balancing risk. If you make the decision yourself it will be fast, but you risk a backlash if others don’t support it. If you seek 100% consensus you may get a better decision with better support, but it could take time – especially for questions where people have opposing opinions.
There is no perfect process, so seek a balance between these extremes! We most often end up in the middle of the scale – “own decision with team input” or “own decision with team anchoring” (where “team” isn’t necessarily the whole team)
What if I still feel unsure of which decision process to use?
Here are some options:
- Take a chance! “Better to ask for forgiveness than permission”. Most decisions are reversible, so you don’t really need to be afraid of making the “wrong” decision or using the “wrong” decision process. Just accept feedback and learn.
- Talk to a verseworks colleague, for example someone who has been around longer and can give examples of what has worked in the past.
- Check if someone else can drive the question for you (or with you). Preferably someone who is strongly engaged in the question. For example if I want next verseworks unconference to be in the Maldives I’d involve the office team, since they usually arrange our unconferences. It’s nice to pair-drive a decision, so you can always ask on the team mailing list to find a co-driver.