Quick answer: This guide looks back at 16–22 February 2026, ISO week 8. To block distracting websites at work, use an approved browser extension for session-based restrictions, or ask IT about broader controls when necessary. Start with a short blocklist, keep essential work tools accessible, and pair focused work with planned breaks.
The week’s context: choosing a method, not just a blocker
The discussion material for this retrospective raised a practical question: how do you make distracting websites harder to reach without breaking the parts of the internet you need for work? The useful distinction is between blocking a site in one browser, restricting it across a device, and applying rules through a managed workplace environment.
The Asian Efficiency guide supplied for this period organizes the options around device settings, third-party applications or services, and browser extensions. That is a helpful starting point, but work adds another consideration: permission. A method suitable for your own laptop may be inappropriate on an employer-managed computer.
This article uses that discussion as context rather than treating every referenced page as a newly verified publication. The workflow below is practical guidance, not a claim that a product launched or changed during that week. NGUMU’s described capabilities reflect the product information available at the time of writing.
Choose how widely you need to block websites
Before installing anything, decide what the restriction must cover. Are you trying to stop opening a news site in your work browser, or do you need organization-wide access rules? Those are different jobs.
| Method | Useful when | Main limitation | Workplace consideration |
|---|---|---|---|
| Browser extension | You want personal focus sessions in a supported browser | Do not assume it covers other browsers or native apps | Check whether your employer permits the extension |
| Device-level controls | Restrictions need to extend beyond one browser | Coverage and setup depend on the operating system and chosen control | Changes may require administrator approval |
| Managed browser policies | An organization needs centrally maintained website rules | These are administrative controls, not necessarily personal focus tools | Ask IT to configure and maintain them |
| Network-level filtering | An organization needs rules for traffic using its network | Coverage depends on the network and configuration | Leave workplace network changes to authorized administrators |
Google documents URL blocking and exceptions for managed Chrome browsers. Those controls are distinct from installing an extension for your own focus sessions.
For ordinary distraction management in a permitted browser, a browser extension is a proportionate starting point. If your goal is security enforcement or restrictions that employees cannot change, speak to IT rather than treating a personal focus tool as a security system.
Set up website blocking for a real work session
1. Check permission and define one task
On a managed work computer, check your organization’s extension policy first. If installation is disabled, do not look for a workaround; ask which tools are approved. Google’s extension installation guidance notes that organizations can restrict extension installation on work or school computers.
Then write down one concrete outcome for your session. “Work on finance” is vague. “Check the expense totals and draft the summary” gives you a reason to stay in the relevant tabs.
This matters because blocking removes an easy diversion; it does not decide what you should do next. Keep the task visible in a note so you can return to it when the urge to browse appears.
2. Identify the sites that actually interrupt you
Start with websites you open reflexively during difficult or dull work. Common categories include social feeds, video sites, and news pages, but your own browsing habits should determine the list.
Separate them into three groups:
- Unnecessary for this task: block them during the session.
- Needed for the task: keep them accessible.
- Occasionally needed: decide before starting whether this session requires them.
Avoid blocking every enjoyable website just to make the setup feel comprehensive. A short, relevant list is easier to test and less likely to interfere with legitimate work.
If social feeds are your main distraction, our January social media blocking guide offers a complementary reset approach.
3. Install NGUMU from the appropriate store
At the time of writing, NGUMU: Screen Time Control is available for Google Chrome, Microsoft Edge, Brave through the Chrome Web Store, and Mozilla Firefox. Choose the listing for the browser where you do your work, and review the installation permissions before approving it.
NGUMU combines focus timers with website blocking during focus sessions. Its available controls include blocklists, allowlists, and curated presets for social media, video, and news.
Use a preset as a starting point if it matches your distractions, then check the resulting choices against your task. Do not assume that a category such as “video” is always nonessential: a training video may be required for today’s assignment.
4. Choose a blocklist or an allowlist
A blocklist makes sense when you need broad web access but want a few distractions unavailable. This often suits research, troubleshooting, and work involving unfamiliar sources.
An allowlist is useful when the task has a narrow set of required websites. Preparing a report from a known dashboard and a document editor is a better candidate than open-ended research.
Whichever approach you use, check access to supporting services such as sign-in pages, file storage, and reference material. Do not assume that allowing one visible website automatically accounts for every service a workflow uses. Test the full journey before an important deadline.
5. Pick a timer that fits the task
NGUMU supports Pomodoro 25/5, 52-17, 90-20, the 20-20-20 eye rule, and custom cycles. Treat these as options rather than a hierarchy of discipline. A longer interval is not automatically more productive.
For a first attempt, a 25-minute focus period followed by a five-minute break offers a straightforward trial. Choose a longer cycle only when it fits the task and your availability. A meeting in half an hour is a good reason not to start a long session.
If interruptions are part of your role, arrange coverage or choose a quieter interval. Keep required communication channels available; website blocking should not make you unreachable when your job requires a response.
6. Test before committing
Start a trial focus session and check both sides of the setup: a distracting website should be restricted, while the tools required for your task should remain usable.
Include a sign-in step and an ordinary work action in the test. Opening a dashboard is not the same as confirming that you can download its report or save your changes.
If something essential is unavailable, adjust the configuration before your main session. The goal is useful friction around distractions, not friction around completing your work.
Handle websites that are both useful and distracting
Work rarely divides neatly into “productive sites” and “bad sites.” A social platform may be necessary for customer support. A video service may host a tutorial. A news website may be the source you are paid to analyze.
The practical answer is to make blocking task-specific. During a research session, leave the relevant source available. During the writing session that follows, block it if you no longer need it.
For example, a marketer might gather references first, then start a focus session to write a campaign brief with social feeds restricted. This separates collection from production without pretending the same website has the same value all day.
Be cautious about promising yourself access to “just one useful page” if your configuration has not been tested for that distinction. This guide does not assume NGUMU offers feed-only blocking or a particular URL-matching behavior. Check your actual settings rather than planning around an unconfirmed capability.
Pair blocking with fewer tabs and real breaks
Website blocking works best as part of a simpler browser workspace. Before a session, close unrelated pages and keep the tabs necessary for the current task. NGUMU includes tab management to limit distracting tabs, but you still need to decide what belongs in the session.
Breaks deserve the same preparation. NGUMU provides a pre-break “blink warning” eye-rest overlay and a full-screen break overlay that discourages returning early. These are prompts to pause, not evidence that the extension makes bypassing a break impossible.
Have a non-browsing break ready: stand up, get water, or look away from the display. Otherwise, a short break can become another round of feed-checking.
The 20-20-20 option is an eye-rest reminder, not medical treatment. Persistent discomfort deserves appropriate professional advice rather than simply a different timer.
For ideas on placing sessions within a broader working rhythm, see our week 4 deep work retrospective.
Review results without turning tracking into another task
After a few sessions, ask two questions: did the setup reduce unnecessary browsing, and did it preserve access to essential work? A blocker that frequently interrupts legitimate tasks needs adjustment, not stricter rules by default.
NGUMU includes session tracking with focus time, session counts, and daily or weekly goals. Use these as feedback about your routine, not proof of output quality. Completing a useful draft matters more than accumulating timer minutes.
At the time of writing, the Pro upgrade includes advanced analytics, extended timers, detailed blocklist controls, and persistent history. Evaluate those capabilities against a specific need rather than assuming an upgrade is required to begin.
For core features, NGUMU collects no personal data, and session data is stored locally. That does not replace your employer’s software review or imply anything about separate workplace monitoring systems.
If distraction extends beyond working hours, our post-holiday screen-time reset can help you think about boundaries outside the workday too.
Common problems and sensible adjustments
You keep switching to another browser
A browser extension should not be assumed to restrict a different browser or a native app. Where workplace policy permits, configure your supported work browsers deliberately. If you need broader enforcement, ask IT about an appropriate device-level or managed solution.
Your blocklist interrupts research
Reduce its scope or separate research and writing into different sessions. If an allowlist repeatedly prevents necessary exploration, a targeted blocklist may be a better fit.
You keep ending sessions early
Make the next session shorter and the task more specific. Identify whether you were stuck, tired, or waiting for information. Blocking can interrupt a browsing habit, but it cannot supply a missing decision or resource.
Every day requires exceptions
Build the routine around types of work rather than one rigid rule for everything. The restrictions appropriate for drafting a proposal may not suit customer support or investigation.
Start with one protected work block
The useful takeaway from this February 2026 retrospective is straightforward: learning how to block websites is mostly about choosing the right scope and preserving necessary access. Start with one task, a small set of distractions, a tested configuration, and a planned break. Review what happened before expanding the rules.
Ready to try it in an approved work browser? Install NGUMU for Chrome, Microsoft Edge, Brave via the Chrome Web Store, or Firefox and set up your first focused session.