What Makes an Internal Portal People Actually Use

Plenty of abandoned internal tools were built exactly to specification. Every requested field is there. Every department got its section. The launch presentation went well. Six months later, the shared inbox and the spreadsheet are back, and the portal is where people go to look up a phone number.Plenty of abandoned internal tools were built exactly to specification. Every requested field is there. Every department got its section. The launch presentation went well. Six months later, the shared inbox and the spreadsheet are back, and the portal is where people go to look up a phone number.

The cause is almost never a missing feature. It is that the portal made the most common task slower than the habit it replaced. Adoption is a comparison, and the comparison happens dozens of times a day without anyone deliberating.The cause is almost never a missing feature. It is that the portal made the most common task slower than the habit it replaced. Adoption is a comparison, and the comparison happens dozens of times a day without anyone deliberating.

Most portals are organized the way the organization is organized: a section per department, a tab per system, a landing page that greets you with a welcome message. That structure is convenient for the people who commissioned it and useless for the person who has one thing to do right now.Most portals are organized the way the organization is organized: a section per department, a tab per system, a landing page that greets you with a welcome message. That structure is convenient for the people who commissioned it and useless for the person who has one thing to do right now.

Instead, find the three tasks that account for the majority of daily use — submit the request, check the status, approve the thing — and make those reachable in one action from the first screen. Everything else can live a level deeper.Instead, find the three tasks that account for the majority of daily use — submit the request, check the status, approve the thing — and make those reachable in one action from the first screen. Everything else can live a level deeper.

A useful test: can a regular user complete their most frequent task in under fifteen seconds, from cold, without scrolling past content written for someone else? If not, the home screen is a lobby, and lobbies are where tools go to be ignored.A useful test: can a regular user complete their most frequent task in under fifteen seconds, from cold, without scrolling past content written for someone else? If not, the home screen is a lobby, and lobbies are where tools go to be ignored.

The single highest-value element in an internal portal is a personal list: what is assigned to me, what is waiting on me, what changed since I was last here. It answers the question people actually arrive with. is a personal list: what is assigned to me, what is waiting on me, what changed since I was last here. It answers the question people actually arrive with.

Generic dashboards do the opposite. Aggregate charts that no individual can act on look impressive in a demo and get skipped in daily use. If a number cannot lead to an action for the person looking at it, it belongs in a report, not on the home screen.Generic dashboards do the opposite. Aggregate charts that no individual can act on look impressive in a demo and get skipped in daily use. If a number cannot lead to an action for the person looking at it, it belongs in a report, not on the home screen.

Personal state also fixes the status-chasing problem quietly. When people can see where their own request stands, the interruptions stop without anyone announcing a new policy.Personal state also fixes the status-chasing problem quietly. When people can see where their own request stands, the interruptions stop without anyone announcing a new policy.

Every real process has exceptions: the rush job, the special-case approval, the customer who is always handled differently. Portals that pretend exceptions do not exist push them into email, and once part of the process lives in email, the portal is no longer the system of record.Every real process has exceptions: the rush job, the special-case approval, the customer who is always handled differently. Portals that pretend exceptions do not exist push them into email, and once part of the process lives in email, the portal is no longer the system of record.

The fix is not to model every exception as its own feature. It is to allow a documented override with a reason and an audit trail. Let people do the unusual thing inside the system, and capture why.The fix is not to model every exception as its own feature. It is to allow a documented override with a reason and an audit trail. Let people do the unusual thing inside the system, and capture why.

Six months of override reasons is also the best requirements document you will ever get, because it shows what the process actually does rather than what the process is described as doing.Six months of override reasons is also the best requirements document you will ever get, because it shows what the process actually does rather than what the process is described as doing.

Permissions are usually discussed as a security control. In portals they are equally a usability control. A person who sees only what is relevant to their role experiences a simple tool; a person who sees everything experiences a filing cabinet.Permissions are usually discussed as a security control. In portals they are equally a usability control. A person who sees only what is relevant to their role experiences a simple tool; a person who sees everything experiences a filing cabinet.

Design roles around jobs — requester, approver, coordinator, administrator — rather than around departments. Then check the empty states: a new user with no assignments should see something helpful, not an empty grid that suggests the system is broken.Design roles around jobs — requester, approver, coordinator, administrator — rather than around departments. Then check the empty states: a new user with no assignments should see something helpful, not an empty grid that suggests the system is broken.

Do not forget the occasional user. The person who logs in twice a year needs different guidance from the person who lives in the tool. A short, dismissible explanation on the primary screen serves them without slowing anyone else down.Do not forget the occasional user. The person who logs in twice a year needs different guidance from the person who lives in the tool. A short, dismissible explanation on the primary screen serves them without slowing anyone else down.

Pick one team and one workflow for the first release, and make that team demonstrably faster. Internal credibility spreads through people saying it saved them time, and that requires someone to have actually saved time.Pick one team and one workflow for the first release, and make that team demonstrably faster. Internal credibility spreads through people saying it saved them time, and that requires someone to have actually saved time.

Migrate history so the tool is not empty on day one. An internal portal with no past looks like extra work; one that already contains last month's requests looks like a better version of what you had.Migrate history so the tool is not empty on day one. An internal portal with no past looks like extra work; one that already contains last month's requests looks like a better version of what you had.

Retire the alternative on a date everyone knows. If the old spreadsheet stays editable forever, half the team will keep using it, and you will run two systems permanently — the worst of both.Retire the alternative on a date everyone knows. If the old spreadsheet stays editable forever, half the team will keep using it, and you will run two systems permanently — the worst of both.

Then keep changing it. Ship a visible improvement in the first month based on something a user said. Nothing builds internal adoption like evidence that feedback goes somewhere.Then keep changing it. Ship a visible improvement in the first month based on something a user said. Nothing builds internal adoption like evidence that feedback goes somewhere.

Internal tools get a pass on quality far too often. But staff use them under pressure, sometimes on a phone, sometimes on an old laptop in a warehouse, sometimes with a screen reader. Keyboard navigation, real form labels, visible focus, and readable contrast are not polish here; they are throughput.Internal tools get a pass on quality far too often. But staff use them under pressure, sometimes on a phone, sometimes on an old laptop in a warehouse, sometimes with a screen reader. Keyboard navigation, real form labels, visible focus, and readable contrast are not polish here; they are throughput.

If part of the work happens away from a desk — a warehouse, an event site, a field visit — check the phone experience before launch rather than promising a mobile phase later. The mobile phase rarely arrives, and the workaround fills the gap in the meantime.If part of the work happens away from a desk — a warehouse, an event site, a field visit — check the phone experience before launch rather than promising a mobile phase later. The mobile phase rarely arrives, and the workaround fills the gap in the meantime.