vibecodingpt2

Vibe Coding Part 2

In this week’s Data Diaries, the second of a five part series on “vibe coding” basics for non-coders. Katie and I have talked extensively about vibe coding in the past on the podcast, but we’ve never really dug into the basics of it. So in this series, completely unsurprisingly modeled on the 5P Framework by Trust Insights™, I’ll cover those basics.

The People Involved

Software should never be built in a vacuum unless you are literally the only person who will ever use your software and its outputs, like a solopreneur. If that’s not the case, if the data you generate from your software has downstream uses, you need to think about how those people will use the software.

Last week, we started this series with this user story:

As a [marketing analyst] I need to [obtain query AND page level metrics from Google Search Console’s API] so that [I can help my SEO team understand what pages are getting the most traffic from specific search queries].

Look at the people involved. You’re in there, but so is your SEO team. Who are they? What do they do? How do they operate? Critically, this data that we’re writing software for – how do they use it today, if they do? Or if they don’t use it, how would they use it?

Gathering requirements for software is as straightforward as asking people what they need. In our specific example, what they get now in Google Search Console is this:

For queries:

  • Impressions
  • Clicks
  • Clickthrough rates
  • Query terms

For pages:

  • Impressions
  • Clicks
  • Clickthrough rates
  • Page URLs

No one in the web interface gets BOTH query terms and page URLs in the same row of data, and that’s what the people on our SEO team desperately want. Instead of:

trustinsights.ai, 22 clicks, 110 impressions, 20% CTR

What they really want to see is:

  • trustinsights.ai, “who is trust insights”, 11 clicks, 55 impressions, 20% CTR
  • trustinsights.ai, “how to hire trust insights”, 11 clicks, 55 impressions, 20% CTR

Knowing what page AND what search term is what our people want. But we don’t want to stop there. We need to know from our people, our SEO team, what they’ll do with the information. Handing them a raw spreadsheet of data might be useful, or it might be shelfware.

If we talk to our people and they say, “Well, part of this will go in our monthly report to the CMO, but part of it will also be used for our content team to help them figure out what we’re getting impressions for but not clicks, and then create more, better content that’s aligned to those topics.”

If that’s what they say, then our deliverables aren’t just a spreadsheet. They could be slides to help the CMO know what’s going on, and it sounds like they might also benefit from something like an AI-generated summary of topics, especially topical blind spots.

And we might benefit from talking to the CMO, as well as talking to the content team, to understand the third order effects of our analysis, of our software. Maybe the CMO doesn’t care at all, or maybe she REALLY cares about high commercial intent terms but not the rest. If we don’t know that, we’ll build a tool that doesn’t provide as much value as it could.

Next week, we dig into the process of vibe coding.

Leave a Reply

Your email address will not be published. Required fields are marked *

Pin It on Pinterest

Share This