TL;DR
If you answer "Sure" in under a minute, you just made a portfolio decision without seeing the portfolio.
That is how teams get crushed.
Not by big launches. By small adds that collide with big work.
This post gives you two tools you can use today: a 5-line reply you can copy and paste, and a 3-scenario card that makes tradeoffs obvious.
The problem is not the request
The problem is the collision.
A collision is when new work lands on top of critical weeks:
- Speaker deadlines
- Venue contracts
- Build weeks for a flagship
- Travel weeks
- Exec reviews
You can handle a lot. You cannot handle everything at the same time.
Tool 1: The 5-line reply template
Copy this into Slack or email. Fill in the blanks.
Line 1: Start with yes to the goal
"Yes, we can support this."
Line 2: Name it in portfolio language
"This is a new [event / scope add] that behaves like a Tier [1 / 2 / 3 / 4]."
Line 3: Give the rough cost
"It will take about [X] hours and [Y] weeks of lead time."
Line 4: Name the collision risk
"It collides with [flagship build week / speaker deadlines / roadshow wave] in [month]."
Line 5: Offer the decision
"I can do it one of three ways: Absorb, Swap, or Shift. Which do you want?"
That is the whole move.
You are not saying no. You are making the tradeoff visible.
Tool 2: The 3-scenario card
Use this as your decision card. Keep it simple. Do not overbuild it.
| Scenario | What happens | Use when | The cost |
|---|---|---|---|
| Absorb | Add it, keep everything | Calendar is clear | Extra hours, quality risk |
| Swap | Add it, cut something else | Already packed | Someone loses a nice-to-have |
| Shift | Move date or reduce scope | Timing is the problem | Happens later or smaller |
Key Insight: If you do not pick a scenario, you picked Absorb.
Quick win: run this in 5 minutes
Pick the newest request in your inbox.
- Label the request Tier 1 to Tier 4.
- Write an hours estimate. Keep it rough.
- Name one collision week.
- Send the 5-line reply.
- Make them choose Absorb, Swap, or Shift.
That is a Portfolio Manager move.
Common mistakes
Mistake 1: You over explain
Leaders do not need a story. They need options.
Mistake 2: You hide the collision
If you hide the risk, your team pays it later. Name it early.
Mistake 3: You offer only one path
If you only offer Absorb, you train people to overload you. Offer all three every time.
How to talk about this
When you say "I don't think we can do that," your boss hears "You are not a team player."
When you say "We can do it three ways," your boss hears "You have a plan."
| Instead of... | Try... |
|---|---|
| "I don't think we can do that." | "We can do it three ways. Which works for you?" |
| "That's going to be really hard." | "That collides with flagship build week. Absorb, Swap, or Shift?" |
| "We're already at capacity." | "We can Absorb it with quality risk, or Swap it for the Austin dinner. Your call." |
Key Insight: You are not saying no. You are making them own the tradeoff.
Frequently Asked Questions
What if my boss just says "make it work"?
That is still a decision. They picked Absorb. Now you have permission to name the risk: 'Got it. We will absorb it. That means quality risk during flagship build week. I will flag it if we hit trouble.' You are not arguing. You are documenting.
How do I know if it is really a collision?
A collision is when new work lands on the same weeks as critical milestones: speaker deadlines, venue contracts, build weeks, travel, or exec reviews. If you are not sure, check your calendar for the 3 weeks before any Tier 1 or Tier 2 event. Those are your collision zones.
What if I do not have tier benchmarks yet?
Use rough estimates. Tier 1: 400+ hours. Tier 2: 100 to 200 hours. Tier 3: 30 to 60 hours. Tier 4: under 15 hours. You do not need perfect numbers. You need defensible numbers. After 3 events, replace these with your real data.
The bottom line
You are not the person who says no. You are the person who shows the options.
Next time someone asks for "one more event," send the 5-line reply. Make them choose. That is the shift.
Want the tool to do the hard part?
The Collision Map shows you which weeks are at risk, compares Absorb vs Swap vs Shift, and exports a plan you can share.
Run a scenario in 5 minutes