How to requests time off from the organization 😃

You can inform any temporary or long-term offboarding to Gravity! → https://the-commons-stack.typeform.com/to/rCVsK5RK

Offboarding process in the TEC

Sometimes, we all need some time off to take care of other priorities. We comprehend the complexity of everyone’s life at this moment and we want people to feel there are safe ways to make rotations and transitions within the workflow of the organization.

These are the steps we propose for this process to go smoothly as possible. And we suggest giving a lot of praise along the way!

1: Make notification (verbal or in writing).

Regardless of how it was first communicated, it’s important to inform via the gravity typeform or to any Community Steward or Graviton the intention to take some time off (for a short or long period). It’s preferable to have this notification with 1 or 2 weeks in advance, so that we can continue smoothly with the next steps of the process.

2: Confirm transition date with Stewards.

Once the offboarding process is communicated, in the next stewards call, the issue will be added to the agenda, to discuss which will be the members that will take care of the tasks that are rotated, and other relevant decisions for the coming changes.

3: Transition work and shift priorities

During the next sprint planning call, the stewards should communicate the offboarding contributors current projects, assess what’s high-priority, and try to assign 1 (or more) member(s) to them. If no member is delegated, the rotating projects are shuffled into the work queues of others in similar roles. The main thing to watch out for is not to dump a ton of extra work on the rest of the team. If something’s critical, the team can stretch for a short period. We want to get back to normal workloads as soon as possible.

For Community Stewards. In a short term escenario, the stewards can search for another member in the organization to fill the role temporally. In a long term offboarding case, the stewards can decide to look for possible replacements in the broader ecosystem, or to make an official promotion to an interim delegate, after a testing period time if all parts agree.

We want to involve the offboarding member to be available for a transition session with the delegate, useful to wrap up any critical projects or help with complex issues if needed.

4: Announce the departure

As we foster transparency and rotation in good terms, its suggested to announce the offboarding process in this order:

First with the Stewards or Gravity, then to their working group, then if needed, to the whole community.

Before breaking the news to anyone, Check with the offboarding contributor and ask them if there’s a way that they want to frame the news. Sometimes, people are happy to share that they’re joining another company or starting a new project. In other cases, they prefer to keep all the details to themselves. We recommend following each one’s respective wishes.

If the offboarding member prefers to keep things private and anyone asks why it happened, any of the stewards can give a brief overview and express that it’s being managed privately.

5: Follow up

Gravitons or Community stewards can check and diagnose the reasons why the member offboarded and care for how they felt during the offboarding process and how they are doing in their new stages. Communicate that the doors are open for any contribution, and ask for insights to know how we can improve as an organization and our different processes.

Adapted to the TEC from https://usefyi.com/offboarding/

3 Likes

Use this!!!

I have been trying to follow this step by step for the two week trip i decided to make to Perú, and think that its being really helpful for me and for the Working group.

  1. I communicated weeks in advance my intention to take some time, after months working with all my heart.
  2. During the next sprint planning I made an issue with the intention of empowering some Gravitons to lead the Wg calls for my off period.
    Project Management and Software Development with GitHub | ZenHub
  3. @durgadas and @ddan are relevant contributors to the TEC, that can deep dive into some core topics of Gravity, like NVC, and decolonization/ unified thinking. This also helps to create new content for the next Graviton Training.
  4. I am happy to say that i love being part of the TEC and that I want to continue giving my best to this community and to Gravity, but i also wanted to recharge and take some time to have fun and connect with nature.
  5. Even though i haven’t been involved in all the activities i like participating, I continue being near the TEC and Gravity, i try to prioritize, schedule certain calls, collaborate async, and keep up with whats happening in the community.

Thanks everyone for your help and understanding! I feel recharged and motivated.

2 Likes