Diagnose before deciding to leave
Giving notice is hard to reverse, so evidence should come first. Separate dissatisfaction into tasks, influence, role conditions, environment, growth, and meaning. One bad week or project proves little; look for a recurring signal and its direction over time. An energy journal records work, people, context, engagement, and the state afterward. It distinguishes a structural problem from temporary frustration and shows what to expand, reduce, or investigate.
Separate negotiable conditions from system constraints. Tasks, boundaries, interaction rhythms, and authority may change; economics, the nature of the business, company strategy, and market constraints often will not. A role also needs workable relationships, meaning, autonomy, competence, and connection. If a sustainable configuration can be negotiated and tested, leaving is unnecessary. If the central contradiction lies beyond practical control, another context becomes a grounded option rather than an emotional escape.
Prototype the next role before the commitment point
Before searching for a title, build a career retrospective: turning points, scale of responsibility, recurring themes, capabilities gained, costs paid, and outcomes created. This is not a promotion chronology but evidence of the problems a person can solve. Describe the target role through accountability, decisions, scale, and outcomes, then connect it to a two- or three-year direction. Opportunities become comparable even when companies use different titles.
Run reversible tests before the final choice. Inside the company, try another project, a temporary function, or informational interviews with domain owners. Outside, calibrate against the market through mutual interviews. Ask why the role exists, what mandate and resources it has, who supports change, and how success will be judged. An internal move lowers adaptation risk, but reputation and proven results create room for the experiment—not a wish for a new title.
Transfer the ability to lead, not a folder of documents
Every outcome requires a handover because even a redesigned role releases some responsibility. Map decisions and authority, people, systems, operating rhythms, risks, and informal connections. The last layer is easy to miss: an experienced leader often becomes an invisible information router. Communication follows an order—align timing and the explanation with the manager, tell key colleagues and direct reports personally, then address the team. The public story should remain calm and consistent.
After notice, the former owner becomes an adviser: explaining decision history, risks, and options without starting long commitments or leading from the shadows. Transfer decision rights first and let the successor make real choices before the final day; then add context, relationships, rhythms, and access. Stop low-value initiatives instead of leaving noise. The exit is complete when the team acts without its former leader's invisible presence and any later help is time-bounded and requested.
What to take away
- 01The last 90 days are a planning horizon for a managed transition, not a mandatory duration or a resignation countdown.
- 02A target role is clearer when defined by accountability, decisions, and outcomes rather than title or status.
- 03Internal and external options should be tested in parallel through reversible experiments before the hard-to-reverse decision point.
- 04A handover is complete when the successor makes decisions independently and the team no longer depends on the predecessor's hidden work.
Sources
- Local transcript of YouTube's automatic Russian captions
- Bilingual episode slides
- YouTube live recording
- VK Video recording
- Podster audio edition
- Yandex Music audio edition
- Apple Podcasts episode