Help Executives Examine Capital Allocation With Shared Criteria

Capital allocation grows difficult when every business leader presents a reasonable investment request. A consulting partner helps an executive group expose criteria behind competing requests before discussion turns personal. Start with a decision horizon, the amount leaders expect to examine, and commitments already shaping a choice. Then ask how leaders weigh customer need, capacity, risk, and strategic direction. The partner supports a fair process. Executives keep responsibility for priorities and allocation choices.

Begin with a purpose sentence. “We need to discuss investments” offers no shared destination. Try, “Jun needs an executive recommendation by September 30 on which proposals move into next year planning.” A purpose sentence names a decision owner, date, and scope. Send words before a first workshop. Ask participants whether a sentence reflects one real choice or joins unrelated decisions. When proposals belong to different time horizons, separate them. A near term repair request and a multi year expansion request need different material.

Ask leaders to describe a request before asking them to defend one. Use questions such as, “Which decision does your request support?” “What changes if leaders defer a request?” “Which assumptions shape your estimate?” and “Which person owns evidence?” A sponsor might begin with a broad statement about customer demand. Ask which records or observations inform a statement, whose perspective a record represents, and which dates apply. These questions do not settle a request. They show a group which parts need evidence before comparison.

Agree on criteria before sponsors prepare cases. Without shared criteria, each sponsor selects favorable measures and describes a comparison as objective. In a workshop, ask executives to name criteria they expect across every proposal. Customer need, operational capacity, strategic fit, timing, financial considerations, and risk exposure often appear in discussion. Do not assume shared meanings. Ask each executive for a working definition. Record agreement and places where leaders need a later definition.

Customer need might mean a documented service issue for one executive and a future market concern for another. Operational capacity might mean staff availability for one leader and facility readiness for another. A partner does not choose a definition. A partner asks, “Which meaning should sponsors address in a request, and what material would show a response?” Leaders establish a shared frame. Sponsors receive a clearer assignment, and an executive group avoids arguing over different meanings during final review.

Treat evidence and judgment as distinct parts of a proposal. A dated operating report, signed decision record, or documented process observation offers evidence. A statement such as “this project deserves priority” expresses judgment. Both belong in an executive discussion. Trouble starts when judgment arrives without clear evidence or evidence arrives as a decision. Ask every sponsor to label sources, dates, scope, and gaps. Ask leaders which judgment they need to make after reading material.

Consider a fictional executive session. CFO Jun says, “We have requests for a new facility, a service platform, and a product launch. I need a recommendation by month end.” Partner Marisol asks, “What would make a recommendation credible to an executive group?” Jun says leaders need to compare investments using a shared horizon and assumptions. Marisol replies, “Let us agree criteria before sponsors bring cases. Finance will define a data format, operations will provide capacity facts, and every sponsor will state a decision supported by a request.” Jun asks Marisol to facilitate a criteria workshop before an investment review.

Marisol opens a fictional workshop with a blank comparison sheet. Across a top row, she writes customer need, capacity, timing, risk exposure, strategic fit, and financial considerations. She asks Jun, “Which columns need evidence from every sponsor, and which columns invite executive judgment?” Jun says every sponsor should provide available source material, while executives decide relative weight. An operations leader asks for a separate readiness column. Marisol asks whether readiness belongs within capacity or needs a distinct definition. Leaders agree readiness refers to conditions needed before work begins. The sheet reflects words leaders chose.

Source material needs clear expectations. A missing figure should stay missing until an authorized owner supplies one. In a fictional example, a facility sponsor has a preliminary space assessment but no agreed timing. Marisol writes “timing source pending” instead of estimating a date. A service platform sponsor has dated customer support notes, yet scope lacks a shared view. She records scope as unresolved. Plain gaps invite focused questions.

Ask sponsors to show relationships between requests. A proposal might depend on another proposal, compete for an operations team, or need a decision first. In a fictional working session, a product launch sponsor says launch preparation needs capacity from a proposed service platform. Marisol asks, “Which preparation task depends on platform work, who owns a decision, and when does a reply matter?” The sponsor names a workflow design task due October 10. Marisol records a dependency rather than assuming approval for either proposal. Leaders see a sequence question beside individual requests.

Test assumptions without turning a review into cross examination. Marisol asks a fictional facility sponsor, “What happens between September 30 and your requested decision date, and who confirmed this timing?” Nia identifies an internal occupancy note with an October 15 planning target. No executive decision date exists. Marisol records both points. Jun asks whether leadership needs a decision before October 15 or only a fuller proposal.

Prepare a review agenda around decisions rather than presentations. Give each sponsor a fixed period to explain a request, source material, assumptions, and dependencies. Reserve time for executive questions. Jun states a decision sequence at an opening: clarify criteria, test evidence, identify requests needing more work, then choose proposals moving forward. A sequence gives each speaker a purpose. Avoid asking sponsors to perform a sales presentation for a group responsible for difficult tradeoffs.

During a fictional review, an executive asks why a service platform request should advance before a facility request. Marisol does not answer for either sponsor. She says, “Which agreed criterion leads you toward a different order, and what source material would change your view?” The executive points to timing and customer need. The facility sponsor supplies a dated occupancy constraint from an internal record. The service sponsor identifies an unanswered scope question. Jun asks both sponsors for a one page update by September 22, then delays ordering until a next session. A pause protects decision quality when evidence differs.

Close with a decision record rather than a vague promise. For every proposal, write current status, material needed, owner, and next decision date. In a fictional record, Marisol writes, “Facility sponsor Nia will provide an authorized timing source by September 18. Service sponsor Theo will confirm scope with a service owner by September 18. Jun will set an executive review for September 24 after both updates arrive.” Do not add assumptions during recap. A record should match words executives used in a room.

Use fictional facility and service platform requests. Draw a comparison sheet using criteria leaders chose. Put a source or clear gap beside each entry. Ask a peer to question the facility request as an executive would. Mark the workflow dependency, ask Nia for the September 18 timing source, then send Jun an updated sheet before the September 24 review.