Short reflections on Product Ecosystems, in practice.

Executive-length thinking, not white papers — the kind of question worth raising in a leadership meeting.

REFLECTION

The two assets every product creates

A product ships once. The reasoning behind it — what was tried, what failed, what a supplier actually told you — can outlive the product itself, if something is built to keep it. Most organisations only manage the first asset.

REFLECTION

What retires with the engineer who leaves

Product data survives a departure. Judgement often doesn't — the reasons a design choice was made, the vendor that quietly under-delivered, the tolerance that mattered more than the spec said. Worth asking who's holding that today.

REFLECTION

Manufacturing learning is a design input, not a debrief

Yield issues, tooling constraints and quality data are usually treated as production's problem to solve after the fact. Fed back into the next design cycle, they're some of the highest-value inputs a Product Ecosystem has.

Case studies

Real programmes, published once approved.

CGC works across consumer electronics, personal care and consumer hardgoods programmes. Named case studies are published here only after the client has reviewed and approved the material — nothing appears without that sign-off.

Have a question worth raising

Bring it to a real conversation.

Start a conversation