The Lore Block: Why Context Before Decisions Matters
The Problem with Learning and Deciding in the Same Breath
In high-consequence work, a meeting where people learn the context and make the decision simultaneously is not efficient. It is dangerous.
When your team walks into a room cold, they reconstruct the entire history of the problem live. Someone shares a screen. Someone else asks clarifying questions that should have been answered before the invite went out. By the time the room has context, half the meeting is gone and people are confidently choosing based on partial information.
This is how groups end up with the organizational equivalent of a gas station sushi decision.
The alternative is simple: send the lore first. Give people the useful backstory before they need to decide.
What the Lore Block Actually Is
The lore is not an archaeological dig into six months of email history. It is the useful backstory condensed into five elements.
The Five Elements of a Lore Block
A lore block answers: Why are we here? What changed? What decision is needed? Who owns the decision? What are the real constraints?
An effective lore block takes the form of a brief section in the meeting invite that includes the purpose, the background that created the decision point, what the decision owner actually needs, and what happens if the group does nothing. It should take less than two minutes to read.
Example 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."
Notice what is missing: hand-waving, corporate softening, unnecessary context, or vague language. Notice what is present: specificity, constraints, and the actual decision that needs to happen.
Why This Matters for High-Stakes Teams
Sending the lore first changes three things.
First, people arrive with thoughts already formed. They have processed the problem asynchronously. They are not learning and reacting simultaneously.
Second, the decision moves faster because the room does not spend the first half of the meeting reconstructing context. The meeting becomes the deliberation, not the orientation.
Third, and most important for high-consequence work: 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 beforehand, the thoughtful people have time to think before the meeting starts.
How to Write One Without Making It Worse
The lore block is not an excuse to send a wall of text. It is a constraint: write it tight. Use short sentences. Lead with the decision owner and the actual decision needed. Bury nothing important in a paragraph at the end.
If your lore block is longer than a few sentences per element, you are burying the lead. Rewrite it.
The real test: Could someone on your team read this in ninety seconds and know exactly why the meeting exists and what needs to happen?
If not, it is not a lore block yet.
The Behavior This Unlocks
Sending the lore first is a signal about how you run meetings and how you respect people's time. It says you have thought this through enough to articulate it clearly. It says you are not gathering people to help you figure out the problem.
Over time, teams that receive clear lore blocks before decisions begin to expect clarity. They show up differently. They think differently. The quality of decision-making improves not because the people got smarter, but because they had space to think before the pressure started.
For leaders in high-stakes environments where decisions move capital, safety, or reputation, this is one of the highest-leverage habits you can build.
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, emotional intelligence, and organizational performance. Subscribe here.