The Briefing Framework for Better Decisions

Deciding Blind

I find myself in the same situation again and again: an employee, founder or entrepreneur comes to me, sums up a complex decision in two minutes and asks for my feedback.

The natural reaction is to answer right away. But honestly, my feedback can then only be generic, vague and mediocre. All I know about the situation is a two-minute summary, and my picture of the context and the options is as incomplete as it gets.

Years ago, I started asking lots of follow-up questions and piecing the context together myself. That costs both of us a lot of time, and the picture still stays incomplete. I can only ask about what I know exists.

Eventually I realized there is only one way to reach a good solution and an efficient process in the long run. I stop the conversation and say: "Please prepare the topic, and then let's talk again."

The framework in this article helps you establish a more effective decision-making process.

Why Meetings Go in Circles

What is already hard in a one-on-one gets worse in a meeting. Several people are supposed to understand the topic at the same time, join the discussion and reach a decision together. That creates typical problems:

  • Ad-hoc topics: Someone puts a topic on the agenda on the spot and talks about it in an unstructured, incomplete way. It takes longer and is much harder for everyone else to follow.
  • Missing context: The listeners lack context and details. At best, they get frustrated and ask lots of questions, which costs time. At worst, they give superficial feedback based on generic advice that doesn't help in the specific situation.
  • No common ground: When everyone argues from a different context, no shared understanding emerges. The discussion drags on, and in the end there is no alignment. "Best ideas win" becomes almost impossible.
  • Snap decisions: People have to think on the spot and weigh arguments they're hearing for the first time. But in complex decisions, what matters is thinking through the different scenarios rationally and thoroughly, rather than following the first gut feeling.

Everyone knows these meetings: you go around in circles for a long time, everyone gets frustrated, and you still don't end up with a good result.

Writing Forces Clear Thinking

The obvious solution: meetings need to be prepared, and in writing. Before a topic is discussed, one person prepares a briefing that everyone reads beforehand. That way, everyone comes into the conversation with the same context, and everyone has had time to form their own opinion and think the content through properly.

Writing a briefing forces you to think thoroughly, clarify your thoughts and build a logical argument. That improves the quality of the decision before anyone else has invested any time.

At the latest when you try to write down the options, you notice whether you have really thought them through. One person at a desk spots that gap, not five people in a meeting.

“We Don't Have Time to Write”

That is the classic objection I hear again and again.

But we have to gather the information anyway. Either we skip it and make a bad decision, or we go back and forth in the meeting until everyone has the same context, because only then can we reach a shared decision. So the real question is who does this work.

If one person prepares, they take the time to gather and structure the information, and everyone else reads it in a few minutes. If nobody prepares, five people reconstruct the context live in the meeting: verbally, without structure, and with interruptions.

Overall, you invest more time up front, but the team saves far more of it later. And the decision itself gets much better.

What Goes Into a Briefing

For open decisions, I've used the same structure for years:

Orientation: One or two opening sentences that tell me which mental drawer to open. That's where I look for context and place what I read next.

Context: The full status quo and the essential background I need to understand the problem.

Problem: What needs to be solved or decided. This isn't just about the problem on the surface, but about the root cause. The problem has to be described and understood in depth.

Options: The available alternatives, initially without any judgment. Describe each option objectively, with its advantages, disadvantages and consequences.

Proposal: Up to this point, the briefing has to stay completely neutral and objective, otherwise "best ideas win" doesn't work. This is now the place to evaluate, and to bring in your subjective opinion and your intuition. What do you recommend, and why?

FAQ (optional): Answers to questions you expect from stakeholders. This isn't the first time you've been in a decision like this, and you can anticipate many of the follow-up questions. So invest a few minutes to answer them up front. That avoids unnecessary meeting loops and saves all of us time.

The Right Format

With external partners, good old email is still the best format. Write the briefing directly into the email, or attach it as a document.

Internally, I'm a big advocate of software tools like ClickUp, where every task is managed as a ticket and the discussion happens right inside the task. The briefing for the decision goes into the matching ticket. That way, the entire discussion stays in one place, organized by topic, instead of being scattered across chats, emails and meetings.

How to Put It Into Practice

