A new hire's first two weeks usually go the same way: a dozen "quick sync" meetings, a scavenger hunt through old Slack threads for context that's technically written down somewhere, and a running list of questions they're too new to know who to ask. None of that is because the person is slow to ramp — it's because the context they need was scattered across other people's heads and individual files instead of somewhere they could actually reach it on day one.
If your team already keeps project work inside a shared AI workspace, onboarding doesn't have to mean recreating that context from scratch for every new person. The material — decisions made, files uploaded, prior work completed — is already sitting there; the new hire just needs a structured way in. This guide walks through six steps to get a new team member from "no context" to genuinely useful, using the shared project memory your team has already built up rather than starting them at zero.
What You'll Need
- Access to the shared Team Project(s) the new hire will be working in
- Admin or Owner permissions to add a new member and assign appropriate access
- A rough sense of which existing Projects and files are relevant to their role
How to Onboard a New Team Member with AI: 6 Steps
Step 1: Add Them to the Right Team Projects, Not Just the Team
Before anything else, decide which specific Team Projects the new hire actually needs — not the entire team's workspace by default. Onboarding goes smoother when someone starts with focused access to what's relevant to their role rather than being dropped into everything at once and left to figure out what matters.
Try this with Noumi: "Add [new team member] to the Q3 Campaign Project and the Client Onboarding Project, with standard member permissions."
Tip: Resist the instinct to grant broad access "just in case." Narrower, role-relevant access up front makes it easier for a new hire to know where to focus, and permissions can always be expanded later as their role grows.
Step 2: Let Them Ask What's Already Been Decided
Once they're in the relevant Team Projects, the single most useful first move is having the new hire ask directly what's already been established, instead of scrolling through file after file trying to piece it together themselves. Because the shared workspace already holds that project's context, the answer comes back grounded in the actual history — not a generic explanation of the project type.
Try this with Noumi: "Summarize the key decisions made on the Q3 Campaign so far — what's been agreed on, what's still open, and who owns what."
Example output: - ✅ Decision: Campaign launches August 26, targeting mid-market teams - ✅ Decision: Creative direction finalized — see brand brief in Project files - ⚠️ Open: Budget for paid social not yet confirmed - Owner: Messaging drafts — Sarah; Design assets — Marcus
Step 3: Have Them Review the Actual Files, Not Just a Summary
A summary is a fast starting point, not a substitute for the source material. The second step is pointing the new hire to the specific files in the shared Project — briefs, prior drafts, research documents — so they can go deeper on the parts most relevant to what they'll actually be doing.
Try this with Noumi: "Show me all the files related to the competitor research for this campaign, and give me a two-sentence summary of each."
Tip: Encourage new hires to ask follow-up questions about specific files rather than reading everything cover to cover on day one. The context is already there when they need to go back to it.
Step 4: Walk Through Any Recurring Workflows They'll Be Taking Over
If the new hire is inheriting a recurring task — a weekly report, a status update, a standing process — this is the point to walk through how it currently works before they take it over cold. Reviewing an existing workflow together surfaces the small habits and edge cases that rarely make it into written documentation.
Try this with Noumi: "Walk me through how the weekly client status update gets put together, step by step, using the last three weeks as examples."
Tip: If a workflow turns out to be one the new hire will run repeatedly, it's worth checking whether it's already saved as a reusable Skill — or flagging it to become one — so they're not rebuilding the same process from memory every week.
Step 5: Assign a First Real Task Inside the Shared Context
Reading and asking questions only gets a new hire so far. The fastest way to confirm they've actually absorbed the context is a small, real task inside the same shared Project — something with a clear, checkable output rather than a training exercise.
Try this with Noumi: "Draft the first section of next week's client status update based on this week's campaign progress, following the same format as previous updates."
Example output: A drafted section matching the established format, referencing the specific campaign details from the shared Project rather than generic placeholder content — a quick, concrete signal of whether the context actually landed.
Step 6: Set Their Ongoing Permissions Once Trust Is Established
After the first few weeks, revisit the access granted in Step 1. Most new hires start with narrower access than they'll eventually need — this is the point to expand it deliberately, project by project, rather than leaving it static indefinitely or over-granting it too early. This is also the moment to double-check what a tool's permission management should actually cover, since a new hire's expanding access is exactly the scenario permission structure is meant to handle cleanly.
Try this with Noumi: "Show me which Team Projects [new team member] currently has access to, and add them to the Vendor Management Project as well."
Tip: Revisiting permissions periodically — not just at onboarding — keeps access matched to actual role and responsibility as both evolve.
Pro Tips for Faster Onboarding
Front-load the highest-context Project first. If a new hire will touch multiple Projects, start them in whichever one has the richest existing history. It gives them a faster sense of how the team actually works together before they're spread across several.
Encourage questions over passive reading. A new hire who asks "why was this decision made" learns the reasoning behind the project, not just its current state — which matters more once they're making similar calls themselves.
Don't skip the first real task. Skipping straight from context review to full autonomy is where gaps in understanding usually surface too late. A small, checkable task in week one catches misunderstandings while they're still cheap to fix.
Onboarding shouldn't mean rebuilding weeks of context from scratch every time someone new joins the team. Noumi keeps that context living inside shared Team Projects from day one, so a new hire's first question can be about the work itself instead of what happened before they arrived.
