Skip to article
Bridge

Onboard a new hire with the meetings they missed

A new hire's hardest gap is context: why things are the way they are. Pick the handful of past meetings that explain it, share them in one place, give the new hire a short reading plan, and let them ask questions of that history before they ask a person.

The job: context, not a recording archive

Docs explain what the team does. Meetings explain why: the trade-offs, the customer that changed a plan, the idea that was tried and dropped.

A new hire doesn't need every meeting. They need the few that hold the decisions they will run into in their first month, and a way to look up the rest.

Pick 5 to 10 meetings that explain the work

Choose meetings by the decision they hold, not by date. A useful set usually covers:

  • The last planning meeting, so they know the current priorities and what was cut.
  • One or two meetings where a big decision was made, including the objections.
  • A recent customer or stakeholder call that shows who the work is for.
  • A retrospective or postmortem, so they hear what the team learned the hard way.
  • The meeting that kicked off the project they are joining.

A first-week reading plan

Spread the history over the first week so it lands next to real work. An example plan:

DayRead or watchWhat they should come away with
1The notes from the last planning meetingCurrent priorities and what is out of scope
2The project kickoff notes and transcriptThe goal, the owner and the first constraints
3One decision meeting, transcript includedWhy the team chose its approach, and what it rejected
4A recent customer or stakeholder callWho the work serves, in their own words
5A retrospective, then a check-in with their managerOpen questions, answered by a person

Let them ask the history first

New hires hold back questions they think are basic. Asking the meeting history first lowers that cost and leaves the harder questions for people.

Good first questions are narrow and point at a meeting:

  • "Why did we stop supporting the legacy export?"
  • "Who owns the billing integration, and when was that decided?"
  • "What did the customer on last month's renewal call ask for?"
  • "Which ideas were raised for the onboarding flow and not chosen?"

Save the answers you give twice

Each new hire asks some of the same questions. When you answer one for the second time, save it so the next person gets the same answer.

Set the answer's visibility to Workspace, or limit it to a group on Business and Enterprise plans. A Private FAQ stays with you, so the next hire won't get it.

Keep these answers short and dated. Review them when the team changes how it works, so the next hire doesn't learn a retired process.

Doing this in Bridge

  • Create a space for onboarding, then open each chosen meeting and choose Add to Space.
  • Share the space with the new hire. Sharing a space with others needs a paid plan, and invitees need a Bridge account.
  • Give them the Member role if they should use the Space Assistant. Guests can view meetings and files but can't use the Space Assistant.
  • Add files such as a team handbook to the space's Files tab. The Space Assistant answers from the space's meetings and files.
  • Save repeated answers in Memory → FAQs with Workspace visibility (or a group, on Business and Enterprise). The Assistant can use them, and agents use them only when their Memory FAQs tool is turned on.
  • Memory, including FAQs, is only available on paid plans.

What to leave out of an onboarding space

Everyone with access to a space can open every meeting in it. Leave out meetings the new hire shouldn't see, such as performance reviews or hiring conversations.

If the new hire already has a role on a meeting, the higher of that role and their space role applies while the meeting stays in the space.

Leave something for the next hire

Record the onboarding sessions themselves, such as the architecture walkthrough or the customer overview. Add the good ones to the onboarding space.

After a month, ask the new hire which meetings helped and which didn't. Swap out the weak ones, and the set gets sharper with every hire.

Sources & further reading