One Page Analysis Plan

Quark Insights: One Page. Sharper Insights. Better Decisions.

The Plan That Makes Your Analysis Land

Analyses achieve more impact — and drive businesses to take action — when you flip your point of view, and begin with the decision instead of the data. That shift sounds simple, but it can really serve to change how you think in your work. I've said it on more than one occasion, begin with the end in mind.

Many of us begin in the same manner. A request comes in, we pull the data, poke around, find something interesting, and build a report around it. We work hard, the deck looks thorough, and then — nothing happens. The stakeholder nods, says "good stuff," and goes back to what they were already doing. That isn't a data problem. That is a direction problem. And it can be fixed before you touch any of your data.

This plays out similarly no matter where you sit — at agencies, at media companies, at brands with smart people and real budgets. The work is solid. The data is clean. But the analysis is built around what was available, not around what someone actually needed to decide. This post walks through the one-page analysis plan I use and teach — a tool built on the decision-first framework I have written about here before — and how the Insights Topline Report template I developed puts that plan into a ready-to-use structure. Whether you are writing your first analysis or your five-hundredth, this approach helps you do more, faster, with results people trust and use.

Connecting Everything Back

Here is a question worth sitting with: what is the analysis actually for?

Not "what data do we have?" Not "what happened last quarter?" But — what decision does someone need to make, and what would a useful answer look like to them?

In my experience, analysis paralysis has a real cost. In a world where leaders want faster answers from growing mountains of data, that paralysis is not just stressful — it is expensive. And it is completely avoidable. The fix is not more data. It is less ambiguity upfront. When you know what decision your work is supporting before you start, every choice you make during the analysis — what data to pull, what metrics to use, what to cut — has a clear filter. Does this help answer the question? If yes, it stays. If not, it goes.

This is what I call the decision-first framework. And the one-page analysis plan is how I put it into practice.

The One-Page Plan: Five Pieces That Do the Work

The plan is intentionally short. One page forces clarity. It is not a project brief or a research proposal — it is a map you write before the trip so you do not get lost halfway through. Each section earns its place.

1. The decision question

This is your anchor. Everything else flows from here. A vague question — "How did the campaign perform?" — invites a general report with no clear purpose. A sharp question changes the game: "Which channels should receive increased investment for Q3, based on first- and second-quarter performance?"

One question. One decision. That is it.

In my "From Guts to Glory: Making the Plan" post, I describe this as a five-step framework — and the first step is always identifying the decision at the center of the work. Planning for 15 minutes can save hours of revision later. I start every engagement with four questions I sometimes write on a sticky note: What decision are we informing? Who owns that decision? By when does it need to be made? What will a useful answer look like to them?

2. Success metrics

Once the decision question is clear, define the specific numbers that will answer it. If the question is about channel reinvestment, you probably care about conversion rate, cost per acquisition (CPA), and return on investment (ROI) — not page views or impressions alone.

Choosing metrics before you pull data prevents a common trap: getting distracted by numbers that are available but not relevant. The metrics on your plan should connect directly to the outcome you are trying to influence. Full stop.

3. Data sources

Be specific here. "Campaign data" is not a source. "Channel-level performance data from Q1 and Q2, pulled from Google Ads and Meta Ads Manager" is a source. Naming it forces you to verify it exists, that it is clean, and that it covers the right time period — before you need it mid-analysis.

4. Context notes

Numbers without context mislead. A 20% lift in conversion rate sounds strong until you learn the previous period had a tracking error that undercounted results. That lift might just be a correction — not real growth.

I build context notes into every plan from the start because they are the frame your audience needs to trust the story you are telling. This does not need to be long. A sentence or two per relevant factor keeps it manageable and makes your final analysis much harder to misread.

5. The recommendation (hypothesis)

Yes, you write this before the analysis is complete. Not as a final answer — as a hypothesis. A starting point that forces you to think like a decision-maker from the beginning.

Writing the recommendation early is one of the most clarifying habits I know. It surfaces assumptions. It tells you what evidence you actually need. And it makes the final recommendation far easier to write, because you have been building toward it the whole time.

Lead With the Answer — Every Time

This is the part of the framework that surprises people most, especially early-career analysts trained to "show the work" before sharing the conclusion.

Decision-makers do not read the way students take tests. They scan. They jump ahead. They have four other things open on their screens. If your key finding is buried on slide 14, it will not be found. And if it is not found, it will not drive action.

Lead with the answer.

