Two Weeks in Borrowed Shoes: Reading Your Collaboration Stack Through a New Starter's Eyes

Every new starter runs an audit of your collaboration tools whether you asked them to or not. They just don't call it that. Over their first fortnight they quietly collect a list of dead ends: the channel that last saw a message in March, the folder labelled Final Final v3, the recurring invite with nine attendees and no agenda.

Nobody ever reads that list. By week three the new hire has learned the workarounds, stopped noticing the friction, and the whole mess is preserved intact for the next person through the door.

The join-up audit is a modest attempt to catch the list while it still exists. Two weeks, a handful of questions, one shared document. It costs about an hour of someone's attention and pays back every time you hire.

Why the first fortnight is the only honest window

Beginner's eyes decay faster than most people expect. Research on onboarding consistently finds that new starters notice far more in their first ten working days than in the ten that follow, and the reason is simple: noticing is expensive. Once you know where the shared drive lives, your brain stops asking whether it should live there at all.

That's why the audit has to be lightweight and time-boxed. You're not asking for a consultancy report. You're asking someone to jot things down as they go, while the bewilderment is still fresh and slightly annoying.

Day one: the access obstacle course

Almost every audit starts with permissions, and almost every team is surprised by what turns up. Common findings:

• A starter who can see the finance channel but not the project channel they were hired to work on.
• A shared drive that's open to the whole company because nobody wanted to be the person who locked it down.
• Two logins for what everyone insists is one tool.
• A guest account that was set up for a contractor in 2023 and never retired.

None of these are dramatic. All of them cost time, and the time is usually spent by the newest, least confident person in the room, who is also the least likely to complain about it.

Ask your starter to keep a note of anything that took longer than five minutes to get into. That list is your permission backlog.

Days two to five: the document graveyard

By the end of the first week, most people have found the documents they need and about four times as many they don't. This is the point where orphaned content becomes visible: files with no owner, no date, and no obvious status, sitting next to the version someone actually relies on.

The tell is a question your starter asks out loud. Which of these is current? If the answer needs a meeting, you've found a gap worth closing.

A quick triage that works on most teams:

• Anything unopened in twelve months goes to an archive and gets a review date.
• Anything without a named owner gets one, even if the owner is a team rather than a person.
• Anything called Final gets renamed to include a date and a status.
• Anything that duplicates a living document gets merged or retired, not both.

Week two: meetings and the handover gap

The second week is where meeting culture shows itself. New starters see the calendar more clearly than anyone, because they haven't yet been socialised into accepting the strange bits.

Watch for three patterns: invitations with no agenda, recurring meetings whose purpose nobody can articulate, and status updates that happen in a call when they could have happened in a message. None of these are catastrophic on their own. Stacked together across a fortnight, they're the reason your team feels busy and still can't say what it shipped.

The handover gap is the other big one, and it's the quietest. It shows up as work that falls between two people: a project that was someone's before they moved teams, a process that lives in one person's head, a client relationship with no documentation behind it. A starter notices this because they're the one asking who to speak to, and the answer keeps being a name rather than a channel.

The checklist you can actually run

Keep it to a single page. Something like this works well, filled in by the new starter over their first ten days:

• Access: anything that took more than five minutes to get into.
• Discovery: documents you were sent twice, or couldn't find when you needed them.
• Channels: any channel whose purpose you had to ask about.
• Meetings: any invite with no agenda or no obvious decision attached.
• Handovers: anything you were told verbally that should probably be written down.
• Wins: anything that genuinely worked well, because those are worth protecting too.

Review it at the end of week two with the hiring manager and whoever owns your tooling. Twenty minutes is plenty.

What to fix first

Resist the urge to rebuild everything. In practice, three fixes tend to deliver most of the value:

Give every channel a one-line purpose, written in the channel description, and archive the ones that can't earn one. Rename or retire orphaned documents so the current version is obvious from the filename alone. Publish a permissions baseline: what a new starter gets on day one, who grants exceptions, and how long it should take.

That's it. Boring, unglamorous, and worth more than most tool migrations.

Make it a habit, not a project

One audit is a data point. The value comes from repetition. Add the checklist to your onboarding pack, ask every new starter to fill it in, and read the results together at the end of their first month. Within a year you'll have a pattern rather than a snapshot, and you'll spot the drift before it turns into a two-week scramble for access.

The best time to see your collaboration stack clearly is before you've got used to it. Borrow a new starter's eyes while you still can.