The PM Tool Audit: You Have 15 Tools and Actually Use 3

Most mid-level PMs are running a stack of twelve to eighteen tools — an issue tracker, two doc apps, a roadmap viewer, a whiteboard, a forms tool, an AI note-taker, and more — but an honest audit almost always turns up only three doing real work: a tracker, a doc tool, and a chat app. Everything else is a recurring attention tax.

Quick answer: List every tool you've opened in the past 30 days, tag each by the job-to-be-done it serves, note the date you last used it for an actual decision, then score it keep, kill, or consolidate. Most PMs discover they truly depend on one tracker, one doc tool, and one chat app — the rest is overhead they've stopped noticing.

Why Your Tool Stack Is Quietly Taxing You

Every open tab and installed app charges rent, even the ones you barely touch, because your brain still has to track what lives where. That tracking cost — not the minutes spent inside the tool — is the real expense. Researchers call it attention residue, and it explains why a lightly-used tool can feel heavier than a well-used one.

Sophie Leroy's 2009 research at the University of Minnesota found that switching between activities leaves a residue of attention on the thing you left behind, so you're never fully present in the next task. Gloria Mark's work at UC Irvine on interruptions found something similar: returning to a primary task after a switch takes meaningfully longer than people assume. Applied to a PM's toolbox, a "quick check" of a roadmap app you rarely touch isn't quick at all.

Tool sprawl taxes you in a few distinct ways, and it helps to name them separately:

• Notification tax — every extra tool is another source of pings competing for your attention, whether or not you act on them.
• Translation tax — retyping the same status, decision, or update across three systems because none of them talk to each other.
• Maintenance tax — permissions, integrations, renewal negotiations, and "who owns this subscription" conversations nobody enjoys.
• Fragmentation tax — the actual judgment behind a decision lives in five places, so nobody, including you, can reconstruct why a call was made.

This is a wellbeing issue as much as an efficiency one — the mental load of monitoring scattered systems is a theme we cover in more depth in our guide to PM wellbeing.

How to Run a PM Tool Audit in Four Steps

A PM tool audit has four steps: list every tool that touches your work, tag each one by the job-to-be-done it serves, mark the date you last used it to make or unblock a real decision, then score it keep, kill, or consolidate. Block 45 uninterrupted minutes — most PMs finish the whole exercise in one sitting.

Step 1: List Every Tool You Actually Open

Don't rely on memory alone. Pull from your browser bookmarks bar, your desktop dock or taskbar, your company's SSO app list, and your Slack or Teams app directory. Check your expense reports or your finance team's SaaS spend for subscriptions billed to your card that you forgot existed.

Most PMs surface somewhere between 12 and 20 distinct tools this way, including a few "shadow" ones a teammate signed them up for. That number alone is usually the first surprise of the audit.

Step 2: Tag Each Tool by Job-to-Be-Done

For each tool, write down the specific job you hire it to do — not its category, its job. This is the same discipline behind the Jobs-to-be-Done framework popularized by Clayton Christensen and refined operationally by Bob Moesta: ask what outcome you were actually trying to produce, not what the software claims to be.

A whiteboarding tool's real job might be "get three stakeholders aligned on a flow before a Tuesday sync" — a job a shared doc plus a screen-share could also do. Naming the job, not the category, is what exposes overlap.

Step 3: Mark Last Real Use, Not Last Login

Distinguish between logging in and actually using a tool to move a decision forward. SSO dashboards will tell you a tool was accessed last week because a digest email auto-refreshed a session — that's not real use.

Write down the last date the tool produced something that changed what you or your team did next. If you can't remember, that's your answer.

Step 4: Score Keep, Kill, or Consolidate

Once you have tool, job, and last-real-use-date side by side, run each one through a simple rubric rather than a gut call. Here's what that inventory typically looks like before scoring:

This audit is really the first move in deliberately designing a personal PM operating system — a stack you chose on purpose instead of one you inherited by accident, one login at a time.

The Keep/Kill/Consolidate Scoring Rubric

Score each tool from 0 to 2 across four criteria — decision criticality, last real use, team dependency, and switching cost — for a total out of 8. Tools scoring 6 or higher are keeps, 3 to 5 are consolidation candidates, and anything at 2 or below is a kill with no further debate needed.

A tool that's easy to replace and rarely used isn't "nice to have someday" — under this rubric, it's a kill.

Run every tool from your Step 1 list through this table. Most PMs find the math brutal but clarifying: a tool you personally like using can still score a 2 if nobody depends on it and it's trivial to replace.

The Classic Finding: A Tracker, a Doc Tool, and a Chat App

Run this audit honestly across a real 15-tool stack and the same pattern shows up almost every time: one issue tracker holds the plan of record, one doc tool holds the thinking, and one chat app holds the coordination. The other twelve tools each handle a single job that one of those three could already do, just with a nicer interface.

