MyPod Intranet Redesign

Overview

MyPod is a redesign of Bitwise’s internal intranet, originally fragmented, content-heavy, and underutilized. The project focused on reducing cognitive overload, clarifying employee priorities, and reframing the intranet as a daily work companion rather than a static information dump.

Instead of adding features, the redesign removed friction, aligned the system to real employee workflows, and introduced clear information hierarchy, resulting in measurable improvements in adoption and engagement.

Impact: +65% daily usage and +70% employee participation

Note on confidentiality: due to enterprise security constraints, actual user data, internal metrics, and sensitive content are anonymized or abstracted in the UI visuals shared.

The starting point: what was broken

The existing intranet failed not because of missing features, but because it did not respect how employees actually work.

Key challenges identified:

Employees could not quickly find relevant or timely information
Content felt top-down, static, and disengaging
The interface lacked hierarchy, clarity, and trust signals
No sense of community, recognition, or participation

From a business standpoint, this translated into:

Low platform adoption
Repetitive HR queries
Missed internal communication
Poor ROI on an internal product already in use

Previous intranet — The previous intranet prioritized content volume over clarity, forcing employees to scan, search, and guess where to act.

Research and understanding the real user

Methods used

Stakeholder interviews (HR, team leads)
Employee interviews across departments
Usage pattern analysis of existing intranet
Competitive benchmarking (enterprise intranets and collaboration tools)

Key UX insights

Employees scan, not read internal platforms
Relevance is time-bound: “What matters today?”
Recognition and visibility directly influence engagement
Trust increases when systems feel predictable and transparent

These insights directly informed every design decision.

Design strategy

The redesign was guided by three principles.

1. Information first, always. Content hierarchy was rebuilt to surface what’s new, what’s relevant, and what requires action.

2. Engagement without compromising security. Community features were introduced within enterprise constraints, avoiding public-social paradigms while still enabling participation.

3. Progressive adoption. Instead of overwhelming users, features were layered to support gradual behavioral change.

Key design decisions and rationale

1. Information architecture redesign

Decision: Replace department-based navigation with task- and intent-based grouping.

Rationale: Employees think in terms of actions, not org charts.

Outcome: Reduced cognitive load and faster access to frequently used resources.

MyPod information architecture — Navigation reorganized around employee intent, not internal structure, reducing time-to-information.

2. Dashboard as modular system

Redesign the homepage as a modular dashboard instead of a static content page. User testing showed employees make a value judgment within seconds: “Does this help me today?” and “Is it worth coming back?” The modular approach allowed clear visual hierarchy, flexible prioritization of content, and future scalability without redesigning the core layout.

Trade-off: Personalization was intentionally limited to avoid security and governance risks common in enterprise environments.

3. Engagement and community features

Engagement was introduced carefully to avoid the perception of an “internal social network.”

Internal blog-style posts for sharing relevant articles and experiences
Lightweight reactions and badges to encourage participation
Celebration widgets for birthdays, work anniversaries, and achievements

Design rationale: Research showed employees were already sharing knowledge informally. The goal was to formalize and surface this behavior, not create new friction. Engagement features were designed to be opt-in, visible, and governed, aligning with enterprise expectations.