Management Team Assessment in the First 90 Days

Executive summary

A management team assessment is a structured judgment about whether the people in the top roles can deliver the plan you now own. For a new private equity owner or a new CEO, it is one of the highest-stakes decisions in the first 90 days, and one of the most commonly made on instinct: a good first meeting, a loud complaint from a board member, a single missed forecast.

The method below replaces instinct with evidence. Define what each role must deliver for the plan. Collect outcome evidence for each role from the records, not from reputation. Map who actually decides what. Compare the capabilities the plan requires with the capabilities the team has. Only then classify each leader as retain, develop, or replace, with a dated rationale. Treat fairness, legal, and HR constraints as part of the method, not as an afterthought, and talk to employment counsel before any action that affects someone's job.

The first move is to write the plan's demands down in role terms. If you cannot say what the CFO, the head of sales, or the plant leader must deliver in the next 12 to 24 months, you are assessing people against a feeling.

When to use this

Use this guide when:

• A sponsor has closed an acquisition and the 100-day plan includes a view on the leadership team.
• A new CEO or operating partner has joined a company with an existing team.
• The value-creation plan requires capabilities the team has not previously needed, such as a pricing function, a finance team that can support a lender, or a more disciplined sales process.
• Results have missed plan for two or more quarters and the explanation keeps changing.
• You are 12 to 36 months from an exit and need management depth that a buyer will credit.

Do not use this to build a case for a decision already made. An assessment that works backward from a conclusion produces weak evidence, damages trust, and creates legal exposure. If you already know you need to make a change, take advice from employment counsel and handle it as a transition, not as an assessment.

Diagnostic questions

Answer these from the plan, the org records, the board materials, and a few structured conversations. Most can be answered in the first two to three weeks.

1. What does the value-creation plan require of the team over the next 24 months, expressed as outcomes by function (revenue, margin, cash, quality, hiring, systems)?
2. For each senior role, what was committed in the last two budget cycles, and what was delivered?
3. For each missed commitment, what was the cause, and was it identified by the owner before it was identified by someone else?
4. Which decisions are made by whom today, and how does that differ from the org chart and the delegation of authority?
5. Where do decisions stall, get remade, or move to the CEO or the founder by default?
6. How does the team report bad news, and how long does it take to reach the CEO?
7. Do the numbers the team reports reconcile to the ledger, and who can explain a variance without a week of preparation?
8. What does each leader's own team say about direction, support, and clarity, gathered in a way that protects them?
9. Which key customers, suppliers, or employees depend personally on a given leader?
10. What capabilities does the plan need that no one on the team has demonstrated, and how long would it take to build or hire them?
11. Are there compensation, equity, or employment terms (notice, non-competes, change-of-control provisions) that affect the options?
12. What has each leader asked of you in the first weeks, and what does that tell you about what they need to succeed?

If questions 1 and 2 cannot be answered, pause the assessment and finish the diagnostic work. Question 4 usually produces the most surprising answers.

The framework: five lenses and one decision

A fair assessment looks at each leader through five lenses and then makes one explicit decision.

The lenses weigh differently by role and situation. A turnaround tolerates less development time than a growth plan. A role that mostly executes a stable process needs less capability headroom than one that must build something new.

Step 1: Write role scorecards from the plan

A role scorecard translates the plan into what each leader is accountable for. Keep it to one page.

A good scorecard has five parts:

1. Mission: one sentence on why the role exists in this plan.
2. Outcomes: three to five measurable results over 12 to 24 months, with the metric, the baseline, and the target. For example, for a CFO: cash conversion, forecast accuracy, a clean quality of earnings, and lender reporting on time.
3. Competencies: the capabilities the outcomes require, stated as observable behaviors.
4. Decision rights: what the role decides alone, decides after consulting, and recommends.
5. Constraints and resources: budget, headcount, systems, and the support the role needs.

Agree the scorecard with the leader. Do this early, and say plainly that it defines what success looks like in the plan. An assessment against criteria that the person has never seen is unfair and produces poor information.

The financial KPIs for executives guide is useful for choosing outcome metrics, and the EBITDA bridge shows how functional outcomes roll up to the plan.

Step 2: Collect outcome evidence, not opinion

For each role, assemble evidence in three categories. The aim is to reduce the weight of anyone's impression, including yours.

