Build the function.
Prepare the person.
Hand it over.

An organization can become dependent on a consultant in surprisingly ordinary ways.

The consultant knows which spreadsheet is current. The consultant remembers why a deadline moved. The consultant can persuade two department heads to settle a disagreement. The consultant understands what the executive meant by a three-word note sent between meetings.

Each of those contributions can be useful. Taken together, they can also create a function that runs on one person’s memory and availability.

The expectation in this engagement was to build toward a different condition: a permanent owner able to understand the priorities, use the processes, maintain the relationships, and exercise judgment without having to reconstruct the entire operation.

That meant treating the eventual transition as part of the work from the beginning. What responsibilities needed a named owner? Which decisions belonged with executive leadership? What information would the successor need? What should be written down, and what would require direct exposure to the people and situations involved?

The work described here concerns strategy operations and enablement within the chief strategy office. It is an overview of the mandate and the principles behind it, with identifying and confidential details omitted.

For the broader commercial role, my companion article explains what a strategy lead does. This account focuses on the organizational work required to make strategy operate consistently and survive a leadership handoff.

Annual planning can create an impressive statement of intent while leaving the difficult operating questions unanswered.

Who is responsible for each priority? What has to happen first? What capacity is available? Which dependencies cross departments? Where does an executive need to make a decision before anyone can proceed?

My responsibilities included coordinating the planning and deployment process so that strategic priorities could become an executable plan. That required working with senior leaders and the people responsible for individual workstreams, establishing the sequence, and defining how progress would be reviewed throughout the year.

The important work begins when two sensible initiatives need the same people at the same time. A planning process has to expose that conflict early enough for leadership to make a choice. Otherwise the conflict gets passed down to teams that lack the authority to resolve it.

I think of the annual plan as a set of operating commitments with explicit assumptions. A priority needs an intended business outcome, an accountable owner, supporting participants, milestones, resource requirements, dependencies, and a review point. It also needs a route for changing the plan when the assumptions change.

Planning periods naturally concentrate pressure. The exact calendar varies by company. A process that depends on everyone remembering every exception during the busiest stretch of the year is already showing where documentation will matter.

Strategy enablement is the work of making strategic decisions usable across the organization.

The remit included leading a small team focused on planning, coordination, governance, and support for important initiatives. A centralized function can establish consistent methods and maintain a shared view of the work while business leaders retain responsibility for the outcomes in their areas.

That distinction matters. If every decision has to pass through the strategy office, the office becomes a bottleneck. If every team invents its own definitions, reporting habits, and escalation rules, executives struggle to compare progress or see dependencies.

The useful middle ground is enough shared structure to coordinate work, with clear authority left close to the people who understand it.

Team leadership belongs in that structure too. People need to understand their responsibilities, receive useful feedback, and develop the judgment to handle more of the work independently. The manager’s contribution should improve the team’s capacity to act, including when the manager is unavailable.

Part of the assignment involved the executive operating rhythm: the recurring meetings, preparation, materials, coordination, and follow-up through which leadership manages the business.

Agendas influence what gets attention. Pre-reading influences whether people arrive able to decide. Attendance influences whether the right expertise is present. Follow-up influences whether the decision becomes anything more than a sentence in meeting notes.

I was responsible for helping that rhythm stay focused on the priorities that needed executive attention, working across strategy, commercial leadership, and the CEO’s office.

A useful agenda distinguishes information from decisions. If a topic requires approval, the material should make the request, alternatives, implications, and unresolved questions clear. If it requires cross-functional coordination, the people who can resolve the dependency need to be involved.

Afterward, the record should show what was decided, who owns the next action, when it is due, and what needs to return to leadership. An unresolved issue needs an owner too.

The purpose is to reduce the amount of organizational memory the executive team has to carry around personally. Leaders should be able to concentrate on judgment because preparation and follow-through are dependable.

Another part of the role was acting as a trusted partner to strategy leadership and representing agreed priorities in day-to-day work.

