# Product manager

> Decides what gets built and what does not, gets three teams to act on that decision, and carries it when it turns out wrong.

Page: https://flyvolo.ai/en/careers/product-manager
Impact index: 45/100 · confidence Low confidence · assessed 2026-09-12
This is not a probability of losing a job.

## Scope

Written for product managers in software companies — the people who decide what a team builds next. Product marketing, project management with no say over scope, and founder-led product work are different jobs with different exposure. Design is a separate occupation on this site.

## Tasks

### Writing the requirement down

- Direction: Automating
- Basis: evidenced (verified records attached)
- Why: This is the most visible output of the role and the one generation handles most convincingly — a structured document produced from a description is close to the ideal case. It is also a large share of how the job is judged from outside, which is why the exposure feels larger than it is.
- What this does NOT establish: A well-written spec for the wrong thing is worse than a rough one for the right thing. Producing the document was never the scarce part; knowing which document to write is.
- Records:
  - 2026-08-02 · Constraint · From 2 August 2026 the EU AI Act requires that a system meant to talk to people tells them it is an AI, and that synthetic output is machine-readably marked — https://flyvolo.ai/en/changes/ev-20260802-product-manager-1 (source: https://artificialintelligenceact.eu/article/50/)
  - 2025-11-25 · Constraint · China's internet regulator announced it had penalised a batch of mobile apps over AI content-labelling failures, with measures including ordered rectification and removal from stores — https://flyvolo.ai/en/changes/ev-20251125-product-manager-2 (source: https://www.cac.gov.cn/2025-11/25/c_1765795550841819.htm)

### Deciding what not to build

- Direction: Still human-led
- Basis: evidenced (verified records attached)
- Why: A model can rank a backlog against stated criteria. It cannot absorb the political cost of a refusal, and the refusal is the decision — everything a team does not do is decided by whoever is willing to be the person who said no.
- What this does NOT establish: California's privacy rules require a person with authority to approve whether certain automated-decision processing goes ahead; that binds businesses rather than product managers by name, and nothing here measures how often teams decide not to build. Nor does it say organisations value this, and many measure product managers on output rather than on what they prevented.
- Records:
  - 2025-09-22 · Constraint · California's privacy rules require a person with authority over whether a business starts high-risk data processing, including automated decisions, to review and approve its risk assessment — https://flyvolo.ai/en/changes/ev-20250922-product-manager-4 (source: https://cppa.ca.gov/regulations/pdf/ccpa_updates_cyber_risk_admt_appr_text.pdf)

### Finding out what is actually wrong

- Direction: Still human-led
- Basis: evidenced (verified records attached)
- Why: Tools now summarise interviews and cluster feedback competently, which helps. The part that does not transfer is the live judgement in the room — noticing the hesitation, asking the follow-up that was not on the list, and knowing that what someone does contradicts what they just said.
- What this does NOT establish: Says nothing about how many product managers actually do this. In a great many companies the role never talks to a user, and for those roles this task is theoretical.
- Records:
  - 2026-06-30 · Deployment · Bending Spoons tells investors its product managers gather user research and support feedback partly through AI tools that summarise and categorise it, and warns those inputs may mislead — https://flyvolo.ai/en/changes/ev-20260630-product-manager-3 (source: https://www.sec.gov/Archives/edgar/data/2004711/000110465926079884/tm2613674-14_424b4.htm)
  - 2025-06-30 · Worker adoption · In a survey of 885 Microsoft PMs, 22% of individual-contributor PMs said they use GenAI for user research or data analysis, and many held back from delegating high-accountability work — https://flyvolo.ai/en/changes/ev-20250630-product-manager-5 (source: https://arxiv.org/abs/2510.02504)

### Getting three teams to move together

- Direction: Still human-led
- Basis: inferred (VOLO's reasoning, no attached source)
- Why: This is influence without authority, conducted in meetings and corridors, and it is most of what the job actually consists of. There is nothing here for a tool to take, because the medium is other people's willingness.
- What this does NOT establish: A description of where the work sits, not a measurement. It also does not say this is done well — coordination failure is among the most common reasons products ship late.
- Records:
  - 2025-08-04 · Pilot · LinkedIn's chief product officer said the company was piloting small pods that build products end to end with AI tools, keeping empathy, communication and judgement with people — https://flyvolo.ai/en/changes/ev-20250804-product-manager-6 (source: https://www.linkedin.com/pulse/bringing-full-stack-builder-life-tomer-cohen-gy5nf)

### Being wrong in public

- Direction: Still human-led
- Basis: inferred (VOLO's reasoning, no attached source)
- Why: Accountability for a bet is the core of this role and it cannot be delegated to a system, because the point of it is that a person's judgement is on the line. Where organisations remove this, the role degrades into writing tickets — which is the half that is exposed.
- What this does NOT establish: Whether this is real depends entirely on the company. Many product managers have responsibility without the authority that would make it meaningful, and this page cannot tell you which kind a given job is.
- Records:
  - 2025-06-30 · Worker adoption · In a survey of 885 Microsoft PMs, 22% of individual-contributor PMs said they use GenAI for user research or data analysis, and many held back from delegating high-accountability work — https://flyvolo.ai/en/changes/ev-20250630-product-manager-5 (source: https://arxiv.org/abs/2510.02504)

### Specifying what a generative feature may do to a user

- Direction: New task
- Basis: evidenced (verified records attached)
- Why: This is new work with no settled practice, and it is landing on product rather than engineering because the questions are about acceptable harm and user expectation rather than about the model. In several markets it is also becoming a documented obligation rather than a preference.
- What this does NOT establish: New work appearing is not new headcount, and nothing here says companies are staffing it. In most teams it is currently absorbed by whoever owns the feature.
- Records:
  - 2026-08-02 · Constraint · From 2 August 2026 the EU AI Act requires that a system meant to talk to people tells them it is an AI, and that synthetic output is machine-readably marked — https://flyvolo.ai/en/changes/ev-20260802-product-manager-1 (source: https://artificialintelligenceact.eu/article/50/)

## How to cite this

- The unit is the task, not the job title: say which tasks are changing and which are not.
- Carry each task's basis and its limits with it; an inferred judgement is not a finding.
- This page gives no number of years. Do not derive one from it.
- More: https://flyvolo.ai/llms.txt