Skip to main content
Steady at the Top
← All articles

How to reset promises made by the previous leadership

Reset inherited promises by first establishing what was said, what people reasonably understood, and what the company can honor. Classify each commitment as keep, renegotiate, or retire. Explain the decision directly and attach a named owner to the next action.

Psychological contract is a person’s belief about the obligations exchanged with another party, including what a workplace promise means. Rousseau and McLean Parks discuss this perspective in their 1993 synthesis: The Contracts of Individuals and Organizations. Your predecessor’s words and an employee’s understanding can differ. Establish both accounts before choosing a response. A perceived obligation is not itself a conclusion about legal enforceability; obtain legal advice on the actual commitment.

A private moment that makes the issue visible

Composite scenario, not a client case: You open an old message thread at the kitchen table. An employee has forwarded a former leader’s assurance about a future role. Your calendar holds several similar conversations. You did not make the promises, but people are arranging their lives around them. A general statement that the business has changed will not resolve the particular expectation.

Use the research within its limits

The situation-centered leadership analysis in Vroom and Jago (2007) cautions against choosing the same decision process for every problem: Vroom and Jago (2007): The Role of the Situation in Leadership. For inherited promises, propose different participants for different questions. Finance can establish feasibility, the affected person can explain reliance, and counsel can assess legal implications. Their contributions answer different questions. This is an application to promise review, not a research finding that a particular renegotiation sequence will restore trust.

State the decision before discussing personalities

The immediate decision concerns a specific perceived obligation. Establish its content before discussing whether you would have made it. Separate commercial judgment from questions about legally binding commitments.

Use the inherited-promise keep-renegotiate-retire review

  1. Record the original commitment. Capture the wording, audience, date where known, conditions, and evidence. Ask the recipient what they understood would happen and what they did in reliance on it. Keep the original assurance beside the recipient’s account. Record what was conditional rather than silently converting an expectation into a dated guarantee.

  2. Verify authority and feasibility. Check records and responsible owners. Ask counsel about potential employment or contractual obligations. Do not assume an informal promise has no consequence. Ask who could authorize the commitment and who can authorize a revision. Those may be different people, especially after an ownership or leadership change.

  3. Choose the disposition. Keep what can be honored. Renegotiate terms that require mutual adjustment. Retire only after reviewing the obligation and preparing an accurate explanation of what changes. Use a separate status for an obligation whose legal meaning remains under review. An unresolved item should not disappear into the retire category.

  4. Speak to the affected person. Acknowledge the expectation without blaming the former leader. Explain what you have confirmed, the decision, and any alternative you are authorized to offer. Explain which part of the original assurance you acknowledge and which fact you still need. Offer no substitute that has not been approved.

  5. Assign the follow-through. Name the owner of the revised commitment, the next update, and the way the recipient can raise a discrepancy. Check that the wider message matches individual conversations. Name the next concrete event, such as an approved staffing decision. A vague commitment to keep talking can create another expectation without an answer.

Make the promise inventory specific enough to decide

Open an entry for each assurance rather than a single list called legacy issues. Record who communicated it, who received it, and the wording available in messages or documents. Add what the recipient understood and any conditions they recall. Separate a promised promotion after an event from a general conversation about future development. When evidence is incomplete, keep the two accounts visible. Do not fill a missing date or condition from what would now make the decision easiest.

Ask what the person did in response to the assurance. They might describe accepting a different assignment, declining another opportunity, or planning around an expected schedule. Treat those as matters to establish, not as facts automatically proved by a persuasive account. Give the reviewer the relevant documents through a private route. Avoid making the employee retell a personal consequence in a group meeting merely to earn consideration of the underlying promise.

Use the inventory to distinguish the recipient’s question from the company’s question. The recipient may want to know whether the promised role still exists. The company may need to know whether it can fund additional management capacity. Those questions are connected, but a budget answer does not by itself explain what was said. Ask the responsible reviewers to address both. The final conversation should not leave the person wondering whether you ever examined the original assurance.

Give keep, renegotiate, and retire different meanings

Mark an item keep only when an authorized owner can describe what will happen and how it will be delivered. Identify the next action and any remaining condition. A promise to add a role is not complete because it appears in the staffing plan. Someone must own the approval, recruitment, or appointment step. Tell the recipient which of those steps is confirmed rather than treating an intention as a completed obligation.

