# Chief of Staff Professional Development Plan: Skills, Evidence and a 90-Day Roadmap

> Use a 90-day Chief of Staff development plan to build mandate clarity, executive briefs, decision flow, stakeholder coordination and evidence of operating impact.

- Canonical page: https://mtfinstitute.com/insights/chief-of-staff-professional-development-plan-90-days/
- Content type: Article
- Editorial category: Guides & Frameworks
- Publisher: MTF Institute of Management, Technology and Finance
- Author: MTF Institute Editorial Team- Published: 2026-09-11
- Updated: 2026-09-11
- Language: English
- Topics: Leadership, Career Development, Chief of Staff, Professional Development, Executive Operations

A Chief of Staff professional development plan should strengthen the operating system around an executive. The role creates value by clarifying decisions, integrating information, coordinating stakeholders and closing commitments without becoming an unaccountable shadow executive.

The plan below is designed for a current or aspiring Chief of Staff. It converts broad competencies into observable work over 90 days.

## The short answer

Build development around five outputs:

1. a written mandate and decision boundary;
2. a reliable executive brief;
3. a visible decision and commitment log;
4. a stakeholder and escalation map;
5. a portfolio showing how the system improved.

Training matters when it changes the quality of those outputs. Course hours alone are weak evidence of development.

## Start with the mandate

Chief of Staff titles vary widely. One role coordinates executive priorities. Another leads special projects. A third manages a function. Before choosing skills, write a one-page mandate with:

- the executive and organization served;
- decisions the Chief of Staff can make;
- decisions the role prepares but does not make;
- forums, rhythms and projects owned;
- information the role may access;
- escalation triggers;
- measures of success for the next quarter.

The mandate prevents two predictable failures: a role that becomes an extra administrative layer and a role that exercises authority nobody formally assigned.

## COS-GROW: the development matrix

Score each capability from 1 to 4: **1 awareness**, **2 supervised practice**, **3 independent delivery**, **4 repeatable system plus coaching**.

| Capability | Evidence at level 3 | Development exercise |
| --- | --- | --- |
| **C — Context synthesis** | concise brief separates facts, assumptions, options and open questions | turn a large source pack into a two-page executive brief |
| **O — Operating cadence** | forums have decisions, owners and closure rules | redesign one recurring leadership meeting |
| **S — Stakeholder coordination** | competing interests are mapped without hidden commitments | build a stakeholder map and engagement sequence |
| **G — Governance and boundaries** | decision rights and escalations are explicit | create a decision-rights map for one initiative |
| **R — Risk and response** | weak signals enter a visible risk and issue process | run a pre-mortem and escalation drill |
| **O — Outcome tracking** | commitments connect to measures and decisions | maintain a commitment and outcome register |
| **W — Written influence** | briefs lead to a clear, accountable decision | write recommendation, options and decision memo versions |

Do not average away a weak boundary score. Governance and written influence should reach level 3 before the role takes on more sensitive scope.

## Days 1–30: diagnose the operating system

### Week 1: mandate and listening

Interview the executive and a deliberately varied set of stakeholders. Ask what decisions stall, which meetings create rework, what information arrives too late and where the role must not intervene.

Deliver:

- mandate v1;
- stakeholder map;
- current meeting and decision inventory;
- list of three friction hypotheses.

### Week 2: information flow

Trace one important decision from source information to final approval. Mark where evidence is duplicated, delayed or transformed without ownership.

Deliver an information-flow map and one executive brief using the format:

| Section | Required content |
| --- | --- |
| Decision | exact decision and deadline |
| Evidence | verified facts and source date |
| Uncertainty | assumptions, gaps and sensitivity |
| Options | feasible choices and consequences |
| Recommendation | reasoned choice within authority |
| Ownership | approver, owner and next review |

### Weeks 3–4: baseline and boundaries

Measure a small number of operating outcomes: decisions waiting, commitments overdue, meeting time, repeated requests and time from escalation to owner. Confirm that the Chief of Staff can access and use the data legitimately.

End day 30 with a mandate review. Remove work that belongs to another role. Add no new recurring forum without closing or improving an existing one.

## Days 31–60: improve one decision loop

Select one recurring decision with enough frequency to learn but limited downside if the first design is imperfect. Examples include weekly commercial prioritization, portfolio risk review or cross-functional launch readiness.

Create:

- a pre-read deadline and evidence standard;
- a decision owner and consulted roles;
- a log of decisions, rationale and review date;
- a commitment register with owner and due date;
- an escalation rule for missing evidence or blocked action.

Compare four weeks before and after the intervention. A shorter meeting is not automatically better. Look for fewer reopened decisions, clearer ownership and faster closure without suppressing dissent.

## Days 61–90: transfer and scale

The Chief of Staff should not become the only person who can run the system. Document the cadence, train an operational owner and test one week in which the owner runs it.

Build a portfolio containing:

1. the final mandate and boundary map;
2. one redacted executive brief;
3. a before-and-after process view;
4. decision and commitment log templates;
5. a short evidence note explaining what improved, what did not and why.

Finish with a 90-day review involving the executive and at least two stakeholders who experience the system. Set the next development goal from observed gaps, not from a generic competency list.

## Use evidence, not proximity, as the career signal

Access to a senior executive can create visibility but does not prove operating competence. Strong evidence shows that the person can synthesize conflicting information, preserve decision rights, improve closure and make the system easier for others to run.

For an external interview, translate confidential work into a protected case:

- describe the decision type and constraint;
- show the generic method;
- quantify an approved, non-sensitive outcome;
- explain your boundary and what another role owned;
- remove names, material information and internal documents.

## Weekly development review

Use 20 minutes each Friday:

| Question | Evidence |
| --- | --- |
| Which decision became clearer? | brief, log or confirmed owner |
| Which commitment closed? | dated status and accepted output |
| Where did I exceed or underuse my mandate? | boundary note and correction |
| Which stakeholder signal changed the plan? | source and resulting decision |
| What will I deliberately stop next week? | removed meeting, task or duplicate report |

The stop question protects the role from accumulating invisible coordination work.

## How to select development or training

Choose learning that requires application across leadership, communication, finance, data and execution. Ask whether the assessment includes a new scenario, written recommendation, stakeholder tension and an explicit authority boundary.

The U.S. Office of Personnel Management's Executive Core Qualifications provide a useful external reference for senior-leadership development: commitment to the rule of law and public trust, driving efficiency, merit and competence, developing the workforce, and achieving results through accountable leadership. The institutional context differs, but the emphasis on evidence, people and results transfers to Chief of Staff development.

## Learning pathway

MTF Institute's [Professional Certificate in Chief of Staff](https://mtfinstitute.com/programs/chief-of-staff/#enroll) develops mandate design, executive communication, decision support, governance and operating cadence through applied work. It is professional, non-degree education and does not guarantee appointment or promotion.

## Sources

- [U.S. Office of Personnel Management: Executive Core Qualifications](https://www.opm.gov/policy-data-oversight/senior-executive-service/executive-core-qualifications/)
- [MTF Institute: The Rise of the Chief of Staff](https://mtfinstitute.com/insights/the-rise-of-the-chief-of-staff/)
- [MTF Institute: Chief of Staff Operating Cadence](https://mtfinstitute.com/insights/chief-of-staff-operating-cadence/)



## Citation

When citing or summarizing this material, link to the canonical HTML page: https://mtfinstitute.com/insights/chief-of-staff-professional-development-plan-90-days/