Designing for focus in a product designed for engagement — YouTube UX case study

I wanted to solve a simple problem: how can YouTube help students find what they need without tempting them into everything else?

A few months back, when I was a college engineering student, I had my semester exams coming up. Like most students, I had a lot to study and very little time left.

One night before an exam (obviously, huh), I sat down with my laptop, opened YouTube, and told myself, “I need to understand this topic, so let’s quickly watch it and then continue studying.”

I found the video I was looking for.

Then another recommended video appeared.

Then a Short.

I watched one.

Then another.

And somehow, that “quickly watch it” turned into a lot more time than I had planned to spend.

The funny part?

I wasn’t on YouTube to procrastinate. I was there to study.

Anyways the semester results came out.

They were… okay. Not terrible. But not exactly what I had hoped for either.

Looking back, there were plenty of things I could have done differently. I could have started studying earlier. I could have managed my time better. And, most importantly, I could have stopped scrolling that night before the exam.

But, as a completely normal human being, I did what many of us do when things don’t go as planned:

I blamed YouTube. Hehe!

And this wasn’t just my problem. When I talked to my friends, I realized many of us had gone through the same thing. We would open YouTube with a very specific study goal, but somewhere between the recommended videos, Shorts, and everything else competing for our attention, we would lose track of why we opened it in the first place.

Of course, YouTube wasn’t entirely responsible. The problem wasn’t that YouTube had Shorts or recommendations. Those features are a huge part of what makes the platform useful and engaging.

But that experience made me think:

What if YouTube had a mode designed specifically for focus?

That was the idea behind YouTube Focus Mode.

Instead of creating another productivity app or blocking YouTube altogether, I wanted to explore a simpler question:

Could YouTube itself become a little less distracting when the user’s goal is learning?

And that question became the starting point for this UX case study.

The Problem

The problem wasn’t necessarily why students opened YouTube.

It was what happened after they did.

I surveyed 32 students who regularly use YouTube for studying to understand when distraction happened, what triggered it, how students currently dealt with it, and what kind of solution they would actually prefer.

The results changed how I framed the problem.

Only 28.1% said they mostly studied what they originally planned. Meanwhile, 34.4% said they usually started studying and got distracted after some time, while 12.5% got distracted almost immediately.

So this wasn’t simply a case of students opening YouTube to procrastinate.

Many were opening it with a genuine learning goal.

What was pulling them away?

The strongest reported first distractions were:

• Home feed recommendations — 50%
• YouTube Shorts — 46.9%
• Notifications — 12.5%

Search suggestions and autoplay were much less significant.

That gave me an important distinction:

The problem wasn’t simply that students lacked self-control. The environment around their intended task was also competing for their attention.

Research Changed the Direction

I initially thought about distraction as something that could be solved with blocking.

But that created another problem:

YouTube was also the thing students needed.

A blocker could remove distractions, but it would also remove the lecture, tutorial, or explanation they came to watch.

The survey pointed toward a different approach.

53.1% of participants preferred controlling what type of content appeared within YouTube, compared with 21.9% who preferred limiting their total time. Very few preferred completely blocking YouTube.

That became the turning point.

Instead of asking: How do I stop students from using YouTube?

I started asking:

How can YouTube give students more control over what they encounter while they’re studying?

This became the core design principle:

Reduce passive distractions without taking control away from the user.

From Research to Concept

I explored four possible directions:

1. A time-based Focus Mode

A timer could create a clear boundary around a study session. But timer preferences varied, so I didn’t want it to become the foundation of the experience.

2. Blocking YouTube

This would remove distractions completely. But it would also remove the learning content students needed — and conflicted with the preference for content-level control.

3. Distraction reminders

Instead of blocking unrelated content, YouTube could remind users when they moved away from their study goal. This preserved user choice, so I kept the idea.

4. Intent-based content filtering

Users could tell YouTube what they wanted to study, and the platform could temporarily reshape their experience around that intention.

For example:

Topic: DSA
Channels: Selected educational channels
Session: Optional duration

This direction connected most directly to the research, so it became the foundation of the final concept.

User Personas

The research helped me move beyond percentages and understand the people behind them. I created two personas representing different ways students use YouTube for learning — one focused on staying on track and the other on exploring through trusted educational content.

Introducing Focus Mode

Focus Mode is a conceptual YouTube feature that temporarily reshapes the experience around a student’s learning goal.

Users can:

• Select topics they want to study
• Optionally select trusted subscribed channels
• Set a session duration or end it manually
• Get a feed focused on relevant content
• Avoid Shorts and unrelated recommendations during the session
• Continue or exit if they attempt to access unrelated content

The important part is that Focus Mode doesn’t completely restrict YouTube.

It gives users more control during a specific study session.

Designing the Experience

Once the direction was clear, I mapped the experience around one question:

What does the user need at each moment to stay in control of their study session?

The core user flow became:

1 — Start with intention