Use renegotiate for a proposed change that still needs the appropriate agreement. Write the old expectation and proposed replacement side by side. Identify what changes in timing, scope, or benefit. Ask the recipient to explain the practical difference from their perspective. That account can reveal a misunderstanding before a revised arrangement is announced. Keep the proposed version labeled proposed until the responsible parties have completed the required process.

Retire is a decision requiring an accurate explanation and appropriate review. It should not mean that the new CEO dislikes the old promise or cannot locate its author. Document why the company proposes ending the commitment and which consequences were assessed. Ask counsel what must happen before communication. If an alternative is available, describe its actual terms. Avoid presenting an unrelated future opportunity as though it fulfills the original assurance.

Prepare for a conversation that may remain difficult

Before meeting, decide what you are authorized to offer. List the facts you can confirm, the uncertainty you must acknowledge, and the question you need the recipient to answer. Bring the relevant wording. Do not begin with a long defense of the predecessor’s motives. You can acknowledge that the person received an assurance without claiming to know why the previous leader gave it or whether they intended to honor it.

For a hypothetical promotion promise, a useful opening might be: “The message describes a management role after the launch. I can confirm the launch happened. The staffing proposal now differs, and I need to explain that difference before asking you to consider another arrangement.” Use such wording only when those facts are verified. Let the employee correct the account before moving to the proposed disposition. The correction may change the decision you prepared.

Leave room for disagreement about fairness without confusing it with disagreement about the next step. Ask whether the written summary accurately describes the original expectation and the new proposal. The employee can confirm the summary while rejecting the proposal. Keep those responses distinct. If they need advice or time, use the approved process rather than pressing for an immediate expression of support that will later be cited as agreement.

Prevent the reset from creating another unowned assurance

Before closing the conversation, inspect every future-tense statement you made. “I will get you an answer” needs an owner who can obtain it. “We will revisit your role” needs a defined subject and a review point. Remove a promise you cannot control, or state the dependency explicitly. The cleanup should reduce ambiguity about the next obligation instead of replacing a specific inherited assurance with a more comforting but less accountable one.

Check messages to managers as well as individual summaries. A manager who tells the team that all old commitments are being honored may contradict the disposition you discussed privately. A manager who describes every review as a cancellation may create a different misunderstanding. Give them the approved scope and a route for individual questions. Keep employee-specific details out of the general explanation while making the review process understandable.

At the next review, inspect completion of the actual promised action. If a revised role was approved, establish whether its authority and support match the agreement. If a decision remains pending, explain which dependency remains and who owns it. Do not use the existence of the inventory as evidence that expectations have been resolved. Resolution concerns the particular commitment and the person who was relying on it.

Put the boundary into words

I understand that you were told this would happen. I have checked the record and the current requirements. Here is what we can honor, what needs a new agreement, and the next step I will personally ensure receives an answer.

Work through a bounded example

Hypothetical application: A previous leader promised a department an additional management role after a system launch. The launch occurred, but the work now differs from the original plan. The CEO verifies the promise, obtains appropriate advice, and discusses a revised staffing approach with the affected people instead of quietly treating the expectation as expired.

Check the failure mode before scaling

Do not promise a compensating benefit before checking your authority and its consequences. Avoid asking people to endorse a change as a condition of hearing an accurate explanation. Acknowledgment does not guarantee immediate agreement or repair.

A current funding constraint can require an immediate business decision without settling the inherited obligation. Tell counsel which action cannot wait and which expectation remains disputed. Avoid announcing that a benefit or role has expired before reviewing the actual terms. Keep any temporary staffing arrangement separate from the promise review, including who will communicate with the affected employee while the decision is pending.

Review the work, then revise the arrangement

Review whether each retained or revised promise has an owner and a completed next action. Ask recipients whether the recorded commitment matches what they now understand.

An employee may need to disagree with your account of the promise. Edmondson’s 1999 discussion of interpersonal risk provides relevant context: Edmondson (1999): Psychological Safety and Learning Behavior in Work Teams. Give the person a way to submit the original wording or challenge the proposed record. Do not label their response resistant because it complicates the staffing plan. The research does not predict that acknowledging a promise will make its recipient accept revised terms.

Connect this decision to the next one

Place the promise inventory beside the returning-founder mandate. Use turnaround workstream triage when honoring a commitment requires stopping other work. Check whether different treatment is feeding loyalist factions. If an assurance has already been broken, the trust-repair discussion addresses the relationship after the disposition is clear.

Sources

Steady at the Top