That requires careful judgment about authority. You need to know what you can settle, what requires consultation, and what must go back to the executive sponsor. Representing someone’s priorities is a responsibility to preserve their meaning, including when the message is inconvenient or incomplete.

It also means anticipating what will be needed. A leadership discussion may depend on commercial analysis that has not yet been requested. A board deadline may require input from several teams. A decision may be waiting because two people each believe the other owns the next step.

The role connects those pieces before the gap becomes an executive emergency.

Discretion is essential. Strategy work can involve sensitive commercial information, organizational changes, competing interests, and conversations that should not travel beyond their intended audience. Trust grows when people see that information is handled carefully and that the person coordinating the work can remain steady under pressure.

The remit also included executive-sponsored projects, ranging from urgent requests to longer cross-functional initiatives.

These assignments require enough structure to move quickly without pretending the uncertainty has disappeared. Establish the question, define the scope, identify the sponsor, sequence the work, and make the next decision visible.

A time-sensitive request may need a short analysis with explicit limitations. A larger initiative may need workstreams, milestones, dependencies, and a more deliberate review cadence. The level of process should fit the consequences of the decision.

Financial and business fluency matter throughout. A spreadsheet should help explain the assumptions behind a recommendation. An executive presentation should make the decision understandable. Software is useful when it supports that reasoning, whether the work calls for analysis, coordination, or a concise narrative.

Managing several concurrent initiatives also means recognizing when urgency has exceeded capacity. Quietly accepting every request can create a plan nobody can deliver. A responsible operator makes the conflict visible while there is still time to adjust.

Initiative tracking was another core responsibility: maintaining a dependable view of where strategic work stood and what leadership needed to know.

An update should distinguish progress from activity. A team may have completed several tasks while the critical dependency remains unresolved. Another initiative may appear quiet because it is waiting for a decision that only the executive sponsor can make.

The reporting system needs consistent definitions, named update owners, reliable source information, and visible dates. “Current” should mean something readers can verify. A report refreshed weekly should not imply that every entry represents live operational data.

The most useful record makes the next action easier to identify. What changed? Why does it matter? What is blocked? Who needs to decide? What is the effect on the intended outcome or timeline?

This is also a handoff issue. If only the original consultant knows how to interpret the status report, the report is carrying less knowledge than it appears to carry.

The responsibilities extended to coordinating and developing executive and board materials, including presentations and written updates.

The challenge is to make complex work understandable without stripping out the uncertainty, risk, or context required to evaluate it.

A leadership narrative should explain what the organization is trying to accomplish, what has happened, what the evidence indicates, where the plan is under pressure, and which decisions are needed. Numbers should connect to their definitions and sources. Assumptions should be recognizable as assumptions.

Good preparation also requires coordination: securing the right inputs, reconciling inconsistent information, managing review, and making sure the final version is actually the final version.

The strategy office supports the quality of that work. Executive sponsors retain responsibility for their recommendations and approvals. Clear review responsibilities protect both the accuracy of the material and the people relying on it.

The role also called for practical use of AI in synthesis, planning, drafting, and the preparation of materials, along with reusable workflows for the broader team.

The important distinction is between an individual using a tool effectively and a team having a process it can repeat and evaluate.

For example, a workflow for synthesizing approved meeting notes needs more than a prompt. It needs a defined input, an output format, a way to check decisions against the source, an owner for review, and a place to store the approved result.

The same applies to planning support or executive drafting. A polished summary can omit a reservation that changes the meaning of a decision. A plausible sentence can turn an unresolved question into an apparent commitment. Review has to examine the substance.

In confidential work, the process also needs clear boundaries around what information may be used in which approved environment. The person preparing the material remains responsible for its accuracy and handling.

Reusable playbooks make the method easier to transfer. They should explain the task, permitted inputs, steps, checks, limitations, and approval requirements. The next person needs to understand how to judge the output, as well as how to produce it.

Documentation earns its place when it helps someone carry out a real responsibility.

A standard operating procedure should tell the owner when the process starts, what information is required, what sequence to follow, what a satisfactory result looks like, and what to do when the normal sequence breaks.

