Key Takeaways
- PMs keep 40-60 browser tabs open on a normal weekday, far above the knowledge-worker average.
- Tool-based browser organization (pinning Notion, Linear, Figma globally) fails because PMs run multiple projects in parallel.
- The PM Tab Stack is a four-layer system: Permanent, Project, Reference, and Open.
- A 10-minute Friday “tab hygiene” ritual prevents the rolling debt that crashes productivity by Wednesday next week.
- Chrome Tab Groups plus a sidebar tool like Leap is enough infrastructure — no need to switch browsers.
Most product managers have somewhere between 40 and 60 tabs open right now. Some of them are open from this morning. Some are from last week's discovery research. A few are from a launch you wrapped two months ago and never closed. There's at least one tab you genuinely cannot remember opening.
This is normal. The PM job spans more tools per project than almost any other role, and most tab-management advice — written for “knowledge workers” generally — fails to address how PMs actually work. This guide walks through a system that does: a four-layer framework called the PM Tab Stack, a weekly ritual that keeps it clean, and clear rules for when to close, save, or pin a tab.
Why Is Tab Management Harder for Product Managers Than for Other Roles?
PMs run more parallel projects than almost any other role on a product team. The Asana Anatomy of Work Index reports U.S. knowledge workers toggle through about 13 apps and 30 app switches per day on average. For PMs that number climbs because a typical week mixes discovery work, delivery work, stakeholder updates, and personal-dev reading — each with its own toolchain.
Engineers usually have one IDE and a handful of GitHub tabs. Designers usually have Figma plus references. PMs have Linear, Notion, Figma, Loom, Mixpanel, Slack, sometimes Jira, sometimes Productboard, plus customer interview tools and competitor sites — all for one feature. Multiply that by 3-7 active projects and the math gets ugly fast.
A 2021 Carnegie Mellon study on tab overload documented measurable disorientation and task loss when participants kept more than 35 tabs open. Most working PMs cross that threshold before lunch on Monday.
Why Does Generic Tab-Management Advice Fail PMs?
The standard advice — “close tabs you haven't used in two hours,” “pin your three most-used sites globally,” “use one window per workspace” — is designed for someone running one main project at a time. PMs don't work that way.
Pinning Notion globally sounds organized, but it means you're staring at the same Notion home screen whether you're in discovery for Feature A or sprint planning for Feature B. Closing tabs based on time fails because the customer interview Loom you opened on Tuesday is exactly what you need for Friday's PRD. One window per workspace sounds clean until you realize you need to copy a chart from your Mixpanel window into the spec in your Figma window.
The deeper issue is that PMs need project context to be the primary axis of organization, not tool context. The right system has to treat “Feature A discovery” and “Feature B sprint” as first-class containers, with the tools inside them. Most tab managers and most browser advice get this backwards.
What Is the PM Tab Stack?
The PM Tab Stack is a four-layer system for organizing browser tabs around how PMs actually work. Each layer has a different rule and a different home.
Layer 1: Permanent. These are the 4-5 tools you open every day across every project — typically Linear or Jira, Notion, Slack, calendar, and email. They get pinned at the browser level, always visible, one click away from any project context.
Layer 2: Project. These are project-scoped tabs grouped into named Spaces. Each active project gets its own Space — Discovery, Roadmap, Active Sprint, Launch — with the project-specific Notion docs, Figma files, dashboards, and customer evidence inside. You open one Space at a time, switch between them with a keyboard shortcut.
Layer 3: Reference. These are saved but closed. Past discovery research, archived sprint notes, last quarter's launch dashboards — anything you might need again but don't need open. Bookmarks folder or a saved-Space feature works well here.
Layer 4: Open. These are the genuinely new tabs you opened in the last hour for unknown reasons — investigating a bug, checking a stat for the spec, reading a competitor announcement. The default state for this layer is “closes by end of day or moves to Reference.”
How Do You Sort Tabs by Project, Not by Tool?
Start with your current open tabs. Most PMs find they have 2-3 truly active projects plus a long tail of “I opened that once last week” tabs.
For each active project, build a Space (using Chrome Tab Groups or a sidebar extension). Drop in only the tabs that serve that project. Discovery for Feature A might be: the project's Notion doc, the Mixpanel funnel for that flow, two Loom recordings from user interviews, and a Miro board with the journey map. Each tab earns its spot by being needed for that specific project.
The rule is simple. If a tab serves two projects, it's a Permanent (pin it). If it serves one project, it's a Project tab (goes in the Space). If it serves no current project, it's either Reference (save and close) or Open (decide by end of day).
Once you've done this for your active projects, you'll usually find you have 15-25 tabs of real Project tabs and another 10-15 tabs that get closed or moved to Reference. The first time you do this audit, expect to take 30-45 minutes. After that, the weekly ritual handles maintenance.
What's the Right Weekly Tab Hygiene Ritual?
A 10-minute Friday afternoon ritual prevents the rolling tab debt that crashes productivity by Wednesday next week. The ritual has four steps.
Step 1: Close every Open-layer tab. If you don't know why a tab is open, close it. If you might need it again, save it to Reference first. Spending 30 seconds deciding is better than carrying it for another week.
Step 2: Archive completed Project Spaces. If a project shipped, move its Space to Reference. You can always re-open it later if a bug or follow-up comes back. Keeping shipped projects open is the single most common cause of PM tab bloat.
Step 3: Audit your Project Spaces for drift. Tabs creep into the wrong Space (the Mixpanel funnel for Feature A ends up in the Feature B sprint Space). Spend 3 minutes per Space dragging tabs back to where they belong.
Step 4: Re-pin your Permanents. If a new tool became part of every project (a new analytics platform, a new feedback tool), pin it. If a Permanent has stopped being used daily, unpin it.
Microsoft's 2024 Work Trend Index found 48% of employees say their work feels “chaotic and fragmented.” The single most-cited cause was tool sprawl without organization. A weekly 10-minute reset addresses that for almost no cost.
When Should You Close, Save, or Pin a Tab?
The decision tree is short. When you look at any single tab, ask three questions.
“Do I use this for every project?” If yes — pin it as a Permanent. Examples: Linear, Notion home, Slack, calendar, email.
“Do I need this for an active project?” If yes — it belongs in that project's Space. Examples: a specific Notion PRD, a particular Figma file, the Mixpanel funnel for one flow.
“Might I need this again, even months from now?” If yes — save to Reference (bookmark or saved Space). Examples: past customer interviews, last quarter's research, an article you want to re-read.
If all three answers are no — close it. Carrying tabs “just in case” is what creates the 70-tab Friday-night browser most PMs are familiar with. The browser is not a filing cabinet. Bookmarks and saved Spaces are.
Which Tools Support the PM Tab Stack?
The system works in any browser, but some tools make it easier. The minimum infrastructure is Chrome's native Tab Groups feature — built into Chrome since 2020, free, and good enough for 3-4 Spaces.
For PMs running 5+ active projects, a sidebar extension is worth installing. The two main options in 2026 are Leap and Workona. Leap is the newer entry, designed around the PM use case, with a vertical sidebar, nested folders (you can group reference research three levels deep), and keyboard shortcuts for switching Spaces. Workona is the older option, broader audience, no nested folders. Both have free tiers that cover 4-6 Spaces.
Arc Browser used to be the best option for this kind of workflow, but The Browser Company froze Arc development in May 2025 and pivoted to a new AI-first browser called Dia. PMs who came from Arc are usually best served switching to a Chrome sidebar extension rather than another full browser.
One tool to skip: OneTab and similar “save all tabs to a list” extensions. They solve memory load (when your browser becomes slow), but not organization. They make every saved tab equal, with no project context — which means finding the right tab six weeks later becomes a small archaeology project.
Frequently Asked Questions
How many browser tabs is too many for a product manager?
Research from Carnegie Mellon (2021) on tab overload found measurable disorientation past 35 open tabs. For working PMs, 30-40 active tabs is manageable if they're organized into Spaces or Tab Groups. Past 60 tabs in a flat list, most people stop being able to find anything and the cognitive cost outweighs the value of keeping them open.
What's the best Chrome extension for managing tabs as a PM?
Leap and Workona are the two most-cited tools among working PMs. Leap is designed around the PM use case with nested folders and keyboard-first navigation; Workona is broader and older, lacking nested folders but with a longer track record. For lighter use, Chrome's native Tab Groups feature is built in and free.
Should I use bookmarks or a tab manager?
Use both, for different purposes. Bookmarks are for the Reference layer — pages you might want again but don't need open. A tab manager (Leap, Workona, or native Tab Groups) is for the Project layer — the actively-used tabs for current projects. Trying to use bookmarks for active projects creates click-tax; trying to use a tab manager for archived content creates clutter.
How do you manage tabs across multiple browser windows?
Most PMs are better served by one Chrome window per device, with Tab Groups or Spaces for context-switching, than by many windows. The reason is keyboard navigation: it's faster to switch Spaces than to switch windows. Use multiple windows only when you need to truly split-screen something, like watching a Loom while writing in Notion.
What's the most common tab-management mistake PMs make?
Keeping shipped-project tabs open “in case a bug comes back.” A shipped feature should have its Space archived (saved to Reference) the day after launch. If a bug comes back, you can re-open the archived Space in 3 seconds. Keeping the tabs open creates a slow accumulation of dead context that builds up over months.