When an intranet feels “broken,” sponsors often reach for a redesign. New visual system. New mega-menu. New agency deck. Sometimes that is warranted. More often, people cannot find the policy, the form, or the working library because information architecture never caught up with how the organization actually works.
SharePoint Online already gives you hubs, navigation, metadata, and search. Expensive redesign theater does not fix a tenant that has fifty team sites named after projects that ended in 2022, three competing “HR” destinations, and no owned labels.
This note is about findability as operating work: hubs with purpose, navigation people can predict, metadata that search can use, and ownership that survives the launch party.
Findability is not branding
Branding answers: does this feel like us?
Findability answers: can a new hire open the right page in under two minutes without pinging a colleague?
Those are different jobs. Confusing them produces a beautiful homepage that still routes people to Slack for the real answer. In regulated environments, that informal detour is not only inefficient—it is how unofficial copies of controlled documents multiply.
Put findability on the critical path. Treat visual refresh as optional once people can locate and trust the content.
Start with hubs that mean something
SharePoint hubs are not decoration. They are the primary way to group related sites under a shared navigation and brand. A useful hub answers one sentence: what belongs here, and what does not.
Patterns that work:
Function hubs — HR, Finance, IT, Operations—when those functions own content and process.
Audience hubs — employees, managers, contractors—when the same policy must be presented differently.
Program hubs — only when the program is durable, not a six-month initiative that will orphan the hub.
Patterns that fail:
One “company hub” that tries to hold everything and becomes a junk drawer.
Hubs that mirror every department in the org chart whether or not those departments publish content.
Hubs created for a project team that dissolved, still sitting in global navigation.
Write the inclusion rule before you create the hub. If you cannot write the rule, you do not need the hub yet.
Navigation people can predict
Global and hub navigation should be short, stable, and owned. A practical target: few enough top links that a person can scan them without scrolling theater. Secondary destinations live one click deeper—or in search.
Avoid:
Labels that only make sense to the team that invented them (“The Bridge,” “OneStop,” “Portal 2.0”).
Duplicate destinations for the same policy family under different names.
Deep cascades that hide the page people actually need behind three hover menus.
Prefer plain language that matches how employees ask: “Time off,” “Expense,” “Safety,” “Policies,” “Templates.” Rename for clarity even if the underlying site title stays technical.
Audience targeting belongs here only when it is backed by real Entra groups and does not disclose sensitive titles to people outside the audience—the access model from the first article in this pack. Findability without permission discipline is just faster leakage.
Metadata and search before another homepage web part
If search returns noise, the fix is rarely “add another news web part.” It is usually:
Managed properties / crawled properties aligned to the fields people actually filter on.
Content types or columns that are few, required where it matters, and owned.
Promoted results / bookmarks for the dozen destinations everyone needs (benefits, IT help, policy index).
Retired or unindexed junk — old project sites, duplicate libraries, and abandoned communication sites that pollute results.
You do not need a perfect taxonomy on day one. You need a small set of labels someone will maintain. Five well-owned columns beat fifty abandoned ones.
A calm standard: every library that holds controlled procedures has a named content owner, a review date, and enough metadata that search and filters can find the current version—not three near-duplicates.
Without expensive redesign theater
Redesign theater looks like:
A six-month visual identity project before anyone owns navigation.
A custom front-end that fights SharePoint updates and needs a specialist for every news post.
Workshops that produce journey maps and no site inventory.
“Phase 2 metadata” that never starts because the homepage launch absorbed the budget.
Useful work looks like:
Inventory of top destinations by actual usage and help-desk tickets.
Hub map with inclusion rules and named owners.
Navigation rewrite in plain language.
Search tuning for the top twenty failed queries.
Retirement plan for orphaned sites.
That work is less photogenic. It is what makes the intranet feel finished.
Ownership is the missing page
Findability decays when nobody owns it. Name:
Intranet product owner — prioritizes destinations and navigation changes.
Hub owners — decide what joins or leaves a hub.
Content owners — keep pages and libraries current.
Search steward — reviews failed queries monthly for one quarter after launch, then on a lighter cadence.
If those names are “the communications team” as a blob, expect drift within a year.
How this fits a Microsoft 365 landscape
Organizations that already run Microsoft 365 / SharePoint Online do not need a second platform to fix findability. They need discipline on the tenant they have: hubs, navigation, metadata, search, and permission-respecting collaboration next to whatever systems of record they already trust.
McCloy Data’s work sits in that adjacency—content people open in Microsoft 365, governed next to OpenText and SAP where that is the landscape—without turning the engagement into a SharePoint SI résumé. The bench has done information architecture and intranet structure as operating work, not as a pitch deck.
A practical checklist
List the twenty destinations people ask for most; make them one predictable click or a reliable search hit.
Draw hubs with inclusion rules; retire hubs that fail the one-sentence test.
Rewrite navigation labels in employee language; remove duplicates.
Tune search for failed queries; promote the critical few.
Assign named owners for intranet, hubs, content, and search.
Schedule a ninety-day findability review after launch—usage, tickets, and search fails—not a redesign committee.
If you want help with the structure
If your SharePoint Online intranet is visually “done” but people still cannot find the work, we can help with information architecture, hub design, and findability on the Microsoft 365 you already own. A short conversation is enough to see whether the gap is structure, ownership, or both.
