After listening to Katie Dill, one theme stood out: design is ultimately about trust. Not just trust between users and products, but trust between the people working together to build them.
And trust is never automatic. It's earned.
1. Focus is a discipline
Katie talked about learning to fly. Flying demands total focus. There's no room for distraction. It forces presence, and that intensity becomes clarity.
The parallel to design is strong. When the stakes are real — when products affect people's money, safety, privacy, or time — quality is not optional. Systems must work. Interfaces must be clear. Decisions must be intentional.
If we want our work to be trusted, it has to feel deliberate. Thought through. Engineered with care. People can feel when something is designed seriously.
2. The parti — the big idea behind the work
In architecture, a parti is the central organising idea behind a building. A simple concept that guides everything. Products need that too.
When there is no clear organising idea, decisions become fragmented, teams debate surface details, and features pile up without cohesion.
A strong core idea aligns design, product and engineering. It makes tradeoffs clearer. It reduces tension, because people understand what we are optimising for. Clarity builds trust internally, and clarity shows up externally in the product.
3. If you're nervous, it probably matters
Katie described the inner voice that shows up before a big presentation — the one telling you that you don't want to do this, that you're nervous, and that being nervous is exactly why you have to.
Sometimes nervousness is a signal of importance. Creative work is vulnerable work. Sharing unfinished ideas. Challenging decisions. Presenting in front of peers. Those moments feel uncomfortable because they matter.
Instead of avoiding them, we can read that discomfort as growth. The work that pushes us often becomes the work that moves the product forward. Supporting each other through those moments builds trust inside the team.
4. Trust inside teams is built through transparency
When Katie joined Airbnb, she moved quickly to change things and immediately faced pushback. The issue wasn't competence. It was trust.
What changed the situation was transparency: explaining what she was observing, sharing why she believed change was needed, making her reasoning visible.
The lesson applies to all of us. If we want alignment across design, product and engineering, we have to make our thinking visible. Not just our final mockups, but what problem we're solving, what tradeoffs we considered, and why we made certain calls.
Trust inside a company doesn't come from perfect Figma files. It comes from shared understanding.
5. Trust with users is fragile
Product design impacts real lives. Trust with users is cumulative, but it can break instantly. If a product causes harm, confusion or doubt even once, the relationship changes — even if everything works perfectly afterwards.
Katie frames quality in a clear order. Solve the right problem. Make it usable. Make it beautiful.
Aesthetic quality is not decoration. It signals care. Care signals respect. Respect builds trust. When something feels sloppy, people hesitate. When something feels intentional, they relax.
Think about flying again. You trust the control system because it feels carefully designed. Thoughtful. Precise. Products are the same. Users feel when something is built with care.
6. Designers have influence when they're present
Designers gain influence not by asserting it, but by being part of the conversations where decisions are made.
When we're involved early — understanding constraints, technical realities and business goals — our perspective carries more weight. Shared goals reduce friction. Trust grows when we show we are invested in the whole product, not just the interface.
7. What this means for us
If we want to build products people trust, and a culture people enjoy working in: focus deeply on craft, anchor the work to a clear central idea, step toward discomfort when it matters, make our thinking visible, and treat quality as a signal of care.
Trust takes time to build and seconds to lose.
Design is not just about solving problems. It shapes how people feel. It shapes whether they trust what we build. And it shapes whether we trust each other while building it.
That responsibility is real, and it's worth taking seriously.