Pfizer RHS Hub
One internal hub for every tool, resource and team, replacing fragmented systems with a single source of truth.
- Client
- Pfizer (RHS)
- Team
- Internal stakeholders and engineers
- Timeline
- About 3 months, rolled out internally
Challenge
Too many tools and no single source of truth. Teams were navigating fragmented systems with overlapping functions, which led to inefficiency and duplicated work, and internal tools risked being ignored.
Approach
We documented every existing tool and workflow, then designed one clear hierarchy that organizes resources by how employees find information. The first release put high-frequency tasks first to drive early adoption, and navigation was refined through internal feedback loops.
01 Information architecture
Structuring the hub.
One clear hierarchy that organises resources and workflows the way employees look for them.
02 First release
Prioritising core use cases.
High-frequency tasks first, to drive early adoption.
03 Iteration
Improving discoverability.
Navigation refined through internal feedback loops.
Outcome
Rolled out internally after about three months. Adoption came from solving everyday problems first, not from trying to replace everything at once.