Design and development across products

Emergente Labs was a contract with the setup I like most: a small team, an existing product that needs steady improvement, and new products taking shape at the same time.

I worked across both, and across both halves of the job, design and development.

Existing products need a specific kind of care. You can't redesign everything, and you shouldn't. The work is to improve the product from inside: better screens, clearer flows, more consistent components, while people keep using it every day.

Because I both design and build, improvements don't stall between disciplines. I can spot a problem, design the fix, and ship it, without a handoff in the middle where nuance usually dies.

The other half is new products. Early on, the questions are different: not "how do we keep this consistent" but "what should this feel like at all". Structure, first screens, the beginnings of a visual language.

Decisions made this early compound more than any others. A good foundation quietly makes every later screen easier. A careless one quietly taxes everything built on top of it. So this is where I try to be most deliberate.

The value of a design engineer on a small team is range. One day the work is a UI problem, the next it's an implementation detail, the next it's deciding whether a feature should exist on one screen or three.

Being able to move between those levels, and carry context across them, is what keeps a small team's product feeling bigger and more finished than the team behind it.