Thank you!

This article is by Sunita Mohanty, who is a Product Lead as a part of Facebook's New Product Experimentation. She has built products for startups, nonprofits and global public companies, most recently leading product teams at Oculus, Facebook Core Growth and as Director of Product at Lumosity. She is also a startup advisor, angel investor, and member of First Round’s Angel Track community.

In my role leading product teams as a part of Facebook's New Product Experimentation, we’re focused on that hazy “0 to 1” stage of building, where ideas are unproven and products are in their most nascent stages. My job is to distill the complicated unknowns of a big, disruptive vision into clear, actionable steps for my teams and increase our chances of finding product-market fit at every step. This focus on taking big swings while still pursuing concrete steps toward building valuable products is the direct result of my previous experiences — I’ve felt the pain that comes from building products that fail to tackle a clear problem firsthand.

Right after grad school at Stanford, I found myself in the middle of my first startup: a failing K-12 analytics company. We were on a mission to improve a broken education system with the promise of interesting technology. But we were stuck in circles of decision-making and couldn’t successfully execute or build traction. Looking back, it’s easy to diagnose that we had a hard time focusing on which problem to solve first because we didn’t understand the actual problems of our audience well enough — we only assumed we did.

Now in my work as an angel investor and advisor, I see teams run into this very same brick wall. As I help them prioritize early product and go-to-market efforts, I often find myself dishing out the same advice: Do the work to make sure you are building a product that people will actually find valuable. That requires an incredibly deep understanding of the user, their hopes, and their motivations, instead of taking the easier path of operating off of untested assumptions.

Many entrepreneurs may do this intuitively — but many others fail to cultivate a deep level of empathy for their users, which ultimately can lead to building the wrong product for any specific market. If you don't put in the work upfront, you risk charting the wrong course towards product-market fit, which you may not discover until you’re facing struggling retention numbers or battling high user churn.

There’s a range of philosophies out there on how to avoid this trap and better approach early stage customer development, but in both my advisory roles and in my day job, I've come to rely on one framework: JTBD (jobs-to-be-done).

I first read Clayton Christensen’s approach to JTBD while in grad school at Stanford, but it didn’t really sink in. After stumbling upon it again years later at Facebook, I’ve since found enormous value in employing a version of this framework as we built Oculus social features, Facebook Preventive Health, and more recently, Tuned.

Sunita Mohanty, a Product Lead in Facebook's New Product Experimentation group

JTBD is by no means a new way of thinking. But it can be confusing to get started with, since it’s heavy on the corporate strategy jargon and has been reinvented many times over. A quick Google search reveals a bevy of confusing terms, from the debate over jobs-as-progress and jobs-as-activities, or the competing visualizations of maps and hierarchies. I’ve also found that JTBD has a bit of a consulting-esque vibe and seems less vision-driven, which can be off-putting to many product-driven founders.

If you’re looking for a deep-dive into the jobs-to-be-done theory and how others apply it, I recommend reading through this primer from The Christensen Institute, this article from Harvard Business Review, Alan Klement’s overview of two different interpretations and Intercom’s guide. But if you’re looking for something a bit more lightweight and accessible for startup product teams, read on for my simplified approach to JTBD.

In this article, I’ll detail the version of this framework that’s used by product leaders at Instagram and Facebook, and applied in my capacity as an angel investor and advisor to early-stage teams. I’ll walk you through my template, examples from other companies for inspiration, and advice for the entire process from early concepting to launching and refining. In addition to outlining the case for using a framework instead of relying only on your gut, I’ll share tactics and templates for pulling together a clear set of product development principles that can inform your value props, PRDs and go-to-market tactics in order to execute with precision.


Do you find your team is unable to align on what matters most about your product as you’re starting out? Or that you’ve worked hard to bring something to market that you were all excited by, but you’re not getting traction with users? Founders, early-stage teams, and even later-stage product orgs run into these problems time and time again. The bottom line is that you can very easily build something, but to increase your chance of creating something that is solving a real problem you need to be more rigorous in your approach.

Anyone can build products. Not everyone can build products that solve a real problem and land product-market fit.

More specifically, here are three common problems I see both early- and late-stage product teams running into that indicate a framework might be useful:

Intuition and conviction are extremely important in building early-stage products, but pairing it with listening to users can increase your chances of being right.


