The human behind the pixels: Who’s Augustine?

I've worked with designers who make beautiful screens and leave the hard questions for whoever builds them. Augustine is the opposite.

When his work got to engineering, I stopped hearing about it: no "what happens when this fails", no missing states turning up as bugs a sprint later. He'd already designed the declined action, the failure after approval, the permission edge nobody asked for. He built our design system alone, tested staging builds himself and retested the fixes. I'd hire him again without thinking about it.

Engineers rate designers on one thing: how many questions we still have after handoff. With Augustine the answer was close to none.

His specs covered the states we usually have to chase down: empty, loading, error, permission-denied, what happens when an action fails mid-flight. He annotated behaviour, wrote acceptance criteria we could build against, then tested our staging builds and filed proper tickets instead of Slack messages. My team shipped faster because design was never the open question.

As a CEO you learn the difference between hiring a function and hiring an owner. Augustine was an owner.

He joined early, built our design practice from nothing, and I never once had to ask where design was on something: he told us first, with the trade-offs already thought through. Forecasting is our core product and brands trust it partly because of how it looks and behaves, and that trust converted to revenue. If he joins your company, design becomes a solved problem.

Supply chain and forecasting are unforgiving domains: the data is dense, and every screen has a dozen ways to go wrong.

Augustine designed tools our brands actually used daily, and when something was off he'd already found it before we reported it. He asks the operational questions most designers don't think to ask.