I Hate It Here

Build vs. Buy: The Intranet Budget Convo You Can No Longer Avoid

There’s a chance you have people making crucial decisions based solely on whichever company document they found first. Are you comfortable with that?

Hebba Youssef · NOV 20

Sponsored by: Haystack

Your benefits policy deserves better than a link that will inevitably get buried in an inbox. Haystack connects company knowledge.

Unbury the answers

There’s a chance you have people making crucial decisions based solely on whichever company document they found first.

Are you comfortable with that??? 👀

Well guess what: if they’re not scraping Google Drive for the info they need, they’re asking you, and I dunno about you, but I don’t love answering the same question a dozen times in a week!

I actually get why employees keep coming to you with basic questions though, even if they’ve been answered before in emails and meetings.

Try remembering where you saw something at work a week ago while you were already busy…was it in Slack? Maybe an email?

Did someone mention it during a meeting where you were also answering a Slack message about a different meeting?

There's so much info coming at people that communication can start to feel like one gigantic blur! 😟

An update could reach an employee while they’re on leave, or disappear under a convo during lunch that somehow turns into a rabbit hole about whether or not you watched all of Will and Grace.

We've all opened a message intending to come back to it, then remembered it approximately 3 business weeks later.

An intranet gives that info a home employees can return to, and I kinda think of it like the drawer where you keep all your keys.

You shouldn't have to search the entire house every time you wanna leave, although I realize some of us are lowkey committed to that lifestyle.

📰 Company news and knowledge belong there, along with useful resources and a directory so people can figure out who does what.

Also, just so we’re crystal clear, I’m well aware that a LOT of HR folks don’t even like the term “intranet” anymore, and it’s probably the equivalent of calling a smartphone a telephone these days!

I’ll use it in this article just for context reasons, but I’ve seen plenty of fun alternative names, including:

  • The Mothership
  • The Matrix
  • Employee Experience Platform (EXP)
  • My[CompanyName]
  • The Backoffice

💡 Pro tip: A lot of this comes down to your own creativity. Even something like a company-wide naming contest or poll can help build early excitement and a sense of ownership!

Putting the semantics aside for a sec, let’s address the elephant in the room that people inevitably ask when it comes to intranets:

“We can just build one of these ourselves…right?”

It’s a fair question, so I wanna highlight some key differences between buying and building an intranet, what you'd be agreeing to maintain if you did build, and how the updates you publish will reliably reach people.

Who the Hell Owns This Thing After Launch?Copy anchor linkCopied

image5.gif

I would love to sit in on the convo where agreeing to build an intranet eventually gives you the realization that you have to update and support it INDEFINITELY.

😮‍💨 Yep, that’s right, getting an intranet live is the beginning of the commitment! 😮‍💨

Once employees depend on it, somebody has to keep it working, even when that somebody has another deadline and would really prefer everyone stop clicking things.

The reality is that security reviews can take time, connected systems will inevitably change, and an integration that worked last month could suddenly need attention.

Eventually, someone might want AI features because a competitor mentioned them in a webinar.

Meanwhile, an employee can't log in, and they have no idea why! 🙄

You need an answer for who handles all of that, along with time in their schedule to handle it…otherwise HR gets to explain why the tool everybody was told to use is currently waiting behind 17 other priorities.

A custom build can make sense if your requirements warrant it and you have people dedicated to the work.

Ask what happens when the original developer leaves, though. Most people kick that can down the road until it becomes a very unpleasant day somewhere in the future. A ticking time bomb, if you will.

And if the plan involves customizing SharePoint or Google Sites, you're still building!

You might already pay for the software, but someone still has to organize the experience and keep your changes working!

Haystack's SharePoint comparison does a good job of explaining why storing documents and running an employee intranet involve different work.

There's a budget question I would put in writing: what happens when this needs work 6 months from now? Get specific about who has the hours available and what gets delayed to make room.

One time I had to put in an engineering ticket every time I wanted to edit the language on our career site… that was something.

Your engineers probably have opinions about being permanently assigned to the company announcement board…

They should get to share those before someone includes their availability in a slide deck and calls the whole project basically free.

I'd also count the hours People Ops spends waiting for a technical change. Having to plead your case every time you need to update your own homepage gets old embarrassingly fast!

Please Stop Making Employees Guess the FolderCopy anchor linkCopied

image6.gif

