Thread by @VaibhaviDesai

Sunsetting programs (/products /projects) is quite normal in today's fast growing companies. Here're my #ReflectionThreads on top five things to keep in mind, while sunseting a program (can be applied to 'transitioning a program' as well to an extent).
#Thread👇

Context - Various reasons to sunset a program could be:

- Change in strategy / vision / priority
- Lack of resources / budget
- Streamlining redundancies
- Unsatisfactory results
- Conflict b/w key stakeholders

... and more

1/ Don't get 'married' to a program (happens esp if it's your brainchild). Overthinking can disturb you, and will often make you take biased actions. Rather, think practically. Best to brainstorm ideas with an outsider who can see both sides of a coin.

2/ Try finding a new home for the program inside your company : another team, another format. Something that's x% aligning with the 'core' vision (with some changes) of your program.

Network, communicate, advocate, promote.

3/ Create a phased 'sunset plan' with clear priorities. Create an 'all-in-one' doc. Try reducing % of your time slowly (ideally sprd across few Q).

Communicate the plan as a part of 'closing the loop' with ALL your stakeholders in advance. This'll help set right expectations.

4/ Involve the team into deep dive discussion (self-awareness).

Take a moment to celebrate accomplishmnets, small wins and impact. Recognize the team & contributions (social-awareness).

If you've dedicated resources, mentor them finding a new role with aligned interests.

5/ Every program incorporates a unique way of managing things. Open source artifacts, templates and tools which can be useful to people running similar programs.

Showcase stories, if possible as 'case studies' of learnings, successes and faliures.

@threadreaderapp
unroll