Read Before You Meet: Pre-Call Research That Works

You accepted the meeting three weeks ago. It starts in twelve minutes. And you are now frantically googling the person's name, skimming a half-remembered article about their company, and hoping nobody asks you a pointed question.

Sound familiar? The problem usually isn't laziness. It's that the useful context existed — you read it, or meant to — but it's now buried across forty open tabs, a starred email, and a bookmark folder you never revisit.

Here's a better system. If you save the right things as you encounter them and tag them for later, your read-it-later queue becomes a ready-made pre-call briefing. This piece shows you how to build that habit and how to run a fifteen-minute prep routine that actually works.

Why meeting prep fails (and it's not your fault)

Meetings eat an enormous share of the modern workday, and most professionals feel that time is poorly spent. In a widely cited Harvard Business Review survey of senior managers, 65% said meetings kept them from completing their own work, and 71% called meetings unproductive and inefficient (Harvard Business Review).

A big driver of that inefficiency is asymmetry: some people arrive prepared and some don't. When half the room is getting up to speed in real time, the meeting becomes a briefing instead of a decision.

The deeper issue is that preparation and reading happen at different times. You stumble onto a great profile of a prospect on Tuesday. The call is next Thursday. Between those two moments, the link disappears into the void of browser history. Your intentions were good; your retrieval system failed.

This gap between what we collect and what we actually use is the core problem. People save far more than they ever return to — the classic "read it later, never" pattern. Solving meeting prep means fixing retrieval, not resolve.

Save with intent: tag as you go

The fix starts before the meeting is even on your calendar. When you use a read-it-later app as your default "save this for later" surface, every article, profile, and report you encounter lands in one searchable place instead of scattering across bookmarks and tabs.

The magic ingredient is tagging. A saved article with no label is just a slightly better bookmark. A saved article tagged #acme-corp or #q3-partnership is a future briefing waiting to assemble itself.

A tagging scheme that scales

Keep it simple and consistent. A few tag categories cover almost every prep scenario:

• By account or company: #acme, #globex — everything you've saved about a specific organization.
• By person: #jane-doe for a founder profile, an interview, or their recent op-ed.
• By initiative: #pricing-project, #hiring-eng — cross-company themes that span multiple calls.
• By intent: #read-before-meeting as a catch-all fast lane.

Tagging takes three seconds at save time. It saves you fifteen frantic minutes later. That trade is the entire strategy in one sentence.

Build the briefing: filter, then skim

When the meeting approaches, you don't re-research from scratch. You filter your queue by the relevant tag, and your app hands you every relevant thing you already saved — in one view.

This is where a good queue beats a search engine. Google gives you what the whole internet published. Your tagged queue gives you what you already judged worth keeping, curated by your past self who had more time and context than your twelve-minutes-before self does.

Skim highlights, not whole articles

You rarely need to reread a 3,000-word feature before a call. You need the three sentences that mattered. This is why highlighting as you read is so powerful: when you highlight and annotate web articles the first time through, you leave breadcrumbs for future-you.

At prep time, you skim only your highlights and inline notes. A ten-article backlog collapses into a two-minute review of the passages you personally flagged. That's the difference between walking in informed versus walking in anxious.

Try this fifteen-minute routine before any meaningful call:

1. Minutes 0–2: Filter your queue by the meeting's tag.
2. Minutes 2–8: Skim your highlights across the saved items.
3. Minutes 8–12: Jot two or three questions the context raised.
4. Minutes 12–15: Note one thing you can offer — a relevant article, an insight, a connection.

Listen to your prep on the way in

Not every prep window happens at a desk. Some of your best pre-meeting time is a commute, a walk between buildings, or the ten minutes you're making coffee.

For those moments, reading isn't practical — but listening is. When you can read articles by listening, your tagged queue becomes an audio briefing you consume hands-free. Filter by the account, hit play, and arrive at the call already up to speed.

Audio prep also fits how a lot of people absorb information best. Flexibility in how we consume content — read, listen, or both — is increasingly the norm for knowledge workers juggling hybrid schedules and back-to-back calls, a shift documented in Microsoft's ongoing research on modern work patterns (Microsoft Work Trend Index).

When you need to produce the briefing yourself

Sometimes the prep material isn't a saved web article — it's your own document. A deal memo, a one-page account summary, or the pre-read your team circulated. If you'd rather listen to that than read it, you can convert it into narration: turning a pdf to audio or a Word file into a clean voice track takes minutes, and you can review it on the move.

The same trick works after the meeting. If you keep structured recap notes, a meeting notes audio template helps you turn them into a short listen-back so nothing from the call slips away before your next one.

Make it a habit, not a heroic effort

The reason ad-hoc prep fails is that it depends on a burst of willpower at exactly the wrong moment. The system above works because it front-loads the effort into tiny, low-stakes saves and tags that you do while you're already reading.

Think of it as compounding interest for context. Every tagged save is a small deposit. By the time a meeting arrives, you're not scrambling to earn context — you're just withdrawing what you already banked.

A few principles keep the habit alive:

• One inbox, not five. If saves scatter across bookmarks, email stars, and Slack messages to yourself, retrieval breaks. Funnel everything into a single queue.
• Tag at save time, always. A three-second label now beats a fifteen-minute hunt later.
• Highlight the first read. You will not reread the whole thing. You will reread your highlights.
• Default to a fifteen-minute ritual. Protect the quarter hour before important calls the way you'd protect the meeting itself.

Do this for a month and something shifts. You stop dreading prep because there's nothing to dread — the work is already done, distributed across dozens of moments when you had the bandwidth to do it well.

The takeaway

Great meeting prep isn't about being smarter or more disciplined in the moment. It's about building a retrieval system so that the context you already collected is waiting for you, filtered and skimmable, exactly when you need it.

Save with intent, tag consistently, highlight as you read, and give yourself fifteen focused minutes before the call. If you want a single place to save articles, tag them by account, skim your highlights, and even listen to the whole briefing on your way in, that's exactly what Omphalis is built for — so you walk into every meeting already informed.

---

Originally published on EchoLive.