It's common for an organisation to spend significant budget on customer-facing UX while its own employees navigate an intranet last redesigned a decade ago. The productivity cost of that imbalance is real, even if it's rarely measured.
Employees are users too, and the same research and design discipline applied to a customer product applies to an internal one: understand the actual jobs people are doing, design the information architecture around those jobs, and test it with real staff before rollout.
The organisations that get this right treat their intranet as a product with a backlog and an owner, not a static repository IT maintains reluctantly.
The return shows up in time saved on internal tasks that were never glamorous enough to prioritise — and rarely questioned until someone finally measures them.