data.day
onboarding / knowledge-management / sop / remote-work

Case: New Hire, Day 3, Still Asking Where Files Live

Onboarding is not about swag bags. It is about access. Why your new hires are failing and how to fix it with a 'Starter Path'.

Marta Clarity Marta Clarity

Stop The Scavenger Hunt

I watched a new Operations Manager start last week. By Wednesday, she had sent 14 Slack messages asking where to find the Q3 report.

Calculated at her hourly rate, plus the distraction time for the three people she pinged, that missing link cost the company about $400 in lost productivity. Multiply that by every new hire, every month.

The Chaos: The “Files Everywhere” Syndrome

We assume that because we know where the files are, everyone does. This is the “Curse of Knowledge.” The reality for a new hire is a digital labyrinth.

  • The Shared Drive: A graveyard of folders named “Project X - FINAL” and “Project X - FINAL FINAL.”
  • The Access Rights: “You need to request permission.” (The hallmark of a broken workflow).
  • The Oral Tradition: “Oh, ask Dave. He keeps that on his desktop.”

This friction destroys confidence. The new hire feels incompetent, not because they cannot do the job, but because they cannot find the job.

The System: The Starter Path

We do not need to clean the entire database to fix this. That is a trap. We just need to build a paved road over the mud.

I use a strict template called The Starter Path. It is a single document (Notion page or pinned Wiki entry) that is given on Hour 1. It contains three specific sections.

Do not give them the directory. Give them the shortcuts.

  • Link 1: The Organization Chart.
  • Link 2: The password manager invite.
  • Link 3: The current active project board (Jira/Asana).
  • Link 4-10: The specific files they need to touch this week.

Rule: If a link breaks, the new hire fixes it. That is their first contribution to the process.

2. The First 5 Tasks (Quick Wins)

Momentum is everything. We assign tasks that require navigating the system, but with clear instructions.

  • Task 1: Update your Slack profile photo.
  • Task 2: Read the “Communication Hygiene” SOP and click “I acknowledge.”
  • Task 3: Request access to [Tool X].
  • Task 4: Book a 15-minute intro with [Key Stakeholder].
  • Task 5: Find the “Q3 Report,” spot the error on page 2, and fix it. (I plant the error intentionally. It proves they have edit access and attention to detail).

3. The Decision Sandbox

Onboarding fails because people are afraid to break things. We give them a safe space to practice authority.

  • Scenario: “A client emails asking for a refund. Based on [Link to SOP], what do you do?”
  • Goal: They draft the response. They do not send it. I review it.

Summary

If you force a new hire to ask “Where is this?”, you have failed as an architect.

  • If they have the path, Then they can walk it alone.
  • If they walk it alone, Then you can do your own work.

Clear is kind. Ambiguity is expensive.

FAQs

Shouldn't new hires learn by exploring?

No. They should learn by doing. Exploring a disorganized drive is just confusion, not education.

It takes too long to organize the whole drive.

Do not organize the whole drive. Organize the 10 links they need today. Ignore the rest.

What if the links change?

Then the process owner updates the index. If no one owns the index, you do not have a team; you have a crowd.