Is DDD still relevant today?
Written by
Passionate Designer & Founder
Growth-driven design is more structurally relevant now than in 2015, but the reason has changed. It's no longer about agile being better in theory. It's about the fact that the average B2B SaaS website was fully redesigned 26 months ago, according to Orbit Media's annual website survey, while the product, positioning, and ICP it was built around have all shifted since then.
The standard take is that growth-driven design reduces risk and fits how modern teams work. That's true, but it misses the sharper point. Static websites are a liability when your competitors are running weekly experiments. Your launch-day assumptions are now 26 months old. Growth-driven design solves this structurally, not philosophically.
The argument against it is also real. AI-assisted design tools, Webflow's native CMS, and no-code testing layers have made continuous improvement easier to run without a formal agency engagement. A product-led growth team at a Series A company can now run basic A/B tests on landing pages without outside help. The tooling has democratised the tactical layer. What it hasn't democratised is the strategic layer: knowing which experiments to run, in which order, and what the data is actually telling you about your positioning rather than just your button colour.
Execution without strategy compounds nothing. This is where most in-house attempts stall. The team runs tests, accumulates data, and optimises toward a local maximum that turns out to be the wrong hill. We see this regularly: conversion rate on a free trial CTA goes up, but qualified activation drops because the messaging attracted the wrong segment. The numbers looked good. The business outcome didn't.
What the methodology looks like in practice today
For Montblanc's digital work, the sprint model let us run six distinct positioning tests across their e-commerce landing pages inside one quarter. A traditional project structure would have required a full brief and sign-off cycle before any variant went live. That speed difference compounds over 12 months in ways that are hard to reverse once you fall behind.
Growth-driven design as a named methodology is less frequently cited by agencies today, partly because the practices have been absorbed into retainer-based design partnerships without the formal label. The sprint cadence, the launch pad site, the backlog prioritisation framework: these are now standard operating procedure for any serious design partner working with SaaS or e-commerce clients. The label faded. The logic didn't.
The real question isn't whether growth-driven design is relevant. It's whether your current design relationship gives you a mechanism to act on data in under two weeks. If the answer is no, your website is running on assumptions that get staler every month. Our design subscription model overview covers the structural difference between project, subscription, and retainer formats if you want to understand which operating model actually enables this cadence. To talk through your specific setup, book a 20-min intro. For the full guide, read our design-driven growth overview.