The principle is quickly explained; the hard part is everyday life. These are the habits I use to apply it consistently:

  1. Plan ahead: Every week, I block a fixed slot to reflect on the past week and plan the coming weeks. Which topics will need a decision in the next few weeks? Which meetings are coming up, and what needs to be prepared for them?
  2. Postpone unprepared topics: When a strategic topic comes up in a meeting without preparation, say: "Happy to schedule a dedicated meeting for this, but first we need a written briefing." It feels impolite at first. Stick with it anyway, or you'll be going in circles again.
  3. Take your writer's block seriously: If you can't write the briefing yourself, the decision isn't ready yet. Clarify what's missing first.
  4. Share early: Send the briefing at least 48 hours before the meeting, so everyone has time to think it through properly.
  5. Start straight with the discussion: Be careful with everyone's time, attention and energy. Don't repeat what everyone has already read, and open with: "Everyone has read the briefing. Where do you see it differently?"
  6. Kill the meeting: Add one sentence to the briefing: "If there are no objections by Thursday, we'll go ahead with the proposal." Many decisions, once well prepared, don't need a meeting at all.

Example 1: The Pricing Decision

Orientation

This is about our pricing model for 2027. It affects every contract renewal from January, so I need a decision from the management team by November 15.

Context

  • We have 180 customers, and the average contract is €14,000 per year.
  • Since spring, three of our five largest customers have asked to reduce user licenses, even though their usage per account has grown by around 30%.
  • Two direct competitors switched to usage-based pricing this year.
  • Our gross margin is currently 71%.

Problem

  • On the surface, it looks as if customers want to save money.
  • The root cause is our pricing model: it ties revenue to the number of users, not to the value customers get from the product.
  • Customers who automate processes and consolidate users get more value and pay us less.
  • Based on the renewals due in 2027, we expect around €250,000 in lost revenue if nothing changes.

Options

(A) Keep per-user pricing and add volume discounts. Advantage: no development effort, and the model is familiar to customers. Disadvantage: the root cause remains. Consequence: revenue keeps falling with every reduced license.

(B) Introduce three usage-based tiers by processed volume. Advantage: price follows the value customers get. Disadvantage: billing needs around six weeks of development, and some small customers would pay more. Consequence: we need to talk to every existing customer about the switch.

(C) A hybrid model with a fixed base fee plus usage. Advantage: revenue becomes more predictable. Disadvantage: the model is harder to explain. Consequence: sales conversations take longer, and the sales team needs training.

Proposal

Option B, combined with a price cap for existing customers, so that no renewal increases by more than 10% in the first year. Usage-based tiers solve the root cause, and two competitors show that the market accepts the model. My gut feeling from customer conversations: most customers will understand the switch if we explain it well. If there are no objections by Thursday, we'll go ahead with the proposal.

FAQ

What happens to the margin in the smallest tier? It drops to around 68%; the calculation is in the appendix.

Does the development clash with the planned release? Yes, so we'll move the release by two weeks. This has been agreed with the head of product.

Example 2: An AI Tool in Customer Service

Orientation

This is about using an AI tool to draft replies in customer service. It affects our support costs and data protection. I need a decision by the end of the month, because that's when the trial access expires.

Context

  • Our customer service answers around 4,000 emails per month.
  • For four weeks, we tested an AI tool from a US provider that drafts replies. Handling time per request dropped by around 40%.
  • The requests contain personal data such as names, addresses and order history.
  • Our data protection officer hasn't reviewed the tool yet.

Problem

  • On the surface, it looks as if the GDPR is slowing down a tool that works well.
  • The root cause: we have no process for reviewing new tools that handle personal data. The trial started before the legal basis, the data processing agreement and the data transfer to the US were clarified.
  • If we keep using the tool without a review, we risk a data protection violation. If we stop it, we lose the efficiency gain.

Options

(A) Stop the tool. Advantage: no legal risk. Disadvantage: the efficiency gain is gone. Consequence: the issue comes back with the next tool, because the missing process remains.

(B) Keep using the tool, pseudonymize customer data before it's transferred, sign a data processing agreement and have the data protection officer review it. Advantage: most of the efficiency gain is preserved. Disadvantage: around two weeks of work for technical changes and contract review. Consequence: the drafts become slightly less personal.

(C) Switch to a provider with EU hosting. Advantage: no data transfer to the US. Disadvantage: in the comparison test, the results were weaker and the costs higher. Consequence: a new trial and several weeks of delay.

Proposal

Option B, plus a short checklist for reviewing new tools before any future trial. That keeps the efficiency gain and fixes the root cause at the same time. My gut feeling: pseudonymization costs hardly any quality, because we review every draft by hand before sending it anyway. If there are no objections by Friday, we'll go ahead with the proposal.

FAQ

Are we even allowed to use a US provider? The provider is certified under the EU-US Data Privacy Framework; the data protection officer will make the final assessment.

Pascal Lindemann

Written by Pascal Lindemann

Founder of Lindemann Ventures. Get in touch

Follow on LinkedIn

Never Miss a Framework