What Creators/Innovators Can Learn from iGen
A designer building a social app for teens keeps hitting the same wall in testing. Her prototype assumes users will meet up after matching, the way she remembers doing at sixteen. Instead, testers keep the conversation going for weeks inside the app, treating the chat as the friendship itself, not a step toward one. One tester mentions, almost as an aside, that she has more "close friends" online than she's met in person, and also that she sometimes feels weirdly alone despite it. The designer wonders whether she's been building for a version of teenage life that no longer exists.
The whole book, compressed
This edition works through 4 core lessons — take them one at a time, not all at once.
What's different for your conditions
Tap whichever ones sound like you. Nothing here is sent or saved — it's just for your own noticing.
0 of 5 selected
The core lessons, applied to you
The audience you're building for grew up on a different adolescent timeline
Twenge's research documents this generation delaying driving, dating, and paid work, spending far more adolescent time at home and connected to a phone rather than gaining early independent experience. Designing around an assumed "typical teen life" of driving to a friend's house or after-school jobs may miss how a meaningful share of your audience actually lives. Products and stories for this generation often need to meet people inside phone-mediated life directly, rather than treating it as a bridge to some other, more "real" experience.
Assuming heavy phone use signals passivity rather than an audience whose social life genuinely runs there.
Watch a small group actually use an early version of your product before assuming what "normal" behavior looks like for them.
Your most engaged users are also the most likely to report feeling lonely or anxious
Twenge documents a real trade-off: more physical caution, like less risky driving behavior, alongside more reported loneliness and anxiety than earlier cohorts. An app that keeps someone engaged for hours isn't automatically making them feel more connected, and might occasionally do the opposite. Building features that genuinely support connection, rather than only maximizing time spent, is both the more honest design choice and, increasingly, the one users themselves are asking for.
Treating high engagement time as proof of positive impact rather than checking connection afterward.
Ask a sample of users directly whether a session left them feeling more or less connected to real people.
Their friendships, family life, and creative outlets all run through the same platforms you're building on
Twenge's four everyday contexts, school, family, work, and friendship, converge for this generation inside the same handful of apps, meaning your product competes not only with rivals but with an entire social ecosystem a user's life runs through. A feature that seems like a small addition to you might represent a meaningful new social space to a young user, carrying real friendship and family dynamics into decisions you didn't design for.
Treating a feature as purely functional when users are actually experiencing it as a social space with real stakes.
Map who else, friends, family, might see a piece of user activity before shipping a feature that surfaces it.
Designing for this generation means understanding the shift, not exploiting or ignoring it
Twenge's broader message, understand this shift rather than judge or dismiss it, applies directly to anyone building products for young audiences. That means taking seriously both the genuine comfort many find in digital connection and the loneliness or anxiety some report, without assuming either cancels the other. It also means remembering your users are individuals, not one generational profile, so testing with real people beats designing from assumptions about a monolith.
A feature that reduces reported loneliness by encouraging real-world meetups might also reduce the time-on-app metrics your team optimizes for, and a feature that maximizes engagement might not serve the connection users say they want. Because Twenge's pattern is drawn from broad survey averages, not any individual user, your audience may include people who want more digital connection, less, or something you haven't built yet; user research beats assumption when designing for this group.
Name one thing, honestly
- Is your product measuring connection, or just measuring time spent? - Where might a feature you consider purely functional actually be operating as a social space with real stakes? - Have you tested your assumptions about "typical" teen behavior against how your actual users behave?
Good. Now look back at the "Try this" line under whichever lesson feels most connected to what you just wrote, and treat that as this week's actual assignment — not all 4 at once.
The practices from this edition
0 of 3 selected
Run this for seven days
Map who else, friends, family, might see a piece of user activity before shipping a feature that surfaces it.