Onboarding Atlas

agents running
multi-agents reasoning
multi-agents reasoning
employee welcome page

When I joined my new company, my onboarding was very slow, confusing, and painful. We all experienced that, right?

The docs were stale; for the first few days, I didn't have the staging environment configurations or the right GitHub permissions, and knowledge was tribalized, i.e., only specific people knew. The people I was supposed to meet in the first week got busy with something else; the senior I was supposed to get help from got stuck in a DevOps failure. We all go through this at some point, right?

Eventually, I was asked to document my experience and help improve onboarding — first for engineering roles, and then everyone else. I usually spend 1 week per new hire to help them get onboarded properly. I started recording my decisions, approach, bottlenecks, etc. to streamline the process.

I realized everything related to onboarding experience is just this: Knowledge + People => Productivity + Navigation

Existing environment (Onboarding Experience)

Knowledge: wiki, slack, github, jira tickets, stale docs, tribal knowledge among team silos, calendars
People: who does what, schedules, what they're busy with, when they've capacity

What matters to new hire (Onboarding Experience)

Productivity: how can they be productive on day 1, week 1, month 1?
Navigation: how can they navigate knowledge + people, i.e., who they reach out to, who is next best person to ask if the current one got busy?

Usual, day-to-day workflow for those handling onboarding looks like:

pre-plan: If 3 new people start on Monday, what specific permissions/access do they need ready? (emails, specific docs, slack, etc.)
suitable task for day 1: A person starting today, looking at his resume and interview feedback, what is one specific task he can finish today or tomorrow that'll make him feel productive?
re-routing meetings: A person who is to meet Senior A at 2 pm for intro, but if Senior A gets stuck on something important, who is the next best person available to induct the new joinee in team?
re-routing help: A person who is stuck on a github issue, and has got no response to his slack question- who is next available person to nudge and reply, based on calender details?
nudging: A wiki and slack-discussion disagree on some configuration; then who is right person to nudge and update the docs?
memory: Keeping a log of where a particular hire is after a few weeks, and helping him based on context and observations.

Each of these questions can actually be answered by Agents well (multi-agents, re-routing, memory). And that is what the "Onboarding Atlas" platform is about, i.e., to help employees navigate knowledge and people in the company, so that they feel productive and at ease, be it day one, day seven, or day thirty.

New hires feel productive every day — company resources are utilized properly — we spend less human time & effort on repetitive onboarding tasks, as well as reduce early attrition rates. Agents do the onboarding, and employees focus on business.