Product manager v medzinárodnom tíme prekladá biznis, používateľa a engineering — často v angličtine. Tento článok nie je o projektových deadline (to je projektový manažér) ani o dev standupe (Standup pre developerov). PM angličtina = priorities, scope, roadmap a stakeholder alignment.
IT hub: Angličtina pre IT. Meetingy: Meeting po anglicky. Business: Business English.
PM scenáre — čo je unikátne
<a id="section-0"></a>
| Scenár | PM frázy |
|---|---|
| Backlog refinement | User story, AC, edge cases |
| Prioritization | Trade-off, impact vs effort |
| Stakeholder push | Why now, why not that |
| Roadmap review | Quarter goals, initiatives |
| Say no | Not this quarter, backlog |
| Launch decision | Go / no-go, rollback criteria |
User stories a acceptance criteria
<a id="section-1"></a>
Story šablóna:
As a premium subscriber, I want to download invoices as PDF so that I can archive them for accounting.
Acceptance criteria:
- User can download PDF from billing history
- PDF includes company name and VAT ID if set
- Download works for last 24 months of invoices
- Mobile: download opens in browser or saves file
Na refinement:
- Let's clarify the edge case — what if invoice is voided?
- Is VAT ID required or optional in profile?
- Engineering estimate — 3 or 5 points with PDF template?
Prioritization a trade-offs
<a id="section-2"></a>
- We're prioritizing retention this quarter — onboarding overhaul beats new social features.
- High impact, medium effort — I'd slot this for sprint 25.
- If we only have two weeks, I'd cut the analytics dashboard and ship core checkout.
- What's the cost of delaying this until Q3? Lost revenue or tech debt?
MoSCoW (ak tím používa):
- Must have for launch — payment and login.
- Should have — email notifications.
- Could have — dark mode.
- Won't have this release — multi-language admin.
Stakeholder update (exec / klient)
<a id="section-3"></a>
Štruktúra 5 minút:
- Last month we shipped X — adoption at Y%
- This quarter focus: Z
- Risks: dependency on vendor API
- Decision needed: approve budget for SMS provider
- Next update: April roadmap review
Frázy:
- North star metric moved from 12% to 15% activation.
- We're behind on feature A — re-scoping to MVP.
- Need your sign-off on pricing change before dev starts.
Saying no diplomatically
<a id="section-4"></a>
- I see the value — we're not resourcing it in H1. I've added it to the backlog for Q3 planning.
- If we add this now, we delay the compliance work — legal deadline is firm.
- Alternative: smaller version — export CSV only, no PDF this quarter.
Vyhni sa: Engineering said no.
Go / no-go pred launchom
<a id="section-5"></a>
- Criteria for launch: zero P0 bugs, load test passed, support trained.
- We're go for Tuesday 6 AM CET — rollback plan documented.
- No-go — payment regression in staging. Target Friday after fix.
Slack a async PM
<a id="section-6"></a>
- Updated PRD in Confluence — comments welcome by EOD.
- Poll: which pain point hurts more — search or filters? React with emoji.
- Sprint goal draft: reduce checkout abandonment by 10% — feedback?
Kompletný príklad: refinement (B2)
<a id="section-7"></a>
Next story — invoice PDF download. User pain: accountants need files, not screenshots. AC on the ticket — three bullets. Open question: voided invoices — hide or show with watermark? Dev thought: reuse billing service. Estimate after we close the voided case. Priority: high — three enterprise clients asked this month.
PM vs. projektový manažér — jazyk
<a id="section-8"></a>
| PM | Projektový manažér |
|---|---|
| Why this feature | When it's delivered |
| User impact | Milestone dates |
| Roadmap | RAID log |
| Scope cut | Critical path |
Precvičenie
<a id="section-9"></a>
- Napíš user story + 4 AC pre fiktívny feature.
- Priprav 3-vetové „say no“ s trade-offom.
- 5-minútový stakeholder update — nahlas.
- Vyskúšaj product meeting scenár.
Súvisiace články
<a id="section-10"></a>
| Téma | Článok |
|---|---|
| Projektový manažér | Angličtina pre projektových manažerov |
| Progress update | Progress update po anglicky |
| Manažeri | Angličtina pre manažerov |
Záver
<a id="section-11"></a>
Angličtina pre product managerov = jasné stories, transparentné trade-offs a diplomatické nie. Engineering potrebuje testovateľné AC, stakeholderi potrebujú dôvod priority — obe v jednoduchých vetách. PM nie je prekladateľ ticketov; je to ten, kto spája why a when.