JTBD analysis: what job is Instagram Stories hired to do?
Instagram Stories grew to 500M daily users in three years. JTBD analysis explains why — it wasn't competing with feed posts. It was competing with sleep.
Instagram launched Stories in August 2016 — a near-direct copy of Snapchat's signature feature. Within three years, Stories had ~500M daily users, surpassing Snapchat's entire app. Most product post-mortems credited "execution speed" and "distribution advantage". JTBD analysis suggests something more specific.
The forward question that didn't work
Pre-launch, Instagram's product team had been wrestling with a long-observed problem: engagement on the main feed was declining despite user count growing. Users opened the app, scrolled briefly, and closed. The feature pipeline reflected the obvious question: how do we get users to post more content to feed? Filters, editing tools, prompts to post — all incremental, all unsuccessful.
The JTBD reframe
Looking at the same observation through a jobs lens, the team identified a different question: what job were users actually using Instagram to do?
The answer was uncomfortable: by 2016, users were no longer "hiring" Instagram to share their best moments with friends — they were hiring it to fill empty moments and feel connected without obligation. Specifically:
- 5-minute waits (elevator, line, between meetings)
- Lonely evening hours
- Procrastination breaks
- Pre-sleep wind-down
The job had drifted away from production (posting) toward consumption (scrolling). The team had been optimizing the wrong side.
What competed for this job
Once the job was named correctly, the competitive set changed:
- YouTube (long-form filler)
- Snapchat (lightweight, low-effort posting)
- Reddit / Twitter (scrolling feeds)
- Sleep — for the bedtime usage moment, sleep is genuinely a competitor
Instagram's feed format was actually a poor fit for the job: feed posts felt high-stakes (they stay forever, get publicly liked or not), so users posted less, so consumers had less to consume, so engagement decayed. A doom loop.
The Stories design as JTBD answer
Stories addressed each pain point of the job, not the original "share your best moments" pitch:
- 24-hour expiration removed the long-term-record anxiety → users posted casual content they'd never have posted to feed
- Full-screen, swipe-through matched the empty-moment consumption pattern (scrollable, ambient)
- No public like count removed the social comparison friction
- Tap-to-skip respected the user's attention budget — they could exit any individual story instantly
The result: users posted ~10× more content to Stories than to feed (per Instagram's 2019 data), and consumers had more to consume, which kept the app open longer. The doom loop reversed.
What this teaches
Most "engagement problems" are job problems in disguise. If you're tuning the UX of the wrong job, you can ship beautifully-designed features that don't move metrics.
The competitive set you assume is usually the one your product was designed for, not the one it's currently being hired for. Instagram's competitive analyses pre-2016 focused on Facebook and Twitter — peer social networks. The actual competition for the user's evening 20 minutes was Snapchat, YouTube, and (genuinely) sleep.
JTBD reframing doesn't tell you what to build — but it tells you what to stop building. Once the team accepted the job had shifted, dozens of in-flight features got cancelled because they served the wrong job.
Run your own JTBD analysis
The full methodology is in the Academy guide →. To structure a JTBD analysis for your own product, open the canvas →.
Frequently asked questions
What job is Instagram Stories hired to do?
Stories is hired for low-stakes social presence — sharing small moments without the permanence and editorial pressure of a feed post. The JTBD statement: 'When I have a moment worth sharing but it doesn't warrant a permanent post, I want to broadcast it to my friends ephemerally, so I can stay connected without curating my profile.' This job is distinct from the 'curate my identity' job that the feed serves, which is why both surfaces grew rather than cannibalizing each other.
Why did Instagram Stories grow so fast after launch?
Stories grew to 500M daily users in three years partly because the JTBD it served — low-stakes ephemeral sharing — was largely unmet by the existing feed. Snapchat had identified the job first but lacked the social graph and discovery surface. Instagram's copy was effective because the underlying job mattered to a large audience already on the platform, not because the feature was particularly novel. Job-fit > feature novelty in this case.
How is the JTBD for Stories different from the JTBD for the Instagram feed?
The feed serves a 'curate my identity' job — posts are permanent, public-by-default, and editorial. Stories serves a 'maintain presence' job — posts are ephemeral, semi-public, and casual. Different jobs require different design defaults. Conflating the two led several feed-based platforms (Twitter, LinkedIn) to launch Stories clones that underperformed, because their existing audiences didn't have the maintain-presence job on those platforms.
What does this example teach about competitive analysis?
Stories' competition wasn't other photo-sharing surfaces — it was sleep, idle scrolling, and not opening the app. JTBD reveals that the relevant competition is whatever else the user could do with the same situation/motivation. This is why JTBD often expands the competitive set beyond what category-based analysis would identify, and why teams using JTBD frequently change which competitors they obsess over.