01
Comparisons of team decision frameworks set out what each one says about a single decision. The difference that decides whether a team keeps using one is what it costs to run, decision after decision, at the volume the team actually decides.
Istanbul — San Francisco
Notes — topic
22 notes
01
Comparisons of team decision frameworks set out what each one says about a single decision. The difference that decides whether a team keeps using one is what it costs to run, decision after decision, at the volume the team actually decides.
02
Corporate leaders adopt decision frameworks built for a single team. In a large company the delay lives above the team, in committees that decide again because no paper told them what they were being asked.
03
Leadership teams adopt decision frameworks by reputation, usually after an offsite. Decisions break at one of four points, and the framework that holds is assembled from rules for the breaks a team actually has.
04
Most leadership teams approve what their members could settle alone and leave the cross-functional calls to whoever holds the budget. Three short written lists put each decision back where its cost lands.
05
Assigning decision rights in a growing company is not a one-off design exercise. Each right fits one size of company, so it is written with a role, a limit, and the event that reopens it.
06
A RACI chart says who does the work and who answers for it. It says nothing about who chooses when two parts of that work collide. That gap is where decision rights begin, and where most programmes stall.
07
RAPID gives every decision a recommender, a decider and three supporting roles. The letters are easy to learn. The framework only works when it is applied to decision types, and when the agree role is kept for boundaries.
08
Consensus works when interests align and a holdout is cheap. Four decision shapes break both conditions, and a team can recognise them before the meeting starts.
09
The norm fails when commitment is demanded before the objection is answered. A written dissent, a stated definition of commitment and a review date give it terms that hold.
10
Most decision rights were never designed. They were inherited from whoever happened to own the first case, and a growing company inherits the wrong owner as often as the right one.
11
Consensus is not the problem. Running it as the decision rule instead of the check is. The method is three lines settled before the meeting, not a better meeting.
12
In fintech the two are named in one breath and handed one seat. One of them is answering a question of law and the other is quoting a price, and a single seat gets both of them wrong.
13
A bank can staff a payment product decision correctly and still get it wrong, because having an owner is not the same question as having the right one.
14
Every checkout roadmap item that removes friction to raise conversion is, from another desk, a change to the fraud-loss curve. Nobody assigned who wins.
15
A payment product touches product, risk, compliance, and technology. The decision belongs, by charter, to none of them.
16
A meeting that keeps not-quite-closing is not short of information. It is running on the wrong decision rule.
17
A decision can be final in the room and still unsettled everywhere the room cannot reach.
18
A strategy can be fully agreed and still decide nothing, because it names several good things without saying which one gives way when they collide.
19
Discipline does not keep a decision closed. A place to check it, and a rule for when it may return, does.
20
Teams do not reopen decisions because they lack discipline. They reopen them because nothing about the original decision was ever closed.
21
Reversible and irreversible decisions carry different risk. Most organisations run them through one process, and pay for it at both ends.
22
The important work is rarely the decision itself. It is the preparation that makes a decision clear enough to carry.