From First Login to Completion

Every design decision in HBP Spark exists in service of one person: the learner. The admin tools, the pathway editor, the notification logic — all of it is infrastructure for a moment when a real person opens the platform, finds something worth learning, and comes back to do it again.

This post traces the full learner experience from first login through content discovery and pathway completion — covering onboarding, navigation, the home page, search, and the pathways experience as one continuous design story.

Onboarding: The First Conversation

Onboarding is the most important experience on any platform and the one most often designed last. It sits at the awkward intersection of business goals (activate users quickly) and user needs (help me understand what this is and whether it’s worth my time). Doing it well requires knowing the minimum information you need to make the platform genuinely useful — and collecting only that.

The Question We Started With

We began by asking: what’s the minimum the platform needs to know about a new learner to give them a meaningfully personalized first experience?

The answer was three things:

1. What level of leadership are they at?
2. What leadership priorities matter most to them right now?
3. What specific skills do they want to develop?

Everything else — full name, profile photo, department — could come later, once learners are invested. But these three things drove the home page recommendations, the skill framework, and the Leader Profile. Without them, the first experience would be generic. With them, it could feel immediately useful.

Step 1: Leadership Level

The options map to the HBR Leadership Framework — meaningfully different leadership contexts that correspond to different learning needs. Importantly, “I lead myself” and “I don’t have direct reports, but my role requires leadership skills” are included. There was pushback on whether a leadership platform should include options for people who don’t yet lead others. Our argument: developing leadership capabilities before you have direct reports is valuable, and excluding these options would implicitly tell those learners the platform wasn’t for them.

Step 2: Development Priorities

Learners select up to two priorities from a list of leadership development goals. The two-item limit was deliberate. Given no constraint, most users would select everything, rendering the signal meaningless. Two forces prioritization — the learner has to decide what actually matters most right now. That intentional choice produces better signal for the recommendation engine and creates a more useful mental commitment for the learner.

Step 3: Skill Focus Areas

The third step asks learners to select up to six specific skills from the HBR Leadership Framework. Before they choose, the platform surfaces “Recommended Skills for You” based on their previous answers — a preview of the personalization to come. This demonstrates immediately that the earlier questions had a purpose. The platform listened and is already responding.

Six skills allow enough breadth for a robust development plan without becoming overwhelming. These selections become the “Focus Skills” that drive everything on the home page.

The Immediate Payoff

The home page after onboarding is not generic. It reflects the learner’s selections immediately: Focus Skills are displayed, recommendations are filtered to those skills, and the Leader Profile is initialized with their stated development goals.

If the platform looked the same after onboarding as before, the questionnaire would feel like a bureaucratic hurdle. The connection between input and output has to be visible.

One note: portions of onboarding can be disabled by organization administrators. Some organizations have their own onboarding processes or pre-assigned skill frameworks. The opt-out capability respects those needs without compromising the default behavior for everyone else.

---

Global Navigation: The Skeleton of Every Experience

Navigation is the most consequential design decision you make on a platform. Get it right and it disappears — users move through the platform without thinking about the navigation itself.

HBP Spark’s navigation serves two user types within the same shell: learners and admins. The architecture keeps them oriented without conflating their contexts.

Destinations vs. Tools

The navigation bar makes a structural distinction that shapes how learners understand the platform:

Primary destinations (where you go):

• Home — the personalized entry point
• Explore — the content catalog and discovery experience
• Labs — specialized content experiences

Persistent tools (what you use from anywhere):

• Ask AI — the AI-powered assistant
• Bell — notifications
• Search — global content search
• Avatar — profile and settings

The order of destinations reflects usage frequency. Home is first because it’s the most personal and most frequently visited — a learner who wants to pick up where they left off has a one-click path to do so. Explore is second because discovery is the next most common reason someone opens the platform. After home, they browse.

Notifications: Labels, Not Counts

The bell icon opens a notification panel sorted most-recent first. Unread notifications carry a “NEW” label rather than a badge count on the bell. This was deliberate: a badge count tells you how many you have; a “NEW” label on each notification tells you which ones specifically need attention. Once the panel is opened and closed, “NEW” labels are removed from viewed notifications, creating a clean state rather than persistent noise.

Ask AI as a First-Class Element

Placing Ask AI in the main navigation — not buried in settings — made a statement about the platform’s direction. AI-assisted learning wasn’t a bolt-on feature; it was a first-class capability available from anywhere. The label “Ask AI” removes any ambiguity about what clicking it does.

