LinkORB Engineering

Asynchronous stand-up

Onboarding into a any organization and team often has hurdles. Onboarding into a fully remote, asynchronous-first organization can present particular challenges. Often times, LinkORB new team members benefit from a recurring, asynchronous stand-up with their team lead or a senior team member when they first join.

Similar to the weekly status update and recurring asynchronous check-in processes, LinkORB follows a lightweight šŸstand-up process to support new team members.

Initiating stand-ups

Most commonly a team lead or senior team member will intitiate the stand-up process with a Cyans topic titled [Stand-up] team-member. For example, [Stand-up] msmith.

For the message body, something similar to the below is suggested:

Hi msmith - welcome again, we are excited youā€™ve joined the team!

Hereā€™s our stand-up topic. The idea is for you to kick-off your day with a short message in this topic specifying:

  1. Cool achievement(s) of yesterday
  2. Goals for today
  3. Anything currently blocking or where help is needed

I will track this topic and help you wherever I can.

Our current focus is:

  • Help you get the hang of our workflow and applying it to the [enter project here].
  • Help close tasks efficiently by raising issues early (you) and ensuring requirements, acceptance criteria, and supporting resources are clear (me).

As you get more comfortable working within the team, we may choose to reduce the frequency of our stand-ups.

You can read more about the process here.

Providing the stand-up

Each working day the new team member should send a message into the topic addressing the 3 requested items.

Best practices

  • Depending on the respective time zones of the stand-up participants, stand-up tranmission at the end of a working day may be more optimal.
  • As the team member gains confidence and efficiency working within the team, stand-up frequency is reduced or stopped.