My leadership principles

4 min read

My leadership principles

4 min read

My leadership principles

My leadership principles

POV

My leadership principles are not posters. They’re defaults I return to when the work gets messy: timelines tighten, opinions clash, and information is incomplete. Over time, I’ve learned that teams don’t need a hero. They need clarity, trust, and a quality bar they can rely on.


An example from my CLM work (signature workflows)

In our Contract workflow's signature workstream, we hit a moment where everyone had a valid perspective, and still nothing was moving. Design leadership had a clear point of view. The designer had another. I had my own take as the design manager owning the space. Product had a different read based on release pressure and workflow expectations. The conversation was heated, it spilled across channels and meetings, and it stayed unresolved longer than it should have for in-flight release work.

The core issue sat inside a self-serve contract request flow, where any employee could raise a request and get it executed without involving specialists. The happy path was solid. The roadblock appeared in corner cases: when additional documents were required midstream, or when signatories had to change for an unforeseen reason. The debate wasn’t about whether these situations mattered, it was about how to keep the requester moving while making the extra steps visible, easy to act on, and context-rich, without turning the flow into a confusing checklist or sending users into dead ends.

At some point, it became clear we weren’t disagreeing because people were careless. We were disagreeing because each function was operating with a different version of truth about what users would notice, interpret, and do next. So I stepped in to change the shape of the conversation. I mapped the tradeoffs explicitly and asked a simple question: can we settle this with rapid evidence instead of more debate? Fortunately, we could. The scenario was testable with generic users.

We pulled in our researcher, wrote a crisp brief, and aligned the central design approval team on an iterative testing plan with a revised sign-off date tied to results. We took a one-week buffer, ran the testing, and came back with a decision that was informed, defensible, and calm. The debate didn’t end because someone won. It ended because the team aligned around shared evidence and a clear path forward for the release.

Tradeoffs I default to (in real moments)

  1. If alignment stalls, I change the input. I move the room from opinions to evidence.

  2. If we’re debating solutions too early, I pull us back to a real user scenario.

  3. If speed conflicts with confidence, I buy clarity by trading scope or timeline.

  4. If the team is holding multiple versions of truth, I make the tradeoffs explicit.

  5. If the work is high-stakes, decisions get written down with intent and a clear owner.

  6. If the room changes, I change the story, not the truth.


Principles underneath

  • People first: Trust and safety before speed.

  • Clarity over control: Align on outcomes and decision rights, then empower.

  • Quality is trust: Build for messy reality, not demos.

  • Ownership is built: Clear boundaries plus real support.

  • Strong opinions, loosely held: Push a POV, change fast with evidence.

  • Match the story to the room: Same truth, different altitude.


What you can expect from me

Direct feedback, delivered with care. A high bar without heaviness. Clear ownership and fewer surprises. Calm when things get tense, action when things get stuck.

Contents

Role

UX & UI

Branding

Product Strategy

Website Development

Team

Duration and date

2 Months

December - November 2023

Role

UX & UI

Branding

Product Strategy

Website Development

Team

Duration and date

2 Months

December - November 2023