Module 3 of 12 · 8 min read
Personal Leadership Presence
Practical routines to speak up, disagree well, propose instead of report, and become visible, in a way that fits your personality.
Why it matters
Many designers who step into a lead role recognise themselves in at least one of these: some shyness, hesitation to take up space in meetings, a wish to be more proactive, or discomfort voicing disagreement. None of that is a disqualifier. Many excellent design leaders are introverts. But leadership requires visibility: people need to hear your direction to follow it. A great idea that stays in your head, or in a file nobody opens, does not lead anyone.
This module is about building presence in a way that fits who you are. It is not about becoming someone else.
Common pitfalls
- Waiting for the perfect moment to speak, which never comes.
- Reporting problems without proposals, so others decide what to do about them.
- Disagreeing too late, after the decision, when it costs the most.
- Copying a loud leader's style that doesn't fit you, and looking uncomfortable doing it.
1. Reframe: introversion is a leadership style, not a deficit
Strengths of quieter leaders (Susan Cain, Quiet; Adam Grant's research):
- They listen, so proactive teams feel heard and contribute more.
- They prepare, which leads to better-quality proposals.
- They prefer written communication, which suits distributed teams.
- They build deep 1:1 relationships, which is how influence works anyway.
If you are a quieter person, your goal isn't to become loud. It's to make sure your perspective is reliably present when decisions are made. If you are naturally outgoing, the same section applies the other way: make room for the quieter people around you, because their preparation and listening are an asset to your team.
2. Proactivity: from contributor to initiator
The "propose, don't just report" habit
Every time you notice a problem, bring:
- The problem (with evidence)
- Why it matters
- Your proposed solution (even a rough one)
- What you need
"The table components are inconsistent across products." "I found 4 different table filter patterns across 3 apps. It costs devs rework and confuses users who switch between apps. I propose we standardise on one in the next design-system release; I can draft it with the product designers. I'd need 2 hours from each of them."
Weekly proactivity ritual (15 min, Friday)
- What did I notice this week that nobody's addressing?
- What one thing will I propose next week?
- Whom do I need to talk to first?
3. Speaking up in meetings
Before
- Know your one point. Write the one thing you want to contribute before the meeting.
- Pre-meet key people (module 10), so you're not the only voice in the room.
- Ask for agenda time for your topic instead of hoping for an opening.
During
- Speak in the first 10 minutes. The longer you wait, the harder it gets. Even a question counts.
- Use bridging phrases:
- "Building on what [name] said…"
- "Can I add a user perspective here?"
- "I'd like to raise a risk before we decide."
- "I see it differently, and here's why."
- "Before we move on, can we be clear on who decides this?"
- Name the disagreement kindly: "I disagree, and I may be wrong. My concern is…"
After
- Follow up in writing: summary, decision, next steps. It turns presence into ownership.
4. Healthy disagreement
A solid basic approach: understand the other person's reasoning first, explain your concerns, support them with evidence, and find a solution together. Add:
- Disagree early. Disagreeing after a decision is much more expensive.
- Separate the idea from the person.
- Strong opinions, loosely held. State your view clearly, change it with evidence.
- Disagree and commit. Once decided, support it, and agree how you'll know if it was right.
Practice script
"I want to flag a concern before we commit. If we remove the confirmation step on bulk cancel, we risk accidental cancellations. With ~X bulk actions a day, even 1% is a lot of rework. Could we keep an undo instead? That keeps it fast and safe."
5. Executive presence (the learnable parts)
| Element | Practice |
|---|---|
| Clarity | Lead with the point (BLUF). Max 3 points. |
| Brevity | Prepare a 30-second and a 2-minute version of every idea. |
| Composure | Pause before answering. "Good question, let me think." Silence reads as confidence. |
| Ownership | "I recommend…" instead of "Maybe we could possibly…" |
| Language | Remove hedges: just, sort of, I think maybe, sorry but. |
| Body/voice (video calls) | Camera at eye level, good light, slower pace, pause at key points. |
6. Communicating across languages and cultures
Many leads work in a language that isn't their first, or with colleagues from many cultures. Both are normal in international teams.
If you lead in a second language
- Short sentences. Simple words. Clarity beats eloquence.
- Prepare key phrases for recurring situations: feedback, disagreement, saying no, closing a meeting (see modules 04 and 10).
- Rehearse out loud and record yourself. Watch once, fix one thing, repeat.
Across cultures
- Cultures differ in how direct feedback is, how decisions are made, and how much structure and preparation people expect. Erin Meyer's The Culture Map is a practical guide to these differences.
- In cultures that value directness, structure and preparation, be clear, factual and well-structured, and don't over-soften. If you are a quieter person, this can help: directness is expected there, not rude.
- In cultures where feedback is more indirect, soften the delivery and use 1:1 settings more, but keep the message itself clear.
- When unsure, ask: "How do you prefer to get feedback: directly in the meeting, or afterwards?"
7. Visibility through writing
Writing is the quiet leader's amplifier, and it works for everyone in distributed teams.
- Monthly UX update (½ page): what shipped, what we learned, what's next, a shout-out.
- Decision memos for important proposals (context, options, recommendation).
- Internal blog / chat-channel posts: "How we moved our team to a new design tool," "5 table patterns we standardised."
- Present at an internal forum once a quarter (start small: your design team or guild, then a wider product or tech forum).
8. Confidence & managing the inner critic
- Impostor feelings are normal for new leads. Treat them as evidence you're stretching, not that you're unqualified.
- Leadership log (template in the Learning plan): write 3 wins every week. Re-read it before important conversations.
- Small exposures: confidence comes after action, not before. Use the stretch ladder below.
Stretch ladder (do one rung per 1–2 weeks)
- Ask one question in a cross-team meeting.
- Share one proactive proposal in writing.
- Facilitate a 30-min team session.
- Disagree (kindly) in a meeting with evidence.
- Present a 10-min topic to a wider audience.
- Lead a stakeholder workshop.
- Present a UX strategy to senior management.
9. Practice
Evidence to collect
Keep proof in your Leadership log:
- Your stretch-ladder rungs, with dates and what happened.
- One proposal you made unprompted, and its outcome.
- One written update or memo that people responded to.
Read / watch
Library → Presence & communication: Quiet (Cain) and her TED talk, The Pyramid Principle (Minto) / BLUF, Crucial Conversations, Amy Cuddy-style presence talks (with caveats), Julie Zhuo on communication.
Talking about it
- With your manager: say which rung of the stretch ladder you're on, and ask for one opportunity to climb the next one, e.g. "Could I present the design-system update at the next product review?" Managers can only open doors they know you want.
- With a trusted colleague: ask them to watch for one thing in a meeting ("Did I speak in the first 10 minutes? Did I hedge?"). Specific requests get useful answers.
- In a promotion or hiring conversation: if presence is one of your development areas, say so, and show the system: "I'm naturally quiet, so I prepare one point per meeting, pre-meet the key people and follow up in writing. In the last quarter I moved from asking questions to running our cross-team critique." A clear routine is more convincing than a claim of confidence.
Check yourself
Answer out loud, then open the section to compare.
- What's your weekly "propose, don't just report" habit? → answer
- How do you prepare to voice disagreement? → answer
- Which stretch-ladder rung is next for you? → answer
Connections
← Module 2: The Role Shift · Learning path · Module 4: People Leadership →
Related
- Module 11: Workshop Techniques: facilitation, including tips for quieter leads
- Module 10: Stakeholders, Influence & Change: the pre-meeting technique
- Module 4: People Leadership: avoid ruinous empathy
- Module 1: Self-Assessment: score your presence and proactivity (area G)
- 12-Month Learning Plan: weekly proactivity & leadership log
Hubs: Frameworks index