Blog · Leading teams

Running a stand-up when you're not technical: what to listen for


The daily stand-up is supposed to take fifteen minutes and tell everyone where the work is. For a manager without a technical background, it can feel like fifteen minutes of a foreign language.

The secret is that you do not need to understand every word. You need to listen for a few signals and ask a few good questions. Here is how.

What a stand-up is for

Each person typically answers three questions:

  1. What did I finish since yesterday?
  2. What will I work on today?
  3. Is anything in my way?

Your job is not to judge the technical approach. Your job is to notice risk to the plan and things only you can unblock.

The five signals worth your attention

1. "Blocked" and "waiting on"

These are the most important words in any stand-up. "Blocked" means the work cannot move until something else happens. Always find out what it is waiting on and who owns that. If the answer is another team, a client or a decision, that is often something you can help with.

2. The same task, day after day

If someone reports the same task three days running, something is harder than expected. Ask kindly whether it is bigger than planned and whether the estimate needs to change. Catching this on day three is far better than on day ten.

3. "Just" and "should be"

"It should just be a small change" is often said right before a surprise. It is not a red flag on its own, but note it and check the next day.

4. Anything about production

Production (or "prod") is the live product customers use. Phrases like "an issue in prod", "a hotfix" or "we rolled back" mean customers may have been affected. Ask whether users noticed and whether anyone needs to be told.

5. Silence about testing

If work is "done" but nobody mentions testing, review or QA, ask where it is in that process. "Done" for a developer can mean "written", not "ready for customers".

Three questions that always work

You do not need technical questions. These three work in any stand-up:

  • "What's the impact on this week's plan?"
  • "Is there anything I can unblock for you?"
  • "Who else needs to know about this?"

They keep the meeting focused on outcomes, and they show the team you are there to help, not to inspect.

Keep the stand-up short

If a technical discussion starts between two developers, it is fine to say: "Shall we take that offline after the stand-up?" This is normal practice, and it keeps the meeting useful for everyone.

Turn the stand-up into a briefing

Many teams post stand-up updates in Slack or a ticket tool. If yours does, Plainlee's stand-up summary can read the whole thread and give you one plain briefing: what moved forward, what is stuck and on whom, and which decisions are waiting on you. It is part of Plainlee Pro.

You can also look up any word you hear in our tech glossary, or paste a single confusing update into the free web app.