What are the 5 types of design process?
Written by
Passionate Designer & Founder
There are 5 widely recognized types of design process: linear, iterative, agile, design thinking, and systems-based. The right choice depends entirely on your current business constraint. Pick the wrong one for your stage and you lose 3 to 6 months on output that doesn't move anything. And the right answer changes as you scale.
Linear design process: steps happen in sequence, research through ship, no loops. This works when requirements are fixed and the audience is well understood, typically government contracts or large enterprise software with compliance specs. It almost never works for growth-stage tech companies, because the market moves while you're building.
Iterative design process: design, test, learn, repeat in 2 to 4 week cycles. This is the right model for most scale-ups between €500K and €5M ARR, where product direction is mostly clear but execution details need constant calibration. The cost is overhead. Each cycle requires facilitation, documentation, and someone with authority to make decisions between rounds. Without that structure, iteration becomes spinning.
Agile design process: agile is not a design process. It's a project management framework that design gets forced into. The mistake I see most often is design sprints running on the same 2-week cycle as engineering sprints, with no buffer for the research that needs to happen 2 to 3 sprints ahead. Designers end up making visual decisions without strategic input. Engineers wait on assets that were never properly defined.
Design thinking: the IDEO framework of empathize, define, ideate, prototype, test. Useful for reframing problems, less useful as a production process. On a Montblanc e-commerce project, we used design thinking in discovery to surface audience insight that completely reframed the conversion strategy. But we didn't run the build inside a design thinking structure. That would have been slow and expensive.
The type the SERP barely covers
Systems-based design process is what growth-stage companies actually need and rarely get. A systems-based process builds reusable components, documented decision logic, and a shared design language across every surface a buyer sees: website, product UI, sales deck, demo, lead capture. The design becomes infrastructure, not a one-off deliverable.
For a SaaS company scaling past founder-led GTM, fragmentation is almost always the real problem. Website built by one team, product UI by another, sales deck by a freelancer. Buyers see four different companies. Trust leaks before the first conversation. A systems-based product design process closes that gap because every surface shares the same component library, the same visual logic, the same narrative.
The tradeoff is real: installing a design system across touchpoints takes 8 to 14 weeks depending on scope, and it requires someone with authority to enforce consistency after the system ships. Without that enforcement role, the system degrades within 6 months. For how this connects to positioning and buyer perception, see category design for B2B and brand-led growth. To map which type fits your stage, book a 20-min intro. For the full guide, read our product design process overview.
