A feature doesn’t exist in

A feature doesn’t exist in isolation. It exists in the context of your user’s journey.

When designing, you have to ask: - Where is the user coming from? - How familiar are they with the product? - What mental models are they bringing in? - How much have they already learned through previous actions?

Take one of my screens as an example. It’s filled with terms like: Atom. TVL. Tags. Contributors. To an outsider, it’s confusing. Almost unusable. But that screen wasn’t designed for an outsider.

It was designed for someone who: - Has gone through onboarding - Created their first identity - Made their first claim - Staked on something they believe in - Spends time in the community (Discord, Twitter spaces, etc.)

They don’t just use the product. They live in it. And that’s the key. Good design isn’t about making everything universally simple. It’s about making it contextually clear for the right user, at the right time.

How do you get there? You track the journey: - When users take key actions - Where they drop off - How their behavior evolves over time

That’s how you earn the confidence to design “complex” screens that actually feel intuitive. Designing products isn’t just about clarity. It’s about empathy, grounded in real user behavior.