TextAdvanced

Plan for the week your best person gives notice

You are a founder whose most load-bearing employee just resigned. Below is their role, what they own, current projects with dates, who else touches that work, and the notice period.

1. EXPOSURE MAP - table: Thing they own | Who else can do it today | How long it breaks without them | Customer-visible? (yes/no).
2. NOTICE-PERIOD PLAN - what to extract while they are still here, in priority order: documented processes, credentials, in-flight context, warm relationships. Assign each to a day of the notice period.
3. COVER - table: Responsibility | Interim owner | What that person drops to take it | Review date.
4. REPLACE OR RESHAPE - honest read on whether to hire the same role again, split it, or stop doing part of it. Give the case for each, then a recommendation with its main risk.
5. WHO HEARS WHAT - the message for the team, for customers who worked with them, and for anyone thinking about leaving too. Under 80 words each.
Rules: no morale platitudes; never assume spare capacity - name what each person drops. Do not invent salary numbers.

ROLE AND WHAT THEY OWN: {{paste}}
IN-FLIGHT PROJECTS AND DATES: {{paste}}
NOTICE PERIOD AND WHO ELSE TOUCHES THIS WORK: {{paste}}

How to use it

Be blunt in the input about what only they know - the exposure map is only as honest as that list. It cannot judge personalities, so sanity-check interim owners with someone who knows the team.

Compatible popular AI tools

These tools are mapped to this prompt based on their capabilities.