Commitment management
Key takeaways
- Collect promises from approved source records.
- Resolve duplicates and conflicting dates.
- Confirm completion with evidence or a stakeholder update.
Operating data
Playbook
Executive commitments are easy to lose because they appear in different forms: a meeting action, an email promise, a calendar hold, or an approval waiting in a project tool. A weekly reconciliation brings these records together without pretending every task belongs to the executive.
Capture the promise, recipient, source, accountable owner, due basis, current status, dependency, and evidence required for closure. The operations follow-through service gives the assistant a governed place to maintain this view and route missing updates.
The assistant can reconcile duplicates, request status, and draft expectation updates. Only the commitment owner may change the promised outcome or date. When two records conflict, return to the latest authorized source and ask the owner to confirm what should be communicated.
Run the review before weekly planning so overdue work and new priorities appear together. Separate completed, on-track, blocked, changed, and obsolete items. Asana's work management resources provide general coordination ideas, while direct commitments and approved decisions remain the source of truth.
Close the review by sending necessary stakeholder updates and recording the next action for every blocked promise. Track repeated slippage by cause instead of assigning blame. Teams can request a tailored support plan to define a sustainable reconciliation cadence and authority boundary.
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.