ReMyndwhat should i say in my daily standup?
say three things: what moved since yesterday, what you will do today, and what is blocked, in under a minute if you can. as of october 2026 the scrum guide no longer sets fixed questions, so the daily standup is a short plan for today, not a report on your hours. in our experience the hard part is remembering yesterday, not the format.
download remynd for mac if you would rather search yesterday than piece it together before your daily standup.
what is a daily standup actually for?
a daily standup exists to adjust today's plan, and everything you say should serve that. the scrum guide says the daily scrum is there to inspect progress toward the sprint goal and adapt the plan.
it also sets the rhythm. the guide holds it for the developers at the same time and place every working day, and the faq below has its time limit.
in our view the people listening want to know one thing. does anything you are doing change what they do today?
what are the three standup questions, and do you still need them?
the classic three still work, but they are a habit now, not a rule. atlassian's standup guide uses these:
- what did i work on yesterday?
- what am i working on today?
- what issues are blocking me?
the official guide moved away from them. we checked both pages on october 18, 2026. its revision notes say the 2020 version removed the daily scrum questions to make the guide less prescriptive. teams can use any structure, as long as the standup stays on the sprint goal and ends with a plan for the next day.
our take: keep the three as a shape, and swap "what did i work on" for "what moved". the first invites a list of activity. the second invites results.
a standup update you can copy
a good standup update is three short lines. here is the shape, with an example for each.
| line | what it answers | weak version | strong version |
|---|---|---|---|
| moved | what changed since yesterday | "worked on the billing page" | "billing page passes review, merging after standup" |
| next | what you will do today | "more billing stuff" | "starting the refund flow, aiming for a draft pr by end of day" |
| blocked | what you need from someone | "nothing" | "need the api key from sam before i can test refunds" |
the strong versions are specific enough that someone can act on them. that is our whole test. if your manager could forward it without editing, we would call it short enough.
how do i remember what i worked on yesterday?
check three dated traces before the meeting. our rough estimate is about two minutes.
the reason it is hard is volume. microsoft's june 17, 2025 work trend index report says the average worker gets 117 emails a day and 153 teams messages per weekday. in our experience yesterday is buried under that by morning.
- your commits. the git log docs list
--sinceand--author. rungit log --since="1 day ago" --author=you --onelinefor a list of what you shipped. - your messages. slack's search help supports
from:with a person andon:with a date. search yourself on yesterday's date. - your app time. apple's screen time guide lets you step back a day with the left arrow in app & website activity, if screen time was turned on. apple's usage guide says you cannot see the reports until you turn it on.
if your team writes weekly summaries too, our guide on how to write your weekly update builds on the same habit.
when should you hold the daily standup?
hold it at the very start of the working day, in our view, so it does not cut a focus block in half. microsoft's data below is about meetings in general, not standups, but it shows when the day fills up.
microsoft's telemetry in that same report found 50% of all meetings fall between 9 and 11 am or 1 and 3 pm, which it describes as the hours when many people hit a natural productivity peak. it also found that 54% of users are active in messages by 11 am, the most overloaded hour of the day.
a standup that lands at 10:30 sits right inside that window. we would rather start the day with it, whether your team meets in microsoft teams, google meet, slack huddles or a real room, and protect the morning after it.
the week has a shape too. the same report says tuesdays carry the heaviest meeting load at 23%, while fridays drop to 16%. if your team also runs a longer weekly sync, friday is the quieter slot.
can chatgpt or claude write your standup for you?
chatgpt or claude can tidy your notes into three lines, but they do not see your yesterday unless you give it to them, and in our experience pasting is the usual way.
that makes the order matter. pull the raw traces first, the commits, the messages, the app time, then paste them into chatgpt, claude or microsoft copilot and ask for "moved, next, blocked" in under 50 words. read the result before you say it. in our experience a model will happily turn a stuck day into a confident one.
our view: use the model for wording, never for facts. if a line is not backed by something you can point to, cut it.
what should you leave out of a standup?
leave out anything that does not change today's plan for someone else. in our experience this is where most standups get long.
- a list of meetings. "i was in four calls" tells nobody what happened in them, whether they ran on google meet, microsoft teams or zoom.
- problem solving. if two people need to dig into something, say "let's take that after" and move on.
- status for people outside the team. in our view a standup is not a status report. if leadership wants one, write it separately.
- defensive detail. you do not need to justify a slow day. say what blocked it.
we think the third point matters more than it looks. in our experience, when a standup turns into reporting up, people pad their updates and real blockers get quieter.
what are the honest limits of a three line update?
three lines are a floor, not a ceiling, and they can hide real problems. we think three limits are worth knowing.
first, in our experience "nothing blocked" is the line most often wrong, usually out of optimism. if something is slower than you expected, that counts.
second, a remote team posting async updates loses tone. if a line hides a worry, say it out loud or message the person directly.
third, the traces above only show what left a record. a call in google meet or microsoft teams, a google doc you read for an hour, or a whiteboard session leaves nothing in git or slack. for that gap, see how to find something you saw on your screen.
where does remynd fit?
remynd lets you search what you did yesterday instead of opening three tabs. it captures the focused window, runs ocr locally with apple vision, and keeps the searchable index on your mac. you can exclude apps and sites, and recordings are kept for 30 days by default.
remynd also has a journal, in early access for now. it writes your day as chapters, with people and project pages and a list of open loops, and clicking a moment takes you back to that point on your screen. people who use remynd can ask to be added to early access.
for the bigger picture, read what an ai memory app is.
download remynd for mac and walk into tomorrow's standup knowing what moved.