# Design is not a process. It’s a system

**URL:** <https://forum.zurb.com/t/design-is-not-a-process-it-s-a-system/478>\
**Category:** Aligning your team\
**Created:** [December 30, 2025, 3:17am UTC](https://forum.zurb.com/t/design-is-not-a-process-it-s-a-system/478 "2025-12-30T03:17:21Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Bryan](https://yyz2.discourse-cdn.com/flex034/user_avatar/forum.zurb.com/bryan/32/448_2.png) [@Bryan](https://forum.zurb.com/u/Bryan)\
**Post date:** [December 30, 2025, 3:17am UTC](https://forum.zurb.com/t/design-is-not-a-process-it-s-a-system/478/1 "2025-12-30T03:17:21Z")

</div>

Most design teams still describe work as a sequence of steps. Discover, define, design, deliver. Or research, ideate, prototype, ship.

That story made sense when design work ended at launch. It does not match how digital products are actually built today.

Agree or disagree?

We featured Thomas’s article on continuous product design.

> **[Design is ongoing. Adapt, refine, and evolve with user needs.

In this...](https://www.linkedin.com/posts/helio_design-is-ongoing-adapt-refine-and-evolve-activity-7411439943501377536-Q6lo)**
>
> Design is ongoing. Adapt, refine, and evolve with user needs.
> 
> In this throwback featured post, we love Thomas Sutton’s argument that digital products need a continuous design process rather than a traditional, one-time design phase. Design should be...

In Sutton’s framework, there are four things always in play:

- messy reality
- insights
- concepts
- product

None of these comes first. None of them are ever done.

---

<div class="post-metadata">

**Author:** ![nikhil\_mahen](https://avatars.discourse-cdn.com/v4/letter/n/58956e/32.png) [@nikhil\_mahen](https://forum.zurb.com/u/nikhil_mahen)\
**Post date:** [December 30, 2025, 2:23pm UTC](https://forum.zurb.com/t/design-is-not-a-process-it-s-a-system/478/2 "2025-12-30T14:23:08Z")

</div>

I dont think both have to be mutually exclusive elusive. I think the difference is in the end of launch phase and the study adapt refine phase. The beginnings and subsequent changes are always going to be different and will need different mindsets but its not either or.

---

<div class="post-metadata">

**Author:** ![Bryan](https://yyz2.discourse-cdn.com/flex034/user_avatar/forum.zurb.com/bryan/32/448_2.png) [@Bryan](https://forum.zurb.com/u/Bryan)\
**Post date:** [December 30, 2025, 6:02pm UTC](https://forum.zurb.com/t/design-is-not-a-process-it-s-a-system/478/3 "2025-12-30T18:02:05Z")

</div>

Like all good frameworks, choose your own adventure wisely. 🙂

I tend to see a sway back to a more organic process across the industry, especially with the tools that enable it… what I don’t see is how the impact is tracked. Process sometimes gives the illusion of a positive outcome, but it’s the results that matter more.

Do you guys use a set process?