Back to insights
ProcessJul 20267 min read

What I Learned From Building Digital Products

Every project teaches something different. These are some of the lessons that continue to influence how I approach design and development.

What I Learned From Building Digital Products
Process
01 / Introduction

Working across design and development creates an interesting perspective. You begin to see how decisions made in one part of a project affect everything else. A visual decision can influence implementation. A technical constraint can change an interaction. A business requirement can completely change the structure of a product.

02

The first idea is rarely the final idea.

Early concepts are useful because they create something concrete to react to.

The goal is not necessarily to get everything right immediately. The goal is to create enough direction to discover what should change.

03

Constraints can improve the work.

Limited time, technology, budget, content, or resources can initially feel restrictive.

But constraints also force prioritisation. They make it necessary to identify what actually matters and remove what does not.

04

Implementation changes your thinking.

Building the product reveals things that static designs cannot.

Responsive behaviour, reusable components, real data, performance, and edge cases all introduce new considerations.

05

The system matters more than the single screen.

A product can have one beautiful screen and still feel inconsistent overall.

Reusable patterns, spacing rules, typography, components, and interaction principles create the consistency users experience across the product.

Final thought

Good digital work is rarely the result of one perfect idea. It is usually the result of iteration, testing, implementation, and continuous refinement.

Have something in mind?

Let's make it
worth seeing.

Start Your Project