01Case study

a lowercase line saying what the product isAccessPosture

Company
JumpCloud
Role
Your role
Timeline
Start – end
Design team
Who was on it
imageCover: Access Posture
21:9

overview

A shared Identity Graph and Risk Engine automate the risk remediation Entra and Okta often miss. MVP in Q2–Q3 2026, cross-provider data in late 2026, then full platform convergence.

Open the clickable prototype: link to come

key metrics

  • %Headline outcome, such as adoption
  • Scale, such as screens or customers
  • Speed, such as weeks to ship
  • %Business result

outcomes

  1. 01

    Outcome one

    What changed for users or the business, and how it was measured.

  2. 02

    Outcome two

    A second result, with the number behind it.

  3. 03

    Outcome three

    A third result, or what the team learned.

problem

What was going wrong, for whom, and what it was costing. Keep it to what a reader needs to follow the rest.

goals

  1. goal 01

    The outcome the business needed, ideally measurable.

  2. goal 02

    What the people using it were trying to get done.

  3. goal 03

    A third goal, such as a constraint to work within.

process & approach

process

  1. 01

    Discover

    • Competitive analysis
    • Market research
    • User interviews

  2. 02

    Define

    • Personas
    • User needs
    • Pain points

  3. 03

    Prototype

    • User flows
    • Build with AI

  4. 04

    Test

    • Userology click-prototype testing
    • Results

  5. 05

    Design

    • North star vision
    • Milestones 1 to 3
    • Main screens

timeline & team

timeline

Product management

  • Requirementsweeks 1–9 (about 9 weeks)
  • Readoutweeks 10–12 (about 3 weeks)

Design

  • Discoveryweeks 1–10 (about 10 weeks)
  • Rapid prototypeweeks 11–18 (about 8 weeks)
  • Milestone 1weeks 19–25 (about 7 weeks)
  • Milestone 2weeks 25–32 (about 7 weeks)
  • Milestone 3weeks 32–39 (about 7 weeks)

Research

  • Interviewsweeks 3–10 (about 8 weeks)
  • Prototype testingweeks 16–21 (about 5 weeks)

Engineering

  • Buildweeks 20–39 (about 20 weeks)

team

One line introducing the team behind the work.

  • Team member 1

    Role

  • Team member 2

    Role

  • Team member 3

    Role

  • Team member 4

    Role

discovery

competitive analysis

Who the main competitors are, how they were chosen, and what the analysis looked at.

feature comparison

FeatureThe productCompetitor 1Competitor 2Competitor 3
Feature 1————
Feature 2————
Feature 3————
Feature 4————
Feature 5————

market research

What the market research covered: its size, where it’s heading, and who is buying.

  1. 01

    Finding one

    A market fact that shaped the product.

  2. 02

    Finding two

    A second fact, with its source.

  3. 03

    Finding three

    A third fact, or a trend to design for.

user interviews

Who was interviewed, how many, and what the sessions set out to learn.

  • Participants
  • Interviews
  • Insights
  1. 01

    Insight one

    Something users said or did that changed the plan.

  2. 02

    Insight two

    Something users did that they didn’t say.

  3. 03

    Insight three

    A third insight, ideally with a quote.

personas

How the personas were drawn from the research, and which ones the product serves first.

primary personas

select a name, or step through with the arrows

secondary personas

  • Secondary persona 1

    Secondary persona 1

    Their role, and why they matter.

  • Secondary persona 2

    Secondary persona 2

    Their role, and why they matter.

user needs

  1. 01

    User need one

    What users need from the product, in their terms.

  2. 02

    User need two

    A second need.

  3. 03

    User need three

    A third need.

pain points

  1. 01

    Pain point one

    What gets in the way today, and what it costs them.

  2. 02

    Pain point two

    A second pain point.

  3. 03

    Pain point three

    A third pain point.

rapid prototype

user flows

  1. 01

    Flow one

    What the flow lets the user do, start to end.

  2. 02

    Flow two

    A second flow.

  3. 03

    Flow three

    A third flow.

build with AI

How AI was used to build the prototype: the tools, what it sped up, and what still needed a designer’s hand.

  1. 01

    A tool or step, and what it did.

  2. 02

    A second one.

  3. 03

    What was learned about building with AI.

imageThe prototype built with AI
16:10

userology: click prototype testing

How the click prototype was tested on Userology: who took part, the tasks they were given, and what was measured.

  • Participants
  • Tasks
  • Sessions
imageA Userology test session
16:10

results

  • %Task success
  • Usability score
  • Findings
  1. 01

    Result one

    What the testing showed, and what changed because of it.

  2. 02

    Result two

    A second result.

  3. 03

    Result three

    A third result.

design

north star vision

The long-term vision for the product: where it’s heading, and the bet it makes.

imageNorth star vision
21:9
imageMilestone 1 designs
16:10

01 milestone

Milestone 1

What milestone 1 set out to deliver, and when.

  • A key screen or feature, and what it does.
  • A second one.
  • A third one.
imageMilestone 2 designs
16:10

02 milestone

Milestone 2

What milestone 2 set out to deliver, and when.

  • A key screen or feature, and what it does.
  • A second one.
  • A third one.
imageMilestone 3 designs
16:10

03 milestone

Milestone 3

What milestone 3 set out to deliver, and when.

  • A key screen or feature, and what it does.
  • A second one.
  • A third one.

main screens

  • imageMain screen 1
    16:10

    Main screen 1

  • imageMain screen 2
    16:10

    Main screen 2

  • imageMain screen 3
    16:10

    Main screen 3

  • imageMain screen 4
    16:10

    Main screen 4

what's next

  1. 01

    Next step one

    What comes next for the product, and why.

  2. 02

    Next step two

    A second next step.

  3. 03

    Next step three

    A third next step.