Restart a Deal After a New CIO Arrives

A new CIO changes the context around an active technology decision. Earlier work still has value, yet the new leader did not choose the old process. They inherit projects, budgets, team relationships, and risks at once. A pause often reflects a need for orientation rather than a verdict on your proposal. Treat a pause as a genuine reset. Your job is to help the new leader understand the decision without asking them to adopt a history they did not create.

Prepare a short transition brief before you request time. Keep the document useful enough for an executive or sponsor to scan before a discussion. State the operating problem in buyer language. Record completed work, such as interviews, process review, or technical questions. Name unanswered questions. End with the decision awaiting direction. Leave out sales history, internal optimism, and every detail from prior meetings.

Separate facts from assumptions in the brief. Facts include named participants, dates of completed conversations, and issues raised during those conversations. Assumptions include expected timing, scope, or internal support. Label assumptions plainly. When a prior sponsor reports executive support, record who expressed support and when. Do not present support as permanent. This distinction helps a new CIO disagree with a prior view without feeling trapped by the record.

Consider a fictional practice situation. Malik, an account executive, spent six weeks with a technology operations group. The former CIO supported an effort to reduce delays in service requests. Two process sessions occurred, and the operations director planned a decision meeting for Thursday. On Monday, the company announces a new CIO, Elena. The director tells Malik, "Elena wants every major initiative under review." Malik does not ask the director to preserve Thursday's meeting or forward old notes without context.

Malik prepares a one page brief for the director to review. The opening states service request delays were the stated issue during process sessions on August 4 and August 18. A second paragraph records interviews with operations and support, a walkthrough of request intake, and an early discussion of security questions. The brief names two open items: ownership for exception requests and timing for a security review. The final line asks whether reducing request delay belongs among Elena's early priorities, should wait for portfolio review, or needs a different sponsor. The director edits wording before sharing any portion.

Request a priority conversation, not a product presentation. A useful opening is, "You are inheriting a full portfolio. Which technology outcomes are you being asked to stabilize or change first?" This question gives the CIO control over the agenda. Listen for words they use about their first ninety days. New leaders often focus on reliability, cost visibility, staff capacity, security posture, service quality, or another concern. Do not force a connection between your project and every priority named.

When the project connects, ask permission to explain the link in a few sentences. Use the buyer's own evidence. Malik might say, "The operations team described delays during exception routing. They asked us to examine a workflow change. Would a short review of their findings be useful while you set priorities?" Such wording does not claim the project solves a broad executive goal. The request asks whether existing work deserves attention within a new agenda.

When the project does not connect, accept the answer with care. Elena might say an unrelated platform consolidation has immediate focus. Ask what condition would make a future review timely. A direct answer often names a planning cycle, a leadership hire, or another project decision. Record the condition and date in your account notes. Ask the sponsor whether they want a short record of earlier work for later reference. Do not keep sending material without an agreed purpose.

A reset also tests sponsorship. A prior champion sometimes loses access, changes focus, or gains a new reporting line. Ask how decision ownership now works. Avoid assuming a title equals authority within the new organization. Say, "As Elena sets her team, who should help decide whether this work moves forward?" The answer often points to an operations leader, a transformation office, or a temporary steering group. Follow the buyer's stated route.

Bring questions which help a new CIO evaluate prior work. Ask what they need before considering an active initiative. Ask how they separate an urgent operating problem from a project waiting for planning. Ask whether a current initiative has a sponsor responsible for its outcome. Ask what evidence they value. These questions show where earlier work lacks substance. They also reveal an evaluation method without pressure for a commitment.

Do not treat silence as agreement. After a meeting, write a short recap using specific choices. If Elena asks for a later review after portfolio planning, state the timing she named. If she requests a different sponsor, state who will coordinate next contact. If she asks for more evidence, list only material she requested. Send the recap first to the contact who arranged the meeting when appropriate. Invite corrections before wider circulation. This process keeps the record accurate and avoids overstating a tentative response.

Handle earlier timelines with equal care. A former target date belonged to a prior decision structure. Do not repeat the old deadline as though nothing changed. Ask whether the date still matters and why. The reason might be a seasonal operating need, an existing planning window, or an informal expectation. If nobody confirms a reason, remove the date from your forecast. An honest view of uncertainty is more useful than an old deadline presented as fact.

Keep communication short between meetings. One clear question serves better than a stream of material. Malik might write, "You asked us to wait for portfolio review. Would an update during the week of October 12 fit your process, or should we wait for your team to contact us?" This note leaves room for a no. If the buyer asks you to wait, honor their request. Do not use other contacts to reopen the decision unless the buyer directs you there.

Practice with a fictional roleplay before a live reset. One person plays Elena. Another plays Malik. Elena opens with, "Every initiative is under review, and I have no room for a vendor presentation." Malik has sixty seconds to acknowledge the review, state the operating issue, name completed work, and ask which outcomes Elena must address first. A reviewer listens for old history stated as fact, a request for a decision, or language treating former support as Elena's commitment.

During a second round, Elena says the initiative should pause for two months. Malik asks what needs to be true for a later discussion, who owns follow up, and whether a transition brief would help. He does not bargain over the date. He then writes a four sentence recap from Elena's answers. Remove each assumption before reading the recap aloud.

For your next reset, draft the transition brief before contacting anyone. Ask the current sponsor to correct the problem statement and open items. Request a fifteen minute priority conversation. If the new CIO chooses a pause, enter their stated review point in your notes. On the agreed date, send one question tied to the condition Elena named and wait for her direction.