That last part is often where the most valuable knowledge lives. The recurring task is easy to describe. The judgment behind an exception is harder to recover after the person who handled it has left.

My approach is to document the work close enough to its use that the process can be checked against reality. If a procedure requires information nobody has, access nobody has granted, or approval from someone who no longer owns the decision, it needs to change.

Different kinds of knowledge need different records. A procedure explains how to perform recurring work. A decision log explains why a direction was chosen. An initiative register records the current state. A role description establishes responsibility. Combining everything into one enormous document can make each part harder to use.

The goal is a small, maintained set of materials that people can find, understand, and rely on. Every important document should have an owner and a reason to be updated.

Helping identify and prepare the right permanent owner was part of the assignment from the outset.

The hiring question should follow the work. What will this person actually be accountable for after the transition? Which relationships will they maintain? What judgment must they exercise independently? Where do they need formal authority, and where will they need to work through influence?

Relevant experience may come from executive operations, corporate strategy, transformation, consulting, program leadership, or a chief-of-staff role. Years of experience and education provide context, but the stronger evidence is how a person handles the situations the job will present.

I would look for someone who can scope a cross-functional initiative, explain a financial assumption, prepare a clear executive brief, develop a small team, and manage sensitive information responsibly. Practical AI fluency belongs alongside those capabilities when the operating model depends on it.

A useful interview can ask the candidate to work through conflicting priorities, an ambiguous executive request, a slipping dependency, or an update that looks reassuring but contains weak evidence. Their questions can reveal as much as their initial answer.

The person maintaining the function may bring different strengths from the consultant who established it. They need the judgment to keep improving the system as the company changes. Hiring a permanent owner should give the business durable capability, with enough support and authority to make the appointment work.

Sending a folder and scheduling a final call is only the administrative part of a transition.

A more useful test is whether the next owner can run the work. Can they prepare the review, locate the current initiative record, explain the important dependencies, recognize when something needs escalation, and maintain the next planning cycle?

The transition should create opportunities to observe, then lead, then operate with progressively less support. Where the successor struggles, the cause may be a knowledge gap, a weak procedure, missing access, an unclear responsibility, or a relationship that needs a proper introduction.

Those are findings to address while the handoff is still underway.

Open issues deserve particular care. A transition record should state what remains unresolved, who owns it, why it matters, and what happens next. Reassurance is less useful than an accurate account of the work that still needs attention.

The test is continuity under ordinary pressure. The company should be able to proceed when a meeting moves, a deadline slips, or an executive asks a new question, without automatically calling the former consultant to reconstruct the process.

Strategy operations puts a person close to pressure, incomplete information, and strong opinions.

Curiosity helps uncover what is actually happening. Clear communication helps people act. Accountability means owning the consequences of decisions and correcting errors promptly. Attention to customers keeps internal priorities connected to the people the company serves.

Constructive challenge matters too. A familiar process may have become inefficient. An impressive report may conceal a weak assumption. A person coordinating the work needs enough confidence to raise the issue and enough respect to make the conversation productive.

Inclusive leadership is practical in this setting. People closest to the work may see a problem that senior leaders have not encountered. They need a reasonable opportunity to contribute, disagree, and explain constraints without being dismissed because of title or background.

The standard I care about is whether the function helps other people succeed with integrity. It should improve the organization’s ability to act, rather than make every accomplishment depend on one highly visible person.

The engagement reinforced why I treat the handoff as a design requirement.

Executive priorities need a path into action. Recurring work needs a dependable method. Important decisions need a record. A permanent leader needs enough context, authority, and preparation to take ownership.

That is why documentation, SOPs, and repeatable processes matter. They preserve the parts of the work the organization needs to keep and give the next person something solid to improve.

If you are considering a similar assignment, define the condition you want the business to be in when the consultant leaves. That conversation should shape the scope, the hiring plan, and the way the engagement runs from its first day.

You can explore my approach to strategy consulting, read more about executive talent and leadership, or talk with me about the function you need to build.