Anand Suraj
SectigoMicrosoft program contextIn progress

Onboarding UX / Rapid prototyping

Microsoft PQC: Onboarding & experience design

The problemPeople joining the initiative needed a clear way in: understandable access, guided onboarding and an easy way to share feedback, designed with consistent, accessible patterns.

My contributionI designed access, onboarding and feedback flows, using rapid prototyping and stakeholder review to refine the interaction direction.

Stakeholder-approved interaction designs

10+

Access, onboarding and feedback flows approved within a one-month review cycle.

Experience map · conceptual
  1. Access & activation

    Clear entry and access states

  2. Interaction design

    Consistent, accessible patterns

  3. Feedback & iteration

    Reviewed and refined

  • NDA
  • Not a product screenshot
My role
Associate Product Designer · Sectigo
Team
Sectigo product, engineering and stakeholders
Timeline
2026 · In progress
Tools
Figma, AI-assisted prototyping, Design-system patterns

Designed at Sectigo; Microsoft PQC is the program context.

Microsoft PQC program · public context

Process

The work behind the decisions.

  1. 01

    Frame the user flow

    Explored how people discover, access and begin the experience, and mapped the key states each step needed to communicate.

  2. 02

    Design reusable interaction patterns

    Designed onboarding and guidance screens with accessible, reusable patterns aligned to Sectigo’s design system.

  3. 03

    Prototype, review and hand off

    Used AI-assisted rapid prototyping and stakeholder reviews to refine the direction, with ten-plus interface designs approved in a one-month review cycle and prepared for thoughtful handoff.

Design decision artifact

UX alignment

Visual hierarchy, guided onboarding and accessible feedback help people understand where to start and what happens next.

  • NDA
  • Not a product screenshot
  1. 1Visual hierarchyOne primary action leads each view
  2. 2Guided onboardingProgress is visible step by step
  3. 3Accessible feedbackStatus uses text, not color alone
  4. 4Clear access statesPending, active and blocked read distinctly
Conceptual design illustration — not an actual artifact or product screenshot

Concept flow

Customer journey

Each stage answers the question a person is likely asking at that moment, so the design decisions stay tied to user intent.

  • NDA
  • Not a product screenshot
  1. 01Access & activation

    “How do I begin?”

    Make the entry point obvious

  2. 02Onboarding

    “What matters first?”

    Sequence essentials only

  3. 03In-product guidance

    “What comes next?”

    Contextual next step

  4. 04Feedback

    “How can I share input?”

    Low-effort, well-timed ask

  5. 05Iteration

    “What gets refined?”

    Review input with stakeholders

Iteration loops back into onboarding and guidance as feedback is reviewed.

Conceptual design illustration — not an actual artifact or product screenshot

Illustrative low-fidelity studies

Early wireframe exploration

Grayscale structure keeps the review focused on order, priority and controls; the accent marks the design intent in each study.

  • NDA
  • Not a product screenshot
  • 1Clear first action
  • 2Information hierarchy
  • 3Guided next step
  • 4Lightweight feedback capture
Conceptual design illustration — not an actual artifact or product screenshot

Key decisions

Design decisions that shaped the experience.

Decision 01

Make the way in obvious

Prioritize clear access and activation states so people understand where they are and what comes next.

Trade-off

Keep early steps simple rather than surfacing every option up front.

Decision 02

Design feedback into the flow

Give people a lightweight way to share feedback so the team can review and iterate on the design direction.

Trade-off

Ask for feedback at meaningful moments without interrupting the main task.

Design value & supporting evidence

Microsoft PQC: Onboarding & experience design

A stakeholder-reviewed design direction for access, onboarding and feedback, built on reusable patterns. The work is in progress; the evidence reflects design delivery, not adoption.

Interaction patterns approved
10+
Approved through stakeholder design review, not user usability testing.
Design review cadence
1 month
Iteration cycle for stakeholder-reviewed designs; initiative remains in progress.

Reflection

The key was deciding which access and feedback states matter most early on, and keeping everything else simple until reviews showed it was needed.

Next case study

Accessible cryptography product journeys

I designed ISARA user flows and accessible, brand-aligned interaction patterns, prototyping quickly for a clear engineering handoff.

View case study
Design exploration · conceptual
  1. Discovery & flows

    Structure the product journey

  2. Interaction system

    Brand and accessibility alignment

  3. Review & handoff

    Implementation priorities