Here are three field-tested ways to use a sabbatical to rethink priorities, test your assumptions, and return with clearer capital-allocation decisions.

Draft a One-Page Asset Map Before You Leave

I used to disappear for a few weeks with a vague intention like "think bigger," "reset," or "read more." Then I'd come back and get swallowed by the same quarterly noise, and the portfolio looked exactly like it did when I left. What finally changed it for me was committing to one physical page I could fold into a notebook: an Asset Map, i.e., a map of which businesses and initiatives the company is investing in, maintaining, or allowing to decline.

Here's what goes on mine, in thick pen so I can't weasel around it later.

• Asset list: 8-12 items max. Products, platforms, data sets, distribution channels, key partnerships, or even a customer segment that behaves like an asset because it funds everything else.
• Owner and cadence: one accountable leader, plus how often decisions happen in practice (weekly, monthly, quarterly). The cadence can reveal how much management attention the initiative actually receives. If something is strategically important but rarely receives management attention, that may indicate a mismatch between its stated priority and the resources devoted to it.
• Capital story in one line: where the money goes and what must be true for it to pay back. I force myself to write it as if I'm explaining it to a board member in an elevator.
• One risk you can feel in your stomach: the thing that makes you check Slack on vacation. Put it down anyway.

Then I draw three boxes at the bottom: Keep Feeding, Hold, Stop Pretending. The point of the sabbatical is to return with cleaner priorities and fewer half-alive initiatives that drain leadership attention. When I'm done, I snap a photo, email it to myself, and I do not touch it again until week two of the break. That distance is the whole trick. When you reread it away from the office, you notice the weird stuff: the asset with the biggest headcount but no decision cadence, the "priority" nobody owns, the partnership you keep funding because it's socially painful to unwind.

Use a Two-Call Rule to Test What Deserves More Capital

Early in my career, I'd come back from time off with a notebook full of "insights" and a head full of urgency. It felt productive, but it wasn't. The insights were usually just opinions that hadn't been stress-tested against the people who'd have to execute them. Now, if I'm taking a sabbatical with any intention of shifting strategic asset priorities, I do one thing that looks almost boring: I schedule two calls and use them to pressure-test the assumptions behind my priorities.

The rule is simple: pick two people who see the business from different angles, and ask them the same three questions about the same asset. One call is usually someone who lives in the numbers (CFO, FP&A lead, or a finance-minded GM). The other is someone who lives in the customer reality (head of sales, support leader, product leader who still listens to calls). I keep it to 30 minutes each, and I make it clear I'm not asking for a status update. I'm asking for a read.

1. Where is this asset compounding, and where is it just consuming? I want specifics: pipeline quality shifts, churn patterns, unit economics drift, roadmap drag. Not momentum.
2. What would you cut first if you had to protect only one thing here? Their answers can reveal which parts of the business they see as essential.
3. What decision are we avoiding because it's politically expensive? This is where the truth leaks out: the legacy SKU nobody wants to own, the partner relationship held together by a personal friendship, the platform rewrite that keeps slipping because it's easier to fund the next feature.

I take notes by hand, then I translate them into one line per question, per person. If both people independently identify the same constraint or opportunity, I treat that as a signal to investigate it further before changing the allocation. If they disagree, I don't rush to pick a side. I write down what would settle it: a single metric trend, a cohort analysis, a pricing test, a renewal pattern by segment. That becomes my first week's work.

The exercise also forces me to practice making decisions from competing perspectives rather than relying on a single view. You're comparing competing views without turning the exercise into a marathon of meetings.

Come Back With an Investment Committee Memo You Can Defend

I don't want to return from a sabbatical and try to sell a new set of priorities from a presentation alone. If the goal is to rebalance strategic assets, I need a format that forces tradeoffs onto paper. So I come back with an Investment Committee memo. Even if you don't have a formal IC, you can use the structure. The trick is that the memo is written as if someone skeptical will try to poke holes in it, because they will.

Mine is five sections, and I keep it to two pages, so it has to be sharp.

• 1) The asset thesis: one paragraph on what we're trying to build or protect. Name the asset plainly. If you can't name it, you can't fund it.
• 2) The capital move: a concrete shift: +$X to platform reliability, -Y headcount from a legacy line, pause a region launch, consolidate tooling. No invest more language.
• 3) The leadership behavior it requires: this is the development angle. Who has to say no, what meeting cadence changes, what metrics we stop obsessing over. I call out the uncomfortable bit, like executives not jumping into every escalation channel.
• 4) The kill criteria: what would make us reverse course in 90 days? Not vibes. A measurable trigger: gross margin erosion beyond a set point, adoption below a defined threshold, uptime not improving despite spend.
• 5) The second-order cost: what breaks elsewhere. Sales capacity shifts, support load spikes, partner fallout, and a temporary dip in bookings due to pausing a shiny feature. This section keeps you honest.

Then I do one more thing that feels small and ends up mattering: I add a short appendix called "What we are not funding". It's three bullets. It prevents the classic executive return-from-leave problem where everyone hears your new priority and assumes it sits on top of all the old priorities. It doesn't. Something has to come off the stove.

When I walk back into the first senior staff meeting, I send the memo the night before, ask people to mark it up, and I start the meeting with, "Tell me what you think I got wrong."