InnerWeb
Skip to main content

Status huddle during a rollout: 10-15 minutes a week

The weekly status huddle lasts about 10-15 minutes and is the cheapest way to keep a rollout from stalling on a missing decision. We describe the agenda, the roles and the decision log that let the administrators on the plant side close matters in the week they appear.

10-15 min
time of the weekly huddle
2
administrators on the plant side

Why a huddle when there are e-mails

In rollout projects delays rarely come from a lack of functions. More often a decision is missing: who approves a given type of permit, how to name a zone, which gate serves which site. An e-mail with a question can sit for several days, while a short huddle forces both sides to answer.

The rollout variant card requires at least 2 administrators on the plant side (one per site) and a weekly status huddle lasting about 10-15 minutes. It is a small workload that protects the acceptance dates.

A three-point agenda

A good agenda fits within a quarter of an hour: what was done since the last meeting, what blocks the next week and which decisions are needed. Anything that needs a longer discussion goes to a separate slot with the people concerned.

  • status: what has been closed and verified (2-3 minutes)
  • blockers: what is missing on the plant or supplier side (5 minutes)
  • decisions: who decides what and by when (3-5 minutes)

Total huddle time during the rollout (sample calculation)

Total huddle time during the rollout (sample calculation)Bar chart: 90, 120 and 180 minutes of huddles for rollouts lasting 6, 8 and 12 weeks.050100150200minutes6 weeks: 90 minutes906 weeks8 weeks: 120 minutes1208 weeks12 weeks: 180 minutes18012 weeks
Source: Sample calculation: 15 minutes times the number of weeks in the schedule (,)

Roles: who should attend

On the plant side the system administrators are mandatory, because they hold the permissions to change the structure of zones and roles. It helps when the OHS manager or the security manager joins once every few weeks, especially before a stage acceptance.

On the supplier side the person leading the rollout attends. Their task is to record decisions and deadlines, not to lead a substantive discussion about the whole project.

When to invite more people

In multi-site rollouts, in the weeks before a stage acceptance and before the security training, it is worth inviting the person responsible for the gate or the gatehouse.

Decision and remarks log

After each huddle send three lines: decisions, deadlines and owners. Such a record makes stage acceptance easier, because it shows when and who made the decision on the structure of zones or the printout template.

The log has one rule: every item has an owner and a deadline. An item without an owner returns to the next huddle as a blocker.

Common pitfalls

The first pitfall is a meeting stretched to an hour, which makes administrators stop attending. The second is postponing a decision that has an acceptance deadline. The third is the lack of a substitute: when the only administrator of a site is on leave, the schedule suffers.

For this reason, appoint a deputy for every administrator and set a fixed huddle slot on the same day of the week.

Checklist

Video

Frequently asked questions

How long does a status huddle last?

About 10-15 minutes once a week, with an agenda covering status, blockers and decisions.

Who on the plant side must attend?

The system administrators, at least one per site. The OHS or security manager joins before stage acceptances.

What to do when a decision is not made?

Enter it in the log with an owner and a deadline. A decision missing after its deadline is treated as a blocker for the schedule and reported to the person supervising the rollout.

Plan the rhythm of the rollout

Let us agree the huddle day, the roles and the deputies with you before the project starts.

Let's talk