What a New Starter's First Week Reveals About Your Intranet

Here is a small experiment worth running if you own an intranet. Find whoever joined your organisation most recently, buy them a coffee, and ask them one question. "In your first week, when you didn't know something, where did you look?"

Ask enough people and the answers are remarkably consistent. They looked on the intranet, once. Then they asked the person sitting next to them, forever.

That is worth sitting with, because a new starter is the most honest reviewer your intranet will ever get. The rest of us have adapted. We know the HR policy is not where it says it is, that the org chart has not been right since the restructure, that the news section is where announcements go to yellow at the edges. We have built workarounds so old we have forgotten they are workarounds. A new starter has none of that scar tissue. They take your intranet at face value, and their first week tells you exactly what that face is worth.

The intranet is the first colleague they meet

Think about what week one actually looks like now. In a hybrid organisation, there is a decent chance your new starter's first day happens at a kitchen table. The laptop arrives, Teams lights up, and somewhere in the welcome email is a link to the intranet, the thing that is supposed to explain how this place works.

Before they have had a single meaningful conversation with a colleague, they have formed an impression from that page. If it is clean, current and obviously cared for, the message is that this organisation has its act together. If it is a wall of dead links and a "Merry Christmas from the SLT" banner in July, the message is just as clear, and no induction presentation will fully talk them out of it.

This matters more than we like to admit. Gallup has found that only about 12 percent of employees strongly agree their organisation does a great job of onboarding new people. The research on the other side of that coin is just as striking: Brandon Hall Group found that a strong onboarding process can improve new-hire retention by 82 percent and productivity by over 70 percent. Nobody is claiming the intranet is all of onboarding. But it is the part that is on duty at 9pm on the Sunday before they start, and it works the whole first month without ever being too busy to answer.

What they are actually looking for, and rarely find

The good news is that new starters are not asking for anything exotic. Week-one questions are almost embarrassingly predictable. Who are these people, and who does what? How do I book leave, claim expenses, report something broken? What is actually going on here this month? And where is the current version of the policy I have just been told to read?

Four questions. People, process, news, knowledge. That is the whole brief.

And yet on most intranets, each one is a small expedition. The who's who is a stale directory with photos missing and job titles from two reorganisations ago. The how-do-I content is scattered across a dozen sites, each owned by a team that thinks another team owns it. The news is either absent or so relentlessly corporate that nobody can tell what actually matters. And the policy exists in four versions, three of them confidently wrong.

None of these are hard problems individually. They persist because nobody experiences them all at once, except the new starter, who experiences nothing else.

The hidden cost of "just ask someone"

When the intranet fails the week-one test, the fallback is always the same: just ask someone. It feels harmless, even friendly. It is neither.

Every question a new starter cannot self-serve becomes an interruption for the colleague next to them, and week one generates dozens. Multiply that across every hire, every year, and "just ask someone" is a quiet tax on your most experienced people, paid in the exact weeks you are also asking them to make the new person feel welcome.

Worse, it teaches the new starter a lesson on day three that they will act on for years: the intranet is not where answers live. Adoption problems do not usually start with a bad launch. They start with a bad first week, one hire at a time. The person who learned in week one that the intranet cannot be trusted is the ten-year veteran who never checks it, and who trains the next new starter to do the same.

The week-one test

So here is the practical part, a test you can run this afternoon without a survey or a project code.

Open your intranet as if you started on Monday.

1. Can you find a current, believable picture of who's who, with faces rather than initials in grey circles?
2. Can you get from the homepage to "how do I book annual leave" in two clicks, and is what you find dated this year?
3. Does the news section contain anything a normal person would care about, published in the last fortnight?
4. If you search for your most important policy, does the top result agree with what HR would actually tell you?

Four checks, ten minutes. If you pass all four, your intranet is doing its job for the people who need it most. If you fail two or more, you do not have an intranet problem so much as a first-impressions machine working against you, quietly, on every single hire.

That fourth check is the one that tends to sting. Finding a policy is not the same as finding the right version of it, and most organisations cannot prove which version anyone actually read. If that lands close to home, it is worth reading how policy management in SharePoint closes the gap between publishing a policy and knowing it was seen.

Where Athena fits

An honest note about our angle. We build Athena, a SharePoint enhancement platform for Microsoft 365, and the week-one test is more or less our product spec. A people directory that is genuinely pleasant to browse. A structured knowledge base where the how-do-I answers live once, with visible owners, instead of four times with none. News that looks like something you would actually read. All of it light, current and cared-for out of the box, because the out-of-box look is the first impression, on a simple per-tenant subscription, so it works the same whether you hire five people this year or five hundred.

But whether or not you ever look at Athena, run the test. Buy the coffee, ask the question, and listen carefully to where your newest colleague looked second, because that is where everyone will be looking in a year.

Where to go next

If the week-one test found gaps, the two that cost you most are usually findability and policy currency. Read what separates a great intranet from the one people work around, see how a SharePoint knowledge base keeps the how-do-I answers in one place, and when you want to see a week-one-ready intranet on your own tenant, you can try it free for 21 days.