What to Decide Now, What to Defer, What to Ignore: The AI Action Matrix

Bottom line. The specific test that separates "decide now" from "defer" from "ignore" is whether a decision's cost of being wrong is bounded by your ability to reverse it. Decisions that must be made now are ones where waiting is more expensive than choosing wrong, because the window closes. Decisions that should be deferred are ones where the information improves quickly with time — deciding next quarter is strictly better than deciding this quarter. Decisions that should be ignored are ones where the question itself won't survive scrutiny — they're topics, not decisions, and spending leadership attention on them produces no value. This briefing is the three-column matrix, the specific sorting test, and a worked example showing how to apply it to a real leadership agenda.

L4.1 gave you the forecast. This briefing turns the forecast into action. Specifically: what belongs on your Q3 agenda, what belongs in Q4's review, and what belongs on the "stop bringing this up in meetings" list. Fifteen minutes to read; thirty minutes to run the matrix against your current AI topics; one clearer leadership agenda by end of day.

---

The three-column shape

Think of every AI-related question on your leadership team's current agenda. Each one belongs in exactly one of three columns:

Decide now. Requires a decision in this quarter. The window for deciding well is shorter than the window before the next opportunity. Deferring has a real cost (missed opportunity, accumulated debt, competitive positioning loss).

Defer. Requires a decision eventually but not yet. The quality of the decision improves meaningfully with another quarter of information. Deferring has a small cost (opportunity cost) that's outweighed by the information gain.

Ignore. Does not require a decision from your leadership team. Either (a) the question is a topic disguised as a decision, (b) the decision belongs at a different level of the organisation, or (c) the decision is premature by a longer time horizon than "defer." Spending leadership attention on these drains the capacity for the other two columns.

Three columns. Every AI topic you're tracking belongs in exactly one of them. The goal of this briefing is to make the sorting test explicit so you can apply it consistently.

---

The sorting test

For any AI topic on your agenda, ask four questions in order:

Q1: If we decide this next quarter instead of this quarter, how much worse is the decision?

If the answer is "significantly worse" — a missed competitive window, an expiring opportunity, a compounding cost of delay — the topic belongs in Decide now. If the answer is "about the same" or "probably better," continue.

Q2: If we decide this two quarters from now instead of next quarter, how much better is the information we'll have?

If the answer is "meaningfully better" — a capability will have stabilised, a regulatory decision will have landed, a competitor will have moved — the topic belongs in Defer. If the answer is "no meaningful new information," continue.

Q3: Does this require a decision from our leadership team specifically, or could someone below us decide?

If the answer is "someone below us could decide" — the platform team lead, the head of product, a department head — the topic should be delegated, not held at the leadership level. Put it on the "delegated" list, not the leadership agenda. Effectively, for your agenda, it's in Ignore.

Q4: Is this a topic or a decision?

If the answer is "this is a topic that people want to discuss but there's no specific decision attached" — like "AI and ethics," "the future of work," "AGI readiness" — the topic belongs in Ignore. Topics can be interesting; topics without decisions waste meeting time.

Four questions, three destinations. Run each of your agenda items through them in order. Items that survive all four questions go in Decide now; items that bail out at Q2 go in Defer; items that bail out at Q3 or Q4 go in Ignore.

---

What belongs in each column, concretely

Let me populate each column with the kinds of AI topics that typically sit there in a 2026 leadership agenda. These are patterns; your specific items may vary, but the shape should be recognisable.

Decide now (this quarter)

Topics where waiting is more expensive than choosing wrong:

• Your AI org pattern (L2.1). If you haven't picked one yet, the cost of delay is that every AI feature you ship is built without shared infrastructure and every engineering team reinvents the wheel. A wrong pattern is recoverable in a quarter; no pattern compounds indefinitely. Decide now.
• Your named AI incident commander (L3.4). If you don't have one when an incident hits, the first six hours are wasted on "who's in charge?" conversations. A wrong commander is replaceable mid-incident (bad but not fatal); no commander at incident time is catastrophic. Decide now.
• Your vendor DPA negotiation strategy (L3.3). New enterprise contracts are flowing. Each one signs under your current DPA terms until you change them. Every month of delay is another quarter of contracts signed under inadequate terms. Decide now.
• Your Q3-Q4 2026 AI budget envelope (L3.1). Fiscal planning won't wait. The range can be wide; the commitment to a range cannot be postponed. Decide now.
• Your top 3-5 AI investment bets for the next 6 months. Not "what are we doing with AI" generally — what are the specific projects that will consume most of the AI engineering capacity this half. Delay means engineering chooses on their own authority, which is usually fine for individual features and terrible for portfolio allocation. Decide now.
• Whether to hire an external platform team lead (L2.2, L2.3). The hiring process takes 3-5 months at senior level. Waiting a quarter means the hire lands in Q1 2027 instead of Q4 2026 — a full quarter of platform-less shipping. Decide now.
• The language in new customer contracts about AI data handling. Sales is closing deals; legal is reviewing each one individually; inconsistencies accumulate. Standardise now or pay for it in contract-review time for the next year.
• Your position on high-risk AI categories (employment decisions, healthcare recommendations, etc. — see L3.2). If any of your features might cross into high-risk territory, the compliance work is expensive. Starting in Q3 and finishing in Q1 is feasible; starting in Q4 and finishing in Q2 is scrambling.

