An Intranet Homepage Without a "Needs Attention" Box: What We Cut, What We Kept, and Why

The homepage of a corporate intranet is the most deceptive feature in the product. It feels like the more widgets you add, the more "useful" the page becomes. In practice, every extra widget steals attention from all the others. By the end of the year, the typical homepage turns into a graveyard: a weather widget, a currency-rate widget, a birthday widget, a news feed shoved in the corner, and an overall sense of "there's a lot here, but I don't open any of it."

Over the past year we went through six iterations of the intranet homepage redesign. We tested with real users, measured metrics, and argued as a team. By spring 2026 we'd arrived at a simple answer: four blocks plus an AI chat. Fewer than what feels like the bare minimum; more than what most scenarios actually need.

Let me walk through what we tried, what we kept, and why. This isn't "the one correct intranet design for every situation" — it's what works for us, and what six iterations taught us.

From Eight Sections to the Canonical Four

V1 — eight sections. Quick Actions, widget of the day, calendar, feed, achievements, surveys, employees online, announcements. When we first launched the intranet, this felt like the "complete set." In practice, users opened Quick Actions and the feed, then closed the page. Eight blocks became noise in which only two carried any real weight.

V3 — five sections. We cut it down to Quick Actions, feed, calendar, achievements, and surveys. It looked cleaner, but the problem hadn't gone anywhere: achievements and the calendar were still ignored, and surveys weren't always active (there were weeks with no pulse survey). The feeling of "lots of blocks, little meaning" remained.

V6 — the canonical four. Quick Actions, Today, Feed, Survey (if one is active) — plus an AI chat instead of a separate "Needs Attention" box. A decision we reached through testing, not through idealizing.

The main lesson from six iterations: a homepage works when every block answers a specific, recurring user question. If a block doesn't close out a clear question, it'll be ignored, no matter how useful the information shown there might be.

Quick Actions / Today / Feed / Survey — What Stayed and Why

Each of the four blocks answers its own question. And that question is recurring, not one-off.

Quick Actions answers "what do I do most often on the intranet?" Four buttons, no more. Our defaults: "Thank a colleague," "Submit an idea," "Find an employee," "Create a post." You can customize it. These four actions cover 80% of an employee's day-to-day operations. Without a block like this, people hunt for the action they need through the menu every time — and after two weeks they stop trying.

Today answers "what's on my plate today?" Calendar events, open tasks (if integrated), colleagues' birthdays, work anniversaries. This isn't "notifications" — it's your day in the context of the company. We used to have a separate "birthdays today" card; we removed it and folded it into Today. It feels more organic now.

Feed answers "what's new in the company?" This is where news, kudos, ideas up for a vote, announcements, and discussions all live. One shared stream where employees see the life of the company. It's not a chronicle, it's a pulse. The feed only works when the content is alive; on a "dead" feed this block just looks empty.

Survey answers "what does the company want to know from me today?" The pulse question of the week or an onboarding check. It appears only if there's an active survey; otherwise the block is collapsed or hidden entirely. Don't "always show a survey" — that turns the block into background noise.

What we removed and why:

• The calendar as a standalone block — folded into Today. Most users don't run their day off the corporate calendar as their primary one; they have it in Google Calendar or Outlook. On the homepage you only need "what's on for me today."
• Achievements — moved to the profile page. People visit their profile about once a week, not every day. On the homepage it was just taking up space.
• Announcements — these are really just part of the feed, not a separate block. We merged them.
• Widget of the day (motivational quote) — removed entirely. Decoration that motivates no one but takes up room.
• Employees online — removed. It once seemed like a "cool feature"; in practice nobody needs to know which of 800 people is currently on the intranet.

The principle: fewer blocks that carry real weight beat lots of decorative ones.

Why an AI Chat Replaced "Needs Attention"

The most contentious move in the redesign. We debated it for a long time as a team and eventually landed on a decision we now consider the right one.

What "Needs Attention" used to be. A list of notifications: "3 unread," "a survey is waiting," "5 colleagues mentioned you," "an overdue task." It looks useful. In reality, the list is never empty. Close one and two new ones appear. It's an eternal source of pressure that never resolves. Within a week, users stopped looking at this block. Within a month, they'd learned to ignore the red dots.

Why we put an AI chat there. A notification list is a passive mechanic: the company pushes something at you. An AI chat is active: you initiate the conversation when you actually need it. That flips your relationship with the interface.

What the AI chat knows and can do:

