Lessons learned
Make the invisible decisions visible
The hardest calls on this project were abstract relationships with implications nobody could see yet, like which way a link points or where a test gets defined. I think design’s power is making those implications visible, through diagrams, lo-fi mocks or working prototypes.
On complex software, that means helping the whole team see how the pieces fit, sometimes from a bird’s-eye view and sometimes at the level of a single interaction. The skill is switching between the two to find where things are most unclear.
Make bets you can build on
Product development is a series of informed bets, sometimes with one-way doors. With unlimited engineering time, a good team can design the perfect experience, but that's seldom the situation.
So as design lead, I try to ground our bets in real evidence from customers and the industry, then think through what each option commits us to: if we do A, what follows, and if B, what follows? Which one lets us come back and improve it?
Working in increments, starting with the first, guards against over-investing and pushes us to think long term when everyone is under pressure just to get it done. On this project that meant plates in worksheets first and a slightly hacky test-order list, each leaving a bigger redesign possible later.