Skip to main content

Meeting decisions that don’t get lost.

Memora brings in your meeting transcripts and connects what was decided to the tickets, pull requests and conversations it affects — so a decision made on a call is as easy to find as one written in a doc.

Memora Icon
Memora

What did we decide about the mobile release date?

Answer

In the Sep 12 planning call the team moved the mobile release to Oct 3 to finish offline sync. The change is tracked in MOB-88 and was announced in #mobile.

Sources

  • Sprint planning · Google MeetSep 12
  • MOB-88 · Offline syncSep 12
  • Announcement in #mobileSep 13

Great meetings, forgotten decisions.

Important decisions are made on calls every week. Afterwards they end up in a recording or a summary in a folder — disconnected from the work they change.

Notes end up in silos

Summaries sit in a drive or a meeting tool, separate from the tickets and code they relate to.

Nobody rewatches the call

Finding one decision in an hour-long recording takes longer than asking someone — so people ask.

Reasons get lost

Action items survive; the reasoning behind them rarely does.

How it works.

Memora treats meetings as one more source of team knowledge, alongside chat, code and tickets.

  1. Bring in transcripts

    Connect Google Meet, Zoom or Microsoft Teams so transcripts flow into Memora.

  2. Decisions are linked

    Decisions, action items and topics are connected to the related Jira tickets, pull requests and Slack threads.

  3. Search what was said

    Ask about any past meeting and get an answer that points back to the transcript and the related work.

In practice.

How teams put this to work day to day.

Planning and stand-ups

Find what was agreed in last week’s planning call without asking the organiser.

Ask Memora“Which items did we move out of this sprint?”

Design and architecture reviews

Keep the reasoning from review calls attached to the code it shaped.

Ask Memora“Why did we reject the caching proposal?”

Customer and stakeholder calls

Connect what customers and stakeholders asked for to the tickets that followed.

Ask Memora“What did the customer ask for on the export call?”

What your team gets.

  • Decisions you can find

    Meeting outcomes become searchable alongside the rest of your team’s work.

  • Connected to the work

    Each decision links to the tickets, pull requests and threads it affects.

  • Less manual note-taking

    Transcripts are processed for you, so nobody has to write up every call.

  • Context for absentees

    Anyone who missed a call can catch up on what was decided and why.

Common questions.

Which meeting platforms are supported?
Memora works with transcripts from Google Meet, Zoom and Microsoft Teams. See the integrations page for the current list.
How does Memora connect a meeting to a ticket or pull request?
Memora recognises the projects, tickets, services and people mentioned in a transcript and links the meeting to the matching items in your connected tools.
Is this just a meeting summary tool?
No. Summaries are a starting point. The difference is that Memora keeps meeting decisions connected to the rest of your team’s knowledge, so they can be found and traced later.

Make every meeting count later.

Connect your meeting tool and your first workspace in one sitting.