Co-architecting a product ecosystem

I joined as the only product designer when the company was a single product. Today it’s a connected ecosystem spanning the full arc of an employee’s time at a company — from the moment they’re a candidate to the moment they leave. I co-architected that arc. This is the story of the decisions that made it cohere.

The strategic problem with ecosystems

Most “platforms” are a collection of products that happen to share a login. Each was designed for its own use case, by its own logic, and the seams show the moment a user crosses from one to the next. For an HR platform, that failure is acute: the entire value proposition is that these stages are connected, and a disjointed product experience quietly contradicts the pitch.

The design question underneath the product strategy was therefore: what has to be true, structurally, for a lifecycle of products to feel like one continuous system rather than a suite?

Where design entered the strategy

I was in the room for the product bet, not handed it afterward — partnering directly with the CEO, CTO, and Head of Product. That position matters, because the decisions that determine ecosystem coherence are made before the screens:

• A shared spine. The products had to be built on common primitives — the same underlying model of a person, a stage, a transition — so that moving between them felt like progression, not relocation. This is as much a data and conceptual decision as a visual one, which is why design had to be in the strategy conversation.
• Sequencing the build. Which products to launch, in what order, so that each one strengthened the spine rather than forking it. I led end-to-end design on three flagship launches; the order they shipped in was a strategic choice, not a backlog accident.
• Restraint as strategy. The hardest ecosystem decisions are about what not to connect. Forcing coherence where the use cases genuinely diverge produces a worse product than honest seams. Knowing the difference is the job.

A real ecosystem isn’t built on shared design. It’s built on a shared understanding of the user — get that right and the rest follows; get it wrong and nothing else can fix it.

Leading the execution

Three flagship products taken from zero to launch, end-to-end. Each one was a test of whether the spine held under a real, specific use case — and each shipped one informed the model the next was built on. That feedback loop, run deliberately, is what kept the ecosystem converging instead of fragmenting.

Honest scope

This was the work of a company, not a person. The product strategy was shaped with executive partners; engineering and product owned enormous parts of it. My contribution was specific: holding the design and conceptual coherence of the lifecycle as a whole, leading the design of its flagship products end-to-end, and being a designer the executive team treated as a partner in the bet — not a service to it.