Bring an Existing Client Into Annual Planning With Evidence

Annual planning starts before a calendar invitation appears. A client sponsor hears unfinished issues in operating reviews, sees different priorities between leaders, and needs help turning scattered signals into a decision conversation. A client partner brings order without turning early discussion into a sales pitch. The useful result is a clear choice, visible evidence, and named questions still needing work.

Start with the sponsor’s decision calendar. Ask when leadership begins next year discussions, when an early finance view goes forward, and when each executive needs material. Then narrow the conversation. Ask, “Which choice needs a working view before your October leadership meeting?” Record a decision owner, people whose input matters, target date, and material leaders expect. Those details turn a broad planning request into a conversation with a purpose.

Listen for a choice hidden inside a broad concern. A sponsor might mention service consistency, growth, efficiency, customer experience, or risk. Each phrase covers different work. Service consistency, for example, might concern handoff steps, local process ownership, or a shared service standard. Ask which unresolved choice slows progress today. Ask whose work changes after leaders choose a direction. Keep the sponsor’s language in notes. Do not rename a concern as a project before leaders describe a decision.

Separate observations from interpretations. “Twenty six people completed agreed training by August 15” records activity. “Training solved adoption” offers an interpretation beyond a completion record. Put a source beside every observation. For a reported adoption figure, name a report, a person who confirmed access, and report dates. For a sponsor statement, label notes as a sponsor statement until a source arrives. This approach lets leaders test whether an item belongs in planning.

Open questions need equal care. A missing answer does not show poor preparation. Often, a missing answer points directly toward leadership work. State what a team knows, what nobody has examined, and why a missing answer affects a choice. Write, “Operations leaders agreed on a shared intake process. Local groups use different handoff steps. Leadership has not chosen whether common steps belong in next year planning.” This wording keeps uncertainty visible and avoids blame.

Hold a short sponsor discussion before building an agenda. Say, “I want our discussion to focus on choices your leadership group faces. Which decision needs a clearer view before annual planning begins?” Pause after asking. A sponsor often needs time to separate an urgent request from a decision leadership owns. Follow with, “Who needs input before a group meets, and what evidence would make a review worth their time?” Record roles and names rather than personal views.

Consider a fictional planning call. Sponsor Morgan says, “Our leadership meeting is six weeks away, yet priorities for next year are still open.” Client partner Inez replies, “Let us identify decisions leadership expects to make. I will bring material from current work and questions awaiting a source.” Morgan says leadership needs to decide whether service standardization deserves a planned review. Inez asks, “Who needs a point of view before a meeting, and what evidence would help them judge a review?” Morgan names an operations lead and a finance partner.

Inez sends Morgan a draft agenda with one purpose per section. The opening names a decision: whether leadership wants a defined review of service standardization. Next comes available material: agreed service measures, training completion records, and operating review notes. A final section identifies gaps. No effort estimate exists, and local process differences lack a shared inventory. Morgan reads a draft and notices finance has no contact named. Inez adds a person before invitations leave her desk. Small checks before a meeting prevent vague requests during a meeting.

During a fictional session, an operations lead says, “Our teams know where service varies. We need to know whether variation affects customers enough to matter.” Inez does not answer from memory. She asks, “Which customer outcome would your group use for a judgment, and where do records sit?” A finance partner adds, “I need an effort range before I support a study.” Inez records each request separately. Customer impact and study effort inform different decisions. One broad follow up would leave both leaders waiting for material they did not request.

Build an evidence packet for reading rather than persuasion. Give every page a single purpose. One page records verified observations and sources. Another page states unresolved questions, likely source owners, and dates for checking each item. Keep source name, date, scope, and limits visible. Remove internal shorthand unfamiliar to client leaders. When an observation applies only within one business unit, name the scope beside an observation. Early visibility lets a leader ask for a different source or move an item later in planning.

In the fictional situation, Inez writes, “August operating review notes describe different handoff steps in three local groups.” She labels this sentence sponsor supplied and names the meeting notes. On another line, she writes, “No shared inventory of handoff steps exists.” An operations analyst owns an inventory check. Leaders see one sentence as a report of available material and another as work awaiting completion. Neither sentence pretends to answer more than a source supports.

Keep sensitive material under sponsor control. Before sharing a draft beyond a small preparation group, ask Morgan who should receive operational notes and whether any local examples need removal. A client partner does not need a complicated approval process for every page. A direct question protects a sponsor from surprise. In the fictional example, Morgan asks Inez to remove local team names from a preparation copy and retain source names in a private working record. Inez adjusts both copies before sending an agenda.

A discussion about further help deserves permission. Inez sees a possible role for a service mapping specialist, yet Morgan prefers internal exploration before an introduction. Inez says, “Our group has people who help teams map service work. Would an introduction support planning, or would you rather settle decision questions first?” Morgan chooses internal exploration. Inez respects a choice and offers the evidence packet for leadership. Sponsor control of pace supports a stronger working relationship.

After a session, send a record of agreements during a period promised at the meeting. In this fictional situation, Inez writes, “Morgan will confirm whether an operations lead wants local process examples before September 18. Finance partner Lee will state an effort range useful for a review by September 16. Inez will send the training completion record and open question page by September 12.” Every sentence names an owner, action, and date. Leave unapproved scope out of a recap. A recap records what people agreed to do, including an option Morgan declined.

Use Morgan’s fictional situation as a practice exercise. On a blank page, write, “Leadership must decide whether to fund a service standardization review.” Add an observation from a named source and an unresolved question with an owner. Draft an opening question for Morgan. Ask an account lead to identify one claim needing a stronger source. Revise the page, send Morgan the September 12 packet, and place the September 18 source check on a calendar.