There are weeks when a team is extremely busy yet does not feel that it is moving forward. Calendars are full, groups send regular updates, many tasks are completed, but three important matters remain unchanged: whether to pursue a large customer, whether to change the way a declining segment is served, and whether to allocate capacity to a new product or keep repairing the old one. When everything is called a priority, a meeting tends to become a place for exchanging information rather than making choices.
The issue is not only time-management skill. Behind a long task list there is often a list of decisions that nobody has named. Each unclear decision generates side work: asking for more data, meeting to ask again, remaking a presentation, waiting for a busy person to approve, or continuing with an old assumption. Building a decision portfolio does not make the organisation less busy immediately. It helps the team see which matters genuinely require a choice, when that choice must happen, and which work has value only after the choice is made.
See work through the question that must be answered
A task usually begins with a verb: survey, analyse, prepare, contact, implement. A manager should add one question: which choice will the result of this work help us make? If the answer cannot be stated, the work may still be useful, but it should not yet take a high-priority place. A marketing team, for example, may be asked to “research campaign feedback.” A clearer decision question is: “Over the next two weeks, will we retain the budget for this channel, adjust the message, or stop the experiment?” Once that question is explicit, the team knows which feedback to gather, when the evidence is sufficient, and who must join the conversation.
A decision portfolio is not a long strategic plan. It can be a table used in a weekly operating meeting, containing only choices that change resource allocation, customer commitments, the level of risk, or a team’s direction. The important discipline is not to put every task in it. A repeat activity with a clear process should run through its normal rhythm; a new, hard-to-reverse, or multi-party decision deserves shared visibility.
| Required field | Clarifying question | Example |
|---|---|---|
| Decision | What exactly must be chosen, in one short sentence? | Should same-day delivery expand into a new district? |
| Timing | If we do not choose by which date, what is affected? | Decide before signing next month’s warehouse lease. |
| Accountable owner | Who makes the final choice; who only advises? | Operations director decides; finance and commercial teams advise. |
| Minimum evidence | What must be known so the choice is not made on feeling alone? | Area demand, delivery capacity, cost, and service level. |
| Consequence of delay | Which work is waiting for this decision? | Hiring, route changes, and commitments to a partner. |
Separate a decision to make from a question to keep learning about
A common error is to force a team to decide too early simply because an item appears in the table. Some issues do not yet have enough evidence, and the best choice now is a way to learn more within a clear time limit. A company may not need to decide on entering a new market before it knows repeat demand, acquisition cost, and service capacity. It can, however, decide to run a small four-week test, specify stop criteria, and name the person who will consolidate the results. The choice “do not decide on the market yet, but decide how to test the assumption” is still a responsible decision.
Conversely, much work is called “further research” when it is really avoidance of a difficult choice. Common signs are that the same question returns across many meetings, additional data do not change the options, or everyone is waiting for an authority figure who has not been asked to choose anything specific. In that case, the facilitator should present two or three options together with their conditions instead of continuing to request a generic report.
Example: product-portfolio priorities
A company has five proposed product improvements and every group says its proposal is urgent. Instead of asking teams to make more slides, the director builds a portfolio of three decisions: retain or stop two low-usage features; select one segment for a new-service trial; and allocate engineering capacity to defect repair or partner integration. For each item, the team agrees the decision owner, decision date, minimum evidence, and work that will wait for the result. The next meeting no longer moves through every proposal equally. It focuses on the three choices with the greatest impact, while the remaining work is ordered by the choices made.
Design meetings around decisions that are waiting
An effective operating meeting does not need to begin with an update from every function. Send background information beforehand; in the meeting, move through the decisions that are due. Each item should begin with three points: what the choice is, what the available evidence says, and what the accountable person needs to decide today. Gaps in evidence should become a specific check with an owner and a return date, not an open-ended note to “research more.”
Decision rights also need protection. If everyone can veto but nobody is accountable for closing, the portfolio merely exposes the deadlock. The decision-maker should know which input is advice, which is a risk warning, and when the matter needs escalation. A participant who disagrees should still be able to record the assumption or condition to be tested later; that is better than reopening the same debate after work has begun.
Measure quality through learning speed and clarity of commitment
A decision portfolio should not be judged by the number of items closed. A fast decision based on weak evidence can create many revision loops later. Better signs are that relevant people can restate the choice and its rationale, follow-on work has clear owners, and when results differ from expectations, the team knows which assumption to revisit. After several weeks, the team should remove items that no longer need attention, add new decisions, and check whether any decision is stuck because authority or data are not fit for purpose.
When everything is important, the answer is not to push people to run faster. Help them see which choices genuinely govern the other work. A simple decision portfolio provides a shared language for that: what must we choose, who chooses, on what basis, and what happens after the choice is made?
