Standup Meeting: Make Weekly MSP Service Decisions

Prepare the Decisions Before You Meet

Ask the desk lead to prepare a short exception list from the service records. Start with repeated work that may need a permanent fix, and risks that could disrupt planned delivery. Link each item to its ticket or change record so the discussion can reach the evidence.

Preparation matters because reading the whole queue aloud consumes time without choosing what to do. Don't call that an alignment session. Put the work that needs a shared decision in front of the people who can decide it.

Keep urgent service action moving through the agreed escalation route. An active client-impacting problem shouldn't wait for a weekly meeting. Bring the remaining delivery decision to the standup if it needs coordination after the immediate response.

Arrange cover for the live desk before bringing people together. Invite the people needed for the decisions rather than everyone who could have an opinion. Leave private performance or employment matters for the appropriate individual conversation.

Use a Fixed Agenda With a Defined Output

Keep the agenda stable so staff can prepare the right information. Set a time boundary that fits your coverage and the decisions required. If a technical investigation needs more work, assign it outside the meeting instead of asking the whole group to troubleshoot together.

The meeting lead should stop an item when the next useful action is clear. Confirm who takes it and where it will be recorded. Don't continue rehearsing the case after the person responsible has enough to act.

If the team lacks information, name the person who will get it and the decision that depends on it. Missing evidence is a task. It isn't a reason to fill the gap with the most confident guess in the room.

Give a Repeat Problem a Fix Owner

A repeated symptom needs investigation before you call it a repeated cause. Check whether the related tickets describe the same failure and what the previous action actually did. A common category helps you find the work; it doesn't establish the diagnosis.

In practitioner service-delivery advice, Erick Simpson recommends reviewing categorized history and assigning a named permanent-fix owner for recurring issues. He asks that owner to check whether the previous fix held, adjust it where needed, and track recurrence. That's his recommended approach, not a measured guarantee of fewer tickets.

Use a hypothetical recurring print failure as the meeting item. Bring the linked incidents and the last documented change. The next action might be a review by the assigned engineer, with a return condition based on checking the suspected cause rather than simply closing the newest ticket.

Give that engineer scheduled capacity for the work. Naming an owner doesn't create an available hour. If the desk cannot release them, the service lead needs to decide what moves or who else can perform the investigation.

Keep the Measure Honest

Choose a measure tied to the problem you selected. For repeat work, record the relevant recurrence using the same definition and the underlying ticket references. A closure total won't tell you whether a fix lasted.

Keep the measure's period and coverage visible. If you use monthly tickets per seat, divide the month's recorded tickets by the supported seats on the same basis. Don't turn the model's monthly benchmark into a weekly target by assuming every month has the same working pattern.

The model's well-run benchmark is 0.5 tickets per seat per month, while a typical MSP runs 1.0 to 1.4. Use your actual rate when planning the desk. A lower count can reflect a smaller scope or missing intake as well as less reactive work, so inspect the explanation before claiming an improvement.

Don't put a new score on the board each week because last week's number is awkward. Keep the definition long enough to evaluate the assigned action. If you change what counts, show the change so the apparent improvement doesn't come from the reporting method.

Make Risks Actionable

An upcoming risk needs a decision attached to it. If an approved change lacks a capable reviewer, name the lead who will provide cover or revise the plan. Saying the week looks busy leaves the receiving technician with the same problem.

Check the work the owner still supplies too. An escalation plan that depends on someone who is already committed elsewhere needs resolving. The standup should expose that conflict before the team treats both commitments as covered.

My test is: what does this do to the board on Monday morning? A useful decision leaves the next action assigned and executable. If the only change is a note saying the team discussed it, the board still carries the original problem.

Close With Owners and Check the Result

• The desk lead prepares the linked exception list and identifies the decisions needed.
• The meeting lead keeps the group on those decisions and assigns deeper investigation separately.
• The fix owner records the agreed action and the evidence needed to check whether it held.
• The service lead confirms capacity and resolves conflicting assignments before treating work as scheduled.
• The meeting lead checks the action record back against the board before ending the discussion.

The model's position is to fix the service factory before adding clients. This meeting can help choose and follow through on that work. It doesn't replace the delivery capacity or technical judgment needed to do it.

After the meeting, open the assigned item as though you were taking it over. Check whether the record tells you what to do and who can resolve the next blocker. Repair that handoff before you ask the team to attend another discussion about the same work.