The holiday-potluck “sure” is already typed, and the quarterly analysis tab is still open behind it. The cursor blinks right before you hit send, and you remember the last time you said yes to a last-minute team event without checking what else was on your plate. The half-finished analysis for your director is due Thursday, and you also promised your roommate you’d pick up their new bike from the shop the same night as the potluck. Your thumb hovers over the trackpad, and you pause instead of clicking send.
List the two competing choices you’re choosing between right now
You pull out the scratch notebook next to your laptop, and write only the two options in front of you, no extra fluff. The first option is hitting send on that “sure” reply, committing to bring a vegan lentil casserole to the team potluck next Wednesday, and attending for the full 2 hours. The second option is deleting that line, typing a polite note that you’re swamped with the quarterly analysis deadline so you can’t make it this quarter, and moving on with your current work. Most yes replies only count visible hours at first glance: you initially thought the potluck would only take 2 hours out of your week, not the extra time tied to prepping the dish, traveling to and from the office off-hours, cleaning the baking dish when you get home, and scrolling through 30 minutes of team potluck photos later that night to catch up on what you missed if you leave early. You don’t add those extra costs yet, just lock in the two core choices so you don’t get distracted by hypothetical middle-ground options that don’t actually exist.
Calculate the hidden time cost for each choice
Now you go line by line for each option, counting every minute you will spend on tasks tied to that choice, even the ones that feel too small to mention. For the potluck yes, you add 45 minutes of prep time to make the casserole, 20 minutes to stop at the grocery store on your way home from work tomorrow, 15 minutes to clean the baking dish after the event, and 10 minutes of travel time to and from the office that night, adding up to 3 hours and 30 minutes of total time, not the 2 you initially assumed. For the potluck no, you count only the 30 seconds it takes to type a polite reply, no extra time required. You also note the unspoken costs that show up two weeks later for each choice: if you say yes, you will have to push the first draft of your analysis to Thursday evening, which means you miss the bike pickup, have to pay the $25 hold fee for the bike shop to keep the bike an extra day, and leave your roommate without their primary commute method for 2 extra days. If you say no, the only unspoken cost is minor temporary FOMO when you see team photos pop up in the Slack channel later that week. You don’t weigh these costs yet, just write them down so they’re not hidden when you make your call.
Log the tradeoffs in a single reference table
You build a quick table right in your scratch notebook, or in the notes app you use for to-do items, so you can see all tradeoffs side by side. The table only includes columns you care about for this specific choice, no extra fields that waste your time. You fill it out as you go, marking illustrative numbers for each row so you can reference the exact math later if you second-guess your call:
| Choice you’re considering | Total time required | Work you will drop to make space | Unspoken non-time costs |
|---|---|---|---|
| Say yes to team potluck | Illustrative example: 3.5 hours | Finish first draft of quarterly analysis 1 day late, skip roommate’s bike pickup | $25 bike shop hold fee + roommate frustration, delayed director feedback on analysis |
| Say no to team potluck | Illustrative example: 30 seconds | No work dropped | Minor temporary FOMO from missing team inside jokes |
| Add optional 1:1 check-in with new intern next Tuesday | Illustrative example: 1 hour | Cancel 1 hour of dedicated deep work block scheduled for that morning | Intern waits 3 extra days for your feedback on their onboarding project |
This list explicitly names the work you will drop for every yes you consider, so you don’t pretend you can “make time” for extra commitments without pulling time from something else that matters. Once the table is filled out, you pick the choice where the tradeoffs feel acceptable for your current priorities. Today, you decide the $25 fee, delayed analysis, and annoyed roommate aren’t worth the potluck, so you delete the “sure” line, type your polite decline, and hit send.
Note the early warning signs of a misaligned choice
Even if you fill out the full list before you make your call, you might realize a few days later that you picked the wrong option. The most common early warning sign is when you find yourself rearranging three or more existing commitments to make room for the new yes you sent. For example, if you had decided to say yes to the potluck, you might realize two days later that you forgot you have a dental appointment scheduled for the same Wednesday afternoon, leaving you with even less time to finish the analysis before the deadline. When this happens, remember that existing overcommitments you can still unwind are always easier to fix than pushing through a choice that will derail your whole week. The small fix here doesn’t require a long, apologetic explanation: you can send a 2-sentence text to the potluck organizer saying you have a last-minute conflict, can’t make the event anymore, and will drop off a pack of sparkling water for the group on your way to the dentist if that helps. This cuts your total time commitment for the potluck from 3.5 hours to 10 minutes, no hard feelings, and you don’t have to rearrange your entire schedule to make up for the missed time.
Save your tradeoff notes in the notes app you open every morning
You save the filled-out table to the top of the daily notes file you open first thing when you sit down at your desk, so you don’t have to build a new list from scratch every time you get a new request. If you want a blank copy to reuse for future choices, you can find one on Find Core Insight to skip formatting the table yourself. The only rule you follow for every future request is that you name the work you will drop before you send the next yes, no exceptions. Next time you see a Slack message, email, or text asking you to commit to a new event, project, or favor, you open the saved list first, fill in one new row for the ask, and make your call in 2 minutes flat, no overthinking, no last-minute regret when you realize you overbooked yourself again. You close the potluck email thread, tab back to your quarterly analysis, and pick up where you left off, no lingering guilt about the choice you just made.