Why preferences drift without anyone noticing
A principal's preferences change as the role, the calendar, and the team change. A format that worked last year may now feel slow, and a meeting that used to be useful may now be redundant. The desk often learns about the shift after a mistake, when the principal says the brief was too long or the update arrived too late. By then the wrong habit has already been repeated.
Drift is hard to see because most preferences are never written down. The desk infers them from corrections, old emails, and memory. Each person on the team may hold a slightly different version of what the principal wants. A short weekly check keeps one shared version current without turning preference management into a project.
Keep a written preference record
Create a single record with sections for communication, calendar, travel, documents, and decision support. Under each section, write the preference as an instruction the whole desk can follow. Include the date it was confirmed and the source, such as a direct conversation or a written note. The record should be short enough to scan before a task.
Do not fill the record with guesses. If a preference is unclear, mark it as unconfirmed and ask about it in the next check-in. Review the record when a new person joins the desk so they inherit the same starting point. A living record is more useful than a polished handbook that nobody updates.
The record should distinguish a firm preference from a temporary adjustment. A principal who asks for shorter briefs during a busy quarter may not want the same format forever. Add an expiry date or a review note to temporary changes. That distinction prevents a short-term exception from becoming a permanent rule.
Ask for exceptions instead of routines
A weekly check-in works best when it asks what felt wrong, not what the principal wants in general. Ask which request took too long, which document needed a different format, or which meeting could have been shorter. Exceptions reveal the routine that needs to change. General questions tend to produce general answers that are hard to act on.
Bring two or three specific observations to the check-in so the principal can react to something concrete. For example, note that a recurring briefing has grown from one page to three, or that a weekly update now arrives after the principal's first meeting. Specific observations make the conversation quick and useful. They also show the desk has been paying attention rather than waiting to be told.
Use a short weekly written check
Send the check-in as a short written note rather than scheduling another meeting. Use three prompts: what worked, what caused friction, and what should change next week. Ask for a reply by a fixed time so the desk can act before the next cycle. A written format creates a record and respects a principal who is already meeting-heavy.
Keep the note under a screen and avoid a long survey. If the principal prefers voice, offer a two-minute call as an alternative. The point is a regular signal, not a comprehensive review. A consistent short check beats an occasional long conversation that never happens.
Update the record after a real change
When a preference changes, update the record the same day and tell the people who need to know. Note what changed and when, so a later reader can see why the desk behaves differently. Remove the old instruction rather than leaving two conflicting versions. The record should describe current practice, not the history of every request.
If the change affects a recurring deliverable, adjust the template or the calendar entry as well. A note in a document that nobody opens will not change the output. Check the next instance of the deliverable to confirm the change took effect. That follow-through is what turns a preference into a habit.
Tell the rest of the desk when a preference changes, even if the change seems small. A format tweak that one person misses can undo the benefit of the update. Use a short message in the team channel and point to the revised record. The next deliverable is the real test of whether the change landed.
Share only what the desk needs
A preference record can contain sensitive details about a principal's health, family, or travel security. Keep those details out of the general record unless they directly change how the desk works. Share the operational version with the team and restrict the sensitive notes to the people who need them. A clear rule about what is stored reduces risk.
Use role-based access rather than sending the full record to everyone. When someone leaves the team, review their access and remove it. The record should be easy to use without becoming a target. For related guidance, see our article on handling confidential executive correspondence.
Review the record each quarter
Every quarter, read the record from start to finish and mark anything that no longer matches the work. Ask the principal whether any section has become stale or overly cautious. Retire instructions that exist only because of an old incident. A quarterly read keeps the document from becoming a museum of past preferences.
Compare the record with the corrections that appeared in the last three months. If the same correction keeps appearing, the record is missing something. Add it in plain language and test it for a month. The weekly check-in then becomes a way to confirm the change rather than repeat the same conversation.
Key takeaways
- Keep one written preference record with a confirmed date and source for each instruction.
- Ask about specific exceptions and friction rather than general wants.
- Use a short written weekly check with three prompts and a reply deadline.
- Update the record the same day a preference changes and remove the old version.
- Restrict sensitive notes and review the whole record each quarter.