Commitments versus delivery. For the last two to four periods, list what the leader committed to (budget, forecast, project dates, hiring plan) and what happened. Include the cause of each miss, and whether the leader flagged it early.

Quality of work. Review a sample of actual work product: a forecast and its reconciliation, a pricing analysis, a supplier negotiation file, a production plan. Ask the leader to walk you through it. How they reason matters as much as the answer.

Consistency of reporting. Test whether reported figures reconcile to the books, and whether the same number appears in the board deck, the lender report, and the operating review. The financial due diligence checklist offers the checks to run on finance. For other functions, ask the equivalent question: can the leader show where each number comes from?

Rules for evidence:

• Separate the person from the system. A missed budget may reflect a flawed budget, an unavailable resource, or a decision made above the leader. Record the cause, not only the outcome.
• Look for patterns, not events. A single miss is information. Three similar misses is evidence.
• Weigh recency and context. What changed in the last six months? Was a leader promoted into a role they were not equipped for, or did a market shift?
• Document sources. Each conclusion should point to a record you can show the leader.

Step 3: Map decision rights

Many underperformance stories are really decision-rights stories. A leader is held accountable for an outcome that they do not control, or controls a decision that they do not own.

Build a one-page map for the ten or so decisions that drive the plan: pricing changes, hiring, capital spending above a threshold, supplier selection, customer concessions, forecast submissions, and so on. For each decision, record:

The gap column is the finding. Typical gaps include a founder who still approves every price exception, a CFO who owns the forecast but not the sales assumptions, and an operations leader who owns on-time delivery but not the purchasing decisions that drive it.

Then ask three questions of each gap:

1. Is the leader unable to decide, unwilling to decide, or not permitted to decide?
2. If the decision right moved to where the policy says it should be, would outcomes change?
3. Does the governance structure, such as the VCP governance charter, need to be clearer?

Fix the decision rights before concluding anything about capability. A leader who is held to outcomes they cannot control has not been given a fair test.

Step 4: Measure the gap between capability and plan

Now compare what the plan needs with what the team can do. A simple numeric scale makes the discussion concrete without pretending to be precise.

1. Define the capability levels the plan needs for each role, on a scale of 1 to 5 (for example, 1 = learning, 3 = competent in a stable environment, 5 = has built and scaled this in a comparable setting).
2. Rate the current level from the evidence collected, with a short note citing the source.
3. Compute the gap: Gap = Required level − Current level. A negative result is a surplus and is not a problem.
4. Estimate the time to close the gap if the person is developed (coaching, training, a strong deputy) versus the time to hire someone who already has the capability.

The comparison matters more than the number. A gap of 1 in a role with a long runway is a development case. A gap of 2 in a role on the critical path of the first 12 months of the plan is a hard conversation.

Weighted scorecard (illustrative)

The numbers below are made up to show the arithmetic. They are not benchmarks and do not describe any real person.

Suppose a scorecard has five criteria with these weights, which sum to 100:

Each criterion is scored from 1 to 5 using the evidence. Three illustrative leaders score:

The calculation for Leader A is (30 × 4 + 25 × 4 + 20 × 3 + 15 × 5 + 10 × 4) ÷ 100 = (120 + 100 + 60 + 75 + 40) ÷ 100 = 3.95. Leader B is (60 + 75 + 80 + 45 + 30) ÷ 100 = 2.90. Leader C is (150 + 75 + 40 + 30 + 30) ÷ 100 = 3.25.

How to use this, and how not to:

• The score organizes the conversation. It is not a verdict. Leader C has the best outcomes and the weakest decision and team scores, which suggests a different conversation from Leader B's low outcomes with a strong decision score.
• Never combine the weighted score with an arithmetic cut-off, such as "replace anyone below 3.0." Context, decision rights, and development time matter, and a mechanical cut-off is hard to defend.
• Have a second person score independently, then reconcile differences. Disagreement of two points or more on a criterion means the evidence is thin.
• Record the evidence next to each score. A number without a cited source should not survive review.

Capability versus plan gap (illustrative)

Required and current levels for one leader's role on the critical path:

The total gap is 2 + 1 + 0 + 1 = 4 points across four capabilities, and the largest single gap is in the forecasting capability the plan relies on in the first two quarters. Whether that points to development (a senior FP&A hire beneath the leader, training, an interim adviser) or replacement depends on how much runway the plan allows.

