You don’t need “Lead” or “Principal” or “Director” in your title to have real influence on a product team…or any design team for that matter.

Some of the most impactful designers I’ve worked with weren’t the loudest voices in the room. They didn’t manage teams or run the big meetings. They just showed up, consistently delivered, and made the people and products around them better. No drama. No title inflation. Just influence, earned quietly and used deliberately.

This post is for the designers who are sitting at that mid-to-senior IC level and asking themselves:

“What does growth look like if I don’t want to manage people?”

“How do I lead without a title?”

The answer: you already can, and probably already are. But the kind of leadership that gets you noticed in this space isn’t loud. It’s strategic, relational, earned, and not assigned.

As a slight aside … Years ago I worked with one of the most amazing QA engineers in my career, I often wondered why she didn’t take on management roles and stayed an IC. The answer was that she didn’t see the need for the title, through her work and actions she naturally became the leader of whatever team she was on. The same can be said for any discipline.

You’re Not Just Responsible for the Work Anymore

Early in your career, your job is to execute well. Ship clean, thoughtful work. Take feedback, and improve your craft.

But as you move into senior IC territory, the job changes. You’re still responsible for your own work, but you’re also expected to:

• Raise the quality of the overall design system or product experience
• Create clarity in fuzzy or undefined spaces
• Anticipate and address problems before they happen
• Help level up other designers, whether they report to you or not

In short, your impact shifts from what you make to what you enable. And that’s where influence starts to show up.

Real Influence Doesn’t Come From Org Charts

Titles can open doors, but they don’t build trust. If you want to lead as a senior IC, the work starts with relationships.

This kind of leadership looks like:

• Looping product managers into early sketches, not waiting for a feature brief
• Helping engineers identify edge cases before they write a line of code (I love this one)
• Coaching a junior designer through a tough review or stakeholder negotiation
• Reframing a vague business request into something that’s actually user-centered

None of this gets you a line item on the roadmap. But it builds equity … the kind that turns into influence over time.

Listen First, Speak Thoughtfully, Elevate the Room

As a younger designer, I thought leadership meant being the one with the best idea. Now I know better.

Some of the most trusted designers I’ve worked with are the ones who speak less but ask better questions. They don’t dominate the room … they become a part of the conversation and they elevate it. They write the strategy doc no one asked for. They say, “Here’s what I think we’re missing.” They give credit freely and absorb blame when things go sideways.

That kind of leadership creates gravity. People start bringing you in earlier because they want your input, and they listen when you speak.

Draw the Map Before Anyone Asks

One trait I see in standout designers: they don’t wait for permission to start exploring.

They sketch where the product could go next. They run that early, scrappy usability test before engineering is involved. They define principles or patterns that make life easier for the rest of the team.

This isn’t about overstepping(although I get it, some “leaders” see it that way) … it’s about proactively shaping the future, not just reacting to it. When you start thinking like this, you’re already leading.

Growth Doesn’t Only Mean “Up”

A lot of designers hit the senior level and assume the only path forward is management. Sometimes that’s true … especially if you love coaching and team-building … or perhaps the business side of things. But it’s not the only route.

Staying on the IC track can mean more depth, more craft, and more direct impact on the product. It can also mean less people management overhead and fewer political landmines.

The key is knowing what you want. What kind of problems energize you? What kind of impact do you want to have? And are you building toward that intentionally? And so many other questions for self reflection.

Final Thought

Quiet influence is still influence. And in many teams, it’s the kind that actually moves things forward.

If you’re a senior IC or on your way there, don’t underestimate the power of showing up with intention, clarity, and curiosity. You might not have the title, and you might not manage the team. But if you help others succeed, raising the bar for the work, and make the product stronger, well … you’re already leading.

So keep going.

Until the next volume, thanks for joining me. 
- Andrew Preble