The road to getting the component to a new state

Working on a two-person design team is always fun, but it can also spark a small uproar over task delegation. The design lead handed me the research: question everything, then come back with an answer.

When I looked closely at the component in its original state, the questions piled up fast – fast enough that I built a running “questions board” just to hold them all.

The pattern I kept circling back to: we were behind on the small UX details that make data binding feel effortless – but the gap was closable without touching our core architecture. Other tools had clearly found a way to add power without adding friction, each with its own learning curve. To understand how, I analysed 5 competitor platforms, relying on Claude to accelerate the research so I could go deeper in the time I had. 

With the use of Claude, I analysed 5 leading platforms:
Here’s what I measured:

• What data sources you can bind FROM (databases, app state, URL parameters, user session, etc.)

• What UI properties you can bind TO (visibility, text, styles, defaults, etc.)

• How easy it is to create those bindings (visual tools vs. writing code)

That matrix was the turning point. It showed exactly where we were ahead, where we’d fallen behind, and – more importantly – a realistic path to closing the gap.

That research pointed to one clear answer: an expression-syntax-based binding solution. Proposing it, though, was where things got harder. 

In our meeting with the engineering lead, I walked through the research and the proposed solution. It didn’t land the way I’d hoped – instead of a green light, I left with 3 new problems to solve:

• If a form was already bound to this Team entity, there was no way to simply tell the data table to display `data.members`.
  You’d need a separate data table context, a re-fetch, or a string of extra configuration steps.

• The component’s event system was incomplete and unclear.

• There was no straightforward way to bind the right-side form to whichever row was selected on the left.

None of these were things I’d missed by accident – they were the kind of integration issue that only surfaces once you start asking how a change to one component ripples through the rest of the system.