Navigation as Brand Expression

An often-overlooked function of navigation: it communicates what a platform is for. “Courses,” “Modules,” “Certifications” implies a formal, structured learning environment. “Home,” “Explore,” “Labs” implies something more personal and exploratory.

HBP Spark’s navigation is an expression of its philosophy: learning should feel personal (Home), exploratory (Explore), and experimental (Labs). Naming and ordering are brand decisions as much as information architecture decisions.

---

Home: The Personalized Entry Point

The home page is where the platform makes its first real promise to the learner: we know what you need, and we’re going to help you find it. Every design decision is downstream of that promise. If the page feels generic or overwhelming, the promise is broken before the learner has done anything.

Recommendations Driven by Focus Skills

The home page is fundamentally a recommendations surface. “Recommended for You” is the main content region, driven by the learner’s Focus Skills from onboarding. The selected skills appear as tags above the recommendations — each skill filtering the content shown below it.

This approach to personalization is different from purely behavioral recommendation (showing you more of what you’ve clicked) or purely curated recommendation (showing you what HBP thinks is good). It’s intention-based: the platform responds to what the learner has told us they care about, not just what they’ve done. The UX advantage: learners feel like the platform is listening. The learning advantage: development happens in areas of intention, not just areas of interest.

Your Leader Profile: Progress Made Visible

The home page surfaces a peek at the learner’s Leader Profile — a progress visualization of their Focus Skills development. The “Your Leader Profile →” link leads to the full profile page.

Surfacing this on the home page was a deliberate motivational choice. A learner who can see their progress at a glance has a reason to come back. The home page isn’t just where you start learning; it’s where you see the shape of your development over time.

What the Home Page Doesn’t Do

Equally important is what the home page avoids:

• Trending content or popularity signals (this is a learning platform, not social media)
• All available catalog content (overwhelming)
• Administrative alerts or organization-wide announcements (admin noise has its own home)

The home page is for the learner’s journey. Anything that’s about the platform, the organization, or other users belongs elsewhere.

Designing for Return Visits

The home page is most valuable as a return destination — the place a learner goes on their tenth and fiftieth visit. For return visits, the page needs to feel both familiar (same layout) and dynamic (different recommendations as the learner progresses, skills update as focus changes).

Completed content doesn’t resurface. New content appears as focus skills change. The “Your Leader Profile” section updates to reflect actual progress. The UI creates the expectation of a living, responsive page. The data layer has to deliver on that expectation.

---

Search: The Most Honest Feature on the Platform

Search is the most honest feature on any content platform. When a learner types a query, they’re telling you exactly what they want — no personalization models, no algorithms, no intermediaries. Just intent, expressed directly.

The Scale Context

HBP Spark’s catalog contains 30,000+ pieces of content. This isn’t a small library where you can present everything and let people scroll. Showing “30,051 Results” as a visible count was a design choice, not just a technical output — it tells the learner the catalog is large, search is powerful, and what they’re seeing is filtered from a broad set. The number creates context for why filters are essential, not optional.

The Filter Architecture

Five filter dimensions map directly to the five questions a learner asks when choosing content:

Filter

The question it answers

Format

What kind of content do I want?

Duration

How much time do I have?

Publication Date

Do I want current or foundational content?

Skill

What am I trying to develop?

Language

What language do I need?

Together these filters let a learner express the full context of their content decision in a few clicks. “I want a 30-minute article on communication skills in Spanish, published in the last two years” is a filterable query that produces a targeted, useful result.

Org Content in the Same Stream

The “From Your Organization” section surfaces org-created content alongside HBP catalog content in search results. This is a fundamental integration decision: learners search by topic or goal, not by content origin. Someone searching for “negotiation skills” wants all relevant content — HBP catalog items and org-created pathways — together. Siloing by origin forces learners to search twice.

The “From Your Organization” badge on individual results provides the origin signal for those who care, without requiring learners to know to look for it.

Sort By: Relevance as Default

The default sort is relevance — how well the result matches the query. This is correct for discovery. A learner who typed a query wants the most relevant result, not the most recent one. Alternative sorts (most recent, shortest duration) serve specific use cases and are available but not default.

Consistency as Trust

Search result cards show the same information as cards throughout the platform — content type, title, byline, description, duration, status. A learner who knows how to read a card in one part of the platform can read a card anywhere. Consistency is a trust signal.