Marty Cagan's writing at the Silicon Valley Product Group has long argued that what separates strong product teams from weak ones is rarely tool sophistication — it's clarity of thinking and empowered decision-making, which no dashboard can substitute for. A fifteenth tool doesn't add judgment; it adds a fifteenth place judgment could get lost.

Here's how the "orbiting twelve" typically map back onto the load-bearing three:

Because so much day-to-day judgment travels through chat threads and DMs, sharpening how you actually use that one channel matters more than bolting on a fourth core tool — a topic we go deeper on in our complete guide to PM communication. For the fuller landscape of what's worth paying for versus skipping, see our complete guide to PM tools and productivity.

Why PMs Accumulate Tools They Don't Need

Tool stacks grow through small, individually reasonable decisions: a manager mandates a new OKR platform, a colleague shares a slick prioritization app, a free trial never gets formally cancelled. Behavioral economics explains why cutting them is harder than adding them — loss aversion makes giving up a tool feel like losing capability, even a capability you haven't used in months.

Daniel Kahneman and Amos Tversky's prospect theory, one of the most replicated findings in behavioral economics, established that people weigh potential losses roughly twice as heavily as equivalent gains. Applied to your app list, that means cancelling a $15/month tool you might need "someday" feels worse than the actual $15 or the hour a month it costs you to keep tracking it.

SaaS management vendors like Zylo and Productiv, which audit enterprise software spend for a living, have reported for several years that the average employee logs into dozens of applications, and PM-heavy teams tend to sit above that average given how many tools market themselves as solving "planning." A few other forces compound the drift:

1. FOMO on new AI tools. A new AI note-taker or AI roadmap generator launches practically every week, and trying "just one more" rarely gets un-tried.
2. Org handoffs. Tools inherited from a predecessor or a reorg rarely get re-evaluated — they just get carried forward.
3. Sunk cost. Time spent setting up a tool makes it feel wasteful to walk away, even when the tool itself is dead weight now.

None of this reflects badly on you — it reflects an industry that keeps selling tools as a substitute for judgment. Recognizing that pattern early is worth doing deliberately as part of your career growth as a PM, since tool fluency is rarely what actually gets a PM promoted.

What to Do With the Other Twelve

Killing a tool isn't always your call alone, so triage by who owns it: cancel personal subscriptions immediately, propose consolidation for team-shared tools at your next planning cycle, and quietly stop opening anything mandated from above that nobody actually checks. The goal isn't zero tools — it's making every tool earn the attention it costs.

A practical triage order:

• Retire silently — tools only you use, where killing them affects nobody else. Cancel today.
• Propose consolidation — tools your team shares that overlap with the tracker or doc tool. Bring the audit data, not an opinion, to your next retro.
• Negotiate upward — mandated tools nobody actually uses. Raise it explicitly rather than quietly tolerating it for another quarter.
• Rehome the judgment work — the reasoning, context, and decisions currently scattered across whiteboards, one-off docs, and orphaned trackers that never had a proper home.

That last category is where consolidation gets genuinely hard, because it's not really about the tool — it's about where your thinking lives. This is the gap products like Prodinja are built to close.

Rather than adding a sixteenth app, Prodinja is designed as a single workspace for the judgment work that usually scatters across half-used tools: RICE/Kano prioritization calls, Customer Jobs discovery grounded in Jobs-to-be-Done and Ulwick's opportunity scoring, a living spec in Spec Studio with PR-style diffs and readiness gates, stakeholder context inside a Stakeholders CRM, and Journals for capturing the reasoning behind a decision in your own voice.

Once that context and those decisions have one home, the audit above tends to reveal which of the twelve orbiting tools you can actually retire — not because Prodinja replaces your tracker or your chat app, but because it removes the excuse for the handful of single-purpose tools that were only ever holding reasoning that had nowhere else to live.

For distributed teams this consolidation matters even more, since async and remote PM work already multiplies the number of channels competing for your attention before you've added a single extra tool.

Key Takeaways

• A tool stack isn't measured by capability added; it's measured by attention taxed, per research on attention residue and task-switching from Sophie Leroy and Gloria Mark.
• Run the audit in four steps: list, tag by job-to-be-done, mark last real use, score keep/kill/consolidate — under an hour, one sitting.
• Score tools 0–8 across decision criticality, last real use, team dependency, and switching cost; 6+ is a keep, 3–5 consolidate, 2 or below is a kill.
• The classic finding holds across most PM stacks: one tracker, one doc tool, and one chat app carry the real weight; everything else orbits them.
• Loss aversion, described by Kahneman and Tversky, explains why cutting a barely-used tool feels harder than it should — name the bias to get past it.
• Triage kills by ownership: retire personal tools silently, propose team consolidation with data, and push back on mandated tools nobody uses.
• Re-run the audit every quarter, ideally timed to your planning cycle, since sprawl re-accumulates quietly between audits.