Which workshop ideas belong in a decision report?
Separate workshop ideas from decisions and open questions. Includes a fictional example, a blank report outline, and review steps.
A workshop can end with a wall of notes and still leave the team unsure what happens next. A decision report should not copy every sticky note. It should show what the group agreed to do, what it chose not to do yet, and who will resolve the remaining questions.
The useful change is from ideas people raised to choices people can act on. You can make that change without pretending that every suggestion became a decision.
Start with the question the workshop was meant to answer
Before you sort the notes, write down the decision the meeting was called to support. For example: “Which change should we try first to make new customers' first week easier?” That question sets a boundary. An idea about a new logo may be interesting, but it does not belong in this report unless it bears on the first-week experience.
Then record who can make the final call and what evidence they need. A workshop group may recommend an option while a manager, client, or wider team must approve it. Label a recommendation as a recommendation until that approval happens. This small distinction keeps a polished report from sounding more certain than the meeting was.
Read the notes as evidence, not as a vote
Group related suggestions by the problem they address. Keep the wording people used where it explains a concern, but combine repeats into one theme. For each theme, ask: What problem did people notice? What could we change? What reason did they give? What do we still need to know?
Do not turn the number of sticky notes into a measure of support. One participant may have written many notes; another may have said one important thing aloud. If the group used a formal vote, report how that vote worked and what it did and did not decide. If there was no vote, describe the discussion instead of assigning a false ranking.
Keep three separate lists as you sort: suggestions, decisions, and open questions. A suggestion is something someone proposed. A decision has an agreed owner or an explicit approval. An open question blocks or shapes the next decision. You can add a fourth list for ideas the team set aside, with a short reason and a date to revisit them.
A small, fictional example
Fictional workshop excerpt: A team is discussing how to help customers start using a new service. The notes say, “People do not know what to do after they sign up,” “send a welcome email with one next step,” “offer a call to everyone,” “keep the help page short,” and “ask three recent customers where they got stuck.” One person asks who can approve new email text. The group agrees to draft the email and talk to customers before changing the help page. No one approves the email for sending in the meeting.
Those notes contain a problem, several possible responses, a question about approval, and a limited agreement. A report that says “The team decided to launch a welcome email and offer calls” would be wrong. The team agreed to prepare and learn, not to launch either idea.
What a finished decision report can look like
Decision report — fictional example
Topic: Helping new customers take their first step.
Decision needed: Which change should we try first?
Meeting outcome: Prepare a short welcome email and speak with recent customers before choosing a change to launch. The group did not approve a launch.
Reason: Participants repeatedly described uncertainty after sign-up. An email with one clear next step may address that gap. Customer conversations can show whether that is the main difficulty or whether the help page needs work instead. These are working ideas, not proven findings.
Agreed actions: The content lead will draft an email with one clear next step by Friday. The research lead will invite three recent customers to short conversations next week and bring back a brief summary. The team will review both at its next meeting. The named roles and dates are part of this fictional example, not a general rule.
Suggestions not yet approved: Send the email to all new customers; offer a call to everyone; shorten the help page. The first needs approval of the text, the second needs a check of available time, and the third needs customer feedback before the group picks changes.
Open questions: Who approves messages to customers? Do new customers struggle most after sign-up or when reading the help page? What would count as a useful first step? The meeting owner will confirm the approver before the next review.
Next decision: After the draft and customer conversations, choose whether to try the email, revise the help page, or gather more information. Record who approves that choice and when the team will review it.
This report is short on purpose. It preserves the limits of what the group agreed to, while making the next move clear.
Use this blank report outline
Copy these fields into a document and fill them from your own meeting notes. Leave a field open if the group did not settle it; do not guess.
- Topic and date: [What was discussed? When?]
- Decision to make: [What choice is needed, and who can approve it?]
- Problem and evidence: [What did participants observe? What remains unconfirmed?]
- Options considered: [What did people suggest? Combine repeated ideas without hiding differences.]
- Decision or recommendation: [What was agreed, if anything? Is approval still needed?]
- Reasons and trade-offs: [Why this option? What would it cost, delay, or leave out?]
- Ideas set aside: [Which ideas are on hold, why, and when will they return?]
- Open questions: [What facts or approvals are still missing?]
- Actions: [Owner, concrete task, and date for each next step.]
- Next review: [Who will decide what, and when?]
Review before you share it
First, compare each “decision” with the original notes. Was it said in the room, confirmed after the meeting, or only inferred by the writer? Change the label if needed. Next, check that each action has one owner and a date people can use. “Follow up soon” is not an action someone can reliably track.
Ask the meeting owner to confirm the record, especially if the workshop included people with different roles. Share the draft with participants so they can point out missing context or a mistaken attribution. If the final approver did not attend, send the recommendation for approval and mark its status clearly until they respond.
Finally, remove detail that does not help the next decision. Keep enough of the discussion to explain why an option was chosen, but do not attach every raw note by default. The report should let someone who missed the workshop understand the choice, its limits, and what happens next.