The Lore Block: Why Context Before Decisions Matters
The problem with learning and deciding at the same time
When the stakes are real, a meeting where people learn the context and make the decision in the same hour is a risk.
Walk your team into a room cold and they rebuild the whole history of the problem live. Someone shares a screen. Someone else asks questions that should have been answered before the invite went out. By the time the room has the context, half the meeting is gone, and people are confidently choosing on partial information.
That's how groups end up with the organizational equivalent of a gas station sushi decision.
The fix is simple, and it's one of the four tools in running meetings that change things: send the lore first. Give people the useful backstory before they have to decide.
What the lore block is
The lore isn't an archaeological dig through six months of email. It's the useful backstory, condensed.
The five elements of a lore block
A lore block answers five questions: Why are we here? What changed? What decision is needed? Who owns the decision? What are the real constraints?
In practice, it's a short section in the meeting invite covering the purpose, the background that created the decision point, what the decision owner needs, and what happens if the group does nothing. It should take less than two minutes to read.
Here's one from a real scenario: "Purpose: Decide whether to proceed with the current launch date. Background: The team identified two unresolved testing risks last Thursday. Customer commitments begin next month. Finance needs a final date by Friday. Decision owner: Zardovan. Desired output: Launch, delay, or launch with conditions."
No hand-waving, no corporate softening, no filler. Just the specifics, the constraints, and the decision that has to happen.
Why this matters under pressure
Sending the lore first changes three things.
People arrive with their thinking already started. They've worked through the problem on their own time instead of learning and reacting at once, which takes a real load off the room. We cover why that matters in cognitive load is your real bottleneck.
The decision moves faster, because nobody spends the first half of the meeting rebuilding context. The meeting is for deliberating.
And the one that matters most when the work carries consequences: quiet thinkers and people who process information differently get a fair seat at the table. In a room where everyone is learning at once, the fastest talkers dominate. When the context arrives early, the careful thinkers have time to think before the meeting starts.
How to write one without making it worse
A lore block is not permission to send a wall of text. Write it tight. Use short sentences. Lead with the decision owner and the decision needed, the same way you'd put the outcome in the invite. Don't bury anything important in a paragraph at the end.
If your lore block runs more than a few sentences per element, you're burying the lead. Rewrite it.
The test: could someone on your team read it in ninety seconds and know exactly why the meeting exists and what needs to happen?
If not, it isn't a lore block yet.
What changes when you do this
Sending the lore first tells people how you run meetings and that you respect their time. It shows you've thought the problem through well enough to state it clearly, and that you aren't pulling people together to help you figure out what the problem is.
Over time, teams that get clear lore blocks start to expect clarity. They show up ready and think more sharply. Decision quality goes up because people had room to think before the pressure started. It pairs well with the other habits in running effective meetings that change things, and it frees up leader time that would otherwise go to repeat explanations, a cost we look at in why manager availability matters more than meetings.
When your decisions move money, safety, or reputation, this is one of the most useful habits you can build. Our field guide collects more of the questions leaders ask before big decisions.
Better meeting preparation is one of the simplest ways to improve decision quality. See how we work at Kestryl Edge.
Dan Korus, Kestryl Edge founder, publishes The Updraft, a weekly newsletter on leadership, trust, and how teams actually perform. Subscribe here.