👩 “If you’re looking for employee resources, everything's in the shared drive.”

Suuuch a generous thing to tell someone who has only worked at your org for like 40 minutes!

Imagine that they're trying to get their benefits sorted out and found two enrollment documents with different instructions, and one belongs to a person who left before they interviewed.

Now they have to decide whether asking HR will make them look helpless.

I truly hate that we've made basic information feel like a test.

When the knowledge base is full of conflicting info and three versions of the same doc, anyone can grab the wrong one. Tenured folks at least have a weird little education about which folder to ignore and who actually has the answer. New hires are starting from zero.

A usable knowledge base should help them get through onboarding without collecting company folklore. 😬

That doesn't require relocating every document your org owns, either!

(Thank god, because imagine the kickoff meeting for that project.)

Haystack connects with SharePoint, OneDrive, Google Drive, and Confluence, giving employees a place to search across those systems. That means your teams can keep documents where they already work, while guaranteeing they’re always finding the correct version of what they’re looking for.

With AI search, an employee looking for the expense policy can start with the question they have, rather than guessing which department's preferred platform holds the answer.

Finance keeps its existing setup, and everybody gets to carry on.

The one thing you would need to sort out is conflicting info. 👀

You can break this up by choosing who owns each resource and when they’ll review it. If two policies disagree, get that resolved before expecting employees to make sense of them. Haystack can help here with a freshness engine that nudges owners when content is about to expire, and conflict detection flags when multiple pieces of content say different things.

Work through permissions with IT, too. Being able to find info easily should respect the access rules you already have in place!

For new hires, start with what they're trying to do that week. Getting paid deserves an obvious link, but so does finding the person who can approve their equipment request.

📒 A directory helps when they know what they need but have absolutely no idea who Linda is.

And when someone asks HR a question you've already documented, take a deep breath before sending the link again, then ask where they looked. They might show you exactly why people keep getting stuck!

Hitting Publish Doesn’t Mean People Got the MemoCopy anchor linkCopied

image1.gif

People usually go looking for a policy when they need it, right?

👀 But company announcements often need to reach them before they know there's anything to look for.

For example, if office access changes on Monday, employees need the instructions before they're standing outside the building.

Waiting for them to browse the homepage over breakfast seems like a lot of faith to place in a homepage!

So consider who needs each update and where they're likely to see it. Someone working a shift away from a desk has a different day from someone who lives inside Slack.

Sending both another email and hoping for the best leaves quite a bit to chance! 🤷‍♀️

Haystack distributes targeted news through email, Slack, Teams, and its mobile app. Its communication tools even let teams see who read a post and send reminders for unread content, which gives you somewhere to start with follow up.

For an important change, you’ll wanna leave room for questions. Someone can open an update and still need help understanding what applies to them.

I also want comms teams to be able to publish the damn thing themselves.

Haystack's templates and drag-and-drop editor give authorized users that ability, so a routine announcement can get out without waiting for an engineer.

You have to use that freedom thoughtfully! Tell people what changed and what they need to do, then put the deadline where they can see it.

Anyone who wants the full policy can follow the link instead of scrolling through a small novel on their phone.

Before launch, have employees try a few ordinary tasks in the hub, and watch without directing them.

💡 Give managers the same links to share as well. Introduce the hub during onboarding by having people use it. Keep reviewing the questions that come back to HR, because those tell you more than everyone agreeing the homepage looks nice.

Your Company Brain Deserves Better HousingCopy anchor linkCopied

image3.gif

I think we both can agree that you deserve a better use of your afternoon than finding the same policy for the 7th person!

Haystack brings searchable company knowledge and targeted updates into an intranet your comms team can easily manage.

Employees get a familiar starting point, while the documents your teams rely on can stay in their existing systems.

Ask Haystack to show you how that would work with your setup, and bring the onboarding questions people always ask.

Seeing those handled will tell you considerably more than admiring a pristine homepage full of info nobody at your company needs. 😉

Retire the Information Scavenger Hunt

In collaboration with: Haystack

Building an intranet comes with a lot more maintenance baggage than you think! Explore Haystack before volunteering engineering.

Audit the commitment

Get I Hate It Here in your inbox

A safe space for jaded, overworked and emotionally burned out HR/People Operations professionals who need a little inspiration to tackle the newest dumpster fire of the week.

Written by Hebba Youssef