The deal from the engineer's seat · Stakeholders

Whose meeting is this

Find what went wrong in a status meeting that ran as a demo, say whose meeting it was, and write next week's one page in the sponsor's units.

critiquemediumExercise · 4 min · 19 of 64

On this page

A 30-minute status meeting in week 7 ended with no decision and the sponsor leaving early. Below is what happened; the question is what should have.

The situation

Attendees: the VP of Claims (sponsor), the acting Head of Claims Operations (champion), the information-security lead, you, and your account executive. The agenda you sent said "pilot update and demo". You opened with twelve minutes showing the retrieved clauses inside the triage screen, the new confidence badge, and the correction button. At minute 14 the security lead asked whether claim text, including claimant names, is sent to the model endpoint; the account executive said "let's take that offline". At minute 19 the VP asked "where are we against the 30%", and you answered that agreement in the shadow run was 96% on motor and property at the week-6 gate. The champion said nothing. At minute 25 the VP said he had another call and left. No decision was recorded. The facts you had and did not show: the assisted teams' measured median on their first 300 claims is 8.4 minutes against the 11-minute baseline; personal columns stay in the tenant and the free text is redacted there, with a measured 3% miss rate; and the champion needs the VP's approval to keep the claims QA lead's two hours a day through week 8 for commercial's rulings.

The question

Whose meeting was this, what went wrong in it, and what does the one page for next week look like, with the number at the top in the sponsor's units?

A strong answer · Rubric · Where answers go wrong

Write your answer first, then open

A strong answer

It was the sponsor's meeting, run as the engineer's. Three things went wrong, costliest first. The blocker asked the only question in the room that can stop the contract, and the one person with a two-line answer let it be taken offline; the security review that answer would have closed is now a formal request. The sponsor asked for his number, minutes per claim, and got yours, agreement; 96% is the engineer's unit and 8.4 minutes against 11, a 24% cut, four fifths of the way to 30%, is his, and it was in your notes. The champion had nothing to carry, and the decision he needed, the QA lead's hours, was never raised, so the sponsor left without making it. The demo was the smallest problem and took the most time; it belongs in the champion's Friday with the handlers, not in the sponsor's thirty minutes, as the stakeholder lesson sets out.

Next week's page, sent the day before, for a fifteen-minute meeting: at the top, "median 8.4 minutes on 300 assisted claims, down from 11; 24% against the 30% target; agreement 96% on motor and property against 95%"; the delta since last week; then the one decision, "approve the QA lead's two hours a day through week 8, by Monday", with the champion's name as the person asking; then the security answer in two lines, "personal columns never leave the tenant; names, phones, accounts and addresses in the free text are replaced inside it, with a measured 3% miss rate; the sample is attached"; then the date of the next number. No demo. The champion presents the number; you answer questions. The security lead gets her written answer today, not next week, because the review clock is already running.

Rubric

names the sponsor as the owner of the meeting and says why the demo did not belong in it
leads with the measured median in the sponsor's unit, minutes per claim, with the arithmetic
identifies the deferred security question as the costliest error and answers it in two lines
surfaces the champion's unraised decision and puts it on next week's page with a date
writes the agenda as one page sent in advance with the number at the top
shortens the meeting and moves the demo to the champion's Friday

Where answers go wrong

"The demo ran long; keep it to five minutes next time." Loses because the demo was the wrong content for this audience at any length; the sponsor reads one page and makes one decision, and the page did not exist.

"The account executive should not have deferred the security question." True, and loses anyway, because the engineer had the answer and stayed silent; the reviewer wants to hear that you answer the blocker in the room and in writing the same day, without routing through sales or the sponsor.

"Report 96% agreement again; it is the honest number." Loses because it is honest in the wrong unit; the sponsor promised minutes, not agreement, and a page that never leads with minutes leaves him to ask for them, which he will not.