• The context of your team and your history. It remembers what you've talked about, who you haven't thanked in a while, and what your recent interactions were.
• Voice support for everyday tasks. "Help me write a thank-you for Anna," "what's important for me today?", "find a colleague in marketing who works with the product team."
• Meeting prep. "I have a 1:1 with Ivan in an hour, what should I raise?" — the AI knows what you discussed last time, what was agreed, and what reminders are outstanding.
• Company search. "Who's responsible for compliance?" — faster than digging through the org chart.

The least obvious advantage of an AI chat on the homepage: it doesn't create fatigue. A notification list drains your attention every single day. An AI chat uses exactly as much attention as you choose to give it. That's a fundamentally different mode of interacting with the intranet.

Notifications haven't gone anywhere, of course — they moved to the standard bell icon in the top bar, like in any modern interface. But they no longer occupy center stage on the homepage. They're where they belong: in the background.

18 Sidebar Modules Without the Cognitive Load

Our product has 18 sections: profile, feed, recognition, achievements, ideas, surveys, learning, org chart, documents, employees, events, analytics, admin, and a few more. This used to be 18 flat items down the left side — users scrolled, searched for what they needed, and got lost.

The fix: grouping by logical sections. Not by technical meaning, but by user meaning. We ended up with four groups:

• Me and my team — profile, org chart, employees, events.
• Recognition and achievements — kudos, leaderboard, achievements, badges.
• Knowledge and ideas — idea bank, learning, documents.
• Administration — admin, analytics (visible to admins only).

Each group collapses and expands. When collapsed, only the group name shows — taking up a single level. When expanded, all its items appear. The collapsed/expanded state is remembered per user — some people like keeping everything open, others only what they need.

And separately, the chevron at the edge of the sidebar. A small arrow on the right edge of the sidebar that collapses everything down to icons. It frees up horizontal space for the main content, which is especially useful on laptops with small screens. It looks like a trivial detail, but plenty of users actively rely on it every day.

Small Things That Move DAU

A few small decisions that, taken together, make a noticeable difference.

Breathing room between blocks. The old version was dense — lots of blocks on a single screen. The new one gave them more space. This simply feels lighter and tires you out less during longer sessions. The "time on homepage per session" metric went up — consistent with what UX research shows: thoughtful use of whitespace increases user attention and engagement time by roughly 20% (Loop11 — The Power of White Space).

Profile menu in the top bar. Profile and settings used to sit at the bottom of the sidebar — users scrolled to find them. Now they're in the standard spot in the top-right corner. That's the convention every web user is used to, and fighting it just creates needless effort.

Skeletons instead of spinners. While the page loads, we show a "skeleton" — gray placeholders where the blocks will be. This creates a sense of fast loading, even when the content actually arrives in the same number of milliseconds.

Mobile-first responsive. The homepage reads well on a phone without rearranging the logic. On a narrow screen, it's the same four blocks, stacked. The AI chat slides up from the bottom as a sheet. This is table stakes for modern design, but a noticeable share of corporate intranets still ship an unreadable mobile version — we see it when we look at competitors' intranets and the legacy of SharePoint rollouts.

No personal pop-up notifications. The homepage has no pop-ups saying "you were mentioned" or "someone reacted to you." Those create a jittery rhythm. Notifications collect in the bell icon and in a digest — the user decides when to read them.

All of these small things seem insignificant. None of them on its own would warrant an article. Together they add up to an overall sense of "this is a pleasant place to spend time," and by our metrics that noticeably lifted intranet DAU at customer accounts in the first weeks after the redesign. The exact percentage depends heavily on the starting state of the intranet (a dense old homepage produces a bigger jump, an already-sparse one a smaller one), so I'd rather not quote an averaged number.

The Bottom Line

Six iterations of the redesign led us to four blocks — Quick Actions, Today, Feed, Survey — plus an AI chat as an active assistant instead of a passive notification list. Fewer than what feels minimal; enough for most scenarios.

The main rule we derived for ourselves, and one you can apply to any corporate intranet: every block on the homepage should answer a specific, recurring user question. If a block doesn't close out a clear question, it'll be ignored — and worse, it'll distract attention from the blocks that do work.

And one last thing: notifications are a passive mechanism that creates fatigue. An AI chat is active and uses exactly as much attention as you give it. That's not a cosmetic difference, it's a paradigm shift in how you interact with the intranet.

Next week: the enterprise AI agent — how it differs from a regular chatbot, what a Memory Palace is, and why context matters more than the model.

If you'd like to see our new homepage live, follow the link in the card — a demo, no slideshows.