How do I explain this to a non-technical exec?

This is a process and stakeholder question — the kind that usually shows up from account lead, managerial interview. It rarely has a one-line answer, because the honest version of “How do I explain this to a non-technical exec” is a shortlist of rival explanations, not a single cause. The job is to work through that shortlist with evidence and stop as soon as one of them is confirmed — not to write a report that mentions all of them.

The rival explanations

Direct answer: Executive communication fails for five specific, fixable reasons — presenting rankings when the exec asked about revenue, narrating a measurement cliff as an algorithm hit, burying the real request (usually a date) inside a complaint, arriving with too many charts and no decision, and failing to price risk in business language — and fixing the wrong one wastes the meeting.

Treat these as competitors, not a checklist. The point of naming five up front is to stop the first plausible-sounding one from becoming the story before the others have been checked.

• The exec is hearing rankings when they asked about revenue.
• A measurement cliff is being narrated as an algorithm hit.
• The request hidden in the complaint is a date, not an explanation.
• Too many charts arrived without a decision.
• Risk (migration, prune, legal) has not been priced in business language.

What the evidence has to show

Direct answer: A single traffic-to-revenue bridge for the period in question, at most two annotated charts, a before/after SERP or URL example instead of a crawl graph, a clear set of options with cost and downside, and the exact decision needed this week are what a usable executive memo actually contains.

None of the five above survives on a hunch. Here is what actually needs pulling before any of them can be ruled in or out:

• One traffic-to-revenue bridge for the period in question.
• Two annotated charts max (GSC non-branded clicks; the specific incident).
• A before/after SERP or URL example, not a crawl graph.
• Options with cost, lag, and downside of doing nothing.
• The exact decision needed this week.

The decision rule

Direct answer: One page, one decision. Lead with business effect, then the mechanism in one analogy, then the ask. Appendix holds the crawl. Never present more than two options plus ‘do nothing’.

What to tell the people around you

Direct answer: The sponsor needs fifteen minutes on the agenda and a clear yes/no ask, with agreement that rankings are a diagnostic — not a data dump that leaves the room without a decision.

The analysis is not finished until it produces something a non-specialist can act on. That means naming the situation, the cost of getting the first move wrong, and a specific ask — not a summary of the investigation.

• Situation — Trust is the asset. Complexity dumped on a board slide spends that asset.
• So what — Unread audits do not get funded. A decision memo does.
• The ask — Fifteen minutes on the agenda. A yes/no on the stated ask. Agreement that rankings are a diagnostic.

SEO writes the one-pager. Sponsor puts it in front of the room.

How to act on this

1. Build one traffic-to-revenue bridge covering the specific period in question, rather than a general performance dashboard.
2. Choose at most two annotated charts — GSC non-branded clicks and the specific incident — and drop everything else from the main deck.
3. Use one before/after SERP or URL example instead of a crawl graph to make the mechanism concrete in plain language.
4. Present at most two options plus 'do nothing', each with its cost, lag, and downside stated plainly.
5. Name the exact decision needed this week, and put the supporting crawl and technical detail in an appendix, not the main slide.

Frequently asked questions

Why do detailed SEO audits so often fail to get funded?

Because they present analysis instead of a decision — an exec reading a 40-slide audit has to do the work of extracting the ask themselves, and unread audits don't get funded regardless of how thorough they are.

How many options should be presented to a non-technical exec?

At most two, plus an explicit 'do nothing' option with its own stated cost — more than that turns a decision meeting into an open-ended discussion.

Should rankings ever be the headline metric in this kind of memo?

No — lead with business effect (revenue, pipeline) and treat rankings as a diagnostic detail that explains the mechanism, not as the top-line result.

What if the exec's real question is hidden inside a general complaint?

Listen for the actual request underneath — it's often a date or a yes/no decision, not a request for a full explanation. The memo should answer that specific request directly.

Where does the detailed crawl data and technical evidence go?

In an appendix, available if asked for, but never the main body of the memo — the main page is reserved for the decision, not the investigation.

What if the exec asks a technical follow-up question mid-presentation?

Answer briefly in plain language and offer to go deeper in the appendix or a follow-up — reopening the technical detail in the main room is what turns a decision meeting back into an audit review.

Is it ever appropriate to bring the full technical team into this meeting?

Only if a genuinely technical decision needs to be made live — otherwise, one person presenting the one-page memo keeps the meeting focused on the decision rather than turning into an open technical discussion.

Sources

1. Google Search Console overview — Search Central
2. Beginner's Guide to SEO — Moz
3. Business communication — Wikipedia
4. Executive summary — Wikipedia

Where nqzai fits

nqzai runs this same rival-hypothesis framework against your own connected Search Console, Analytics, and audit history, and returns a keep / change / stop decision with the evidence named — including which of the explanations above it could not test, and what to connect to close that gap. No extra cost for the analysis itself; it reads measurements already on file.

Ask nqzai: “How do I explain this to a non-technical exec?”