What changes when some people are on site?
An estimate is a conversation about size, not a stick. On the morning a sponsor will open the pack, use an agile cadence for an insurance claims queue. Someone will be in Pretoria, someone will be in Midrand, and someone will join from Johannesburg while an insurance claims queue is underway. Attention is short and the first screen has to earn the next one.
On site, the claims lead can point at the file waiting on a document. That is useful only if the people not in the room see the same words.
What changes for the people on the call?
On an insurance claims queue, the usual slip is using a missed estimate to blame a person. The claims lead can see the file waiting on a document. The pack leads with activity and hides the decision. Left unnamed, the same item is still open when the week runs out.
The useful move is comparing the estimate with what happened and adjusting the next split. Lead with the decision, the date, and the constraint. Done, for this work, means the file has a decision or a named request for what is missing. The claims lead should be able to say that without translating it for a colleague elsewhere.
What must match between the room and the call?
A sponsor should be able to see what the team learned about size. A meeting in Johannesburg cannot help if the note is a private list from Pretoria while Midrand is already working around the file waiting on a document. Agile is a way to change next week, not a costume for the same queue.
- Usual slip: using a missed estimate to blame a person.
- Useful move: comparing the estimate with what happened and adjusting the next split.
- Lead with the decision, the date, and the constraint on an insurance claims queue.
- Done means the file has a decision or a named request for what is missing.
What does MetaServ keep consistent?
MetaServ is based at 340 Witch-Hazel Street, Highveld, Centurion, Gauteng, 0157. From that base the same work happens on-site in Pretoria, on client sites in Midrand, and with teams in Johannesburg, including on an insurance claims queue. The useful move here is comparing the estimate with what happened and adjusting the next split.
If you are weighing comparing the estimate with what happened and adjusting the next split, read Local leads in each workplace in Gauteng and Leading signals you can influence in Gauteng. The wider frame is project management and the approach used with a delivery team.
If the file waiting on a document is already stuck, talk to MetaServ and bring what you have today. Stop treating a forecast used as a performance score as the update.
Questions before you rename another meeting
What belongs in the first note when you estimate to learn, not to punish on an insurance claims queue?
An estimate is a conversation about size, not a stick. On an insurance claims queue, the useful move is comparing the estimate with what happened and adjusting the next split.
What goes wrong on an insurance claims queue if Johannesburg skips the step to estimate to learn, not to punish?
Pretoria, Midrand, and Johannesburg should name this slip: using a missed estimate to blame a person. On an insurance claims queue, done means the file has a decision or a named request for what is missing.
What should the claims lead bring to a agile delivery session on an insurance claims queue?
Bring an insurance claims queue as it stands today, not a blank example.
