Product Thinking — Part 2: Personas & Jobs to Be Done

maang.io AI-Native Builder Series

What is this?

Think about how a great novelist writes. They don't write for "readers." They picture one specific person in a chair — her age, what she worries about at 2 a.m., what makes her laugh — and they write to her. Strangely, by writing for one vivid person, the book ends up resonating with millions. Writing "for everyone" would have produced something true to no one.

Designing an app is the same craft. In Part 1 you learned to aim at a specific user instead of "everyone." This chapter gives you the two tools that make "specific" real and usable. The first is a persona: you stop saying "the user" and instead invent one concrete person — give them a name, an age, a phone, a frustration — so that every design question becomes "would Maya actually do this?" instead of an abstract guess. The second is even sharper: figuring out the job people are really hiring your app to do — because people don't want your app, they want the thing it gets done for them.

The one-line idea: design for one vivid imagined person (a persona) by understanding the real job they're hiring your app to do — because nobody wants software, they want a job done.

The novelist writes to one person and reaches millions. You're about to do the same thing with StreakUp.