---

Pathways: From Discovery to Completion

The pathway experience is the most important learner-facing experience on HBP Spark. It’s the core product promise: curated learning sequences that make expert knowledge accessible and actionable. Designing it well meant thinking across every phase of the journey.

Discovery: The Pathway Card

Pathways first appear as cards in the catalog — the same card format as individual content items but with a pathway-specific badge. Each card shows format indicator, title, description, skill tags, duration, and status (Not Started / In Progress). These cards are information architecture optimized for a decision: should I click this? Every piece of metadata exists to answer that question.

Evaluation: The Pathway Page as Preview

When a learner opens a pathway, they’re in evaluation mode. They want enough to decide whether to start. The design provides full title and description, skill context, duration and item count, and a section-by-section structure preview.

That section preview is particularly valuable. Seeing the sections and their descriptions before starting tells the learner the narrative arc of the pathway — what they’ll learn and in what order. This reduces the “commitment uncertainty” that prevents people from starting long pathways.

The Less Details / More Details toggle in the header lets learners access additional metadata — publication date, product ID, available languages — without cluttering the default view. Most learners won’t need the product ID; for those who do (often for administrative purposes), it’s one click away.

The “Start Pathway” Activation Moment

The “Start Pathway” button is a transition action — it moves the pathway from “not started” to “in progress” and unlocks progress tracking. We designed this as an explicit action rather than an automatic trigger because beginning something intentionally is meaningfully different from it happening to you.

There’s research supporting this: explicit commitment actions increase follow-through compared to passive entry. “Start Pathway” creates a micro-commitment moment.

Orientation Within the Pathway

Once inside, learners need to know where they are and what’s required:

• Section headers show title, description, duration, and required item count — giving a structural overview before diving into any item
• Required vs. optional labels on individual items let learners under time pressure focus on what they must complete and return to optional content later
• Breadcrumb navigation shows the hierarchy: where this pathway lives in the content structure. For learners who arrived via a direct link or recommendation, breadcrumbs provide context they’d otherwise lack

The required item count at the section level was a late addition driven by user testing. Learners were consistently underestimating pathway time commitments because section durations weren’t visible at a glance. Making it explicit reduced anxiety and improved planning.

Progress: The Visual Feedback Loop

As learners complete items, several things update: the item’s status changes to “Viewed” or “Completed,” section progress advances, and the overall pathway completion increases. These visual updates need to be satisfying — not flashy, but clearly communicating that something meaningful happened.

Progress feedback is what transforms learning into an experience of measurable advancement. Without it, learners don’t know where they stand and are less likely to return.

The Org Logo: A Signal of Belonging

For org-created pathways, the organization’s logo appears in the viewer. This seemingly small feature has a real impact: it connects the content to the learner’s specific organizational context. For a learner at Company X opening a pathway built by Company X’s L&D team, seeing Company X’s logo sends a signal — this was made for you, by people who know your context. That signal has real implications for engagement and trust.

Completion: What Happens at the End

When a learner completes all required items, the pathway is marked complete in their Learning History and their Leader Profile updates if skills are associated. The completion is permanent — even if the pathway is later archived by the admin, the completion record remains.

The completion moment deserves design attention — a clear, positive acknowledgment that something meaningful was accomplished. We kept it appropriately understated. Learning completion isn’t a game achievement; it’s a professional development milestone. The celebration should match that register.

---

The Experience as a System

Looking across these surfaces together, a few principles ran through every design decision:

Personalization has to be earned, not assumed. Onboarding collects the minimum information needed to make the platform genuinely useful. The home page delivers on that investment immediately. Every subsequent experience — recommendations, search defaults, Leader Profile progress — builds on what the learner told us about themselves.

Discovery should feel effortless. Navigation, home page recommendations, and search all reduce the friction between a learner and relevant content. The right content should be findable in seconds, whether the learner knows exactly what they want (search) or is open to guidance (home page).

Commitment should be explicit, not accidental. “Start Pathway” is a button. “Mark Complete” is a button. These are intentional moments designed to create micro-commitments that research shows increase follow-through. The learner is always in control of what they’ve started and what they’ve finished.

Progress has to be visible. The Leader Profile on the home page, the completion indicators within a pathway, the Learning History at the profile level — every part of the experience reinforces that learning is cumulative and trackable. That visibility is what turns a catalog into a development journey.