---
summary: "New hire week-one knowledge requirements: four things every new hire must understand by end of week one, with manager as responsible owner."
usage_mode: auto
sort_order: 0
tags:
  - orbit
  - policy
refs:
  - orbit-company-overview
  - orbit-how-we-work
---

## New Hire Week-One Onboarding Policy

**Source:** Notion - People & Operating Norms, last edited 2026-05-07
**Owner:** Manager (not People Ops)

---

## Policy

Every new hire must understand **four things by end of week one**. The manager - not People Ops - is responsible for supplying this context.

## Required Week-One Knowledge

| # | What the new hire must understand |
|---|---|
| 1 | **What Orbit sells** - the core procurement workflow product and value proposition |
| 2 | **Why procurement workflow gets messy inside a customer** - the pain points that make Orbit necessary |
| 3 | **Which team handles which part of the customer lifecycle** - team lanes and ownership boundaries |
| 4 | **What their first useful project is** - a concrete, scoped piece of work they can contribute to immediately |

## Ownership

- The **manager** is responsible for delivering this context, not People Ops or a generic onboarding doc.
- If the manager cannot supply item 4 (first useful project) by day one, they should have it ready by end of day two at the latest.
- Items 1–3 can be covered via existing documentation; the manager should point to the right pages rather than re-explaining from scratch.

## Suggested Reading for Items 1–3

- Item 1 & 2: [[orbit-company-overview]]
- Item 3: [[orbit-company-overview]] (Team Lanes section)
- Operating norms and how decisions are made: [[orbit-how-we-work]]

---

See also: [[orbit-company-overview]], [[orbit-how-we-work]]
