A Practical Decision Framework Survives the Next Committee

Two weeks of method, four months of travel

The pattern starts well. A divisional head at a retail bank wants to change how a savings product is priced, and the division runs the decision properly: a named owner, three costed options, a recommendation the team argues over and then backs. It takes two weeks. The framework they used, adopted after a leadership programme, did what it promised.

Then the decision left the division. The product committee asked for the options in its own template and reopened the margin assumption. The asset and liability committee reopened the deposit forecast. The executive committee received it as a noting item and sent it back as a question. Four months after the division had decided, the price changed, at a level close to the one first proposed. The framework had governed two weeks of a four-month decision, and the four months were where the time went.

Why the models stop at the team's edge

This is the ordinary shape of decision making in a large company, and it is the part a search for a practical decision framework for corporate leaders rarely reaches. Most of the familiar models were written for a single team: one room, one owner, one close. In a corporate, the decisions that matter most are rarely closed in one room. They are recommended at one level, reviewed at a second and ratified at a third, and each level holds a right the framework never mentioned.

What the committee assumes its job is

Committees reopen recommendations for a reason that is easy to miss. A paper arrives without saying which of three things the committee is being asked to do: decide, approve within a limit, or note. Without that sentence, a conscientious committee assumes the widest version of its role and decides again from the start. The members are not being obstructive. They are doing the job the paper left open to them.

Three things are usually missing from a recommendation as it leaves a team, and each one invites a full re-examination:

• the request, meaning whether the forum is deciding, approving within a limit, or noting a decision already inside delegated authority
• the settled ground, meaning which assumptions were tested at the level below and by whom, so the committee can challenge them rather than rebuild them
• the boundary, meaning which change in the forum's view would send the decision back down, and which would only be recorded as a condition

A committee that is not told what it is being asked will answer the largest question available to it. The four months in the bank were three committees answering the largest question, one after another, each starting from the beginning because the paper gave them no other place to start.

Writing for the receiving forum

A framework becomes practical in a corporate when the team uses it to produce something for the forum above, not only a decision for itself. In the engagements where this works, the decision record is written in the shape the next forum needs. It opens with the request in one line. It names the options the team rejected and what each would have cost. It states which assumptions came from which function, and which of them the committee members' own functions have already signed.

The rejected options matter more than they appear to. A committee that cannot see them will propose them again, and the team will spend a sitting defending a choice it made weeks earlier.

A committee that cannot see the rejected options will propose them again.

The template matters less than the conversation behind it. Before the record is written, the owner asks the chair or secretary of the receiving forum what a recommendation from this level must contain for the forum to act on it at one sitting. The answer is usually short and specific, and it is rarely what the team would have guessed.

Reading the delegated authority first

The second habit is to read the delegated authority before deciding anything. Many decisions travel upward because nobody checked whether they had to. In the bank, most of the price change sat inside a band the product committee had delegated to the division a year earlier. Only the move beyond the band needed the committee, and only the deposit forecast needed the asset and liability committee. A decision that knows where it lives can be split: the part inside the division's authority closes there, and only the remainder travels. The same principle inside a single team is set out in who decides what in a leadership team. A decision split along its delegated limits travels less far and carries less with it, which is most of what makes it fast.

The second run

The following pricing round went through the same committees with a different record. The division read the delegated band first, closed the change inside it on its own authority, and noted it upward. The part that moved the deposit forecast went to the asset and liability committee with a one-line request, the treasury assumption already signed by treasury, and the two rejected options costed. The committee challenged one assumption, attached a condition, and approved at one sitting. The whole cycle took five weeks.

Nothing about the committees had changed: the same members, the same calendar, the same appetite for scrutiny. What had changed was that the framework now reached the edge of the division and one step beyond it. The practical decision framework was the original one, with a final step that wrote the decision for the forum that would receive it.

Where the method stops working

The method has a limit worth naming. It shortens the path through committees that exist for a reason. It does not remove a committee whose remit has outlived its purpose, and it cannot rescue a decision whose owner was never clear at the level below. When a recommendation keeps returning from the same forum despite a clean record, the problem is usually the forum's remit rather than the paper, and that is a governance question for whoever set the delegated limits. Where the break sits inside the team rather than above it, choosing a framework by where decisions break is the better starting point.

Our work on this in large companies begins with a single decision followed end to end: from the team that first recommended it to the forum that finally ratified it, with the dates, the papers and the questions each level asked. One traced decision usually shows which forum reopened it and what that forum had not been told.

From there our consulting work inside the decision architecture pillar maps the delegated limits and writes the decision record with the forums that receive it, and our training programmes build the habit of writing for the next level up in the people who own recommendations. A practical decision framework for corporate leaders is one whose output the next committee can accept without deciding again.