Should You Take the Job?
You've received a job offer that looks great on paper but comes with real hidden costs. This scenario walks you through a structured decision tree to uncover what you actually value, how much each factor is worth to you in real terms, and why our first instinct about "obvious" decisions is often wrong. No math required — just honest thinking about trade-offs.
The Situation
"The offer comes in: 20% more salary, but the commute is 45 minutes longer each way and the team culture seems a little off. Your gut says yes. Your gut might be wrong. How do you decide?"
🎯 Place Your Bets
Before we break this down, what do you think you'd do? Take the job, stay put, or negotiate? And what's the one factor that matters most to you?
🎯 Your Prediction
Locked in
—
Background
Decision trees are a way of mapping out choices and their consequences before committing to a path. The key insight from behavioral economics is that we're bad at evaluating trade-offs in the abstract — we need to convert them to comparable units. A 45-minute daily commute adds up to roughly 187 hours per year. At your current hourly rate, what is that time worth? Does the salary bump still look as large? This is called 'opportunity cost' thinking, and most people skip it entirely.
🔒 Lock in your prediction above to reveal the game
Your Result
You completed this scenario
—
Game results coming soon
Share your result — others can click through and play the same scenario.
💡 What This Reveals
We tend to overweight immediate, salient benefits (the salary number) and underweight ongoing, diffuse costs (daily commute stress, cultural friction). This is called 'focusing illusion' — whatever you're thinking about right now seems more important than it actually is. The antidote is to imagine yourself six months into the new job on a random Tuesday. What does that day feel like?
Reflect
"What would you need to know that you don't know yet to feel confident about this decision? What's the cheapest way to find that out before committing?"