Three years ago, we made a deliberate decision to take on more product design work alongside our brand engagements. We've now shipped or significantly redesigned ten digital products — across healthcare, fintech, EdTech, and SaaS. Here is what that experience has taught us.

Research is not optional. Every product engagement we've rushed through the research phase has paid for it in revisions. The clients who pushed hardest to skip discovery were, without exception, the ones who needed it most. Real users have beliefs, habits, and mental models that no amount of internal stakeholder alignment can substitute for. Find them early. Listen hard.

The first version should do less. There is enormous pressure — from founders, from investors, from enthusiasm — to build the full vision at launch. This is almost always a mistake. The features you think are essential are often not the ones users actually need first. Ship less. Learn faster. Iterate with real data.

Design and development are not sequential. Handing off a completed design to a development team and expecting it to survive intact is a fantasy. The best products we've shipped were built by teams where designers and developers were in constant conversation — not just at handoff, but throughout. This requires a different kind of relationship than most organisations are used to. It's worth building.

Accessibility is not a feature, it is a baseline. We now conduct accessibility audits at every stage of a product build, not as a final checklist. WCAG compliance is the floor, not the ceiling. Designing inclusively makes products better for everyone, not just users with specific needs.

The work is never finished. Every product we've shipped has needed meaningful iteration within three months of launch. That's not failure — that's how good product development works. Build with the expectation of learning, not with the expectation of completion.

Three years ago, we made a deliberate decision to take on more product design work alongside our brand engagements. We've now shipped or significantly redesigned ten digital products — across healthcare, fintech, EdTech, and SaaS. Here is what that experience has taught us.

Research is not optional. Every product engagement we've rushed through the research phase has paid for it in revisions. The clients who pushed hardest to skip discovery were, without exception, the ones who needed it most. Real users have beliefs, habits, and mental models that no amount of internal stakeholder alignment can substitute for. Find them early. Listen hard.

The first version should do less. There is enormous pressure — from founders, from investors, from enthusiasm — to build the full vision at launch. This is almost always a mistake. The features you think are essential are often not the ones users actually need first. Ship less. Learn faster. Iterate with real data.

Design and development are not sequential. Handing off a completed design to a development team and expecting it to survive intact is a fantasy. The best products we've shipped were built by teams where designers and developers were in constant conversation — not just at handoff, but throughout. This requires a different kind of relationship than most organisations are used to. It's worth building.

Accessibility is not a feature, it is a baseline. We now conduct accessibility audits at every stage of a product build, not as a final checklist. WCAG compliance is the floor, not the ceiling. Designing inclusively makes products better for everyone, not just users with specific needs.

The work is never finished. Every product we've shipped has needed meaningful iteration within three months of launch. That's not failure — that's how good product development works. Build with the expectation of learning, not with the expectation of completion.

Three years ago, we made a deliberate decision to take on more product design work alongside our brand engagements. We've now shipped or significantly redesigned ten digital products — across healthcare, fintech, EdTech, and SaaS. Here is what that experience has taught us.

Research is not optional. Every product engagement we've rushed through the research phase has paid for it in revisions. The clients who pushed hardest to skip discovery were, without exception, the ones who needed it most. Real users have beliefs, habits, and mental models that no amount of internal stakeholder alignment can substitute for. Find them early. Listen hard.

The first version should do less. There is enormous pressure — from founders, from investors, from enthusiasm — to build the full vision at launch. This is almost always a mistake. The features you think are essential are often not the ones users actually need first. Ship less. Learn faster. Iterate with real data.

Design and development are not sequential. Handing off a completed design to a development team and expecting it to survive intact is a fantasy. The best products we've shipped were built by teams where designers and developers were in constant conversation — not just at handoff, but throughout. This requires a different kind of relationship than most organisations are used to. It's worth building.

Accessibility is not a feature, it is a baseline. We now conduct accessibility audits at every stage of a product build, not as a final checklist. WCAG compliance is the floor, not the ceiling. Designing inclusively makes products better for everyone, not just users with specific needs.

The work is never finished. Every product we've shipped has needed meaningful iteration within three months of launch. That's not failure — that's how good product development works. Build with the expectation of learning, not with the expectation of completion.