Can growth-driven design work on WordPress without a special theme?

Growth-driven design has three stages: strategy, a launchpad site, and continuous improvement. The method's site models the improvement stage as 14-day sprints, and it describes each cycle as planning around a focus metric, building, learning from the result and sharing what was learned. In practice that asks a site for three abilities: changing pages, seeing what visitors did, and sometimes comparing two versions. Those abilities are also a fair basis for comparing platforms for growth-driven design.

Lean Labs' growth-driven design program runs on HubSpot CMS in 30-day cycles, so its platform is a different one. Its description of the work still shows how little of the method lives in a theme. The agency reviews page behavior, form results, CRM lifecycle data and feedback from the sales team. It then ranks candidate changes by expected pipeline impact, by buyer relevance and confidence, and by effort.

The review and the ranking in that description are evidence and judgment. A team on WordPress can gather the same kinds of input and make the same calls. The software affects how the resulting change gets made and measured, and the theme's share of that is editing.

WordPress has two kinds of theme, and the difference is about editing. Block themes let you use blocks throughout the site, including in templates and template parts, and you edit them through the Site Editor and Styles. Classic themes are built on PHP templates and don't use the Site Editor.

The consequence shows up when a cycle calls for a change above the level of one page's content. Suppose your plan is to add a proof section to the template every service page uses. On a block theme, a marketer with access to the Site Editor can make that change there. The same reach has a cost: a change to a shared header or footer applies to every page that uses it, so check where a shared part appears before you edit it. On a classic theme, the same change depends on what the theme and its plugins expose. Where they offer no control for it, the change goes through the theme's files, and that is developer work.

So a block theme is an editing convenience. It makes more changes available to the people who decide on them, and it can shorten the wait between a decision and a live page. We look at that side of the work in running growth-driven design without coding experience. A classic theme you already have supports the process as long as it lets you make the changes you plan and measure the result.

Seeing what visitors did is a separate job from editing. Site Kit, Google's free and open-source plugin, connects Search Console, Analytics and PageSpeed Insights to WordPress. It shows metrics for the site and for individual posts inside the dashboard, which puts the numbers where the team already works.

Site Kit doesn't choose what to work on or run experiments. Connecting Analytics also doesn't mean the outcome you care about is being counted. If your focus metric is demo requests, confirm that a submitted form is recorded as an event before you take a baseline. And read the numbers on the live site. Site Kit needs a publicly accessible site for setup, and a staging copy can display the production site's data.

Some evidence doesn't come from an analytics plugin. What the sales team hears on calls and what happens to a lead after the form are part of the picture in the Lean Labs process, and a WordPress team has to bring those in from its CRM and its own conversations.

A split test needs something that divides visitors between two versions and counts what each group does. Neither a block theme nor Site Kit does that. One plugin that does is Nelio A/B Testing. Its free plan covers 500 tested pageviews a month and one active test, with any type of test and most features. Paid plans allow several tests at once and larger quotas. Some advanced features depend on the plan, and session recording is an add-on.

That allowance is a limit on how much traffic the plugin will include. It isn't the amount of traffic your question needs. Suppose the page you want to test gets 450 views a month, and it's the only test you're running. All of that traffic fits inside the free plan's allowance. Whether 450 views can separate two versions is a different matter. As Optimizely's guide to experiment length explains, the answer depends on the page's current conversion rate and on the size of the difference you want to detect, and a small difference needs more data than a large one.

A quiet page doesn't stop the process. You can watch a few people who resemble your buyers use both versions, ship the one that evidence favors, and record the decision as a judgment. We describe that route in turning user insights into hypotheses and experiments.

Each row above is one way to do the job. A different analytics tool or testing service fits the same slot, and a team can run useful cycles before it has the third row at all.

The theme question is best settled with a list. Write down the changes you expect to make over the next few cycles and note who can make each one today. If most of them are edits to page content, your current theme is doing its job. If most of them are template changes waiting on a developer, a move to a block theme is worth pricing, because it can put more of those changes in your team's hands. That is a judgment about editing speed, and the cycle itself runs the same way on either kind of theme.