Whether you’re a product manager innovating within a larger company, or building a brand new early-stage product at a startup, the JTBD framework works to create better, non-obvious insights about your audience. Ultimately, the core value of this framework is that it provides an approach to gathering an understanding of who your user is, and what their motivations and hopes are. You as the founder or product leader are left to determine how to translate this into what matters most for your product — combining great intuition with great information gathering to make better bets on where to invest resources.

While JTBD has been used for 30 years in industries making physical goods, it’s relatively newer in software building circles. The theory of jobs to be done centers around understanding customer behavior and underlying rationale for making choices.

The idea is that innovators win by resolving a consumer’s struggle and satisfying their unmet aspiration. Harvard Business School marketing professor Theodore Levitt explained it this way: "People don't want to buy a quarter-inch drill. They want a quarter-inch hole!” When describing his now classic milkshake example, Clayton Christensen summed it up this way:

“People don’t simply buy products or services, they ‘hire’ them to make progress in specific circumstances.”

In this theory, people are trying to complete certain “jobs,” which they in turn “hire” a specific product or service to help them accomplish. They may “fire” a product or service if it is not adequately completing the job.


A jobs to be done statement concisely describes the way a particular product or service fits into a person's life to help them achieve a particular task, goal, or outcome that was previously unachievable. When crafted well, these statements create clarity around what doesn’t exist today and what product builders can focus on to innovate. In my experience, the exercise of creating a clear JTBD statement is the most important part of this framework. In this section, I’ll walk through why you need one, offer both advice and my go-to template for putting your own statement together, and share example statements from several companies as inspiration.

Why you need one:

A good, crisp JTBD statement captures underlying motivations, triggers and context for the problems your user faces. This statement can be foundational for your entire product and GTM planning, from focusing your PRD or product spec, to identifying your channels and marketing messages.

A good statement will help remove bias, build empathy for users and bring alignment across product, marketing and eng teams. When you have a well-crafted (and well-communicated) jobs to be done statement, the following things start to fall in place:

Here’s an example of the power of the JTBD statement in action: Recently, one of the startups I angel invested in reframed their early product thinking using the JTBD framework. As a team of two engineers, they found themselves thinking along the lines of very specific user stories based on the broad goal of their product for remote teams. After re-thinking their approach to customer interviews using JTBD and arriving on a clear statement based on what they heard, this team was able to re-frame their product to focus on encouraging fun — and found promising early traction with this new value prop.

Put in the legwork: A template and 4-step process for crafting a standout JTBD statement

Before putting pen to paper, lean on these guidelines:

A clear JTBD statement should help you communicate with absolute clarity what a specific group of people want in a specific circumstance — and their barriers to getting it.

The basic jobs-to-be-done statement framework is specific about the context people are in today, the barriers in the way of achieving their goals, the goals they want to achieve and their desired outcome.

To put that into practice, here’s a JBTD statement template that I find helpful and is commonly used amongst Facebook and Instagram product teams:

With those principles and end goal in the background, follow these four steps to gather all the info you’ll need to fill out your JTBD template:

1. Start by defining your audience clearly.

Think about the defining characteristics that help you develop a crystal-clear image in your head of your audience. Without a clear definition, you risk going too broad or gathering signal from the wrong kinds of people.

2. Ground yourself in market research.

Understand as much as possible about this audience’s behavior: what they currently are using to solve this specific problem and where they feel the most pain in the customer experience. Test out all the products related to what you’re building or what users have hacked together to accomplish the job. You should arrive at a clear understanding of the alternate products they are “hiring” or “firing” to accomplish the job and why.

3. Talk to your users.

Using surveys and interviews, get a firsthand account about your user’s mindset and decision process (related to what you are building). More specifically, try to:

Whether you’re using surveys or interviews, carefully word questions so that you are not leading people to a specific answer. For example, when we started concepting Tuned, we began by doing research into couples’ general communication patterns before asking specifically about apps for couples or the solutions we were thinking about. The problems we heard from these conversations helped us to prioritize amongst a range of ideas to focus on emotional connection over tactical task management, like keeping track of grocery lists.

Stepping back to understand deeper context and underlying motivation is important because people are notoriously bad at predicting what they want.

4. Prioritize.

There are many customer jobs your product could tackle, but focus is paramount here. From user interviews, look for themes that emerge in jobs to be done. You can also run surveys that ask users to rank the importance of jobs and how well each job currently is served by another app or product to gain a better understanding of the market opportunity. This can help you to narrow down jobs and prioritize those with the most demand and the largest gap to be filled.

