Founder voice reference
Key takeaways
- Define the founder voice reference owner and source record.
- Separate assistant coordination from executive or specialist authority.
- Close the work with evidence and a dated review trigger.
Operating data
Playbook
Founder voice reference begins with a purpose question for a founder delegating routine message preparation while retaining control of consequential communication: drafts mimic surface phrasing but add positions, certainty, or commitments the founder never approved. Name the decision, its accountable owner, and the evidence needed before work begins; this keeps careful administration from turning an assumption into an executive commitment.
The working record should contain message type, audience, purpose, approved examples, prohibited claims, review lane, send authority, and correction note. Use stable source links instead of copied conversations, label facts whose meaning changes with time, and consult the email draft approval guide for the related authorization pattern; conflicting records stay open until their owner resolves them.
The assistant may adapt verified examples for approved message classes; new positions and commitments require founder review. Put that authority boundary beside the live request, particularly when the recipient is sensitive, the message changes policy, or the draft relies on facts absent from approved sources; the reconciliation condition sends the item back for judgment and never grants permission to improvise.
A routine thank-you draft starts promising a future introduction. The assistant removes the promise because no authority or named contact supports it, then leaves the decision for review.
Close the founder voice reference case by recording the selected action, responsible owner, next observable step, communication status, and audit trail, including a decline or deferral when that is the real disposition.
Review stale sources, corrections, missing ownership, expired permissions, and repeated exceptions on a cadence proportionate to the consequence. PlainLanguage.gov guidelines supplies governed context while local policy and named specialists remain controlling; after mapping the current lane, teams may request a tailored support plan.
FAQ
When should a leader delegate this workflow?
Delegate it when repeated coordination, routing, or follow-up is taking time away from decisions that only the leader can make.
What should the assistant own first?
Start with intake rules, status visibility, and escalation timing so the assistant can act consistently before the workflow expands.