Opportunity-Cost Cards: What You Give Up by Saying Yes. Yes is never free. An opportunity-cost card makes the trade visible before enthusiasm books you.
The memo format for every yes longer than two hours
An opportunity-cost card is a five-line memo you write before accepting work that exceeds two hours this month. It makes the trade visible on purpose. Busy calendars are not infinite; they are ledgers where every yes spends something else.
Fields that matter:
- The yes — what you are agreeing to deliver, in one sentence.
- Hours this month — realistic estimate, multiplied by 1.5 for coordination tax.
- What drops — named work that will slip, delegate, or cancel.
- Who is affected — stakeholders who should expect delay elsewhere.
- Review date — when you will check if the yes still fits.
Keep the card in the same doc or note every time. Consistency beats a beautiful template you fill once. The memo is for you first; sharing it is optional but powerful when the ask crosses teams.
Think of the card as a receipt for your calendar. Receipts are not pessimistic—they make later audits possible. When someone asks why a project slipped, you can point to dated cards instead of reconstructing memory under pressure. That shift alone reduces defensive conversations in busy teams.
Filling the card before you reply in chat
Chat rewards instant yes. Cards reward honest capacity. When a request lands in Slack, open the card template before typing “sure.” Two minutes of writing prevents two weeks of silent resentment when the promised deck never arrives.
Hard rule: if you cannot name what drops, decline or explicitly drop something else the same day. Nameless drops are lies about capacity. Practice the sentence until it is boring: I can do X if we drop Z this month. That sentence is a negotiation tool, not rudeness.
Example: a designer asked to join a rebranding task force (~12 hours/month). The card named dropping two standing critique sessions and delaying a internal template refresh. The requester chose to keep critiques; the designer declined the task force without guilt because the trade was on paper, not in their head at midnight.
Another pattern: the “quick favor” that never ends. A card on a two-hour favor revealed three follow-up meetings already implied. The designer replied with a narrower yes—one asset, one review cycle—and linked the card. The requester accepted because the trade was visible, not because anyone got emotional.
Negotiating with your manager using named drops
Managers often stack priorities because drops stay invisible. Bring the card to a one-on-one as data, not drama. “Here are three yeses totaling forty-eight hours; here are twenty-six hours of committed ship work” is a capacity conversation. “I am overwhelmed” is a mood conversation.
Ask which drop they prefer if a new urgent item arrives. Let them choose the sacrifice explicitly. Shared visibility prevents the pattern where sleep, deep work, or a committed launch date always loses without anyone admitting it.
Managers can require cards for asks over two hours without becoming bureaucratic if the card stays five lines. The goal is tradeoffs, not paperwork theater. Teams that share cards quarterly see over-yes patterns by requester or theme—useful for staffing conversations that would otherwise stay vague.
Reading a quarter of cards for pattern
Archive cards for ninety days. Once a quarter, skim titles only: which work always wins, which always loses, which requesters assume infinite capacity. Patterns beat willpower lectures.
If every card shows the same dropped item—Friday focus blocks, documentation, mentoring—that is a role design signal, not a personal failure. Bring the pattern to a staffing or priority review with dates attached. Cards turn private tradeoffs into evidence.
Cards also expose optimistic hour estimates. If every card multiplies by 1.5 and still misses, your baseline estimates are fantasy, not your discipline. Adjust the multiplier before you adjust your sleep schedule again.
Some teams keep a shared folder of anonymized cards for leads only—useful when staffing plans ignore coordination tax. The folder is not surveillance; it is evidence that “just one more small project” has a cumulative shape. Evidence beats vibes in quarterly planning.
Hour estimates should include reading time, meetings implied by the yes, and rework risk—not only hands-on keyboard time. Underestimation is predictable; the 1.5 multiplier is a cultural admission that optimism exists, not a personal insult.
Memo discipline for leads who assign work
If you manage people, model cards when you assign work. When you hand someone a new initiative, ask them to fill what drops before end of day—not as punishment, as respect for finite capacity. You will learn which commitments on your roadmap are imaginary.
Leads can also write cards for their own yeses to executives. “Yes to board prep drops two customer calls this week” makes escalation honest. Executives often choose to defer board prep once the trade is named; they rarely choose when the trade stays invisible.
Cards do not require declining. They require visibility. A visible yes with a named drop is leadership. An invisible yes that silently kills deep work is how teams burn out while hitting every superficial request.
Individual contributors without formal power benefit most from cards. The memo gives you a neutral artifact in negotiations that would otherwise feel personal. “Here is the card” beats “I feel overloaded” in cultures that respect written tradeoffs.
Review date on the card is non-optional for yeses longer than a week. Without review, temporary commitments become permanent obligations you resent silently. Review is where you renew, renegotiate, or exit with data instead of guilt.
One card before the next big yes
Before you accept the next request longer than two hours, fill all five fields—including what drops—and send the card to whoever needs visibility. If the drop field stays blank, treat that as a no until something else is named. Workplace productivity ideas for general audiences, not HR policy or employment advice.