On this page
Running a Quarterly Principal and Assistant Retrospective

The working relationship between an executive and an assistant improves by accident or by design. By accident, it improves when something goes wrong and both people adjust. By design, it improves on a schedule. A quarterly retrospective is the schedule.
The meeting is short, usually 45 minutes, and it covers three things: what the assistant should keep owning, what should change, and what the executive should stop doing. Done well, it prevents small frustrations from becoming a resignation.
Prepare with evidence
A retrospective without data becomes a conversation about feelings. Spend 20 minutes beforehand gathering evidence. Pull the numbers you already track: items returned for missing context, escalations after the decision window, repeated corrections, and the categories of work that consumed the most time.
Do not build a performance scorecard from this. The purpose is to find system problems, not to grade a person. Present the numbers as observations and ask what explains them.
Use a fixed agenda
A fixed agenda keeps the meeting from drifting. Try this structure.
Start by reading the previous quarter's action list aloud. It takes two minutes and signals that the meeting is about follow-through, not complaint. Then move into the segments below.
| Segment | Time | Purpose |
|---|---|---|
| Wins | 5 min | Name what worked and why |
| Friction | 15 min | Identify the top three recurring problems |
| Scope | 10 min | Decide what to add, drop, or change |
| Norms | 10 min | Adjust communication and escalation rules |
| Actions | 5 min | Record owners and dates |
Keep the friction segment honest. The assistant usually knows where the problems are before the executive does. Ask directly: what takes longer than it should, and what requires a decision you should not have to make?
Review scope deliberately
Scope creeps in both directions. The assistant may have quietly absorbed work that belongs elsewhere, or the executive may still be doing work the assistant could own. List the current scope and mark each item as keep, expand, or hand back.
Expanding scope is the usual goal, but only with the access and authority to match. If the assistant will now approve travel exceptions, grant the approval limit in writing.
Renegotiate the norms
Communication norms drift. Revisit response-time tiers, the channels used for different request types, and the escalation triggers. Ask whether the current norms still match the executive's actual week.
If the executive has been sending urgent requests outside the agreed channels, that is a norm to fix, not a habit to tolerate. The assistant should be able to point to the agreed rule.
Close with owned actions
Every retrospective should end with a short action list. Each action needs an owner and a date. Keep the list in the same place as the rest of the operating notes so it does not get lost.
Review the previous quarter's actions at the start of the next retrospective. Closing the loop is what makes the meeting credible.
Handle the difficult conversations
If the relationship is not working, the retrospective is the right place to surface it. Be specific and behavioral. "Board packets have been late three times this quarter" is workable. "You seem disorganized" is not.
If the problem is capacity, consider adding hours or support. If the problem is fit, address it directly rather than letting it fester. A quarterly conversation is far better than a surprise resignation.
Prepare a short evidence pack
Bring three things to the meeting: the tracked numbers, a list of the top recurring requests by category, and any decisions that required the executive but should not have. Keep it to one page. The point is to make the discussion concrete without turning it into a performance audit.
The evidence pack also gives the assistant a voice. When the assistant can show that a category of work is growing, the conversation shifts from impression to fact.
When you disagree
Disagreement is useful if it is about the work rather than the person. If the executive wants to expand scope faster than the assistant believes is safe, say so and propose a smaller first step. If the assistant wants to hand back a task the executive still values, ask what would make it worth keeping.
Record the decision either way. A disagreement that ends without a recorded outcome will return next quarter.
Frequently asked questions
How is this different from a performance review?
A performance review evaluates the person against a scorecard. A retrospective evaluates the system the two of you operate. You need both, but they are not the same meeting. The U.S. Small Business Administration's guidance on managing employees is a useful reference for the performance side.
Should the assistant lead the meeting?
Either person can lead. Many pairs alternate. The person who leads is responsible for preparing the evidence and capturing actions.
What if we have nothing to discuss?
That usually means the evidence was not gathered. Pull the data and look for the small frictions. A retrospective with nothing on the agenda is a missed opportunity, not a sign that everything is perfect.
Make improvement routine
A 45-minute quarterly conversation is one of the cheapest ways to protect a working relationship. If you want a support team that already runs this cadence, see our executive support services and our guide to the executive assistant quarterly review agenda.