Run a process performance review by circulating the evidence first, discussing only issues that need shared judgment, and closing each item with an explicit decision, owner, deadline and verification condition. If the responsible people can settle every item in writing within their existing authority, cancel the meeting and retain the decision record.
A process performance review meeting should answer what happens next. Reading the scorecard aloud does not do that. Neither does asking each person what they worked on while an unresolved customer commitment waits until the final minute.
This is a review of how work performs across a process, not an employee appraisal. It assumes an existing scorecard and a named process owner. Building the measures and governing the whole improvement program are separate jobs.
Quick answer: what should a process review produce?
A useful review leaves a small set of decisions that someone can carry out without reconstructing the conversation. Each decision needs the evidence behind it, the person authorized to make it, the person accepting the next action, and a way to verify completion.
The sequence is straightforward:
- Share the current scorecard and unresolved action records before the review.
- Admit only questions needing discussion between responsible people.
- Check what the evidence supports before debating explanations.
- Decide within existing authority or make an explicit escalation.
- Confirm accepted actions, dates and verification before people leave.
KPI.org, a Strategy Management Group company, describes review meetings in HOW TO DEVELOP KPIS / PERFORMANCE MEASURES as occasions to review, interpret and discuss performance information, organized around desired results and actions addressing performance gaps. That is professional performance-management guidance, not evidence that a particular meeting length improves small-business results. The agenda and decision record below are our practical recommendations.
Does this process need a meeting this time?
Hold the meeting when a live decision needs people to interpret evidence together, resolve a tradeoff or coordinate commitments across owners. Routine updates can stay in the shared record.
Before sending invitations, the process owner asks: “What decision will remain unresolved if we do not meet?” A blank answer is a reason to reconsider the meeting, not to fill the agenda.
| Current situation | Appropriate route |
|---|---|
| Results are current, no attention rule is triggered, and no action or concern needs discussion | Owner confirms the review in writing; no meeting needed unless one is required |
| A responsible person can resolve the item within existing authority | Assign and confirm it asynchronously, with a due date |
| Owners disagree about the evidence or a decision affects another team’s commitment | Meet with the people needed to settle that question |
| Evidence is missing and nobody can yet make a useful decision | Assign evidence repair; retain any urgent protective action rather than debating an invented explanation |
| A control breach or threatened commitment needs immediate attention | Follow the existing escalation route now; do not wait for the scheduled review |
Cancellation removes the appointment, not the review obligation. The owner records what was checked, confirms how open items will be handled and tells participants when the next check is due. Required regulatory, contractual or governance reviews still apply. This agenda is not a substitute for them.
A satisfactory overall result also cannot cancel a credible concern from someone doing the work. The owner checks that concern before declaring there is nothing to discuss.
Prepare a decision list, not a presentation
Send one link to the existing scorecard, the open action record and the questions proposed for discussion. Participants need enough time to check evidence before the meeting; agree a practical cutoff around the work rather than imposing a universal pre-read deadline.
A proposed item can be one sentence: “The unresolved rescheduling requests threaten Friday’s commitments; do we have authority to offer different appointment dates?” Add its evidence reference, decision deadline and the people whose authority or work is affected.
The scorecard should already make its period, definitions, evidence state and attention rules clear. If it cannot, How to Build a Process Performance Scorecard owns that repair. Do not spend this meeting designing a new dashboard.
Bring only the detail needed to decide. Customer and employee records stay in their authorized systems; attendees receive appropriate references and access, not copied personal information in a broadly shared slide deck.
Invite for a decision role
The process owner remains accountable for the review’s outcome. A facilitator keeps discussion on the question. The decision-maker holds the authority for the proposed choice, while the action owner accepts the resulting work. Someone also records the decision. In a small team, one person may hold several roles.
Those meeting roles do not create new organizational authority. If the process owner’s mandate is missing, establish it through What Is a Process Owner?. If a choice exceeds delegated limits, Decision Rights for Small Business covers who may decide.
An absent decision-maker needs an authorized delegate or a named escalation. Attendance by everyone else is not permission to proceed. Other items may still be resolved; the blocked choice must remain visibly pending.
How do you run a short process review agenda?
Start with commitments from the previous review, check the evidence for today’s decision items, then reserve time to confirm what people have accepted. Keep routine reporting outside the conversation.
For one process and a small decision list, try this illustrative 25-minute agenda. The allocation is a starting point, not a benchmark or a limit on necessary risk discussion.
| Time | Discussion | Required output |
|---|---|---|
| 0–4 minutes | Which previous commitments are complete, blocked or overdue? | Verified closures or a decision on each unresolved commitment |
| 4–8 minutes | What changed, and is the supporting evidence usable? | Agreed facts and visible uncertainties |
| 8–20 minutes | What choice does each admitted item require? | Authorized decision, bounded investigation or named escalation |
| 20–25 minutes | Who has accepted what, by when, and how will completion be checked? | Read-back of the decision record |
The facilitator can interrupt a status tour with: “What decision do you need from this group?” If there is none, the update returns to the written record. That protects time for the issue that actually needs discussion.
When the allotted time is insufficient, do not compress a consequential decision into the last minute. Name the unresolved question, who will resolve it and by when. Extend deliberately or arrange a focused follow-up, while protecting any live commitments in the meantime.
Separate the observation from its explanation
“The overdue count increased” is an observation. “The coordinator is too slow” is an explanation that needs evidence. Put them in separate sentences before choosing an action.
Ask whether the work being compared is comparable, whether unfinished cases remain visible and what uncertainty could change the decision. The meeting need not prove the entire cause. It can commission a bounded investigation with a specific question and due date. How to Find the Root Cause of a Business Process Problem covers that investigation.
Similarly, agreeing that an idea deserves a test does not authorize an unbounded change. Send test design to the PDSA cycle guide. The review records who will prepare or authorize that test, rather than improvising it in the room.
An example: the decision-maker is not in the room
Consider an invented service-team review, not a client result. The existing appointment register shows three unresolved rescheduling requests with customer response commitments due Friday afternoon. The team wants to offer alternative dates, but the proposed dates need approval from the service lead, who is absent.
The coordinator reports: “I’ve chased the dates.” That describes effort. It does not settle what customers can be told.
The process owner narrows the question: “Who can authorize the alternatives before our response deadline?” Nobody present holds that authority. The review therefore records an escalation, not an approved reschedule.
A completed entry could read:
| Decision-record field | Illustrative entry |
|---|---|
| Evidence and question | Appointment register references R41–R43, checked October 8 at 09:00; can the proposed alternative dates be offered? |
| Decision and authority | No revised date is authorized. Service lead Leena must approve or reject the proposal; owner Tomas sends the request. |
| Accepted action and due time | Tomas accepts responsibility to obtain Leena’s response by October 8 at 15:00. |
| Verification | Leena’s explicit approval or rejection is linked to the three records; coordinator Inez checks the response against each case. |
| If blocked | If no response arrives by 15:00, Tomas contacts the named duty manager under the existing escalation rule. No alternative date is promised without authorized confirmation. |
| Customer protection and follow-up | Inez keeps the October 9 response commitments visible and follows the existing communication procedure; Tomas checks the decision record at 15:00. |
All dates are in 2026 and all times use the invented team’s local office time. For this example, the October 9 customer response deadline is 16:00; Inez has accepted responsibility for that communication, even if approval remains pending. The duty manager is Noura, whose existing mandate covers escalation of a blocked decision, not automatic approval of new dates. These roles and authority limits are assumptions, not rules to copy into a real business. Replace them with actual names, dates and approved arrangements.
If Leena replies, “Approved,” but identifies only two requests, the third remains unresolved. The record must match the scope of the decision, not merely contain a reassuring message.
This is the practical difference between a discussion and a decision: someone who missed the meeting can tell what is authorized, what remains blocked and who is responsible before the deadline.
Close the review without creating another tracking system
Keep the decision record beside the existing work or action log. For each item, retain its evidence reference, decision and rationale, authority, accepted action owner, due date, completion evidence and escalation condition. A paragraph can hold those fields; a new application is unnecessary.
Before the meeting ends, the recorder reads back the consequential commitments. The decision-maker confirms the choice and the action owner confirms capacity to do the work. An absent person’s name in the minutes is a proposed assignment until they or an authorized delegate accept it. The process owner remains responsible for securing that acceptance.
“Monitor” also needs an owner, a next check date and a condition that would require action. Otherwise, it is an unresolved item disguised as a decision.
At the next check, completed work is verified against the agreed condition. For an evidence-gathering action, that may be a checked case record. For a process change, finishing the task is not proof that performance improved; link to the separately agreed evaluation rather than closing it on activity alone.
An overdue action returns as a decision: remove a blocker, obtain capacity, reassign with acceptance, or cancel with a recorded reason and any required approval. Moving the date without addressing why it was missed simply postpones the same conversation. If the revised timing threatens a commitment, escalate immediately rather than waiting for the next meeting.
When reviews repeatedly expose conflicting records or founder-dependent decisions, Download the Operational Drag Diagnostic Kit. The agenda and decision record remain usable without it.
Frequently asked questions
How often should a process performance review happen?
Match the review to how quickly evidence becomes useful and how soon a decision must be made. A weekly check may suit recurring service work; slower work may need a different interval. Set explicit check dates, and keep urgent escalation separate from the calendar. A review checkpoint need not always be a meeting.
Does the founder need to attend every review?
Only when their authority or judgment is needed for an admitted item. If every ordinary choice waits for the founder, clarify delegated authority rather than making permanent attendance the workaround. The process owner should know which decisions can proceed without them.
Can AI prepare the notes?
AI can draft a summary from authorized records, but a named person must verify the facts, decision scope, owners and dates before the notes become authoritative. It must not infer approval from silence or turn a suggestion into a commitment. People still make and accept the decisions.
Can one review cover several processes?
Yes, when they share a decision that needs the same people. Keep each process’s evidence and accountability distinguishable. Combining unrelated scorecards just to fill a recurring appointment recreates a departmental status meeting; separate the decision lists when the participants or authority differ.
When a review cannot resolve cross-team authority or competing commitments, Book a SYSIPHANY discovery call. Bring one unresolved decision and the records behind it. A larger meeting will not supply the missing authority.