I like to use this framework when thinking about which jobs to tackle:

How to think about which jobs to tackle in the JTBD framework

If you can, try to go through the steps above to develop a first pass at a JTBD statement, and then retest it using surveys or interviews, asking users questions to find out if this job matters most to them in order to tighten your JTBD definition. Taking in new information to refine your JTBD allows you to re-examine your core assumptions and update your own intuition.

JTBDs IRL: Examples to bring this framework to life

To take it from the realm of theory to the more practical, let’s unpack some different products (some I’ve worked on and my analysis of others), their audiences and their JTBDs. These aren’t the case studies you’d encounter in business school, but rather quick real-world examples (from companies I respect and my own team) that might help guide your own thinking.


Discord JTBD: When I want to jump into my favorite game, but I don’t know if there are people around to play, help me safely coordinate with a group of like-minded gamers, so I can easily find a way to enjoy my favorite multiplayer game. This suggests features like making it easy to find people through public or private servers and switching easily from text to voice chat as you organize and jump into a game.


Peloton JTBD: When I need an option to workout, but I can’t go to my favorite studio, help me to get a convenient and inspiring indoor workout, so I can feel my best for myself and my family. This suggests features like an instructor-led experience, light social motivation through leaderboards and high fives and, most importantly, a physical bike are important core parts of the value.


Segment JTBD: When I need to understand what people are doing on my platform, but I have different sources of data that all tell me different stories, help me easily pull together one source of truth so that I can make better product and marketing decisions to improve my business. This makes clear the core value of Segment’s single API that allows companies to tap into dozens of analytics services to create a single view of a customer.


Mutiny JTBD: When I need help enterprise accounts discover and trust our value prop, but I have limited time and resources to test different approaches that might resonate, help me quickly and confidently deliver the right message. This makes clear how Mutiny conveys its value prop — rather than focusing on its capabilities as a personalization platform, it suggests emphasizing ease of use and ROI when ABMs use their platform.


Tuned JTBD: When I want to feel connected to my partner, but don’t have a special way to share my feelings, help me be more emotionally expressive, so we can strengthen our bond. This suggests a set of features that give you a wider emotional range (like sharing your mood, stickers, greeting cards) to feel a moment of deeper connection with your partner vs. tactical features like keeping track of grocery lists.


JTBD isn’t a static statement, nor is it a one-time exercise suited for the entirety of a company’s lifespan. I see teams often go through this process once, but then fail to revisit this with new information as they execute. This is a framework to be regularly updated, and it’s relevant across all stages and challenges that product teams encounter. If used well, it can continually focus on what matters most as a north star and increase the odds of finding product-market fit.

How to incorporate JTBD into the product org:

Beyond the value of clearly capturing JTBD in the early days, you can weave it throughout your product team’s process as you start to spell out your value props, PRDs and go-to-market tactics. Through each step of planning to execution, JTBD can provide the clear set of principles that drive the hypothesis you are trying to prove of what brings value to users.

See below for some more specific ideas of how you can weave the JTBD framework into each stage of product development — and check out the templates I’ve come to lean on in my own role.

How to revisit your JTBD statements:

Through each of the above stages, you can come back to JTBD statements to help your product, eng, design, marketing, research and all other cross functional teams understand who you are building for and what matters most. This shared understanding makes it much easier to navigate tradeoffs — such as which features to prioritize building in your roadmap or what channels of acquisition to invest in.

Even if you’re not an early-stage product team or startup, it’s never too late to tighten up your messaging with the findings from JTBD research — or pivot to ensure you’re solving the needs that drive people to hire products. As you revisit your growth strategy, periodically do interviews to understand how your customers currently use your product. You can specifically ask people if the product is solving the job you intend it to tackle in order to validate your understanding. In the process of building Tuned, we are taking this approach to keep evolving what we know about our core audience which has led us to find more focus and opinion in our product.

Remember that this isn’t a static process. The best product teams continue to refine their understanding of users and what problems are most important — improving intuition along the way.

Ultimately, building products people love requires curiosity, deep listening and truth-seeking to make sure the problems you think you should solve are truly real pain points. Taking that work on with an open mind and a systematic approach is key to instilling — and reinforcing — this mindset in your own product org.

Thank you to the First Round Review team, AJ Frank and Jaleh Rezaei for the thought partnership on this piece.

Cover image by Getty Images / Sainam Poploy / EyeEm.

First Round ReviewThe best advice in tech
Subscribe for Exclusive Access