Decision-Making Framework
DOCX download
Decision-Making Framework
Free editable Word guide you can copy, fill in, and share with your band. Also readable on this page.
How to use this guide
Framework for making band decisions. The result is a written decision log entry — method, decider, date — carrying its own reopen conditions.
Log a live decision here — method, decider, date, and the 'review if' trigger — and keep the log beside your booking notes, adding an entry after every settled call.
Endless debate is usually missing a decision rule. Frameworks make speed and fairness possible when stakes and stress rise.
Match method to stakes
Membership changes, big money commitments, and genre pivots deserve full consensus because everyone shares the risk permanently. Tuesday-level operations like rehearsal start times, merch reorders, and which photo leads the EPK can run on a quick majority or a leader call after hearing input.
Agree on the style before the argument starts, because switching from a vote to a veto halfway through is how people feel cheated. A poster font should never consume the same process as adding a fifth member; treating them alike is how bands die of procedure.
Input then decide
Open a written input window with a hard close — say, comments in the shared doc by Sunday at nine — and then one named person calls it. Endless group-chat threads reward whoever types most, and quiet members stay quiet unless someone asks them directly by name.
Once the call is made, log what was chosen, who owns the follow-through, and when it takes effect. Undocumented choices get re-argued three rehearsals later as if they never happened, because everyone honestly remembers a different ending to the same meeting.
Review when reality changes
Every settled call should carry its own reopen conditions: a booking assumption that broke, a member joining or leaving, costs that doubled since the vote. Without that clause, the choice between revisiting everything and revisiting nothing gets made by whoever complains loudest in the room that week.
A bad mood after a rough gig is not new information, and neither is one member's second thoughts a week later. When someone wants to reopen, they name which assumption changed; if none did, the log entry stands and the band moves on to the next thing.
Fill-in: Decision log
Decision: ________
Method: ________
Decider: ________
Date: ________
Review if: ________
Putting it into practice
Adopt a written decision rule for money and booking this week.
FAQ
When should a band use consensus vs. majority vote vs. leader-decides?
Use consensus for membership, major money, and direction changes; majority for medium choices with clear options; leader-with-input for operations and time-sensitive calls; delegated for role-level details. Matching style to stakes is the whole point of this framework.
How do we stop reopening the same decision every rehearsal?
Write the decision, the style used, and a review date. Agree that reopening requires new facts or a consensus to revisit—not whoever complains loudest in the group chat. Commitment after disagreement is a cultural skill, not rudeness.
Who should document decisions and where should they live?
Pick one owner (often the leader or admin) and one place everyone can find: shared doc, ops folder, or band workspace. Unwritten "we decided that" is how three versions of the setlist appear on show day.
Which decisions always need full-band buy-in?
Adding or removing members, large financial commitments, genre/identity pivots, and any choice that permanently changes who shares risk. Operational items (rehearsal time tweaks, gear choices within role) should not require a summit. Pair this framework with written decision criteria so you evaluate options the same way twice.
