TellenzeA practical workshop · Suggested 45 minutes
Review what was delivered, discuss what happened and choose one working change to try in the next relevant focus.
No account or email needed. Suggested timing is a facilitation guide, not a delivery estimate.
Before you meet
Use it when a focus has delivered useful value and the team needs to carry its learning into the next piece of work.
Keep the notes where your team agrees. This page does not collect your workshop answers.
An agenda you can adapt
Ask one person to guide the conversation and one to keep the decisions. Extend a step when the facts need more work; leave a question open rather than inventing an answer.
Compare the intended outcome with the actual evidence. What can you show? What remains unmeasured? The Product Owner decides closure when the focus’s main delivery value is achieved; every ticket need not be finished.
Keep: Checked delivery value, unmeasured benefits, open evidence and the closure decision if one is made.
Give each contributor room to share observations. Discuss a few patterns in the work, decisions and handoffs. Keep an observation distinct from an explanation or assumption; include different views.
Keep: The most useful observations, their supporting examples and unanswered questions.
Agree one small working change that addresses an observed problem. Ask someone to volunteer as its owner. Say when it will first be used and what evidence would suggest it helps. Any AI-suggested change needs a person’s decision.
Keep: One action, an agreed owner, a next use and a check for whether it helped.
Keep the lesson and decision with the relevant guide or next focus brief. Give unfinished work a follow-up home without marking it complete. Agree when to revisit the learning action and how you will revise it if needed.
Keep: The next work or guide link, the action’s review trigger and the true unfinished state.
Use the pieces you need
These portable Markdown templates include a blank version and a clearly labelled fictional example. Choose the sections your group needs.
Only when the decision needs it
You can finish the agenda in your own notes. If the group is stuck on one of these questions, a tool can give you a starting point.
The group needs a shared space for independent reflection, themes and agreed actions.
Where the work stays: A shared guest room, with a 24-hour lifetime. Use fictional or approved information; visitors with access to the room can take part.
You want an agent to propose a bounded change to a guide or next brief after people agree the action.
Where the work stays: The draft stays in memory by default; saving on this device is optional. It does not call an AI provider or run the brief.
After the conversation
Keep the agreed notes beside the real work. An expected benefit still needs evidence; the meeting alone does not show that it happened.
Follow a retrospective action into an improvementTake the useful part
Copy or download the agenda, blank decision prompts and resource links. Fill it in with your team. The file does not create workspace work, install templates or run an agent.
Downloads work without JavaScript. Opening another tool or a shared room follows that tool’s data handling.
Portable Markdown
Use the preview below, then copy the text or download a .md file.
Review what was delivered, discuss what happened and choose one working change to try in the next relevant focus.
Suggested meeting time: 45 minutes. Adjust to your group; this is not a delivery estimate. Participants: The Product Owner, people who contributed to the focus and reviewers who can explain the delivery evidence. Useful output: One agreed learning action with an owner, a next use and a check; unfinished work keeps its real state.
Compare the intended outcome with the actual evidence. What can you show? What remains unmeasured? The Product Owner decides closure when the focus’s main delivery value is achieved; every ticket need not be finished.
Keep: Checked delivery value, unmeasured benefits, open evidence and the closure decision if one is made.
Give each contributor room to share observations. Discuss a few patterns in the work, decisions and handoffs. Keep an observation distinct from an explanation or assumption; include different views.
Keep: The most useful observations, their supporting examples and unanswered questions.
Agree one small working change that addresses an observed problem. Ask someone to volunteer as its owner. Say when it will first be used and what evidence would suggest it helps. Any AI-suggested change needs a person’s decision.
Keep: One action, an agreed owner, a next use and a check for whether it helped.
Keep the lesson and decision with the relevant guide or next focus brief. Give unfinished work a follow-up home without marking it complete. Agree when to revisit the learning action and how you will revise it if needed.
Keep: The next work or guide link, the action’s review trigger and the true unfinished state.
This is a portable agenda. It does not create workspace work, invite anyone, install native templates or run an agent. Fill it in with your facts and agreed decisions. Keep private material in a place approved by your team. Opening a linked tool follows that tool’s data handling.
Keep the loop connected
COME TAKE A LOOK
Curious? Join the waitlist and see how we welcome your team.
Tell us a little about your team. We’ll explain the next steps and invite you when we have capacity for your workspace.
Join waitlist Start with your email. No payment needed to join.