The first interaction introduces Focus Mode and lets the user set it up. I kept the explanation short because a focus feature shouldn’t become a distraction before the session even begins.

2 — Define what to focus on

Users can choose topics such as AI, Coding, and DSA.

They can also select specific subscribed channels if they want a narrower content filter. Channel selection is optional because not every student wants to restrict their learning to specific creators.

They can also set a focus duration for the session. Users can choose from preset time options or set a custom duration, while also having the option to end Focus Mode themselves whenever they want. The timer is designed to support structure without making the experience feel restrictive.

3 — Reduce passive distractions

Once Focus Mode is active, the Home feed prioritizes content related to the selected topics. Shorts and unrelated recommendations are removed from the experience. The goal wasn’t to redesign YouTube. It was to temporarily change what deserves attention.

The session also remains under the user’s control. Even if a timer was set, users can end Focus Mode at any time before the selected duration is over. The timer provides structure, not a restriction.

4 — Handle distraction without blocking

What happens when a user deliberately tries to watch something unrelated?

Instead of blocking them, Focus Mode shows a neutral reminder. The user can continue with the content or end Focus Mode. This was an intentional choice. The research showed that distraction was already associated with feelings such as guilt, stress, and frustration for many participants. I didn’t want the product to turn that moment into “You failed to focus.” It should simply remind the user “Focus Mode is active. Do you want to continue?”

Usability Testing

With the clickable prototype ready, I tested the experience with 5 users, with some sessions conducted remotely through Google Meet. Rather than explaining how Focus Mode worked, I gave users realistic study-session tasks and observed how they navigated the prototype on their own.

I asked users to:

1. Set up a one-hour DSA study session.
2. Configure access to their study playlists.
3. Set up Focus Mode using only topics.
4. Handle an attempt to watch something outside their selected topics.
5. End Focus Mode.

Most of the core flow was understandable, but two issues created confusion.

“Sidebar access” wasn’t clear

Only 3/5 users completed the sidebar configuration task. Two users were confused by the term “Sidebar access.” The functionality wasn’t necessarily the problem. The language was. So I revised the helper text to explain what the option actually allowed users to access.

Channel selection felt mandatory

When asked to set up Focus Mode using only topics, 4/5 users understood the flow, but one expected channel selection to be required. That wasn’t the intended experience. I added an “Optional” label to channel selection.

A small change, but an important clarification:

Topics are enough. Channels are an additional layer of control.

What I didn’t change

Not every test result needed a redesign.

All 5 users completed the initial Focus Mode setup, and all 5 could show how they would end the session. Those flows remained unchanged.

This was a useful reminder that usability testing isn’t about changing everything. It’s about finding where the experience actually creates friction.

Click here if you want to see the working prototype.

What the Project Taught Me

The biggest shift happened between my initial assumption and the final concept.

I started with:

“How can I stop students from getting distracted on YouTube?”

I ended with:

“How can YouTube better support what students came there to do?”

That difference shaped the entire project.

I learned three things in particular.

1. Start with intent

The feature became much more useful once I stopped treating distraction as the starting point and started looking at the user’s original goal.

2. Research should change your solution

The research didn’t just validate Focus Mode. It pushed me away from a traditional screen-time blocker and toward content-level control.

3. Small UX problems matter

Two users being confused by a label may seem minor. But if someone has to stop and figure out what an option means, the interface has already created unnecessary cognitive load. Sometimes the best iteration isn’t adding another feature. It’s making an existing decision easier to understand.

What I’d Improve Next

Focus Mode is still a concept, so I can’t claim that it actually reduces distraction or improves study outcomes in real-world use.

The usability test told me that users could navigate the prototype. It didn’t tell me whether the feature would change their behavior over days or weeks.

If I continued the project, I’d focus on three areas.

1 — Test real study sessions

I’d observe how Focus Mode performs during longer sessions:

• Do users stay within their intended topic?
• How often do they exit early?
• Do they return to unrelated content?
• Which settings do they actually use?

2 — Test the reminder experience

I’d explore whether the distraction reminder genuinely helps users reconsider — or eventually becomes another interruption.

3 — Stress-test the content filtering

I’d test what happens when the system gets the user’s intent wrong:

• Test content classification: What happens when a relevant video isn’t classified under the selected topic?
• Test content relevance: What happens when a video matches the selected topic but isn’t useful for the user’s actual study task?
• Test adjacent exploration: What happens when a user wants to explore something related but outside their original topic?

These questions would become important before considering the concept production ready.

Final Thought

This project started as a question about distraction. It ended up being a project about intent. Students don’t always need products to tell them what not to do. Sometimes they need products to make what they came to do easier. And that’s the idea I’d take with me from this project:

Design for what the user came to accomplish — not just for what the product wants them to do.

Designing for focus in a product designed for engagement — YouTube UX case study was originally published in Bootcamp on Medium, where people are continuing the conversation by highlighting and responding to this story.