"Reinvest 60% of the marketing budget in paid search next quarter. Paid search delivered a 25% higher ROI than social media over the past two quarters, with a lower CPA and more consistent conversion performance."

Then show the supporting evidence. The data, the context, the charts — all of it follows the recommendation, not the other way around.

This is the backbone of what I call the "Winning Toplines" approach: lead by priority, put your strongest finding first, and focus only on findings that change outcomes. It mirrors the classic journalistic inverted pyramid — most important information first, supporting detail after. I describe it in my "Toplines: Best Analysis Practices" post as working like an inverted funnel: start with the most critical information, then move to the supporting layers. This structure respects your audience's time. It also makes you easier to work with — and harder to ignore.

Context Is the Difference Between Data and Insight

It is worth pausing on this because context is the piece analysts most often skip — and the piece decision-makers most often misread without.

A number without a reference point is just a number. Context is what makes it meaningful. I have written about this before: context transforms isolated numbers into actionable intelligence. Without it, even accurate data can send a business in the wrong direction.

When you build context notes into your one-page plan from the start, you are not adding extra work at the end — you are building the frame your audience needs to trust the story you are telling.

A few practical context questions I include on every plan:

• What time period does this data cover, and how does it compare to prior periods?

• What counts as normal or expected performance for this metric?

• Which channels, regions, or customer segments are included — and which are not?

• Are there any known data issues, seasonality factors, or external events that affect interpretation?

None of these require lengthy answers. A sentence each is enough.

The Scope Sheet to Stay on Task

The one-page plan also serves a second function I do not talk about enough: it keeps projects from quietly expanding beyond what was agreed.

Scope creep is one of the most consistent time-killers in analysis work. A stakeholder asks mid-project, "Can we also look at the last three years?" You want to be helpful. You say yes. Suddenly your two-day project is a week, and the original decision has gotten buried under new requests.

I call this the scope sheet, and it changes that conversation entirely. When someone asks for something new, I point to the plan: "Here is what we agreed is in scope. Here is how your new request fits. Here is what it means for the timeline — and here is how we could address it in a follow-up." That simple habit turns scope from an emotional negotiation into a shared reference point.

No surprises. No invisible deadlines. No work that quietly doubles.

A Real-World Example: Where to Put the Q3 Budget

Say a marketing team needs to decide how to allocate its third-quarter budget across paid search, social media, and display advertising. Here is what the one-page plan looks like in practice.

• Decision question: Which channels should receive increased investment for Q3, based on Q1 and Q2 performance?

• Success metrics: Conversion rate, CPA, and ROI by channel

• Data sources: Google Ads and Meta Ads Manager exports for Q1 and Q2; internal CRM (customer relationship management) revenue data

• Context notes: Q1 results were affected by a creative refresh in February — weight Q2 results more heavily. Scope covers U.S. digital channels only.

• Recommendation (hypothesis): Shift budget toward paid search; reduce display spend; reassess social media based on Q2 CPA trends.

From here, the analysis has a job. You know what data to pull, what to compare it against, and what question your final presentation needs to answer. The plan keeps every decision you make during the analysis pointed in the same direction.

The Template That Makes This Repeatable

If you want a ready-made structure to work from, I built the Insights Topline Report template for exactly this. It is a single Microsoft Word document — available in the Quark Store — that puts all five components of the one-page plan into a format you can overwrite with your own content.

The template is built around the same principles I have described throughout this post: lead with the recommendation, support it with data, and frame everything with enough context that the decision is obvious. For new analysts, it works as a checklist — a way to make sure nothing important gets skipped. For experienced professionals, it creates consistency across projects and makes it easier to hand work off, collaborate across teams, or revisit past analyses without losing the thread.

This is something I care deeply about: making excellence repeatable. A strong one-time analysis is great. A professional workflow you can rely on every time — that is what separates good analysts from trusted advisors.

Before You Open the File

The one-page plan takes 20 to 30 minutes to write. It saves hours of misdirected analysis, rounds of revision, and the particular frustration of presenting something thorough that nobody acts on.

Start at the finish line. Write the decision question first. Name the metrics, the sources, the context. Draft a hypothesis for the recommendation. Then — only then — open the data.

Your analysis will be sharper. Your presentation will be clearer. And the people on the receiving end will know exactly what to do next.

The best question to ask yourself when you are done: did the decision-maker know what to do the moment they saw your first slide? If the answer is yes, you are doing it right.

Ready to build your first one-page plan? Download the Insights Topline Report template from the Quark Store and use it on your next project.