The third way I build. Where the other two arcs go from research to a stage and to a product, this one goes from execution to a redesigned process: I took client reporting that stopped at "what happened" and rebuilt it to answer "so what" — at scale, across a team.
① The problem — reporting that stopped at "what happened"
The reports clients received were descriptive: this campaign performed well; it drove this many impressions, at this CPC, with this CTR. Accurate, but inert — a recap of numbers with no interpretation and no line drawn back to what the client was actually trying to achieve. The "so what" was missing, and with it, the reason the client should care.
② The why — what a report is actually for
Before touching the format, I reframed the purpose. A report isn't a data dump; it's how an agency tells the story of its impact on a client's goals. I built the redesign around three questions every report has to connect: what does the client want to achieve, how does our strategy serve that, and what progress are we making toward it? Everything ties back there — otherwise you're just reporting motion, not impact.
③ The redesign — insight first, numbers in support
The new format leads with the narrative — a plain-language summary of what changed and why it matters — and then backs it with templated visualizations instead of raw tables. The structure carries the mechanical load, which frees the analyst to spend their time on the interpretation rather than assembling charts. The report becomes an argument, not an inventory.
④ Made repeatable — templated and automated
Then I made it stick. I built a reusable report template and presentation structure the whole team could run, so quality didn't depend on who happened to assemble the deck. And when a client needed something that didn't exist yet — an automated biweekly report — I built it end to end inside TapClicks (VisionPoint's reporting platform) and set it to run itself, so the insight went out the door on schedule without manual rebuilding every cycle.
This is the process half of how I build: not a metric or a product, but a better way for an entire team to turn spend into a story clients can actually act on.