Step 5: Decide retain, develop, or replace

Use a three-way framework, with specific criteria for each decision and a dated next step.

Some principles for the decision:

1. Be explicit about time. The same leader may be a retain in a stable plan and a replace in a plan that needs a new capability within two quarters. State the horizon.
2. Decide with coverage in mind. Replacing a leader without an interim or a successor can cost more than the problem it solves. Customers, suppliers, lenders, and employees may depend on that person.
3. Beware the halo and the horn. A leader who presents well may be rated above their results. A leader who irritates you may be undervalued. Return to the evidence.
4. Consider the move before the exit. Some people are in the wrong role. A move into a better-fitting role may be worth more than a replacement.
5. Give feedback before you decide, where you can. A leader who has never been told the criteria has not had a fair chance. Documented feedback, a reasonable period to respond, and a follow-up are better for the person and for the company.
6. Decide as a group on the hard calls. The CEO, the sponsor's operating partner, and an HR or employment-law adviser should agree on the rationale and the record. This reduces individual bias and protects the company.
7. Keep the decision log. For each leader, record the date, the evidence, the decision, the rationale, and the next review.

Fairness, legal, and HR cautions

This section is general operating guidance, not legal advice. Employment law varies by country, state, and contract. Involve employment counsel and HR before any action that changes a person's role, pay, or employment.

• Use job-related criteria only. Assess against the scorecard. Do not let age, gender, race, disability, family status, health, or other protected characteristics (or proxies such as "cultural fit" or "energy") influence the decision. Vague criteria are a source of both bias and legal risk.
• Apply the same process to everyone in comparable roles. If one leader gets a development plan and another with similar evidence gets terminated, you need a documented reason.
• Document honestly and contemporaneously. Write down evidence and rationale as events happen. Records created after the decision look like justification.
• Respect contracts. Employment agreements, equity documents, notice periods, severance terms, restrictive covenants, and change-of-control provisions affect the options and the cost. Read them before you promise anything.
• Protect confidentiality. Limit who sees the assessment, keep it separate from general files, and avoid discussing individuals in email threads.
• Handle interviews and surveys carefully. Skip-level conversations should be voluntary, with a clear explanation of how the information will be used. Do not promise confidentiality you cannot keep.
• Do not make promises about job security during the assessment, and do not suggest a decision has been taken before it has.
• Treat integrity concerns separately. If you suspect misconduct, stop the normal assessment and bring in counsel and, where appropriate, an independent investigation. Do not conduct your own.
• Plan for the aftermath. Include the legal and HR steps, the communication, and access and data security in the transition plan.

Communication

How the outcome is communicated affects retention of the people you want to keep.

1. Tell individuals first and in person. No leader should learn about a decision from a colleague or an announcement.
2. Be specific and fair. Give each person the evidence behind the decision and the next steps. For a development decision, state what must change, by when, and what support is provided.
3. Sequence the audiences. Board and sponsor, affected leaders, the wider management team, then employees, then external parties such as lenders and key customers where relevant.
4. Agree the message with counsel and HR for any exit, including what will be said about the reason, the transition, and references.
5. Say what is not changing. People fill silence with rumor. Confirm the plan, the priorities, and who covers which responsibilities.
6. Follow up. Check in with the retained team after a change. A decision that is right on paper can still lose the people around it if the follow-up is weak.

Common mistakes

1. Assessing against an unwritten standard. Symptom: leaders are told after the fact what they should have delivered.
2. Letting the loudest voice stand in for evidence. Symptom: a decision rests on one board member's complaint or one customer's story.
3. Confusing decision-rights gaps with capability gaps. Symptom: a leader is judged on an outcome the founder still controls.
4. Over-weighting presentation. Symptom: polished slides earn a higher score than reconciled numbers.
5. Moving too slowly on a critical-path gap. Symptom: two quarters of "development" while the plan slips.
6. Moving too fast without coverage. Symptom: a replacement decision with no interim, and a key customer relationship leaves with the person.
7. Mechanical scoring. Symptom: a numeric cut-off is used as a decision rule and nobody can explain the exception.
8. Poor documentation. Symptom: the rationale for a decision is reconstructed from memory after the fact.
9. Skipping HR and counsel. Symptom: the first conversation with employment counsel happens after the exit has been announced.
10. Ignoring the rest of the team. Symptom: attention on the CFO and the head of sales while a key plant manager quietly leaves.

