B.

Works

TEAM ACTIVATION

Defining the strategy to close the gap between setup and handoff

Overview

Admins often hit a false finish line after cloud onboarding because they assume the job is done, leaving the cloud and AI features inaccessible to the team behind the invite user step.

To meet the spring launch, I am aligning two product teams on a phased strategy: focusing on a short-term safety net to establish a baseline, while running parallel research to validate if a more aggressive, high-guidance intervention is needed for the future roadmap.

Timeline

Nov 2025 - Ongoing(HP)

My Role

Lead Product Designer | Strategy Definition | User Research

Admins often hit a "False Finish Line" after cloud onboarding.
They assume the job is done, leaving the features and values locked behind a missing step.

STEP 1 : Cloud Onboarding
The Admin enables the features.
STEP 2 : This Project
The Admin must distribute invites to allow access to Cloud and AI features.
STEP 3 : Invited User Flow
The End User receives the key and experiences the value.

Mixed Signals vs. Cumulative Load

I'm currently defining the right scope for user guidance, with three conflicting factors at play:


1

The Internal Reflex: The team sees "standard patterns" (like Guided Tours) as a safe default because they were used in previous tools.

2

The Research Data: Existing research on similar product show a split audience. One segment is eager for help, while another is exhausted and abandons any guidance.

3

My Contextual Analysis: I flagged that this flow is unique because entry points vary. A user might arrive via a focused scan setup, or a marathon journey (Hardware Unboxing - Driver Installation - Cloud Onboarding).

I highlighted that given the cumulative cognitive load, committing to a heavy tour is too risky. Optimizing for the users who want help is easy, but it ignores the risk of alienating the exhausted users who just want to finish.

The Short-Term Baseline

To bridge the gap while we validate the long-term needs, I proposed a Smart Notification + Support Page model. This serves as the initial safety net, which ensures no user is left without help, regardless of which direction the final strategy takes.

The Mechanism

I added a Smart Notification to the restructured Support Page. Reusing these existing components allowed for rapid deployment with minimal effort to meet immediate needs.

Invitation email before
Before: Users faced undefined next steps and an unfamiliar product reference ("HP Smart"), leading to hesitation.
Get software page before
Adding the missing information to educate the admins the need for invite users.
The Logic

This pattern is non-blocking. It allows the exhausted user to bypass it without friction, but creates a permanent path to the detailed help content for the eager user.

Current Status

Determine Final Scope

We are effectively using the short-term solution to buy time for data collection. I am currently leading the Validation Phase.

The Research

Working with UX researchers, I'm designing testing questions to assess user sentiment and validate our deisgn asusmptions. The findings will help us decide the right moment and the right method to best present information that's critial for cloud and AI success.

Next Steps

The project remains open. The research will decide if we scale up to the high-guidance solution or maintain the low-friction baseline.
Research questions draft