Stop relearning what your organisation already knows.
Carry decisions, tensions and open questions from one conversation into the next. Harmonica gathers individual perspectives and helps your team review what has changed.
You’ve had this conversation before.
The same argument starts again
The team remembers making a decision, but the reasoning is scattered across notes and old conversations. The next project spends its first meeting reopening it.
Give the next conversation a starting point
Keep related sessions in one project and attach earlier summaries as context. Ask what has changed since the last decision, so the group can build on its reasoning or deliberately revisit it.
Context leaves when people do
A new colleague inherits the documents, but not the thinking behind them. The people who can explain the trade-offs are busy, on another team, or gone.
Keep a record the team can revisit
A Team OS project keeps decisions, tensions, questions and themes across sessions. Entries can be emerging, contested, settled, reopened or retired, so readers can see what is still being worked through.
Follow-through disappears between retros
The report lands, the team gets busy, and an open commitment quietly ages out. By the time anyone asks what happened, the context has to be assembled again.
Make the next cycle someone’s responsibility
Name a host to review the record, bring open commitments into the next session and arrange the next check-in. The recurring conversation is where the team tests whether its changes worked.
Start with one recurring question.
Start for freeA learning loop your team can keep running.
Use the deliberation loop as a recurring practice. Each cycle gives people a chance to contribute, question the emerging picture and decide what should carry forward.
-
Express
Invite people to describe what happened through one-to-one AI conversations, in their own time.
-
Map
Bring their perspectives together into themes, tensions and an emerging shared picture.
-
Reflect
Share that picture back. Ask what is missing, misread or worth another conversation.
-
Validate
Let people challenge the picture and work through the points that remain unsettled.
-
Conclude
Review what the group has learned, update the record and carry it into the next cycle.
The next cycle starts with the record the last one left behind.
Read the deliberation loopWhat you actually set up.
One project, a recurring conversation and a person who keeps the learning moving.
A Team OS memory record persists between sessions. Synthesis can propose changes as new sessions arrive; the host decides what stays.
See the Team OS setup guide-
Create one Team OS project
Choose a standing question, such as “What keeps getting in the way of delivery?” Keep the related conversations together and attach the context they should share.
-
Run a short first conversation
Start with a retrospective template or your own method. Invite the people who lived the work to explain what changed, what surprised them and what is still unresolved.
-
Review the memory record
Synthesis proposes changes to the project’s record. Review them as the host and decide what is settled, contested or ready to retire. A state you set yourself is preserved through later synthesis.
-
Choose who returns, and when
Assign someone to bring the record back at the next project milestone or team check-in. Add the previous session’s summary as context, refreshing it when needed, and check what happened to the open commitments.
Project context sources are a Pro feature. Compare plans. Give the practice a regular place in your team’s calendar and a named person to follow it through.
Why memory needs a rhythm.
Retrospectives shouldn’t be projects
The case for making reflection small and regular, with lessons the next decision can reach for.
Read the argumentThe deliberation loop
The five moves that turn individual perspectives into a shared picture people can question and carry forward.
Explore the mechanismGive the next conversation a starting point.
Start with one team and one question worth returning to. Keep the context, review the learning, and use it next time.