Prepare a Sponsor for Board Questions on Technology Spend
Help a sponsor explain a decision without giving them a scripted promise.
A board question about technology spend is rarely a request for a seller speech. A sponsor needs language for leaders who were absent from early conversations and who must understand the decision in front of them. Good preparation narrows a request, separates evidence from assumptions, and leaves internal judgment with the sponsor.
Start with the decision. Ask, “What are board members being asked to approve, release, or review?” Board awareness, permission for a limited evaluation, and approval of a purchase are different requests. A sponsor who seeks awareness does not need material for a final recommendation. Write the answer at the top of a preparation page. Every later statement should support this single request.
Ask which question has the most weight. A board member might ask why work deserves attention after earlier spending, why internal improvement is not enough, who owns delivery, or what evidence exists so far. Do not assume each concern matters equally. Ask a sponsor, “Which question would make support pause?” Listen for the tension behind the first answer. “We spent heavily last year” might refer to credibility, unfinished work, or a competing priority rather than price alone.
Keep sources visible. One part of a preparation page contains buyer supplied information. Another contains approved product information or material from a demonstration. A third contains open questions. Use direct labels such as “Priya said,” “approved material,” and “needs confirmation.” This simple separation helps a sponsor avoid presenting an assumption as evidence. A seller should not add a financial figure, outcome claim, delivery estimate, or risk estimate without an authorized source.
Write current work in customer wording. “Department leads receive updates from several sources before monthly review” is clear when a sponsor gave this account. “Reporting inefficiency” hides useful detail. Ask what happens today, who gathers material, who relies on an update, and what event prompted review. These questions produce a factual explanation without turning normal operating work into a sales problem.
Treat options fairly. A sponsor might consider keeping current practice, changing an internal process, or reviewing an external option. Do not write a case against any option unless a customer supplied relevant evidence. A board deserves an honest view of what evaluation is for. “The team is comparing internal process changes with an external approach” is stronger than a sentence claiming one path already won.
Here is a fictional practice situation. Priya is a CIO preparing for an October 14 board discussion. Her organization approved several technology projects during the prior year. A program sponsor has asked whether a new operating workflow deserves further review. Priya expects a board member to ask, “Why should we spend attention here before last year’s work settles?” She wants a concise request for continued evaluation, not a promise from a seller.
An account executive asks Priya what decision belongs on the October agenda. Priya says no purchase approval is planned. She wants board awareness and permission for her team to continue a limited evaluation after security and operations provide input. The account executive records “October 14 board awareness discussion” and “possible next step is limited evaluation.” Those phrases define scope. No later note should imply a committed purchase.
Priya describes a work pattern. Department leads send updates from different sources. During a monthly meeting, leaders reconcile differences before deciding what needs attention. An operations leader prepares material for this meeting. Priya says her team has seen an overview of an external approach. Security and operations have not finished their input. The account executive writes each point as customer supplied information. No line predicts lower cost, faster delivery, or a chosen outcome.
Together, Priya and the account executive create a one page input sheet. The decision is board awareness of a limited evaluation. The operating issue is conflicting updates before monthly review. The reason for review is a leadership concern Priya reported. Current options are internal process changes and an external approach. Available evidence is Priya’s account of current work plus approved material already shared. Security input, operations input, and a delivery owner are open questions. Priya owns internal coordination. The next decision date is October 14.
Ask Priya what would make a board discussion useful. She replies, “I want permission to continue a limited evaluation, with clear questions for security and operations.” Her answer sets the proposed request. A full purchasing case would create noise because no such decision is on the agenda. The preparation page should help Priya say why continued work deserves attention and what her team intends to learn next.
Practice an opening in the sponsor’s own voice. Priya might say, “I am asking for awareness of a limited evaluation. Our leaders spend monthly meeting time reconciling different operational updates. We are reviewing internal process changes and an external approach. Before a later decision request, security and operations need to assess open questions.” Every clause follows information Priya supplied. She should remove or revise any wording which does not fit her view.
Prepare for an interruption without inventing an answer. A board member asks, “Why not improve your existing process first?” Priya responds, “Internal improvement is one option under review. We also want to understand whether an external approach fits our security and operating needs. We have not chosen a path.” This response respects the question. The response also prevents a seller from turning an early evaluation into a promise.
Another board member asks who would own delivery if a later decision favored an external approach. Priya does not need a name before her team has reached one. She says, “Delivery ownership is an open item. Our program sponsor will gather input from operations during evaluation, then we will bring back a proposed owner if work proceeds.” The account executive should not fill this gap with an internal title or a delivery timetable.
Review every sentence before sharing a draft. Ask Priya, “Is this statement ready for board material, or is this a working note?” Keep sensitive wording, early assumptions, and unresolved items outside her prepared remarks unless she chooses otherwise. Then ask the account executive to point to a source for each factual statement. If a source is unclear, change the sentence into a customer question or remove the claim.
Use a fictional roleplay to test the page. Priya provides three facts: recurring reconciliation work, an October 14 awareness discussion, and pending security input. A second person acts as account executive. A third person acts as a board member. Give the account executive eight minutes to prepare Priya’s page. The board member interrupts twice, first about prior spending and then about delivery ownership. Priya answers only from her supplied facts or states an open question.
After practice, cross out each unsupported line. Replace “This project will improve leadership decisions” with “Which leadership decision becomes harder when updates conflict?” Let Priya answer in her own words and record her answer under the operating issue. Schedule a fictional October 7 review with the program sponsor. At this review, Priya checks whether security input arrived and decides whether her October 14 request still fits the board agenda.
Practice these next
Move an overlap objection from a feature debate to a discussion of the current workflow.
Replace vague stakeholder lists with evidence about roles, influence, and open questions.
Turn broad AI concern into specific governance questions for buyer evaluation.
Find the planning path when a buyer cannot spend in the current cycle.
Coordinate legal review without losing sight of the business decision and timeline.
Learn whether poor data blocks a project, signals another issue, or defines its purpose.