Operating Cadence
Part of Startup operating systems
Distinguishing urgent work from important operating commitments
Triage urgent requests against standing startup commitments by checking deadlines, impact, authority and what must move.
A request is urgent when delay has a near-term consequence. An operating commitment is important when missing it would undermine an agreed result, even if its deadline is further away. The two can overlap.
When a request arrives, check its deadline and consequence, then decide what it would displace. Do not let the loudest message silently cancel a standing commitment.
Test the deadline and the consequence
Ask four questions before changing the team's work:
- What happens if this waits?Name the customer, service or internal result affected.
- When does the consequence occur?Separate an actual deadline from a preferred response time.
- Can someone contain the problem now?An acknowledgement or suitable interim step may allow the substantive decision to wait.
- Who can decide the trade-off?The person receiving the request may not have authority to move another commitment.
A request can be time-critical but limited in impact. Another task may have no immediate deadline yet be essential to reliable delivery. Consider timing and impact together rather than using a single “high priority” label.
Protect commitments that become invisible between crises
Standing work can prevent later problems: checking an unresolved delivery issue, maintaining a handover or reviewing access after a role change. Name the owner, due point and visible result for each commitment. Put it where the team already tracks work so it remains visible when a new request competes for time.
Protection does not mean a commitment can never move. If an immediate customer problem needs the owner today, record the new due point, who covers the work if necessary and who must be told. An explicit postponement lets the team assess the cost; an unrecorded one makes the commitment disappear.
Choose a response
Situation / Possible response
- High impact and time-critical
- Act or escalate now; identify what other work must move.
- High impact with time to plan
- Reserve an owner and a future work slot.
- Time-critical but limited impact
- Contain, delegate or use an agreed routine response where appropriate.
- Low impact without a real deadline
- Defer, decline or group it with similar work.
This table is a discussion aid, not an automatic scoring system. Follow any applicable safety, security or incident response procedure. A contractual deadline or a dependency affecting others can also change the decision. Check the facts and the authority of the person making the call.
Make the trade-off visible
Suppose a founder is due to check open customer deliveries this afternoon when a colleague asks for help preparing an optional presentation tomorrow. The presentation has a near deadline, but the delivery check may expose a promise that needs action.
The founder could ask whether the presentation can be shorter, delegate part of it, or assign the delivery check to someone else. The choice depends on actual commitments and available capacity.
When the team changes course, record what came in, why it took precedence, what moved and who owns the revised date. Review repeated interruptions later. If the same “emergency” keeps returning, the team may need a clearer intake rule or a change to the underlying process. If important work is repeatedly postponed, reduce lower-value work or renegotiate commitments.
