Nobody Wants to Read Your Meeting Notes! Here's What They Actually Want

Let’s face it: nobody wants to read your full meeting notes. That detailed play-by-play you spent hours perfecting? It's probably just collecting digital dust. Sorry, but unless it’s a best-selling novel, most people would rather avoid it. But don’t take it personally—people are busy, attention spans are short, and what they really care about are the essentials: Decisions, Actions, Risks, and Expectations.

So how do you stop writing the meeting novel no one wants and instead deliver what people need? Let’s break it down:

1. Decisions: What Did We Actually Agree On?

This is the heart of the matter. People are impatiently scrolling through your notes, looking for one thing: What did we decide? Clearly highlight the key decisions made during the meeting. Was it to move forward with the new software? Approve the budget increase? Axe that unrealistic deadline? Make it crystal clear—preferably in bold, bulleted points, right at the top. Remember, your readers are here for quick answers, not a long debate recap.

Tip: Don’t just say “Discussed the timeline”—say, “Decided to extend the project timeline by two weeks.”

2. Actions: Who's Doing What (and When)?

Everyone is secretly scanning the notes for the same thing: Is there something I need to do? This is why action items are gold. For each action, list who’s responsible, what they’re doing, and when it’s due. Keep it short, specific, and actionable (pun intended).

Example:

• John: Draft project proposal by October 20
• Samantha: Schedule client meeting by end of week

The clearer you make it, the less likely your colleagues will 'forget' their to-dos. And bonus points if you remind them before they come asking!

3. Risks: What Should We Be Worried About?

Every meeting has its “uh-oh” moments. People need to know what could derail the project, and they want to know it quickly. Identifying risks shows you're thinking ahead and have a grip on potential issues. Plus, if something goes wrong later, people will thank you for raising the flag early (or at least they should).

Example:

• Risk: Supplier delays could push delivery back by two weeks.

4. Expectations: What’s Coming Next?

To really nail down what happens after the meeting, set clear expectations for the team. What’s the next big milestone? Is there a follow-up meeting? Should everyone expect a project update in two weeks? Lay it out so people know what’s on the horizon and can prepare.

Example:

• Expectation: Next status update in two weeks to review progress on action items and address risks.

The D.A.R.E. Formula: Decisions, Actions, Risks, and Expectations

And there you have it—the secret formula to meeting notes people will actually read. Stick to the D.A.R.E. framework, and you’ll be the hero of meeting summaries, delivering exactly what your team needs without drowning them in unnecessary details.

Remember: nobody wants to read your meeting notes, but if you give them the D.A.R.E. essentials, they’ll love you for it. Go ahead, dare to simplify!