Progress update na meetingu je moment, keď tím potrebuje vedieť, kde si — nie celú históriu projektu. Dobrý update je krátky, jasný a hovorí o tom, čo ovplyvňuje ostatných: termíny, závislosti a blokery.
Tento návod pokrýva frázy a štruktúru pre bežný status na meetingu. Pre denný standup máme samostatný článok Daily standup po anglicky. Kompletný prehľad: Meeting po anglicky.
Štvorica, ktorú potrebuješ vedieť
<a id="section-0"></a>
| Stav | Čo znamená | Typická fráza |
|---|---|---|
| Completed | Hotovo | I've finished… / I completed… |
| In progress | Pracujem na tom | I'm currently working on… |
| Delayed | Mešká | It's taking longer than expected… |
| Next steps | Čo bude ďalej | Next I'll… / My plan for today is… |
Na väčšine meetingov stačí pokryť 2–3 z týchto bodov. Nemusíš spomínať všetky štyri.
Completed — čo je hotové
<a id="section-1"></a>
B1
<a id="section-2"></a>
- I finished the report yesterday.
- I completed the first version of the design.
- I sent the proposal to the client.
- The testing is done.
B2
<a id="section-3"></a>
- I've wrapped up the API integration — it's ready for review.
- I completed the user research phase and shared the findings in Confluence.
- We've delivered the first milestone on schedule.
Príklad:
Quick update — I've completed the competitor analysis and shared the document in the shared drive. The main takeaway is that we're well positioned on pricing.
In progress — čo prebieha
<a id="section-4"></a>
B1
<a id="section-5"></a>
- I'm working on the presentation.
- I'm doing the bug fixes now.
- I'm preparing the budget for next quarter.
B2
<a id="section-6"></a>
- I'm currently working on the frontend tests — about 60% done.
- I'm in the middle of the onboarding flow redesign.
- We're refining the proposal based on yesterday's feedback.
Príklad:
Today I'm working on the integration with the payment provider. I should have a working prototype by end of day.
Delayed — keď meškáš
<a id="section-7"></a>
Meškanie nie je zlyhanie — je to informácia. Povedz prečo a kedy očakávaš dokončenie.
B1
<a id="section-8"></a>
- The task is taking longer. I need two more days.
- I'm behind schedule because we're waiting for approval.
- I couldn't finish yesterday — I'll do it today.
B2
<a id="section-9"></a>
- The timeline slipped slightly — we're waiting on legal review, which is taking longer than expected.
- I underestimated the complexity. I now expect to deliver by Friday instead of Wednesday.
- We're a day behind, but I have a plan to catch up by reallocating the testing phase.
Príklad:
The documentation is taking longer than I planned — the API changed mid-week. I expect to finish by Thursday if there are no more changes.
Next steps — čo bude ďalej
<a id="section-10"></a>
- Next I'll start on the deployment.
- My plan for today is to finish the review and send it to the team.
- After this, I'll focus on the client presentation.
- Tomorrow I'll sync with the design team on the mockups.
Next steps ukazujú, že máš plán — aj keď ešte nie všetko je hotové.
Kompletný príklad: developer (B2)
<a id="section-11"></a>
Quick update from my side. I completed the authentication module yesterday — it's merged and deployed to staging. Today I'm working on the dashboard widgets; I'm about halfway through. I'm blocked on access to the production logs — could someone from DevOps help with that? Once I have access, I should be able to finish testing by tomorrow.
Štruktúra: completed → in progress → blocked → next steps.
Kompletný príklad: non-tech role (B1)
<a id="section-12"></a>
Yesterday I finished the client presentation. Today I work on the follow-up emails. I have one question about the pricing — I'll ask Anna after the meeting.
Pre marketing, HR, sales alebo project management platí rovnaká logika — len iná terminológia.
Frázy na začiatok a koniec update
<a id="section-13"></a>
Začiatok:
- Quick update from my side…
- Here's where I am on the project…
- Status on [task name]:
Koniec:
- That's all from me.
- Happy to answer any questions.
- Let me know if you need more detail.
Čo nerobiť
<a id="section-14"></a>
| Chyba | Prečo | Namiesto toho |
|---|---|---|
| Príliš dlhý monológ | Tím stráca pozornosť | Max 1–3 minúty |
| Žiadne čísla ani termíny | Nejasné pre ostatných | by Friday / about 50% done |
| Skrytie meškania | Prekvapenie neskôr je horšie | Povedz to skoro s dôvodom |
| Technický žargón bez kontextu | Non-tech tím nerozumie | It affects the login page |
Prepojenie s blockerom
<a id="section-15"></a>
Ak nemôžeš pokračovať, povedz to explicitne:
- I'm blocked on…
- I can't move forward until…
- I need help with…
Detailný návod: Ako vysvetliť blocker po anglicky.
Precvičenie
<a id="section-16"></a>
- Zapíš si svoju aktuálnu úlohu.
- Rozdeľ ju na: completed / in progress / delayed / next steps.
- Napíš 3–4 vety po anglicky.
- Povedz nahlas — cieľ je do 60 sekúnd.
- Vyskúšaj v standup scenári.
Súvisiace články
<a id="section-17"></a>
| Téma | Článok |
|---|---|
| Kompletný prehľad | Meeting po anglicky |
| Daily standup | Daily standup po anglicky |
| Blocker | Ako vysvetliť blocker po anglicky |
| Frázy | Frázy na meeting |
Záver
<a id="section-18"></a>
Progress update je krátky report o tom, kde si. Povedz, čo je hotové, čo robíš, čo mešká a čo bude ďalej. Buď konkrétny, nezatajuj meškanie a ak si blocked, povedz to hneď. Tím potrebuje informácie, nie perfektnú gramatiku.