Most leadership teams have 5-8 items in this column on any given quarter. If you have 20, you've mis-sorted and some of them belong in Defer. If you have 2, you're either very well-organised or you're missing real decisions.

Defer (next quarter or later)

Topics where the information improves meaningfully with time:

• Commitment to specific 2027 capabilities (L4.1's forecast). The five shifts are likely but not certain; committing roadmap to them before Q1 2027 is premature. Scope discovery for the likely shifts now, but don't commit engineering until the capability has stabilised. Defer the commitment, not the discovery.
• Your position on emerging AI frameworks and tooling. Every quarter a new agent framework, vector database, or observability tool gets hyped. Most of them are not worth adopting. Wait a quarter; the ones that survive become clearer. Defer adoption.
• Replacement of your primary model provider. Your current provider is working. The grass may be greener elsewhere, but the migration cost is real and the information about the alternative improves as you get more data on your own workloads. Defer unless a specific triggering event (price increase, regulatory issue, quality regression) forces the hand.
• Building your own in-house AI platform from scratch. Almost never the right call in 2026. The question of whether you should do it improves dramatically with another 6-12 months of information about what exists in the market. Defer; re-examine when you have specific evidence the existing options don't fit.
• Pricing changes tied to AI features (Course 3 P5.1). Unless you have a specific pricing problem right now (margin erosion, competitive pressure), the pricing question benefits from more data about your feature's actual usage. Defer until you have 2-3 quarters of production usage data.
• Long-term AI workforce planning (the "how many engineers do we need in 2028" question). Plan the next 2 quarters concretely; treat anything beyond that as aspirational. Defer concrete commitments; plan ranges.
• Fine-tuning strategy for your models. Most teams should not fine-tune (Course 2 B6.2). The question of whether you should fine-tune benefits from waiting to see if prompting and retrieval cover the need. Defer until you have a specific failure that prompting and retrieval can't address.
• Specific agent-based features (Course 2 Module B4). Reliability is improving but still uneven. The question of which agent features to ship gets easier to answer with another quarter of data. Defer build; start discovery.

Most leadership teams have 6-12 items in this column. The defer list should be longer than the decide-now list, because most strategic questions benefit from more information.

Ignore (not your level, or not a real decision)

Topics that drain leadership attention without producing value:

• "Is AGI coming by 2027?" — this is a topic, not a decision. There's no leadership action that depends on the answer. Ignore.
• "Which frontier lab is 'best'?" — not your decision, and the answer changes every quarter. Track at the platform team level; let them swap as appropriate. Ignore at leadership level.
• "Should we have an AI ethics committee?" — see L2.1's "AI Council" anti-pattern. Either operationalise governance through named owners (L3.2), or don't. Committees without decisions are theatre. Ignore as a standalone question; fold into the org pattern conversation.
• "What should we do about AGI risk?" — not actionable at mid-market business scale. Track; don't plan. Ignore.
• "Which AI programming assistant should our engineers use?" — this is a tooling decision for engineering leadership, not strategic leadership. Delegate and ignore at the exec level.
• "Are we behind on AI?" — this is anxiety, not a question. Reframe as specific decisions (do we need to hire, do we need to change our pricing, do we need to reposition) and those land in Decide now or Defer. The meta-question itself is unproductive. Ignore.
• "Should we build our own LLM?" — virtually never the right call below frontier-lab scale. If someone keeps bringing it up, the answer is no. Ignore the recurring question.
• Philosophical debates about AI's societal impact. Real questions for real philosophers and policy thinkers. Not decisions your leadership team should spend its quarterly review time on. Ignore.

Most leadership teams have 3-5 recurring items in this column that absorb meeting time without producing value. The single biggest productivity gain from this matrix is explicitly naming these and declaring them off-limits for leadership discussion.

---

A worked 2026 example: sorting a real leadership agenda

Let me walk through a realistic leadership-team agenda with AI items, and apply the matrix.

The setup: a 450-person B2B SaaS, Pattern 2 org, mid-market. Chief of Staff sends around the pre-read for the next leadership meeting. Twelve AI-related items are on the list. Run them through the matrix.

Sorted totals: 5 decide-now, 4 defer, 3 ignore.

What changes in the next meeting: the 5 decide-now items get 80% of the discussion time. The 4 defer items get brief status checks (any change in signal? no? move on). The 3 ignore items are explicitly named as off-limits and the chief of staff is asked to stop including them in future agendas.

Before the matrix: the meeting probably spent 10-20 minutes on each item, ran over, and made no actual decisions on the decide-now items because time got burned on the ignore items. This is the default pattern at most leadership teams in 2026 and it is what the matrix prevents.

After the matrix: the meeting spends 12 minutes per decide-now item (1 hour total), 5 minutes per defer item (20 minutes total), 0 minutes per ignore item. Meeting ends in 80 minutes with five decisions made. Compare to the counterfactual of 2 hours with zero decisions.

This is what the matrix saves — roughly a meeting's worth of time per week, and five decisions that would otherwise slip to the next cycle. Across a quarter, it's several real decisions made earlier and a lot less executive meeting fatigue.

---

The 90/10 rule for leadership attention

One last principle: 90% of your AI leadership attention should go to Decide now items; 10% should go to Defer items. Zero percent should go to Ignore items.

The pattern is inverted at most companies. Leadership spends 40% of its AI attention on Ignore items (AGI, philosophical debates, "are we behind" anxiety), 30% on Defer items (speculating about future capabilities), and only 30% on Decide now items. This is why the decisions that actually matter for the quarter feel like they're always slipping.

The fix is simple: name the three columns explicitly on your agenda. Every AI item is labeled. Ignore items are explicitly called out as "will not be discussed today." Defer items get 2-3 minutes each. Decide now items get the remaining 90% of the time.

The cultural shift: leaders who try this once usually experience significant discomfort, because some of their peers believe the Ignore items are important. The discomfort is real and temporary. Two meetings later, the new rhythm feels natural, and the team is making more decisions per meeting than before. Most leadership team productivity problems in 2026 are agenda-sorting problems, not substance problems, and the matrix is the cheapest available fix.

---

The failure mode: "everything is urgent"

The specific failure mode that breaks the matrix: treating every AI topic as urgent ("this is all moving so fast, we have to decide everything now"). Leaders who default to this fill their decide-now column with 15-20 items, none of which get adequate attention, and end up making rushed decisions on all of them.

The pattern is driven by anxiety, not by strategy. It comes from leaders who feel behind on AI, who worry about missing something, and who translate that worry into a bloated agenda. The cost: every decision gets 5 minutes of consideration instead of the 15-20 it needs, quality drops, and several decisions turn out wrong.

The defence: explicitly cap the decide-now column at 5-8 items per quarter. If you have more than that, you have a sorting error — something in the cap is actually deferrable or ignorable. Force-sort the list down to the real cap and address the rest in future quarters or at lower organisational levels.

The test: if asked "which of these five items is the most important?", a senior leader should be able to answer in 10 seconds. If the answer is "they're all equally important," the list is too long and the sorting hasn't been done. Rank; then commit to the top.

---

What to decide on Monday

• Print the three-column matrix and apply it to your current AI leadership agenda. 30 minutes with your chief of staff. Output: every item sorted into exactly one column.
• Cap the decide-now column at 5-8 items this quarter. If you have more, force-sort until the list fits. The excess items move to Defer or Ignore.
• Name the Ignore items explicitly to your team and ban them from meeting agendas. The cultural friction of this move is temporary; the productivity gain is permanent.
• Give the decide-now items 90% of your AI meeting time, the defer items 10%, the ignore items 0%.
• Revisit the matrix quarterly. Items migrate: Decide now items become decided (yay), Defer items become Decide now or Ignore (promote or drop), Ignore items occasionally become relevant (rare but possible).
• When a new AI topic surfaces, sort it into a column immediately using the four questions from this briefing. Don't let it float unsorted.
• Stop treating every AI item as urgent. Anxiety is a bad sorting heuristic.

Next briefing, L4.3, is the closing post of Course 4 and the entire AI Zero to Hero portfolio. A short reading list and two habits that keep you current in ten minutes a week — calibrated for senior leaders who have Course 4's mental models in place and need a durable way to keep them sharp without drowning in AI news.

---

Course navigation

📚 AI for Leaders · Course Home — 15 briefings, four modules.

---

Cover photo via Unsplash. This post is part of the AI for Leaders series.