Writing on what it actually takes.

The most uncomfortable truth in ResearchOps right now — and a challenge to our own community.

How REA Group measured and communicated the value of its enterprise design system.

How REA Group built its DesignOps function and why it was necessary.

Most design systems fail at adoption, not craft. The component library is well-designed. The documentation is thorough. Engineering doesn't use it consistently — and product teams keep going around it.

The gap isn't design quality. It's governance, token architecture, and whether engineering was a co-owner from day one or an afterthought at handoff.

A design system that engineering doesn't trust isn't a design system. It's a reference document nobody reads.

If design isn't embedded in how your organisation prioritises work — RICE scoring, OKR setting, investment planning — it will always be overridden by product and technology pressure.

Not because the work isn't good. Because it was never part of the decision.

The organisations that get design right don't just hire better designers. They change where design sits in the prioritisation conversation — and what evidence it brings to the table.