The Proactive Work Problem
Three structural conditions that mid-level PM work systematically eliminates.
One-line summary: Proactive problem identification requires three structural conditions that mid-level PM work systematically eliminates, and until organisations understand this, the advice stays aspirational.
Most times, senior product work means identifying problems that nobody assigned to you, surfacing the issues that haven’t been named yet, and building the case for why they matter before anyone else sees them. It is good advice. It is also, in practice, almost impossible to act on — not because PMs lack ambition, but because the conditions required to do it well are the exact conditions that most organisations have quietly eliminated.
I’ve watched mid-level PMs try to make this shift. They read the right things, they understand what’s being asked of them, and then they sit down at their desks on Monday morning and get pulled straight into reviews and numerous firefighting meetings. The week ends. Nothing was proactively identified. They tell themselves they’ll create space next week. They don’t.
The problem is infrastructure. Proactive problem identification requires three things that mid-level PM work actively discourages — and until you understand what those three things are, “find the problems nobody named” is just a career aspiration with no clear path.
The First Condition: Unstructured Thinking Time
Cal Newport named something important in Deep Work: the average knowledge worker switches tasks every three minutes. Three minutes. In that environment, you cannot do shallow work well, let alone the kind of thinking that proactive problem identification demands. Spotting a problem nobody named requires you to hold multiple threads simultaneously — user signals, business context, competitive shifts, organisational dynamics — and find the pattern.
The reason mid-level PMs rarely have unstructured thinking time is that execution mode rewards the opposite. The metrics that evaluate you as a mid-level PM are mostly about delivery: did the feature ship? Did the metrics move? Did the roadmap stay on track? These are answerable questions with measurable outputs. Thinking time produces nothing you can point to in a performance review. So it gets cut — by your manager, by the team’s cadence, and eventually by you, because you’ve internalised that busyness is productivity.
Senior PMs who proactively identify problems almost always do so by actively protecting time that looks, on the surface, unproductive. They block mornings. They take longer lunches and use them to think. They leave meetings early so they can sit with what they just heard before the next calendar item erases it. This is a practice that requires both structural space and the willingness to defend it against a culture that treats all unscheduled time as available time.
The Second Condition: Peripheral Vision
The problems nobody has named are almost never visible from inside your own product area. They live between teams, between metrics that nobody is reading together, between what users say in one channel and what the data shows in another.
Mid-level PM work is designed to focus you. You have a squad, a domain, a backlog. You get good at going deep on your specific surface area. That depth is genuinely valuable — but it produces tunnel vision. You optimise your corner of the product without ever seeing how it connects to the shape of the thing as a whole.
Peripheral vision requires deliberate exposure to things that are not your problem. It means sitting in the data review for the team next to yours. It means reading customer support tickets outside your product area. It means being in conversations where you have no deliverable, just presence and attention. Most mid-level PMs are too busy managing their own surface area to have any of this. Their calendar won’t allow it. Their manager won’t prioritise it. And so the problems that sit in the gaps — the ones that can only be seen by someone who holds multiple views at once — stay invisible.
This is one of the reasons proactive problem identification looks like intuition when you see a senior PM do it. It isn’t. It’s the accumulated signal of someone who has been paying attention to the periphery for long enough to notice when something is off. The pattern recognition looks effortless because the exposure was slow and systematic over time.
The Third Condition: The Psychological Safety to Be Wrong
This is the one that gets spoken about the least, and it is probably the most important.
When you identify a problem nobody named, you are doing something socially risky. You are saying: I see something that nobody else has raised. I believe it matters enough to claim resources and attention for it. You are asking the organisation to look in a direction it wasn’t already looking — based on your judgment, not an assignment.
If you are right, this is impressive. If you are wrong, you have wasted people’s time and revealed a gap in your thinking. Amy Edmondson’s research makes the stakes clear: the default human response to this kind of asymmetry is silence. As she has put it, nobody gets fired for silence. But people do get penalised — formally and informally — for surfacing a problem that turns out not to be a problem.
The specific challenge for mid-level PMs is that this asymmetry is sharpest early in a career. You haven’t yet built the credibility that absorbs the cost of being wrong. So the calculus shifts naturally toward caution: wait until the problem is obvious to everyone, then raise it — by which point it isn’t proactive problem identification, it’s just observing the obvious slightly before the post-mortem.
What changes at senior level isn’t that the risk disappears. It’s that you have enough accumulated credibility to afford the occasional bad call. The organisation treats your judgment as an asset worth investing in even when it doesn’t immediately pay off. Mid-level PMs often don’t have that buffer yet. And if the culture doesn’t actively protect the right to be wrong, the natural response is to wait until you’re certain — which means waiting until someone else has already seen it.
What Organisations Actually Need to Examine
The advice to “find the problems nobody named” treats proactive problem identification as a personal skill — something PMs develop through ambition, curiosity, and career seriousness. But it is at least as much an organisational condition as a personal one.
An organisation that fills every PM’s calendar with delivery tasks, measures them purely on execution metrics, and punishes public misjudgment has not created the conditions for proactive problem identification. It has created the conditions for very efficient execution of the problems that were already named. That is worth something. But it is not the same thing.
The senior PMs who identify the problems nobody named aren’t just more strategic. They are operating in environments or have carved out conditions where unstructured thinking is protected, where peripheral visibility is actively enabled, and where raising a wrong hypothesis carries no permanent cost. Sometimes they created those conditions themselves. Sometimes their organisation gave them to them. Usually it’s both.
If you’re a mid-level PM reading this and wondering why you can’t seem to do what the career ladder is asking of you, it may not be a skill gap. It may be a condition gap. And the first step to closing that gap is naming it precisely.
The problem isn’t that you don’t know what to look for. The problem is that you have been given no time to look, no vantage point wide enough to see, and no permission to be wrong about what you find.
That is not a personal failing. It is an organisational design problem. And it is one that, in most companies, nobody has named.
Your PM Takeaway
Before you try to become more proactive, audit the three conditions honestly. Do you have any unstructured thinking time in your week — time that isn’t assigned to a task or meeting? Do you have peripheral visibility into areas outside your product domain? And does your culture protect the right to surface a problem that turns out not to be a problem?
If the answer to any of these is no, the work isn’t to try harder. It is to negotiate for the conditions that make proactive work possible — with your manager, with your team’s operating rhythms, and sometimes with yourself.