AI prompt assistance

AI can help structure the work and draft documents. It cannot assess a person, and it must not be used to make or justify employment decisions. Supply the data yourself, verify the output, and keep personal information within your company's approved tools and privacy rules. Have HR and employment counsel review anything that affects an individual.

1. Draft role scorecards from the plan.

Here is our value-creation plan summary and the org chart. For each of the CEO's direct reports, draft a one-page role scorecard: a mission sentence, three to five measurable outcomes with metric, baseline, and target, the competencies required, and the decisions the role should own. Mark every number you did not take from the plan as a placeholder to be confirmed.

Check: each leader and the CEO review the draft. Do not accept targets that are not in the plan.

2. Build a commitments-versus-delivery table.

I will paste the budget, the actuals, and the board commitments for the last four quarters for one function. Produce a table of each commitment, the outcome, the variance, and the stated cause. Flag any variance with no stated cause.

Check: confirm each figure against the source and ask the leader to verify the causes.

3. Compare decision rights.

Here is our delegation of authority and a list of notes about who actually approved ten recent decisions. Produce a table of formal owner, actual decider, and the gap, and list the three largest gaps. Do not assess individuals.

Check: validate with the people involved before drawing a conclusion.

4. Draft a development plan.

A leader has a capability gap in [capability], from level 2 to a required level of 4 within two quarters. Draft a development plan with milestones, support options, and a checkpoint at 90 days. Do not comment on the person's character or potential.

Check: HR reviews the plan, and the leader co-writes the final version.

Implementation guide

Governance: the CEO owns the assessment and the decisions, the sponsor's operating partner challenges the evidence, HR owns process and documentation, and employment counsel owns advice on any action affecting employment. Report the summary (not individual details) to the board.

What to expect: the first 30 days usually surface decision-rights issues that explain part of the underperformance. The capability picture needs 60 days of evidence to be fair. Development plans take two or more quarters to show in results. Re-run the assessment at 180 days and again before an exit, because the plan and the team will have changed.

Related resources

• 100-day plan template for private equity: where the leadership assessment sits in the first 100 days.
• VCP governance charter template: clarifying decision rights and reporting.
• Financial KPIs for executives: choosing outcome metrics for role scorecards.
• EBITDA bridge with continuous tracking: linking functional outcomes to the plan.
• Financial due diligence checklist: testing the quality of the finance function's reporting.
• Margin expansion playbook: the commercial and operating levers the team has to deliver.

Frequently asked questions

How do you assess a management team in the first 90 days?

Write role scorecards from the value-creation plan, gather outcome evidence from budgets, forecasts, and reconciled reporting, map who actually decides what, then compare the capabilities the plan needs with the capabilities the team has. Only after that, decide retain, develop, or replace for each leader, and keep a dated record of the evidence.

What should a role scorecard include?

A role scorecard states the role's mission in the plan, three to five measurable outcomes with baseline and target, the observable competencies required, the decisions the role owns or recommends, and the resources it needs. Agree it with the leader early so the assessment uses criteria they have seen.

How do you decide whether to retain, develop, or replace a leader?

Retain when outcomes and capability meet the scorecard, develop when a real gap can close within the time the plan allows, and replace when a critical-path gap cannot close in time or repeated failures follow fair feedback. State the time horizon, plan interim coverage, and take employment counsel's advice before any replacement.

How long does a management assessment take?

A fair assessment typically takes about 60 to 90 days, because decision-rights issues surface in the first month and capability evidence needs a full cycle of reporting and work samples. Rushing it risks acting on first impressions. Re-run it at about 180 days and again before an exit.

What are the legal risks in assessing executives?

The main risks are decisions based on criteria that are not job-related, inconsistent treatment of similar cases, poor records, and ignoring employment contracts and equity terms. This is not legal advice. Use written scorecards, document evidence as it arises, and involve HR and employment counsel before any change to a person's role or employment.

How this works in a System of Performance

An assessment is only as good as the evidence trail behind it, and that trail is usually scattered across budgets, board decks, spreadsheets, and memory. A Performis routine can take on a recurring job like this, with the scope and fit agreed with you: it works from the records your team supplies, prepares the work for your named reviewer, and keeps each approval on record. To see where your own commitments and results already line up, bring it to us as a launch partner.