Why 1 Hour of Meetings Turns Into 3 Hours of Work

The meeting ended in 60 minutes. You opened your notebook to record what was decided. You sent an email to the team with the next steps. You re-explained everything to the colleague who was absent. And you spent 20 minutes searching your own notes to check whether the final decision was Friday or Monday.

In the end, that 1 hour turned into 3. And you still hadn’t gone back to the work you were doing before it.

It’s not an exaggeration. It’s the real cost that almost no one calculates.

The math no one does

A 1-hour meeting with 6 people costs 6 company hours. But the work doesn’t stop when the call ends. Here’s what comes after:

• Writing the minutes or summary: 15 to 30 minutes
• Sending follow-up to the team: 10 to 20 minutes
• Recapping for those who were absent: 15 to 30 minutes (and you need to remember what was said)
• Searching for a specific decision later: 10 to 20 minutes (because no one remembers where it landed)
• Context switching: 23 minutes to regain the focus you had before the meeting (research by Gloria Mark, UC Irvine)

Add it all up: 1h of meeting + ~1h40 of post-work + 23 min of focus recovery. That’s over 3 hours. Per person.

Multiply that by the 62 meetings an average professional attends per month — half of them considered wasted time — and you reach 31 hours per month thrown away on ineffective meetings. That’s 4 business days that aren’t coming back.

Why it got worse with remote work

In the in-person model, someone would leave the meeting room and catch a colleague’s eye: “close on what we agreed in there?”. Information flowed in the hallway.

In remote work, there’s no hallway. Everything became a call. A Microsoft study showed that 70% of employees experienced a 70% increase in the number of meetings after moving to remote. Another study, from the NBER, measured a 10% increase in total time spent in meetings — 3 more meetings per week, per person.

Meetings got 20% shorter, but 13.5% more frequent. More short meetings seem more efficient. They’re not. Each one triggers the same cascade of post-work: minutes, follow-up, recap, search.

The cascade effect is this: 5 meetings of 20 minutes cost more than 1 meeting of 100 minutes. Because each one sets off its own chain of documentation and communication.

Where information gets lost

The problem isn’t the meeting itself. It’s that the meeting content doesn’t get recorded in a searchable way.

Ask any professional: “what was decided in Tuesday’s meeting?”. If there are no minutes, the answer is based on memory. And memory is terrible for decisions — good for impressions, bad for details.

What gets lost:

• The exact phrasing of a decision (“we’ll deliver Friday, not Monday”)
• The reason for the choice (“we went with vendor A because B doesn’t have an API”)
• Who became responsible for what
• Objections that were raised and dismissed
• The context that makes the decision make sense three months later

Without this, two weeks later someone reopens the discussion. Another meeting is scheduled. The cycle starts over.

The solution isn’t fewer meetings. It’s capturing right.

Saying “have fewer meetings” is like saying “sleep less.” At some point you need to align people, and the fastest way to do that is still talking. The question is what happens to the conversation afterward.

Here’s the point: if the meeting is recorded and transcribed automatically, all the post-work compresses. You don’t write the minutes — they already exist. You don’t recap for those who were absent — you send the summary. You don’t search for the decision — you search the text.

The flow becomes:

1. Meeting happens (1h, normally, recorded with consent)
2. Automatic transcription comes out in seconds (without typing anything)
3. Summary generated with decisions and next steps (without rereading the entire transcript)
4. Those who were absent receive the summary (without you spending time explaining)
5. Specific decision is found via search (without listening to the recording again)

The post-work that used to take 1h40 becomes 10 minutes. Focus recovery still exists — you still need a few minutes to get back to what you were doing — but the documentation part disappears.

How Sintesy compresses the cycle

Sintesy does exactly this heavy lifting. You record the meeting — on Google Meet, Teams, Zoom, or a recording of an in-person conversation made on your phone. The audio goes into Sintesy and it delivers:

• Complete transcription in Brazilian Portuguese — with punctuation, paragraphs, and speaker identification
• Automatic summary — the key points instead of the entire conversation
• Decisions and next steps — separated, ready to share
• Searchable text — to find “when is the delivery” or “who took on X” in seconds

The result is that the 1-hour meeting goes back to costing 1 hour and 10 minutes — the 10 minutes being the time to review the summary, adjust something, and send it to the team.

The new math

Compare before and after:

Without automatic capture:

• 1h meeting
• • 30min writing minutes
• • 20min sending follow-up
• • 30min recap for absentees
• • 20min searching for a decision later
• • 23min context switching
• Total: ~3 hours

With voice AI (Sintesy):

• 1h meeting
• • 2min reviewing the generated summary
• • 3min sending to the team
• • 0min recap (those who were absent read the summary)
• • 0min searching (search the text)
• • 23min context switching (this doesn’t go away)
• Total: ~1h25

The savings: 1h35 per meeting. Over 10 meetings per week, that’s 15 and a half hours that go back to real work.

What to change tomorrow

You don’t need to change everything at once. Start with one thing:

At your next meeting, record. Not to “listen later” — no one listens later. Record to transcribe. The transcription is the asset. The summary is what you share. The search is what you use when someone asks “what did we decide again?”.

If you already use Sintesy, the flow is ready. Connect your calendar or upload the recording manually. The transcription, summary, and next steps come out automatically.

If you don’t use it, test it with one meeting. Record on your phone, upload the audio, see the result. One meeting is enough to understand the difference between 3 hours and 1h25.

The time you spend in meetings won’t decrease. But the time they cost can.