Blogs / Building Trust Through Five Clear Expectations
Building Trust Through Five Clear Expectations

Design, Extractives · 5 min read

Building Trust Through Five Clear Expectations

How shared expectations help designers work with autonomy, responsibility, and a clearer sense of purpose. Written by Fas Lebbie

Earlier in my leadership career, I sometimes assumed that hiring sharp people, giving them interesting problems, and mostly staying out of their way would be enough. Some designers flourished with that freedom. Others needed more context, clearer feedback, or a stronger connection between their work and the decisions around them.

Over time, I’ve distilled those experiences into five expectations I establish, discuss, and revisit with designers. Their application changes as I understand the person, the team, and the organization. They’re less about rules than shared understanding: knowing what we can expect from one another, where judgment is needed, and when to ask for support.

When people understand the principles guiding their work, they can exercise judgment without constantly seeking permission or direction.

That clarity gives trust something practical to grow from.

Know How You Work Best (and Tell Me)

Start with the person, not the process.

I use a simple Working Style sheet: nothing fancy, just questions about when you think deepest, how you like feedback, what drains you, and what lights you up. The answers are a starting point, not a permanent description of how someone works.

One example from this practice involved a designer whose weekly syncs were interrupting her momentum. We adjusted the cadence to protect longer, uninterrupted mornings, giving her more room to focus and move her work forward. The useful question wasn’t whether weekly syncs were good or bad, but whether the arrangement helped her do good work.

When you can tell me what helps you contribute and where you need support, I can make more thoughtful decisions about collaboration, feedback, and team balance. These conversations have helped me recognize difficulties that a performance review alone might miss.

Own the Full Wake of Your Decisions

Your work keeps living in the world long after you ship it. Stay awake to what it’s doing.

Notice when a pattern quietly shifts power, creates friction for certain users, or locks in a behavior we may regret later. Bring it forward. Those observations are where real strategic thinking begins.

I’ve seen designers recognize second-order effects that prompted teams to reconsider roadmap priorities. That requires room to raise an uncomfortable concern: something we built may no longer be working as we intended.

Owning the wake doesn’t mean controlling every consequence.

It means paying attention, making concerns visible, and helping the people with the relevant authority understand what needs addressing. Trust matters here because responsibility becomes hollow if people are expected to notice problems but discouraged from naming them.

Protect Deep Work While Staying in the Conversation

Great design needs both solitude and collision. Guard the first, show up fully for the second.

Block real thinking time without guilt: turn off Slack, close the door, whatever helps. Make that time visible so others know when you’re available and how to reach you when something genuinely needs attention.

At the same time, when it’s time for crit, a sync, or helping a teammate unblock, be there, prepared, and generous.

The balance needs discussion, not guesswork. In teams I’ve led, trust has grown when people could rely on one another without expecting constant availability. The rhythm feels almost biological: inhale alone, exhale together.

Always Know How Your Work Moves the Company

Never let your designs be the best-kept secret in the building.

I ask designers to stay curious about how their work contributes, even when the effects aren’t immediately measurable. Once a month, surface one clear example: adoption, fewer support requests, revenue contribution, or something important learned about a user’s needs. Turn it into a short story you can tell upward or sideways.

I’ve seen a clear account of design’s contribution change a planning conversation.

The point isn’t to claim sole credit for a result.

It’s to explain what changed, what you contributed, and what remains uncertain.

That takes access to relevant information and conversations. Where that access is missing, raise the gap rather than manufacture a success story. This habit makes design’s contribution more visible and helps you avoid waking up one day to realize you’ve been decorating someone else’s strategy.

Build Real Relationships Across the Org

Design is always a collaboration within complicated systems.

Make time for your key product, engineering, research, and marketing partners, whether through coffee or a focused 20-minute conversation. Learn with genuine curiosity what keeps them up at night. Show early work, ask basic questions, and give people context before they need it.

Over time, those relationships become the hidden rails that let good design actually ship. People can question an idea earlier, explain a constraint more honestly, or bring you into a decision before it hardens.

I’ve seen designers gain a stronger voice as colleagues came to understand their thinking and judgment. Relationships don’t remove structural barriers, but they can create more opportunities to work through them together.

Laying Foundations for Great Design Work

These expectations need organizational room to work: access to information, appropriate authority, support, and opportunities to raise concerns. They cannot compensate on their own for conditions that consistently undermine them.

I hold them as a foundation, not a fixed test. Some need more attention at different moments; their application should change with the people and the work.

The point isn’t compliance; it’s shared clarity.

Trust grows when we can discuss what we expect, recognize what makes those expectations possible, and adjust when the arrangement no longer serves the work.