Reset Engagement Governance After a Client Merger

A client merger changes the ground under an active engagement. A former sponsor might still care deeply about the work while a new leader controls spending. A regular steering meeting might no longer include the people with authority. A delivery team might hold dates, interviews, and workshops on its calendar without knowing which activities still have support. A governance reset gives everyone a shared view before uncertainty turns into conflicting instructions.

Begin with the work already underway. List every deliverable, meeting, decision, approval, and customer dependency due during the next thirty days. For each item, record the current owner, the original approval source, the cost or resource commitment involved, and the consequence of delay. Keep the list practical. “Executive decision on operating model” is more useful than “governance issue.” “Customer data access needed by Tuesday” is more useful than “project risk.”

Separate current authorization from future authorization. Work already approved might have a different status from new scope, extensions, or optional workshops. Do not infer approval from a former sponsor’s encouragement after the merger. Ask which commitments still stand, which require a new review, and which activities must pause until a named leader responds. The client partner prepares facts and options. Customer leaders decide their authority structure and approval route.

In a fictional meeting, program director Helen says, “Please keep going while we sort out the merger.” Client partner Devon replies, “I want to protect momentum and make the next decisions visible. Which work is already approved for this month, and who now confirms spending or scope changes?” Helen says the acquiring company has a forty five day spending freeze. She also says the new sponsor has received no program brief. Devon writes those facts into the decision record during the call.

Devon then asks about the immediate calendar. A workshop is scheduled next Wednesday, interviews start Monday, and a proposed analysis phase awaits a signature. Helen says the workshop supports a board discussion, the interviews need data access from a newly combined team, and the analysis phase was never approved. The conversation produces a first operating view. The board workshop needs confirmation from the incoming sponsor. The interviews need an access owner. The analysis phase stays open until the customer chooses a review route.

Set up a short governance reset session with the people who hold different parts of the answer. The meeting might include the former sponsor, the incoming sponsor, procurement, a finance contact, a delivery director, and a program operations lead. Do not invite people merely because they held a title before the merger. Invite people whose decisions affect scope, budget, access, timing, or delivery priority. Send a one page pre read before the meeting so everyone arrives with the same facts.

The pre read should contain four parts. First, state the active work and planned dates. Second, name decisions waiting for customer direction. Third, show the effect of each decision on people and dates. Fourth, propose the exact decision needed during the session. For the fictional case, Devon writes: confirm whether the board workshop proceeds. Name an owner for interview access. Approve, defer, or stop the analysis phase. Confirm the next steering forum. These requests are specific enough for leaders to answer.

Avoid presenting a long risk register without a choice beside each item. A risk statement such as “merger uncertainty affects delivery” gives no one a next move. A useful entry says, “Interview access is unassigned. If no owner is named by Monday, interviews move from Tuesday to the following week.” The language lets the incoming sponsor see the practical effect and select an action. Facts build confidence better than pressure.

In the fictional reset session, the incoming sponsor says, “I need time to understand this program before I approve more work.” Devon responds, “We have separated next week’s board workshop from the new analysis phase. Helen says the workshop supports a scheduled board discussion. Would you like to review a one page brief today and confirm the workshop by Thursday?” The sponsor agrees to a twenty minute review. Procurement asks for a statement of current commitments. The delivery director names an operations manager for interview access. Each decision has an owner and a date.

The client partner should send notes soon after the session. Record decisions, open questions, owners, dates, and consequences of missing a date. Use direct verbs. “Priya confirms workshop status by Thursday.” “Marco provides an interview access contact by Monday.” “The analysis phase awaits procurement review.” Avoid vague entries such as “team aligned” or “follow up as needed.” A delivery team needs instructions team members are able to follow without interpreting meeting mood.

Build a contact map as the new organization takes shape. Name the executive sponsor, program lead, procurement contact, finance contact, data or access owner, and day to day delivery contact. Add a short note about what each person decides or supplies. Keep former leaders on the map when they still provide history, but do not label them as approval owners without confirmation. The map makes staff changes visible and reduces repeated questions from the delivery team.

Establish a temporary rhythm while the customer settles new governance. A weekly decision call might suit one engagement. Another might need a short written update before an existing steering meeting. Choose a rhythm connected to upcoming decisions rather than habit. Each update should show what changed, what decision approaches a deadline, and what evidence the customer needs to decide. Do not fill updates with internal activity reports when no customer action follows from them.

Give the delivery team a clear escalation route. A consultant might receive a request from a former sponsor to add work before approval is settled. A project manager might hear a new leader say to stop a task already scheduled. Team members need a simple response: record the request, avoid promising a change, and route the request to the named client partner and delivery lead. This process protects the customer from conflicting commitments and gives leaders one place to resolve differences.

In a fictional practice situation, a former sponsor messages a consultant: “Please add competitor interviews next week.” The consultant replies, “I will record the request and ask Devon to include the request in the current decision review.” Devon checks the contact map and sees no approval for new analysis. He brings the request to the incoming sponsor with an estimate of the effort needed and the effect on the board workshop. The sponsor chooses to defer the interviews until after the budget review. Devon records the date for reconsideration rather than leaving the request in an inbox.

Prepare for the moment when governance becomes stable again. Ask the incoming sponsor which decisions belong in the regular steering forum, what spending threshold requires procurement, and how new work enters review. Update the contact map and decision log after their answer. Do not keep a temporary merger process alive once a clear route exists. The account team should make the new routine easy for customer staff to use.

Practice with a fictional two week delivery calendar. Put a workshop, an interview round, a scope change, and a data request on separate days. Ask a colleague to play Helen during a merger freeze. List the decision owner, evidence needed, deadline, and delay effect for each item. Then ask the colleague to approve only the workshop and data request. End by sending a short meeting note to your own practice file naming the postponed scope change, its future review date, and the customer owner who will revisit the request.