UX Case Study · Digital Privacy · Gen Z · Mobile Concept

Zia

Designing a Digital Privacy Coach for Gen Z

Helping Gen Z understand and take control of their digital privacy without fear, jargon, or friction. A concept mobile experience that teaches privacy through quizzes, guided action, and lightweight gamification.

Role

UX Designer & Researcher

Timeline

6 weeks · Mobile concept

Methods

Interviews · Personas · Prototyping · Testing

Platform

Mobile (Concept)

01 — Problem

Privacy tools are broken for Gen Z

Gen Z users care about digital privacy, but most rely on default settings and only take action when something feels invasive. Existing privacy tools are complex, buried in menus, and written in technical language that discourages engagement. The core problem is not awareness — it's translation.

The Awareness Gap

Users recognize privacy terms e.g., cookies, tracking, VPNs; but can't explain what they mean or how they affect daily life. Recognition ≠ understanding.

Awareness ≠ understanding

The Action Gap

Privacy concern is reactive. Users only act after something crosses a personal "creepy" threshold. Proactive behavior is rare — not because users don't care, but because the tools make it hard.

Discomfort drives action

The Trust Gap

Users rely on default settings not because they trust them — but because alternatives feel time-consuming and confusing.

Defaults trusted by necessity

The Translation Gap

Privacy systems fail to translate abstract risk into understandable, actionable moments. Gen Z isn't apathetic...they're overwhelmed.

Abstract risk = paralysis

02 — Research

5 interviews · ages 22–26 · TikTok, Discord, YouTube users

I chose qualitative interviews over surveys because privacy attitudes are emotional and contextual. Interviews captured discomfort, resignation, and trust signals that surveys flatten.

User Interview Notes

30-min remote interviews — 5 Gen Z participants capturing emotional privacy patterns

Research Insights

Awareness ≠ Understanding

Participants recognized terms like cookies, tracking, and VPNs, but struggled to explain what they meant or how they affect them.

"I've heard of all them...I probably interact with them, but I don't really know what they mean."

Discomfort Drives Action

Privacy concern is reactive. Users act after something feels invasive or "creepy" — not proactively.

"If we were to talk about a certain product now...I'd probably see that exact product up on Amazon."

Defaults Trusted by Necessity

Users rely on default settings not because they trust them — but because alternatives feel time consuming or unclear.

"I just trust that the privacy settings that are already in place are good enough."

Expectations vs. Reality

Assumption	Reality
Gen Z doesn't care about privacy	They care when it feels personal
They understand privacy terminology	Recognition, not comprehension
Concerns lead to actions	Action follows discomfort, not concern

→

Opportunity: Design a privacy experience that connects abstract risk to everyday behaviors and shows users their actions actually matter.

03 — Personas

Two users at different privacy awareness stages

The Privacy Aware SkepticDevin — Community college student, Discord & YouTube user

The Cautious CreatorJasmine — High school student, TikTok & Instagram content creator

Design Principles

01 — Teach Without Lecturing

Use quizzes, examples, and friendly language instead of dense explanations.

02 — Make Privacy Feel Personal

Anchor learning in real triggers like ads, links, and app behavior.

03 — Reward Progress, Not Perfection

Encourage small wins rather than total mastery.

04 — Show Proof to Build Trust

Confirm actions clearly so users know something changed.

04 — Design

Wireframes → High-Fidelity

Early wireframes focused on minimal cognitive load, conversational guidance, and clear hierarchy. As designs evolved: visual feedback for actions, clearer progress indicators, stronger differentiation between quiz types.

Rather than acting as a control panel, Zia acts as a translator — turning complex systems into understandable moments.

Zia Chat — Initial Flow

Post-Quiz Chat Flow

05 — Usability Testing · 5 Findings · 5 Iterations

4 tests · 25–30 min · every finding iterated

Task-based flows mapped to both personas. Evaluated first-time clarity, educational effectiveness, quiz engagement, and trust signals.

Finding 1 — Users Wanted Faster Context

💬

"I was expecting to just kind of be brought directly to a quiz… Now it seems like I'm back at a dashboard."

Iteration

Notifications now lead directly to the relevant quiz or action bypassing the dashboard when coming from a privacy alert.

Finding 2 — Quizzes Needed Better Feedback

💬

"There wasn't really an explanation... just a check mark."

Before — No Explanation

After — Contextual Feedback

Finding 3 — Quiz Types Felt Repetitive

💬

"The lightning round has some of the same questions… but I get why they're repeated, to drill it into your brain."

Iteration

Differentiated quiz types by intent: learning quizzes introduce new concepts; lightning rounds reinforce existing knowledge. Visually distinct to set expectations.

Finding 4 — Users Wanted Proof of Action

💬

"I just get another chat saying that it was done. I guess I don't know for sure if it was actually done or not."

Before — Vague Confirmation

After — Visible Confirmation

Finding 5 — XP Lacked Meaning

💬

Users liked earning XP but didn't know what it was for or how it connected to their privacy progress.

Before — Meaningless XP

After — Progress Tied to Outcomes

06 — Outcome

What Zia demonstrates

Zia feels supportive, not judgmental, positioning privacy as something users can understand and manage. The final prototype presents a clear learning entry point, actionable guidance, and visible confirmation of progress and protection. This project demonstrates the ability to translate qualitative research into design direction, design for trust and comprehension, and iterate based on usability evidence.

Next Step 1

Test with younger Gen Z users (ages 13–18) to validate design for earlier digital behaviors.

Next Step 2

Measure long-term behavior change — does learning translate to sustained privacy actions?

Next Step 3

Explore browser or OS-level integrations to reduce friction and increase contextual relevance.

Want to discuss this project?

I'd love to walk through my research process, design decisions, and usability testing insights.

Get in touch