Most designers think promotions happen because of ideas — strong opinions, taste, visibility, and the ability to articulate what others can’t yet see. Those things matter in a design career, but they stop being the deciding factor sooner than most people expect, because senior roles are less about contribution and more about stability.

At higher levels, organizations don’t promote you because you’re clever. They promote you because the system feels more reliable when you’re involved. Decisions get made with fewer unintended consequences. Teams don’t get whiplash as often. Executives don’t feel surprised by realities they should have understood earlier. That reliability isn’t about certainty. It’s about containment.

Table of Contents:
The Misunderstanding That Stalls Careers
The Design Leader as Shock Absorber
Risk Doesn’t Disappear — It Moves
Why This Work Is So Often Overlooked
Promotion Is About Reducing Cognitive Load
The Three Directions Risk Flows
Why This Determines Who Advances

The Misunderstanding That Stalls Careers

Designers learn to reduce friction for users by confronting what’s actually causing it. You don’t just polish the interface — you identify the bottleneck, remove the obstacle, and simplify the path. That “root cause” mindset is the most critical core skill a designer can possess.

The shift into leadership is not abandoning that mindset. It’s applying it to a different kind of friction: the organizational friction that prevents good work from happening in the first place. Misaligned stakeholders, unclear ownership, late-stage surprises, brittle processes, and decision avoidance all create “user friction” too — the user just happens to be the organization.

At senior levels, leaders are valued for their ability to remove those constraints without destabilizing everything around them. They surface the right problems, but they also control the blast radius: how urgency is communicated, how conflict is handled, how trade-offs are made, and how decisions stick. That’s what creates sustainable outcomes.

The Design Leader as Shock Absorber

A metaphor I’ve found useful is the design leader as a kind of shock absorber in the organization. Not because leaders eliminate uncertainty — they don’t — but because they reduce how violently uncertainty moves through the system. In any organization, there’s constant force: shifting priorities, incomplete information, cross-functional tension, and real human stress. Someone has to regulate how that pressure travels, or it simply passes to the most vulnerable point.

When that function is working, it often looks unremarkable from the outside. People stay oriented. Problems are handled before they become public drama. Teams keep doing real work instead of spending their energy bracing for the next surprise. When it’s not working, everything feels brittle, even if no one can immediately name the cause.

Risk Doesn’t Disappear — It Moves

One of the most dangerous illusions in organizations is believing risk can be eliminated. It can’t. It can only be managed — contained, translated, or displaced.

When leaders don’t absorb risk at their level, it shows up somewhere else, usually in ways that are more expensive. Teams absorb it as burnout, anxiety, or silence. Partners absorb it as missed expectations and blame. Executives absorb it as surprise, reactive decisions, and loss of trust. None of those outcomes help the business, and they rarely help the careers of the people caught in the blast radius.

The leaders who advance aren’t the ones who escalate volatility. They prevent it from spreading. Often quietly. Often without credit.

Why This Work Is So Often Overlooked

Risk management doesn’t always read as “leadership” in the way people expect leadership to look. It’s not charismatic. It doesn’t produce a portfolio artifact. It rarely creates a clean story for a performance review.

More often, it looks like steadiness when a situation could easily become emotional. It looks like issues being handled early, while they’re still solvable. It looks like fewer surprises — not because nothing goes wrong, but because someone is paying attention to the right signals and addressing them before they harden into crises.

Many designers do this work instinctively, without realizing it’s one of the main things senior leaders pay attention to when deciding who gets more responsibility. Others avoid it, because it feels like “politics,” or because they assume it’s outside their role. In practice, it’s one of the clearest indicators of readiness for leadership.

Promotion Is About Reducing Cognitive Load

Executives live under constraint: too many decisions, not enough context, constant second-order consequences. They promote people who make that environment easier to operate within — not by hiding problems, but by making complexity manageable.

This is where a lot of “reporting” conversations go wrong. Data doesn’t reduce risk on its own. Interpretation does. Leaders earn trust by surfacing the right problems early, framing them accurately, and preventing leadership from being surprised by outcomes they’ll be held responsible for.

At senior levels, being “right” is less important than being steady. Trust tends to form around the people who consistently reduce uncertainty and prevent avoidable chaos.

The Three Directions Risk Flows

Most leadership risk flows in three directions, and each requires a different kind of containment.

Downward: People risk. Pressure, urgency, and ambiguity tend to travel downhill. When leaders pass it through unfiltered, teams become reactive, guarded, or exhausted. When leaders absorb it and respond with clarity, teams can focus and make better decisions. This isn’t about avoiding hard truths — it’s about preventing emotional volatility from becoming systemic damage.

Across: Execution risk. As you move up, work increasingly happens across boundaries: agencies, vendors, partners, adjacent teams, and dependencies. Leaders own outcomes even when they don’t control every input. They close accountability gaps early, align expectations before they become conflict, and prevent external uncertainty from turning into internal dysfunction.

Upward: Narrative risk. Executives don’t experience the work directly; they experience representations of it — dashboards, summaries, narratives, and interpretations. Leaders don’t just report reality. They translate it in a way that supports good decisions, avoids false confidence, and prevents unnecessary alarm. Bad framing creates bad decisions, even when the numbers are technically accurate.

Why This Determines Who Advances

Designers sometimes ask why someone with “less talent” gets promoted. The uncomfortable answer is often simple: that person makes the organization feel safer. They handle uncertainty without broadcasting it. They reduce volatility instead of amplifying it. They keep problems from spreading before anyone has to clean up the mess.

It’s the literal definition of “manager”: they don’t wait for authority to do this work. They practice it long before their title changes.

What Comes Next

Over the next few articles, I’ll break this down into three focused pieces:

• How design leaders absorb pressure downward so teams can function without burning out

• How they own outcomes across boundaries they don’t fully control

• How they translate reality upward to protect trust and decision quality

If you’re aiming for leadership, this is work worth practicing now — not because it’s glamorous, but because it’s what organizations quietly rely on when the stakes rise.

Enjoyed this piece?

I write articles for designers and design leaders who want to grow their impact, lead with clarity, and build careers that actually feel sustainable.

Share

Most designers reach a point where mastery of the craft is no longer enough. You’ve developed sharp instincts, you deliver reliably, and people come to you with questions that reach beyond the visuals. It’s a sign that leadership is calling — even if no one’s offered you the title yet.

But how do you prepare for that next step? The path from designer to design leader is rarely clear, and even less often explained. This roadmap is meant to change that — not through platitudes or corporate jargon, but through the habits and mindset shifts that help you grow into the kind of leader others trust.

Table of Contents
Redefine What “Leadership” Means in Design
Strengthen the Core Skills That Earn Trust
Build Systems Thinking Into Your Craft
Learn to Manage Up and Across
Recognize the Signals That You’re Ready for Management
Prepare for the Emotional Shift of Leadership
Continue Leading Before You’re Promoted
Expand Your Definition of Success

1. Redefine What “Leadership” Means in Design

Leadership doesn’t begin with a promotion. It begins when others start looking to you for clarity.

Many designers treat leadership like a noun — a title, a department, a group you eventually join. But leadership works better as a verb. It’s something you do: stepping up when clarity is missing, taking ownership of problems beyond your day-to-day, and helping others move forward.

In design, leadership is less about managing people and more about managing context — helping others see the constraints, options, and trade-offs that shape the work. Great leaders create clarity where none exists. They don’t make all the decisions; they make decisions easier for others.

You can practice this today. Lead the next critique, organize the chaos of a hand-off, or summarize stakeholder feedback in a way that keeps the team moving forward. These are the early reps that build trust long before titles do.

Read: The Invisible Promotion →

2. Strengthen the Core Skills That Earn Trust

Communicate Design Decisions with Clarity

As you move toward leadership, your influence depends on how clearly you connect design rationale to business and user outcomes.

When explaining your work, start with what’s true for the user, then bridge to what’s valuable for the business. Avoid defensive language (“I think,” “we liked”) and replace it with directional framing (“Users need clarity here, so we tested…”). Communication is the moment where design becomes shared understanding.

When your explanations link user insight to business impact, your voice naturally shifts from defending design decisions to influencing strategy.

Read: Negotiation & Consent Culture →

Read: Transparency Isn’t Optional →

Practice Decision Velocity

Teams follow designers who reduce friction, not those who add to it.

Decision Velocity means making small, reversible choices quickly instead of waiting for certainty. It’s about progress with feedback instead of perfection by committee.

When you model that behavior, others mirror it. Projects move faster, and your reputation grows as someone who keeps momentum alive. That’s what leadership looks like in practice.

Read: Decision Velocity →

Cultivate Team Awareness

Individual skill will get you recognized; building bridges will get you promoted.

Pay attention to how people around you work — who’s overloaded, who’s stuck, where communication breaks down. Leadership is as much about sensing the health of a team as it is about improving the product.

When you help others anticipate blockers or translate feedback across roles, you become a force of alignment. Designers sit between stakeholders and engineers, strategy and execution, business and customers — don’t forward emails, add value to the conversation.

Read: Invisible Skills That Make or Break Design Careers →

3. Build Systems Thinking Into Your Craft

Every growing designer hits the same wall: you stop being evaluated only on your own work. What matters next is how your decisions scale.

Systems thinking means zooming out — seeing your design not just as an artifact but as part of a living ecosystem of code, content, and customer behavior.

When you connect design choices to business outcomes (conversion, retention, satisfaction), you bridge the gap between design and strategy. That’s how you shift from “designer who delivers” to “leader who steers.”

Read: Proving the Value of Brand Expression →

Read: The Design Leadership Pipeline Challenge →

4. Learn to Manage Up and Across

As you rise, your ability to influence without authority becomes essential.

Managing up is about helping your manager see what’s coming — surfacing risks early, clarifying trade-offs, and proposing solutions instead of problems. Managing across means translating priorities with product, engineering, and marketing partners.

The designers who grow fastest are the ones who make collaboration feel easy. They anticipate confusion and reduce it. They use empathy as a strategic skill, not just a personal trait.

Read: Managing Up for Designers →

Read: Transparency Isn’t Optional →

5. Recognize the Signals That You’re Ready for Management

Leadership readiness isn’t a checklist — it’s a shift in perspective. But a few reliable signals often appear first:

You’re Already Being Asked for Direction

Colleagues come to you for feedback, context, or clarity — even when it’s not “your” project. It’s the purest indicator that people trust your judgment.

You’re Thinking in “We” More Than “I”

You start measuring success by team outcomes instead of individual wins. The lens widens; the ego quiets.

You’re Building Others’ Confidence

You notice how your encouragement or clarity lifts someone else’s work. You start designing less for users and more for the designers serving them.

Leadership begins here — not with a promotion, but with practice.

Read: Core Skills from Team Sports →

Read: Build Your Career →

6. Prepare for the Emotional Shift of Leadership

Management doesn’t simply add responsibility; it reshapes identity.

Suddenly your success depends on how others perform. Your day fragments into one-on-ones, feedback sessions, and cross-team negotiations. You’ll spend more time creating conditions for good design than making it yourself.

That shift can feel disorienting. Many new managers grieve the loss of deep craft time — and the comfort of being one of the team. The tone of conversations changes, the jokes land differently, and the distance can surprise you. But leadership offers a different kind of creative satisfaction — designing systems of trust, growth, and accountability.

To stay balanced, practice the mindset of anti-fragility: treat every challenge, misstep, or miscommunication as fuel for growth. The goal isn’t avoiding stress but using it to expand your capacity and resilience.

Read: The Anti-Fragile Design Career →

Read: From Burnout to Boundaries →

7. Continue Leading Before You’re Promoted

The surest path to leadership is acting like one before it’s official.

Volunteer to mentor junior designers. Facilitate retrospectives or project kick-offs. Document learnings and share them in team channels. These small acts establish you as someone who uplifts others and builds clarity.

Then, when the opportunity arises, you’re not asking for a chance to lead — you’re already doing it. The title simply catches up.

Read: The Invisible Promotion →

8. Expand Your Definition of Success

As a design leader, your impact shifts from creating things to creating conditions.

You start measuring success not by how polished your work looks, but by how effectively your team operates. Did you unblock decisions? Build trust? Increase confidence? These are the less visible metrics that drive lasting design maturity.

That’s how you stay a designer at heart, even as your tools change from Figma to feedback, from prototypes to people.

Read: Stretch Goals Aren’t About the Work →

Read: Mastering the Art of Adaptation →

Closing Reflection

The move from designer to design leader isn’t a leap, it’s steps along a path; a gradual expansion of perspective.

Every conversation, critique, and collaboration becomes part of the training. You don’t stop designing — you start designing the environment where great design can happen.

Enjoyed this piece?

I write weekly articles for designers and design leaders who want to grow their impact, lead with clarity, and build careers that actually feel sustainable.

Subscribe now

It usually starts like this:

A designer presents a homepage refresh. The dev lead points out that the animation will tank performance. The marketing stakeholder insists the hero needs more “energy.” The deadline’s already circled on the calendar.

Everyone’s technically right — and no one’s aligned. What happens next often determines how the project feels for weeks. Does it turn into silent frustration and Slack sidebars, or does it become a quick, clear, “let’s find something safe to try” decision?

That difference isn’t about process or authority.

It’s about negotiation and consent — two skills designers rarely get formal training in but use every day.

Table of Contents
Negotiation Happens Constantly in Design Work
Consent vs. Consensus (and Why It Matters)
Scenario 1: Designer : Developer
Scenario 2: Designer : Stakeholder
Scenario 3: Negotiating Within the Team
How to Practice Negotiation and Consent Daily
Why This Matters for Career Growth
What Changes When Teams Adopt Consent Culture

Negotiation Happens Constantly in Design Work

We imagine negotiation as high-stakes table talk: salary reviews, client contracts, business deals. But in design and development, it’s a daily habit.

Every time you balance user needs against deadlines, advocate for accessibility over aesthetics, or try to merge five stakeholder opinions into one direction, you’re negotiating.

The skill isn’t about getting your way — it’s about creating shared clarity so progress doesn’t stall.

(If you’ve read Decision Velocity, you’ll recognize this pattern.)

Negotiation in creative work means naming the trade-offs out loud and choosing together what’s “good enough for now, safe enough to try.”

That’s where consent culture comes in.

Consent vs. Consensus (and Why It Matters)

Most teams default to consensus — everyone must agree before moving forward.

That sounds collaborative and democratic, but in practice it slows everything down.

Consent means you move ahead as long as no one has a material objection.

Not “I don’t love it,” but “this will cause real harm.”

It’s a principle borrowed from sociocracy and open-source governance, and it works beautifully in product teams. Consent gives people a voice without giving every opinion veto power. It moves decisions from “endless alignment” to “informed momentum.”

Scenario 1: Designer : Developer

Negotiating craft vs. constraints

Let’s go back to the “energetic” homepage concept that includes looping background video to create emotional impact.

The developer flags performance concerns.

Old pattern:

• You dig in to defend the design.

• They cite load time impact.

• Both sides feel unheard.

Consent-based negotiation looks different:

“Is there a material objection if we ship this as a short test? If it fails Core Web Vitals, we’ll revert.”

You’re not ignoring performance — you’re framing it as a shared experiment.

That mindset honors both sides’ goals: design finesse and performance reliability.

You can also ground the conversation in evidence rather than ego — for example, referring to Proving the Value of Brand Expression methodology to measure inspiration and performance together.

The result isn’t compromise for compromise’s sake — it’s forward motion without resentment.

Scenario 2: Designer : Stakeholder

Negotiating expectations and outcomes

A marketing director wants a more “premium” checkout flow before a big campaign.

You know the team’s bandwidth is limited, and pushing major design updates into production this late could risk stability.

Instead of defaulting to “we can’t,” negotiate what premium actually means.

“If premium means confidence and polish, we could focus on micro-interactions and error states instead of a full redesign.”

You’re reframing abstract preference into measurable outcomes — turning taste into intent. You’re translating leadership language (“premium,” “impact,” “confidence”) into actionable design trade-offs.

Consent culture adds one more layer:

“Does anyone have a strong objection to testing these smaller improvements first?”

You make progress, preserve trust, and keep the door open for future iteration.

Scenario 3: Negotiating Within the Team

Balancing autonomy, critique, and pace.

Internal alignment is where negotiation often gets sloppy — not out of malice, but fatigue. Teams over-discuss because they care.

When rounds of feedback spiral, consent helps teams decide when “good enough” truly flies.

You can even script it:

“Do we have any material objections to moving forward with Option B this sprint? If not, we’ll ship it and review outcomes next retro.”

This phrasing short-circuits the perfection trap. As I wrote about in Stretch Goals Aren’t About the Work, it frames progress as learning rather than flawless delivery.

The key is documentation. Once a decision is made, log it. It closes loops and prevents old debates from reopening.

How to Practice Negotiation and Consent Daily

1. Name the decision before debating.

“What decision are we here to make?”

That single sentence transforms most meetings.

2. Ask clarifying questions instead of defending.

“What outcome are you optimizing for?”

“Is this a preference or a blocker?”

3. Summarize shared goals aloud.

Repetition signals alignment: “We all want a smoother checkout — we just differ on how.”

4. Offer reversible next steps.

Frame experiments with built-in exit ramps: “Let’s try this for two weeks; we’ll roll back if metrics dip.”

5. Document the decision and why.

Even a quick Jira or Figma comment: “No major objections → Option B → revisit after sprint.”

It sounds trivial until you need to remember what everyone agreed to.

Why This Matters for Career Growth

Negotiation and consent don’t just make projects run better — they shape how people experience working with you. You become the person who can navigate conflict calmly, keep projects on track, and make collaboration feel lighter.

That’s a leadership skill that builds trust and credibility — skills no one puts in a portfolio, but everyone remembers. When teams know you’ll hear them, not bulldoze them, you gain respect and authority.

What Changes When Teams Adopt Consent Culture

• Meetings shrink. You focus on decisions, not opinions.

• Tension drops. People feel heard before being overruled.

• Design and development trust each other more. You share accountability for risk.

• Leaders relax. They see consistent progress instead of surprise escalations.

This combination of structure plus empathy connects to one of Design Leadership’s core themes:

Transparency isn’t optional — it’s the foundation of trust.

Consent culture is transparency in action.

Closing Thought

Design and development thrive on negotiation. But the healthiest teams don’t treat it as a tug-of-war — they treat it as a dance. Each side gives, listens, and adjusts. The rhythm is built on respect, not authority.

When you replace consensus with consent, and defensiveness with curiosity, decisions stop feeling like battles and start feeling like momentum.

Enjoyed this piece?

I write weekly articles for designers and design leaders who want to grow their impact, lead with clarity, and build careers that actually feel sustainable.

Subscribe now

FAQs

What does “consent culture” mean in design work?

In design and product teams, consent culture means moving forward once no one has a material objection — not waiting for everyone to fully agree. It replaces “endless alignment” with informed progress and shared accountability.

How is consent different from consensus?

Consensus seeks unanimous agreement before taking action. Consent focuses on safety and shared understanding: “Is this good enough for now, safe enough to try?” That distinction keeps creative teams agile without sacrificing inclusion.

What if someone still disagrees after a consent‑based decision?

Consent doesn’t erase disagreement — it contains it. Teams record the decision and reasoning, then revisit it if data or outcomes suggest a change. That documentation builds trust and prevents old debates from resurfacing.

How can designers practice negotiation without authority?

Start by clarifying outcomes and asking questions that reveal others’ priorities. Framing decisions as shared experiments (“Let’s test this safely”) turns potential conflicts into opportunities for co‑ownership and learning.

How does negotiation and consent support career growth?

When you model calm, fair decision‑making, people see you as a leader — regardless of title. Negotiation builds credibility, consent builds trust, and together they create the kind of influence that drives design careers forward.

Decision velocity = how quickly a team moves from problem to clear decision to action, without trading away quality. And you don’t need a title to impact it. In this piece you’ll get: a one-page decision map (RAPID-lite), a pre-read that prevents meeting rehash, a clean “consent vs. consensus” move, a lightweight decision log, and simple metrics to prove it works. (Hello, influence without authority and fewer stalled projects.)

Table of Contents
Why decision velocity is a quiet superpower
The 5 common blockers (with counter-moves)
Playbook: raise decision velocity in 7 days
Scripts for sticky moments
Make it visible to compound influence
Proving it works (tiny metrics, real signal)
Sources and further reading

Why decision velocity is a quiet superpower

Design work stalls less on drafting and more on decisions: unclear owners, vague asks, too many cooks, or no deadline for feedback. Research from McKinsey & Company during and after 2020 found that faster decisions can coexist with quality when roles are clear, debate is focused, and teams feel empowered — all levers you can pull without a title.

Definition you can use in a deck:

Decision velocity: the speed from problem through decision to first action, at a quality bar the team accepts.

The 5 common blockers (with counter-moves)

1. “Who decides?” is fuzzy → Map roles on one page (RAPID-lite).

2. Re-hashing the last meeting → Send a short pre-read 24 hours ahead.

3. Waiting for full agreement → Use consent when consensus isn’t needed.

4. Decisions evaporate after the call → Log the decision in 5 lines.

5. We can’t tell if this helps → Track cycle time and first actions.

Let’s walk through each one—designer to designer.

1) RAPID-lite: a one-page decision map

When debates loop, it’s usually because roles are unspoken. Borrow RAPID and shrink it to something you’ll actually use:

• R — Recommend (one person drafts the decision)

• A — Agree (must sign off, e.g., legal/brand)

• P — Perform (who executes after the decision)

• I — Input (whose info shapes the decision)

• D — Decide (the decider; name the human)

Post this as a single table in your doc and pin it in the project channel. RAPID is a Bain & Company framework — use the roles, skip the ceremony.

Tip: If you’re choosing between RAPID, RACI, or DACI, pick RAPID when the real risk is “who gets to decide.” Use RACI/DACI when execution ownership is the pain.

2) Pre-read, not re-hash: the 3-3-3 one-pager

Your meeting shouldn’t be the first time people see the problem. Send a tight pre-read the day before:

• Evidence points (up to 3) — plain language, with a screenshot or quote

• Constraints (up to 3) — tech, brand, legal, timeline

• Viable options (up to 3) — each with a one-line tradeoff

Open the meeting by reading the info together (2–3 quiet minutes works surprisingly well). Amazon’s long-standing memo culture uses silent reading to align fast; you can adopt a tiny version without the six-pager.

Pro move: Put “Decision we’re here to make:” at the top with a deadline. That single line turns a status chat into a decision call.

3) Consent beats consensus (most days)

Full consensus is slow and rare. For many product/design calls, consent (no significant objections) is enough to move, especially when decisions are reversible. Sociocracy’s consent model is built for progress: ship “good enough for now, safe enough to try,” then iterate. Pair it with the phrase “disagree and commit” for momentum when opinions diverge.

Script you can borrow: “We don’t need unanimity; we need no material objections. If none, let’s consent to Option B for two weeks and review outcomes. If you disagree, can you disagree and commit so we can learn?”

4) Keep the receipts: a 5-line decision log

Re-debating old choices is a time sink. Capture decisions where the team lives (notion, wiki, repo) using a tiny Decision Log:

• What: The decision in one sentence

• Why: 1–2 bullets (evidence, tradeoffs)

• Owner: Name + date

• Next step: The first action with a date

• Links: Brief, mock, Product Requirements Document (PRD), test doc

If you already use Architecture Decision Records (ADRs) on the engineering side, mirror the structure for cross-functional calls. ADRs exist to record intent and rationale — perfect inspiration for product/design decisions too.

5) Meeting choreography (so decisions actually happen)

• Start with the pre-read. 2–3 minutes of quiet reading aligns context.

• Name the roles. “I’m the R; Jamie is D; Legal is A.” (referencing RAPID)

• Time-box debate. “We have 12 minutes for critique; then we call it.”

• Default to consent. Consensus when necessary.

• Close with the log. Read it aloud; confirm the next step and owner.

Playbook: raise decision velocity in 7 days

Day 1–2 — Pick one recurring decision that stalls (e.g., “Which variant do we promote to full rollout?”). Draft a RAPID-lite for that decision and socialize the one-pager.

Day 3 — Send a 3-3-3 pre-read for the next meeting. Make the decision question explicit.

Day 4 — Facilitate the call. Use consent if no material objections arise; ask for “disagree and commit” when opinions diverge.

Day 5 — Publish the decision log and link it in the project README / channel.

Day 6–7 — Measure: How long from pre-read sent to decision made? Did the first action start within 48 hours?

Repeat the pattern on another decision next week.

Scripts for sticky moments

• When the owner is fuzzy:

  “Before we debate, who’s the D on this? I’ll take R, and I need A from legal if we use this claim.”

• When debate expands sideways:

  “We’re deciding placement, not strategy. Two options on the table; we have 8 minutes to choose or set a deadline.”

• When one team blocks due to preference:

  “Is this a material objection or a preference? If it’s preference, can we consent to test for two weeks and revisit?”

• When you can’t get unanimity:

  “We’re past diminishing returns. I’m asking for disagree and commit so we can learn from real data.”

Make it visible to compound influence

• Make a slide for weekly 1:1s. Screenshot the latest decision logs + “what happens next.”

• Increase demo cadence. If the decision produces a change, demo the outcome — even if small.

• Receipts doc. A living page of before/after, dates, outcomes. When review season hits, you’re not scrambling.

These small rituals create a “gravity field” — people start routing decisions to you because it’s faster when you’re involved. That’s leadership without a manager title in practice.

Proving it works (tiny metrics, real signal)

Track these for a month:

• Decision cycle time: pre-read sent to final call.

• First-action rate: % of decisions with an action started within 48 hours.

• Re-litigation rate: # of times a closed decision gets reopened.

• Assist metric: # of cross-team decisions you facilitated (shows influence).

If your boss wants external validation that speed ≠ sloppiness, point to mainstream management research since 2020 on faster and better decisions through clear roles and focused debate (links at the bottom).

Final thought

Influence isn’t telling people what to do — it’s making it easier for them to decide well and move. If you raise decision velocity on two or three recurring calls, you’ll feel the difference in a week. Keep the roles clear, put a real pre-read in front of people, move ahead with consent when you can, and log the call. Titles don’t matter like momentum.

Sources and further reading

• Working Backwards: Insights from Inside Amazon - Colin Bryar, Bill Carr

• RAPID Decision Making Framework - Bain & Company

• What is decision making? - McKinsey & Company

• Consent Decision-Making - Sociocracy 3.0

• How to Make Great Decisions Quickly - Harvard Business Review

• Documenting Architecture Decisions - Michael Nygard (Cognitect)

• DACI: A Decision-Making Framework - Atlassian

Enjoyed this piece?

I write weekly articles for designers and design leaders who want to grow their impact, lead with clarity, and build careers that actually feel sustainable.

Subscribe now

FAQs

What slows decision-making on cross-functional teams?

Unclear roles, no pre-read, and chasing consensus. Map RAPID roles, ship a one-pager pre-read, and use consent for reversible calls.

RAPID vs. RACI vs. DACI—what should designers use?

Use RAPID when “who decides?” is the bottleneck; use RACI/DACI when execution ownership is messy. Keep any model to one page so people use it.

What belongs in a decision log?

Context, options considered, the decision, the owner/date, and the next step — link to artifacts. ADRs are a solid reference pattern.

Is consent “lower quality” than consensus?

No. Consent allows movement when there are no material objections; you can revisit with data. Consensus demands full agreement, which is slower and rarely necessary.

The case for testing “inspiration,” not just funnels

Most of our testing time goes to the obvious: faster flows, reduced noise, fewer checkout hiccups. Necessary — but incomplete. Between “I’m curious” and “I’m ready,” people loop through exploration and second-guessing. That’s where inspiration can be the differentiator. Photography that shows context, quality, and possibilities. Copy that touts outcomes and lowers risk. Helpful content that demonstrates expertise and answers the question on a buyer’s mind. Clean, confident design that reps the brand. Together, they build trust and momentum.

This isn’t about making pages “prettier.” It’s about making decisions easier and building confidence. In this piece we’ll keep the stats light and the practice heavy: where to test first, what to measure (attention, confidence, and momentum), how to run simple A/Bs with holdouts, and how to keep performance solid while you raise the creative bar.

Table of Contents

What we mean by “inspiration”
Best surfaces to start testing on
What to measure (beyond CVR + AOV)
How to design the experiments
Practical test ideas designers can run
Reading results (+ business case)
Keep inspiration fast (and accessible)
A simple 2-week rhythm
Sources & (designer-friendly) reading

What we mean by “inspiration” (so we can measure it)

• Photography that adds information: context-of-use, details, and visualization — not decoration.

• Copy that clarifies outcomes, reduces risk, and matches how people actually read online. Make it scannable and concrete.

• Helpful content like size/fit tools, “which plan is right for me?” guides, short explainer sections, or comparison tables — placed near the decision, not buried.

• UI design that lowers visual noise, respects familiar patterns and is consistent with marketing look and feel. Consistency is key.

Best surfaces to start testing branding & content

If you can’t test everywhere at once, start where decisions crystallize:

1. Product/detail experiences (PDPs and equivalents). This is where images, copy, and proof points carry outsize weight. Invest in richer galleries (context, scale, zoom/360, video, augmented reality) and precise copy near the media. Baymard Institute’s multi-year work shows how much PDP clarity drives decision-making.

2. Category/solution landing. Use inspiration to frame “Why this category and not another” (use-case imagery, plain-English benefits, quick comparison). It’s the bridge from browsing to shortlisting — and often under-resourced compared with the homepage.

3. Homepage hero & first screen. Great for first impressions; just make sure you measure downstream assists (did the new hero increase qualified product exploration, not just clicks?).

4. Brand story / About page / editorial hubs. Treat these as mid-funnel accelerators, not vanity pages. People buy when they trust; current consumer data keeps linking trust with purchase, loyalty, and advocacy.

5. Checkout reassurance. Small copy and micro-illustrations that reaffirm delivery, returns, warranties, and security — protect the wins as you earn them.

Subscribe now

What to measure (beyond CVR and AOV)

Keep it simple and honest. You’re trying to see whether inspiration creates attention, confidence, and momentum — without breaking performance.

Don’t expect every inspiration test to spike same-session conversion.

1) Attention & interaction (on-page)

• Engaged time (exclude idle time).

• Module reach & scroll: % of users who reach the gallery, story block, or comparison table.

• Media interactions: image expands/zoom, gallery swipes, video quartiles.

• Copy interactions: accordion opens, “read more,” comparison toggles.
  Designers: the goal isn’t “more time” but meaningful time that leads to a clearer choice. Nielsen Norman Group reminds us engagement isn’t a single number — use a small set of relevant signals.

2) Confidence (quick pulse, not a survey slog)

• Single-Ease Question (SEQ) right after a decision-y action: “How easy was it to choose?” (on a scale of 1-7).

• Decision confidence: “How confident do you feel about your choice?” (1–7).
  These are light-touch and map well to the question you’re really asking: did the page make choosing easier?

3) Momentum (micro-conversions)

• Add to shortlist/save/wishlist

• Add to a compare tool

• “Email me this guide” / “Talk to an expert” / store-locator or appointment clicks

These capture progress in the messy middle even when the final purchase is delayed or happens elsewhere.

4) Brand & long-cycle indicators

• Repeat-visit rate (within 7 and 30 days) to the product or category

• Branded search trends in Google Search Console (query impressions/clicks for your brand or hero products)

• Assisted conversions and downstream revenue attribution when available

Use these to see if inspiration expands consideration, not just session-level clicks. (Google’s docs clarify how to read impressions/clicks in Search Console.)

5) Performance guardrails (non-negotiable)

Keep it fast and steady. Don’t trade speed for prettier pages. Watch your real-user data for three basics:

• LCP (how quickly the main content shows) — aim ≤ 2.5s

• INP (how quickly the page responds to taps/clicks) — aim < 200ms

• CLS (does the layout jump around?) — aim < 0.1

Hit those targets for at least 75% of users.

Note: Interaction to Next Paint is the new responsiveness metric that replaced First Input Delay in 2024.

How to design the experiments (without overcomplicating it)

• Start with classic A/B/n. One inspirational change per test: a new image set, a re-written hero, an added explainer block. Pre-declare the primary metric and the guardrails above.

• Add holdouts when you go wide. If you’re changing inspiration across many surfaces or running an always-on editorial hub, use holdouts to read real lift amidst market noise.

• Use “brand-lift” style studies sparingly but helpfully. For big creative shifts (new photography system, brand story revamp), measure recall, consideration, and ad recall via platform lift or onsite surveys with exposed vs. control.

• Bandits later, not first. Bandits are great once you know inspiration matters on that surface and want to auto-allocate toward better variants. Use fixed-split A/B for the first read so you learn the true effect size.

Practical test ideas designers can run this quarter

Photography

• Context & scale: Replace sterile silos or packshots with real-world scenes and “in-scale” references (hands, people, objects). Track gallery interactions + add-to-cart/favorite after viewing.

• Detail clarity: Add a tight detail shot (materials, texture) for products where touch/quality is a question.

• Order of images: Lead with the most goal-relevant shot (context, not just the prettiest). Measure reach to secondary shots.

Copy

• Outcome-led headlines: “Sleep cool without sacrificing support” vs. “Our new model X9.” Pair with one proof point and one next step.

• Risk reduction near the decision: Warranty, returns, sustainability, or craftsmanship — short, plain, specific. Trust grows when content is comprehensive and current.

Helpful content

• Quick-compare or “which is right for me?” Give people just enough to choose, then link to detail.

• Micro-explainers beside complex specs (“What does ‘solid-wood frame’ mean for longevity?”). Place visuals next to the relevant text to reduce cognitive load.

Design craft

• Visual hierarchy cleanup: Reduce decorative noise, tighten spacing, and align with familiar patterns for the category. Aim for quick scanning, not maximal novelty.

Share

Reading results (and making a case your CFO will respect)

Don’t expect every inspiration test to spike same-session conversion. Instead, build a small Inspiration Scorecard for each surface:

1. Reach & interaction: module views, engaged time, image/video interactions

2. Confidence: SEQ & decision-confidence delta

3. Momentum: micro-conversions (shortlists, comparisons, appointments)

4. Performance guardrails: LCP/INP/CLS stable or improved

5. Downstream signals: repeat-visit rate and brand/search trends over 2–4 weeks

When a variant wins on 1–3 and keeps 4 green, promote it — and schedule a follow-on A/B that’s closer to purchase (e.g., PDP → cart progression) to demonstrate business pull-through. That two-step pattern is often what turns design craft from “nice” into “valuable.”

Keep inspiration fast (and accessible)

Richer media shouldn’t punish users on slower devices. Use modern formats and a lightweight system:

• Image handling: next-gen encodes, responsive sizes, lazy-load below the fold, pre-connect for CDNs.

• Video: short, captioned, and silent by default with explicit play; defer noncritical embeds.

• Core Web Vitals: watch your field data and keep the thresholds; INP is the new responsiveness standard.

• Accessibility: descriptive alt text on key images; pair visuals with short, clear text (Google’s “helpful, people-first content” guidance aligns here).

A simple 2-week rhythm (so this actually happens)

• Week 1: Pick one surface and one inspirational lever. Draft creative and copy; define a tiny plan (primary + guardrails).

• Week 2: Launch the test; watch performance; collect SEQ/decision-confidence pulses.

• Friday recap: 10-minute readout with visuals and a one-slide scorecard. Decide: promote / iterate / archive.

Then move to the next surface. (Keep holdouts for bigger rollouts or when market noise is high.)

Final thought for design leaders

When you test inspiration, you’re not defending taste — you’re reducing decision friction in the messy middle. Start with one surface, one lever, and a humane scorecard. Keep it fast, keep it honest, and let the evidence show how craft converts.

Sources & further (designer-friendly) reading

• “Messy middle” research (Google)

• The aesthetic-usability effect and using information-carrying images (NN/g)

• PDP and homepage/category UX priorities (Baymard)

• Quick engagement metrics guidance for UX folks (NN/g)

• Brand trust and purchase/loyalty links (Edelmen)

• Core Web Vitals thresholds (Google) and the 2024 INP change (web.dev)

• Meta and Google on holdouts & geo lift

Enjoyed this piece?

I write weekly articles for designers and design leaders who want to grow their impact, lead with clarity, and build careers that actually feel sustainable.

We all know the urge to do something the moment we feel stuck. We fill notebooks with ideas. We search job boards. We schedule meetings. But action isn’t always the answer — at least, not right away.

In Part 1 of this series, I shared how freewriting — fast, unfiltered writing — can help you surface what’s really on your mind. It’s a way to clear the fog, confront hard truths, or just take inventory of the mental clutter that’s been building up. But there’s a step that comes after writing and before acting.

It’s this: Sit with it. Let it steep.

Writing surfaces insight. Stillness reveals meaning.

After a productive writing session, your brain might feel scrambled — like you’ve dumped out all the puzzle pieces but haven’t put anything together yet.

This is where stillness comes in.

Moments of quiet, intentional pause — whether through meditation, a walk, or just silence — give your mind a chance to connect dots you didn’t even realize were related. Neuroscience backs this up: when your brain enters a resting state, the Default Mode Network (DMN) activates. This network supports self-reflection, creative insight, and mental “time travel” — connecting past experiences with imagined futures. It’s in these quiet moments that new ideas often take root.

In other words: the good stuff happens when you’re not thinking so hard.

Let it steep, like tea.

This process is a lot like steeping tea. You’ve dropped the leaves — now give them time to transform the water.

Too often, especially in career or leadership dilemmas, we rush from idea straight into action. But insight that hasn’t had time to settle can lead to impulsive decisions, not informed ones. What felt right in the heat of writing might feel different after you’ve given it some air.

Meditation for Designers, Developers, and Leaders

Let’s lower the stakes on “meditation” for this context. You don’t have to sit in lotus pose, chant, or have your eyes closed for hours on end.

If you’ve ever stood in the shower and suddenly remembered the perfect word, solved a UX flow, or figured out a tricky team dynamic — that’s your brain making sense of things in stillness.

As creative professionals, we spend a lot of time making decisions under ambiguity. We’re expected to lead calmly, deliver confidently, and explain the “why” behind every design choice. That means clarity isn’t just nice to have — it’s the whole game.

Stillness is how you gain that clarity.

Practical ways to integrate this into your week

After you write, don’t race to the next task. Try one of these:

• Sit for 5–10 minutes. Eyes closed. Focus on your breath or the feeling in your body.

• Go for a short walk with no podcast, no music. Just notice what sticks with you from your writing.

• Reread your notes and ask, “What here feels most true?” Then sit with that.

• Use a timer. Even five minutes of presence is better than zero.

• Optional journaling prompt after meditation: What do I feel pulled toward next?

If you already have a meditation practice, great. If not, this might be the simplest place to start — not as a separate wellness routine, but as an extension of your creative and professional process.

Make space for insight to land

This isn’t about productivity. It’s about presence.

Adding freewriting and reflection to your week isn’t a hack — it’s a way of staying close to what matters. It’s how you reconnect with the values, instincts, and priorities that too often get drowned out by the noise of Slack pings and back-to-back meetings.

Try scheduling one short writing session with a quiet moment right after — even just once this week. Pay attention to what surfaces, even if the result isn’t immediate. (Spoiler: it often won’t be.) But a week from now, or a month from now, you may find that your next move feels less forced and more obvious.

Don’t rush the decision

Big insight? Great. Now pause.

The best decisions I’ve made — about projects, team changes, career moves — didn’t come from a brainstorm or a whiteboard session. They came from silence. They came from dredging things up, then letting them settle over time.

Sometimes, the most productive thing you can do is nothing at all.

This article is Part 2 of a series on clarity and creative decision-making.

If you missed Freewriting as a Tool for Career Clarity, start there.

If it resonated with you, I’d love to hear what rituals or reflection practices you use to move forward with confidence — and what you might try next.

Enjoyed this piece?

I write weekly articles for designers and design leaders who want to grow their impact, lead with clarity, and build careers that actually feel sustainable.

Sometimes your brain gets noisy when you’re not sure what to do next. You feel stuck on a decision. No direction, or five directions. Or like your day is full but nothing feels important.

When that happens, I often turn to writing. Not polished writing — just fast, honest, unfiltered thoughts on a blank page. Freewriting. It’s a way to clear the fog, hear what’s really going on beneath the surface, and get unstuck — whether I’m solving a design challenge or figuring out what I want from the next chapter of my career.

Freewriting Isn’t Just for Writers

Think of freewriting as a tool to get out of your own way. It helps you bypass the critic, the imposter voice, and your well-rehearsed explanations. It makes space for truth.

You’re not writing to explain — you’re writing to understand.

The magic of freewriting lies in its simplicity. You sit down with a blank page and a question, set a timer, and go. No structure. No grammar rules. Just momentum. And in that flow, unexpected thoughts emerge. Ideas get clearer. Tensions reveal themselves.

Use Cases from My Past

In my work as a design director and function lead, I’ve used freewriting to think through a range of challenges: a team restructure that was fraught with landmines, a frustrating executive dynamic I couldn’t decode, a product direction I was confident in but wasn’t gaining traction.

And in my personal career moments — wondering if I was ready for something new, gut-checking if I was still growing in my role — freewriting helped surface the real questions I needed to be asking.

Sometimes what came out was just venting. Other times, I saw connections I otherwise hadn’t been able to reach in conversation or even deliberate thought. But either way, it gave me something solid to build on.

Use It for Design, Leadership — or Big Career Questions

Freewriting works because it slows you down and gives your inner logic room to speak. That’s valuable in every layer of professional life:

As a Designer:

• Think through a sticky UX challenge or product compromise

• Reflect on a user research insight that’s stuck with you

• Process how to handle contradicting feedback

As a Leader:

• Explore how to approach a tough conversation or 1:1

• Clarify your own goals when everything feels reactive

• Deconstruct team dynamics that feel “off” but aren’t readily explained

As a Professional Navigating a Career Path:

• Revisit your role — is it still aligned with who you are?

• Examine whether burnout is creeping in — and why

• Articulate what you’re actually looking for in the “next thing”

How to Start Freewriting (Even If You’ve Never Tried)

You don’t need a special app or a fancy notebook (but if it motivates you, treat yo self). Here’s a dead-simple guide to try it this week:

1. Pick a Prompt

Start with a focused question like:

• “What’s bothering me about work right now?”

• “What would a great week (or year) look like?”

• “Why does this project feel blah?”

• “Where do I feel friction between who I am and what I do?”

2. Set a Timer

Ten to fifteen minutes is perfect. Long enough to get past the noise, short enough to not feel overwhelming.

3. Write Without Stopping

Keep your fingers moving. If you don’t know what to say, literally write “I don’t know what to say” or “I’m exploring an idea” until something else comes out. Don’t overthink. Don’t reread. Don’t polish.

4. Step Away, Then Reflect

Later that day or the next morning, come back and skim. Underline anything surprising, anything repeated, anything that stirs emotion. These are usually the seeds of deeper insight.

What It’s Helped Me Unlock

For me, the biggest value in freewriting isn’t always the clarity I get in the moment. It’s the accumulation of clarity over time. A few pages every so often turns into a personal record of what matters, what frustrates me, what energizes me — and eventually, patterns form.

More than once, I’ve realized I already knew what to do about a situation way before I acted — I just didn’t have a clear enough plan to trust it. Freewriting has helped me form that plan.

This Substack is actually a manifestation of freewriting for me. Sometimes I refer back to my journal to dig up a new topic. Or — if I have one already — writing for 15 uninterrupted, stream-of-consciousness minutes can give me my angle.

You Know More Than You Think

There’s a myth that clarity can only come from the outside — a mentor’s advice, a job offer, a new framework. And those can help. But often, the most accurate, grounded insight is already inside you. It’s just buried under layers of busyness, second-guessing, and overthinking.

Freewriting lets that signal cut through.

And once it does, the next step isn’t always action — it’s integration. That’s what we’ll cover in Part Two: what happens when you don’t immediately act on your insights, but instead let them steep through meditation, reflection, or quiet walks. That pause, too, can be powerful.

Enjoyed this piece?

I write weekly articles for designers and design leaders who want to grow their impact, lead with clarity, and build careers that actually feel sustainable.

A New Kind of Collaboration

The conversation around AI in creative work has been full of extremes — utopian and apocalyptic. But in between, where most of us actually live and work, something far more nuanced is happening: a shift in how creative professionals can use AI to support their best thinking, not replace it.

Design leaders aren’t being asked to hand over the wheel. But we are being asked to reconsider what the road looks like, and push on the gas.

Whether you’re skeptical or excited, AI tools are increasingly integrated into the design process. The question isn’t if they’ll be part of your workflow — it’s how to use them well.

Efficient UX Research Analysis

UX research has always been one of the most human parts of the process — listening, observing, interpreting. That hasn’t changed, but AI now acts as a research assistant.

Tools like Dovetail, Condens, and Userlytics can transcribe user interviews, highlight recurring themes, identify conflicting points of view, and surface patterns faster than a team could on its own.

You still need human judgment to draw conclusions, design follow-ups, and make decisions. But the early stages of sorting and synthesis can now move from hours to minutes — giving researchers more time to do what only they can do: ask more and better questions.

Subscribe now

From Blank Page to First Draft

One of the hardest parts of creative work is starting. A prompt, a blank canvas, a new flow — where to begin?

This is where generative tools like Figma’s Make can excel. It can draw directly from your existing design system to generate layout variations in seconds. The results aren’t perfect yet, but progress is fast, and refinement is just around the corner. Instead of starting from scratch, you’re curating, adjusting, and making strategic decisions from the outset.

The point isn’t perfection — it’s acceleration. The tool gives you momentum. You bring the direction.

UX Writing Assistance

Microcopy, tooltips, error messages — they all carry more weight than they get credit for.

AI can help generate tone-matching variants, brainstorm alternatives for button copy, or localize messaging for international markets. When your UX writing team is stretched thin (or nonexistent), this can be a useful baseline.

It still takes an experienced eye to select the right phrase, apply the right tone, and understand how copy supports the overall experience. But having a collaborator who never gets tired of offering options can ease the load.

Rapid Interaction Prototypes

Sometimes the best way to sell an idea — or test it — is to show it in motion.

AI tools can generate code snippets for hover states, modals, or even multi-step flows that let you show “live” interactions for stakeholder reviews or usability testing. Think of it like a prototype that’s 80% demo, 20% duct tape — fast, disposable, and clear.

For teams exploring new concepts or trying to validate ideas with limited dev bandwidth, this kind of support shortens the path between idea and feedback.

Dev Handoff with Precision

Once the design is final, the job isn’t done.

Tools like the Handoff plugin for Figma or Zeplin’s AI-enhanced exports help translate designs into specs — extracting sizes, spacings, font details, and component relationships for engineers without extra documentation.

Less time spent clarifying specs means more time refining product outcomes. For busy teams, the precision AI brings isn’t about skipping communication — it’s about handing over handoff.

Share

Additional Emerging Uses

Other promising areas where AI is becoming a creative partner include:

• Accessibility audits: flagging contrast or focus issues early in the process

• Visual asset generation: creating icons, placeholders, or mock assets in the right style

• Voice-of-customer summaries: processing support tickets, reviews, or survey data for design insights

• Component refactoring: identifying redundancies in large design systems to simplify and streamline

Each of these gives designers leverage — freeing up energy for strategy, empathy, and exploration.

What AI Can’t Do

Despite the hype, AI isn’t magic.

It can’t define product vision. It can’t replace human empathy. It doesn’t know your user, your brand, or your business the way you do.

It lacks context, originality, and judgment — the things design leaders cultivate over years of experience. That means the most successful teams won’t be the ones who chase every tool, but the ones who stay grounded in purpose and use AI with intention.

Leadership in the Age of AI

Design jobs aren’t disappearing. They’re continuing to evolve, and that’s part of the job.

The rise of AI as a creative partner invites us to focus more on what humans do best — synthesizing complexity, designing with empathy, and shaping experiences that resonate.

As a design leader, your role is to make space for thoughtful experimentation with these tools. Stay curious. Stay critical. And above all, stay grounded in what good design looks and feels like.

Enjoyed this piece?

I write weekly articles for designers and design leaders who want to grow their impact, lead with clarity, and build careers that actually feel sustainable.

It’s easy to get swept up in the urgency of the week. The Slack messages. The surprise meetings. The fire drills disguised as opportunities.

But if you’re leading design work — whether as a manager, a senior IC, or the team’s unofficial mentor — your impact depends not just on what you produce, but on how you spend your time.

So what if you approached your week the way you’d approach a design problem?

Not by default. But with intention.

Start With Purpose, Not Just Priorities

In The 7 Habits of Highly Effective People, Stephen Covey makes a powerful distinction: don’t prioritize your schedule — schedule your priorities. That means stepping back from your task list and asking a more important question:

What does success look like by Friday afternoon?

Instead of diving into calendar invites and task tickets, start with a future state: What do you want to feel at the end of the week? Accomplished? Clear-headed? Proud of a team win?

Once you define that end, work backward. Identify the 2–3 “big rocks” — high-leverage activities — that would get you there. These could be coaching a team member through a tough challenge, completing a thorny UX flow, or setting the direction for an upcoming initiative.

Prompt: What would make this week feel like a meaningful one — not just a busy one?

Use Futurecasting to Anchor Your Focus

Once you’ve defined what success looks like by the end of the week, take it one step further: feel it.

Futurecasting is the practice of mentally placing yourself in a future moment to experience the emotions, clarity, or momentum that comes from achieving something meaningful. Stephen Covey points to this technique in Habit 2: Begin With the End in Mind. It’s not just about imagining a checklist completed — it’s about visualizing how progress feels, so you stay grounded when distractions or detours threaten your focus.

Here’s how it might look for a design leader:

• Picture yourself at the end of the week having finally mentored that junior designer through a tough review process. You’re calm, supportive, they feel valued — and you realize how much that moment mattered.

• Visualize wrapping up a rough draft of your team’s design principles. The doc isn’t perfect, but it exists now. And in that Friday afternoon moment, you feel proud that you started something meaningful for the team’s future.

• Imagine saying “no” or “not now” to a reactive request that doesn’t align with your priorities. You’re not guilt-ridden — you’re relieved. You honored your time and modeled boundaries for others.

Futurecasting is especially helpful in “the moment of truth” — when a meeting gets dropped on your calendar, a request pops into Slack, or an email thread starts spiraling and you feel that pull to jump in. Those moments test your plan. But when you’ve already pre-experienced the satisfaction of a focused, values-aligned week, it’s easier to stay the course.

Try this:

• Close your eyes and picture next Friday. You’re logging off. What does your ideal self feel proud of?

• Write it down in a sentence or two. Keep it visible — on a sticky note, in your weekly planning doc, or pinned in your digital workspace.

• When priorities get fuzzy, return to that note. Ask yourself: Will this new thing move me closer to that feeling — or away from it?

Block the Big Rocks First

Covey popularized the idea that if you fill your schedule with sand and pebbles (emails, updates, urgent-but-not-important asks), you’ll never have room for the big rocks. But if you place the big rocks first, the smaller things can settle around them.

For design leaders, this might mean:

• Reserving time for deep work on Monday morning, before the week crowds in

• Blocking 90 minutes on Thursday for strategic planning instead of letting it get squeezed by meetings

• Creating a fixed slot for mentoring or feedback — not when you “find time,” but when you make time

I have 30 minutes blocked at the end of every Friday to take a look ahead at the next week and block time for my Big Rocks. It’s not about being rigid. It’s about being protective — of the work that actually moves things forward.

Design for Flexibility, Not Fantasy

Let’s be honest: your plan will get disrupted. A stakeholder will cancel, a team member will need support, a launch will shift.

That’s why your weekly plan needs to be flexible, not idealized.

Design your week like you’d design a resilient system:

• Include buffer zones for overflow or unexpected requests

• Pre-plan a “triage hour” midweek to reassess priorities

• Don’t overcommit — leave space to respond without derailing yourself

Run a Weekly Retrospective

End your week the way you’d end a sprint: reflect, learn, and iterate.

Try a Friday ritual with these prompts:

• What went well — and why?

• Where did I lose time or focus?

• What should I do differently next week?

Over time, you’ll notice patterns. You’ll plan around them. And the result won’t just be better weeks — it’ll be a better, more intentional version of your leadership.

Final Thought: You’re a Product Too

As a design leader, your job is to build systems — not just for your team, but for yourself.

You can’t lead effectively if you’re always reactive. The best design leaders make time for the work that matters before the urgent knocks. They treat time as a resource to shape, not just spend.

Your week deserves the same thoughtful attention you’d give a project. So design it.

With clarity. With purpose. With yourself in mind.

Enjoyed this piece?

I write weekly articles for designers and design leaders who want to grow their impact, lead with clarity, and build careers that actually feel sustainable.

You don’t need a title to be a leader.

In fact, some of the most effective influence in a design or tech org comes from people without a formal management role. These peer leaders help shape team culture, elevate project quality, and guide others through tough problems — not because they were assigned to, but because they chose to.

And their careers often accelerate as a result.

What Is Peer Leadership?

Peer leadership is the ability to support, influence, and guide others at your level — sometimes even above your level — without relying on hierarchy or job titles.

Peer leaders don’t wait to be promoted to start making an impact. They look around, see what needs doing, and help the team get there. That could mean mentoring a new teammate, championing best practices in design critiques, or stepping in to de-escalate conflict when emotions run high.

Peer leadership is a proving ground for future roles — and in many cases, a fulfilling path all on its own.

Paid subscribers get access to exclusive content, commenting on posts, and the Design Leadership chat group with myself and others on similar journeys.

Why Peer Leadership Matters in Design and Tech

Design and development work is rarely solo. Most progress is made in collaboration: designers working with engineers, UX researchers guiding product direction, brand designers aligning with marketers. When those connections are strong, work flows more smoothly — and outcomes improve.

Read more

You’ve refined your eye for hierarchy, built out effortless flows, and even run your own usability studies. Your portfolio’s solid, your resume’s strong — but something’s not clicking.

If you’ve ever felt stuck in your design career without a clear reason why, it might be this: the skills that unlock your next level aren’t the visible ones.

Let’s get into what these invisible skills are with concrete examples.

Context Awareness

Reading the room, the org chart, and the business landscape

You’re not just designing for users — you’re navigating an ecosystem. Great designers know how to align their work with where the business is headed, what leadership cares about, and what the team around them is struggling with.

Context awareness means understanding:

• Who’s really the decision-maker (even if they’re not in the room)

• What constraints matter — and which ones are just old habits

• When to move fast vs when to slow down and get alignment

Often when redesigning a page layout I’ll start by labelling each piece of the existing page with the purpose it’s trying to serve and the stakeholder(s) who will care about it. This helps me tally “representation weight” across varying concerns and prepare questions and talking points for feedback sessions later on.

Communication Timing and Framing

It’s not just what you say — it’s when and how

Your work isn’t finished when the design file is. The way you talk about your work — to stakeholders, engineers, other designers — has an outsized impact on how it’s perceived and implemented.

Some examples of invisible-but-crucial comms decisions:

• Presenting early sketches in a way that invites collaboration

• Giving context before critique to avoid defensiveness

• Sharing rationale instead of asking people to just “trust the process”

Ownership Without Ego

Taking initiative without overstepping

This one’s tricky: you’re stepping in where help is needed — not to steal the spotlight, but to keep momentum. You’re fixing issues that don’t technically belong to you. You’re the person others go to when they’re stuck, not because you “own” everything, but because you show up like someone who cares.

Ownership without ego sounds like:

• “I noticed this hasn’t been updated — want me to take a pass?”

• “I’m happy to wrangle feedback across teams if that helps move things forward.”

• “I added a quick mock to help us visualize the options. Totally open to discussion.”

Just because I transitioned from designer to web developer didn’t mean I was ready to drop my Sketch and Adobe seats (yes, this pre-dated Figma). Rather than wait for rigid hand-offs of pixel-perfect designs, I would often rough in new widgets or page templates for the design director to review. This let us both move faster: I could work ahead of polished final approvals and the designer could see living, responsive examples of components they hadn’t gotten to yet.

This type of partnership is often how designers build credibility and influence long before their titles change.

Emotional Regulation and Recovery

Design is personal. But leadership is not reactive.

We all care deeply about the things we make. But part of maturing in your role — especially if leadership is the goal — is learning how to care without combusting.

Emotional regulation in a design context can look like:

• Receiving blunt critique without spiraling

• Pausing before reacting to unclear feedback

• Not taking scope changes or shifting timelines personally

Burnout often creeps in when our emotional investment outweighs our recovery time. Learning to self-regulate doesn’t mean you don’t care. It means you’re building the endurance to lead.

Influence Without Authority

The art of peer leadership and guiding the process when you’re not the decision-maker

Every designer hits a ceiling when their influence ends with their Figma file. If you want to grow, you have to learn to lead across — not just up.

You do that by:

• Bringing clarity, not just questions

• Showing what’s possible without demanding it

• Building cross-functional trust through responsiveness and reliability

It’s subtle. But over time, people start seeing you as someone who makes things better — and makes things happen.

How to Build Invisible Skills (Even If They’re Not Taught)

You may not get a performance review that says, “Be better at reading the room.” But you can build these skills through practice and feedback.

Try:

• Journaling after tricky meetings to review what went well and what didn’t

• Asking trusted peers what you’re known for (and what you’re not)

• Watching how respected leaders navigate conflict, pushback, or ambiguity

You don’t have to guess. You just have to start paying attention.

Design careers don’t hinge on craft alone.

The further you go, the more it’s your invisible skills — how you show up, how you communicate, how you lead from wherever you are — that define your impact.

You can’t show them in your portfolio. But you’ll absolutely carry them into every interaction that matters.

Enjoyed this piece?

I write weekly articles for designers and design leaders who want to grow their impact, lead with clarity, and build careers that actually feel sustainable.

When the work that once energized you starts to feel like a weight, it’s tempting to assume the answer is quitting. Sometimes it is. But often, what you actually need is a reset, not an escape.

This article is for designers who are hitting a wall but still want to care. You’re not done — but your current situation is. Let’s redesign your role, so you don’t have to torch your career to feel whole again.

Burnout vs. Misalignment: Know Which One You’re In

Burnout is emotional and cognitive exhaustion — often caused by an overload of responsibilities, long hours, lack of autonomy, unclear expectations, or chronic under-recognition.

Misalignment is different. It means the shape of your role no longer fits the shape of your strengths, values, or goals.

You can be misaligned without being overwhelmed. You can be burned out even in a job that looks perfect on paper. And you can absolutely be both.

Start by asking:

• Am I doing too much? Or the wrong mix of things?

• Do I feel energized by anything at work right now?

• Is this a sustainable pace — or am I slowly draining?

The answers will help you decide whether to renegotiate your role — or exit.

Paid subscribers get access to exclusive content, commenting on posts, and the Design Leadership chat group with myself and others on similar journeys.

Step 1: Audit Your Actual Role

What you were hired to do and what you’re currently doing are rarely the same thing after a year or two.

Take 15–20 minutes to list out your recurring tasks, projects, and responsibilities. Then ask:

• Which tasks energize me?

• Which feel neutral?

• Which drain me — and why?

• Which are high impact for the org vs. just “keeping the lights on”?

Important notes:

Read more

Typically I chip away at an outline during the week, sometimes I get GPT assistance with expanding on an idea or structuring the thoughts into a logical order. Then the weekend comes and I write the thing.

But this weekend is Father’s Day and I make no apologies for that role being the most important one I will ever have. So this week — late on Sunday afternoon — I thought I would post something about balance, and the interplay of personal and professional roles.

When Keeping Score Stops Making Sense

Any adult, and particularly parents of young kids, knows the no-win situation weekends often present: you do the things you want to do or you do chores and either way it’s the wrong choice. Meaning — come Sunday night — you might regret working too much, or too little. And then start Monday carrying that stressful feeling into your work week.

So this weekend I decided to just focus on family and take a break from writing. No post this week, no big deal.

But after going back and forth a few times I landed on this — a hybrid, low-effort post that puts out into the world what is really happening in hopes it resonates with many who struggle with the same balance.

What I Did This Weekend (Instead of Writing)

So here’s how I chose to spend my weekend — one honest choice at a time without keeping score between work, chores, and personal fulfillment.

Friday evening: rush home from work to have a quick, healthy dinner before taking my daughter to a Glow Party at her school. Not an activity I was super thrilled about but one that meant a lot to her in her last year in elementary school.

Time is moving too fast, make long-lasting memories.

Saturday morning: make scrambled egg tacos with my son like we do most weekends, try a new variation and write down the recipe. Build raised beds for the dahlias we’ve been wanting to plant for years. Last year my wife’s parents sold their home, and the gorgeous dahlias her dad loved to grow are no more. Time to take over.

Carrying on traditions is a quiet act of appreciation and tribute.

Saturday afternoon: visit family for a cookout, catch up with the adults while the cousins run around. Play tickle monster, light a camp fire, burn sparklers. Get home late and wiped, try to watch a funny movie but both fall asleep on the couch.

Nothing is more important than family — really listen, connect and get those goodbye hugs.

Sunday morning: take the kids to help an elderly neighbor with some yard work. Someone in the neighborhood had the nerve to write them a note objecting to a broken sidewalk and some weeds. Bonus: we took home some day lilies to transplant.

Helping others for its own sake is obviously a nice thing to do, but people don’t talk enough about how good it is for your own mental health.

Sunday afternoon: play a card game with the fam, then take a walk to our neighborhood Indian spot for dinner. Walk home, have some chill time and a celebratory Father’s Day drink with my partner, go to bed with zero regrets. But I will need to mow the lawn Monday night.

Big trips or big gifts are great but there are chances almost every day to something little together, and those add up.

Why I’m Sharing This With You

So I’m not 100% sure who will care, but this post is meant to:

• Highlight the importance of intentionally investing as much in your personal life as your career

• Show how that investment can offer mental restoration that actually makes you more productive when you go in on Monday

• Put some of my personal life “out there”, for readers to get a fuller picture of the person offering perspectives on growth

If you made it this far, thanks for indulging me and if any of this spoke to you, please send me a note on Substack or LinkedIn. I appreciate every reader and love to hear feedback.

Enjoyed this piece?

I write weekly articles for designers and design leaders who want to grow their impact, lead with clarity, and build careers that actually feel sustainable.

In the design world, we talk a lot about resilience: how to bounce back from setbacks, handle tough clients, and adapt to shifting priorities. But what if bouncing back isn’t enough?

There’s a concept from systems theory and economics called anti-fragility that goes a step further. It describes things that don’t just survive volatility — they get better because of it. Unlike something fragile (which breaks), or something robust (which resists change), an anti-fragile system uses stress and disruption to become stronger.

The concept has since found its way into how we raise children. Educators like Jonathan Haidt emphasize that kids grow stronger when they face manageable challenges, “rejection, failure, and discomfort”. This isn’t neglect — it’s investment in long-term resilience.

That idea belongs in every designer’s toolkit.

Designing for Change, Not Just Stability

Designers often build for change — we expect the web to evolve, products to pivot, users to surprise us. But we don’t always design our careers the same way. We optimize for the title we want next, or the perfect job at the perfect company. We try to make the unpredictable feel safe.

Anti-fragility flips that.

When you embrace anti-fragility, you stop treating disruption as a threat and start treating it as fuel. You seek out the hard projects. You try roles that force you to think in new ways. You grow skills that stretch your range, not just your specialization.

This isn’t about being reckless or chasing chaos. It’s about building a professional life that thrives on evolution.

What Anti-Fragility Looks Like in a Design Career

You might already be stronger under pressure than you think. Anti-fragility shows up in subtle ways:

• Taking on a role that doesn’t have a roadmap — and building one

• Learning a new tool or discipline because the project needs it

• Choosing to work under a leader who challenges you to level up

• Asking for feedback when you know it will be uncomfortable

These moves don’t just build skills. They shape your instincts, your pattern recognition, your ability to navigate ambiguity. And they do something even more important: they make you less dependent on circumstances being “just right” in order to do your best work.

It Starts With How You Frame Setbacks

If you’ve ever had a job change unexpectedly, a project fall apart, or a role eliminated, you already know what fragility feels like. But you also know that what comes next matters more than what went wrong.

Anti-fragile designers ask:

• What did this situation teach me that success wouldn’t have?

• What did I gain from the hard part — a new skill, a new boundary, a new relationship?

• How will I use this in my next move?

That mindset turns pain points into confidence boosters. It makes you a better designer and a more strategic teammate.

In “Burned By Loyalty? What to Do After a One-Sided Exit” I wrote about not taking business-survival-mode decisions personally and actively detecting and avoiding leadership red flags. Every experience can teach you as much about what to avoid as what to do.

On the flip side, as a result of that same surprise exit, I asked myself — of everything I’ve done so far — what strengths should I lean into? I recognized mentoring and coaching as the most personally rewarding aspect of my career and decided to launch a business doing just that.

You Don’t Have to Wait for a Crisis

Anti-fragility isn’t just reactive. You can actively build it into your career. A few ways to get started:

• Rotate into different kinds of projects, even if they don’t align perfectly with your comfort zone

• Take on a mentorship role, even if you’re still figuring things out yourself

• Learn the business side of your work — strategy, revenue, influence

• Explore work outside your core medium (print designers, try UX; UX designers, try motion)

The goal isn’t to become everything to everyone. It’s to create enough surface area for opportunity and growth to find you, even when the market or your company shifts.

Resilience Helps You Recover. Anti-Fragility Helps You Evolve.

Resilience is noble. But it’s reactive. Anti-fragility is proactive. It asks: what might this experience make possible that wasn’t before?

Designers who cultivate this mindset stand out — not because they do everything perfectly, but because they adapt visibly, with purpose. Their portfolios show growth, not just skill. Their careers are shaped by intention, not just luck.

Build for the Future You Can’t Predict

Design is, at its core, a practice of navigating ambiguity. Your career deserves that same creative thinking.

Build something that doesn’t just survive change — build something that grows because of it.

Enjoyed this piece?

I write weekly articles for designers and design leaders who want to grow their impact, lead with clarity, and build careers that actually feel sustainable.

Your 1-on-1s with your manager are one of the few recurring meetings actually designed for you. But too often, designers show up underprepared, overly deferential, or focused entirely on project tasks — missing the opportunity to advocate for themselves and shape their own growth.

Here are five of the most common mistakes I’ve seen (and made) — and what to do instead.

Using the whole time as a project status update

It’s tempting to rattle off the sprint board: “Homepage design is 70% there, waiting on content for the About page, and I left comments for devs on that mobile issue.” But your 1-on-1 isn’t a stand-up. Your manager can probably get those updates from tools or team syncs.

Instead:

Use this time to talk about you. What’s working? What’s frustrating? What feedback have you gotten? Where do you want support? Bring one work update that needs input — but spend the rest discussing growth, alignment, or challenges.

Subscribe now

Avoiding conflict or hard conversations

Many designers are peacemakers. We don’t want to rock the boat. But if something’s off — expectations, team dynamics, leadership communication — and you never bring it up, nothing improves.

Instead:

Practice flagging concerns with clarity and curiosity. “I’m noticing X, and I’m not sure if it’s a one-off or a pattern. Can we talk about it?” You’re not being difficult — you’re showing leadership.

Waiting to be asked about your goals

If your manager hasn’t asked about your career path in a while, it’s easy to assume it’s not on their radar — or that you shouldn’t bring it up. That’s a missed opportunity.

Instead:

Come prepared with your own agenda. “I’d love to use a few minutes today to talk about where I’d like to grow this year.” It signals initiative and gives them something to work with. Managers can’t support goals they don’t know about.

Share

Expecting them to read between the lines

“I guess I’ll just keep doing this work and hope someone notices,” is not a strategy. Hoping that your value is self-evident or that someone will offer you feedback unsolicited often leaves designers feeling invisible.

Instead:

Ask directly. “I’d really appreciate your feedback on how I’ve been handling the new stakeholder relationship. Is there anything I could improve?” It opens the door for growth and builds trust.

Not taking notes or following up

Your manager may support you, but they’re juggling competing priorities. If you leave every 1-on-1 with good intentions but no action, progress gets fuzzy.

Instead:

Document action items. “To recap, I’ll send over the workshop outline and you’ll follow up with PM about timeline shifts.” These little habits build momentum, clarity, and confidence.

Use It or Lose It

Your 1-on-1 isn’t just a checkpoint — it’s a leadership gym.

Show up ready to grow.

Even if your manager isn’t a perfect mentor or coach, you can set the tone by making space for the career conversations you wish they were initiating. If you treat your 1-on-1s like a design problem — with intention, iteration, and honest feedback — you’ll see better outcomes over time.

Enjoyed this piece?

I write weekly articles for designers and design leaders who want to grow their impact, lead with clarity, and build careers that actually feel sustainable.

The Work You “Shouldn’t” Be Doing

Not long ago, I found myself refreshing web pages — reworking layout, tweaking copy, updating styles. On paper, it might seem like work better suited for someone earlier in their career. I’m in a director role. Shouldn’t I be delegating?

The truth is there was no one to delegate it to, and also I wanted to do it. The project called on a blend of skills I’ve collected over the years: design thinking, user flows, Photoshop fluency, CSS updates, twisting CMS blocks into a design. It was work I knew how to do efficiently and well.

More than that, I saw a gap that needed filling. And that’s part of what leadership actually is: seeing a need and stepping in where you can create momentum — without fixating on whether it’s “your level.”

Often the most satisfying projects aren’t the ones that showcase your title. They’re the ones that let you use all your tools.

All the Nooks and Crannies

The longer your career runs, the more oddly-shaped your skillset becomes. You pick up little pockets of expertise that don’t always appear on a job description — and yet, when the right project comes along, they become your secret weapons.

You might be a creative director who can still jump into Photoshop and finesse a tricky mask. Or a UX strategist who can debug a bit of layout CSS without calling in dev support. These aren’t fallback skills. They’re part of what makes your experience comprehensive.

Being able to jump in across layers of execution makes you not just useful — but uniquely equipped for certain kinds of work.

What the Market Gets Wrong About Senior Talent

Hiring processes often assume a senior designer or director won’t want to do hands-on work. Or that they’ll expect to operate purely at the strategic level.

But real-world needs aren’t always that clean. Sometimes a team needs someone to jump in on a high-priority deliverable, today. It may not justify hiring another full-time specialist. The budget may not stretch to support both strategic and tactical hires.

In those cases, hybrid senior designers — the ones who can lead and execute — are a hidden asset.

That said, there’s a line. If the tactical work becomes a drain that blocks your strategic contributions, it’s time to advocate for handoff. Leadership doesn’t mean doing everything — it means helping the org scale well.

How to Search for Work That Matches Your Shape

If you have range, don’t hide it.

Too many resumes are reduced to the last job title or most recent buzzwords. But those side skills — HTML fluency, branding chops, motion instincts, presentation design, CMS admin — they matter.

Include them. Talk about them. Not as “also” skills, but as part of your full contribution.

Because sometimes, the role you applied for isn’t the only need that org has. And your past experience may be the very reason you stand out. A hiring manager might see in you the answer to two problems instead of one.

At the interview stage, share your toolkit. Let them know how you’ve flexed in past roles. Show them you’re not a single title — you’re a resource.

A Message for the Mid-Career Hybrid

If you’re feeling like your resume doesn’t quite fit the molds you’re seeing, maybe that’s because you’re not meant to shrink into one.

Look for the roles that want your shape. Or mold a role to fit.

The work that lights you up likely won’t fall in a clean job description box. But it will feel familiar in the best way. Like using every corner of your craft. Like being useful and lit up.

When you find that kind of work? It doesn’t feel beneath you. It feels like yours.

Enjoyed this piece?

I write weekly articles for designers and design leaders who want to grow their impact, lead with clarity, and build careers that actually feel sustainable.

You started saying yes because it felt like progress.

More responsibility. More visibility. More trust.

But eventually you realized something. Your title hadn’t changed. Your pay hadn’t changed. But your workload had — a lot. And suddenly, you weren’t sure if you were being seen as a rising star or just… available.

Welcome to the invisible promotion: when your role quietly expands to resemble a more senior one, but without the recognition, support, or reward that real growth deserves.

Let’s talk about how to spot it, how to respond, and how to turn invisible growth into real career momentum.

Why It Happens (and Why It Feels Good at First)

Designers tend to be helpful, curious, and ambitious. We raise our hands. We offer solutions. We’re good at filling gaps.

When a manager says, “Can you take this on?” it feels like trust. And it often is. And in healthy cultures, increased scope can lead to real growth.

But in lean orgs or poorly structured teams, it often just leads to quietly expanded expectations with no formal shift in role, pay, or path.

Signs You Might Be in an Invisible Promotion

• You’re doing manager- or director-level work with no change in title or compensation

• You’ve taken over strategic responsibilities (roadmapping, client pitching, performance reviews) without support

• You’re the go-to person for new initiatives, but not included in leadership decisions

• You’re told you’re “not quite ready” for promotion — while doing the work of the next level

This isn’t about not wanting to stretch. It’s about not letting the stretch become the standard without recognition.

What to Do About It

1. Document Your Actual Role

Start by writing down what you actually do — not what your job description says. Compare it to the role you were hired for, and to descriptions for the level above you.

Ask yourself: “Would this list make sense for someone with my title, or does it look like a level above?”

This gives you clarity and evidence.

2. Ask for Clarity, Not Just Praise

If you’re hearing a lot of “great work,” but not getting role clarity, try a conversation like:

“I’ve taken on a number of higher-scope responsibilities over the past few months. I’d love to talk about how that aligns with my role level and what the path to formal growth looks like.”

This signals initiative and prompts your manager to engage intentionally, not just reactively.

3. Define What Real Growth Looks Like

Promotions aren’t always about changing tasks — sometimes it’s about decision rights, compensation, and influence.

If you’re doing more but still can’t say no to projects, can’t influence timelines, or aren’t included in roadmap discussions, you’re not operating at a true next level. You’re being stretched within the same lane.

Real growth means more than more work. It means more autonomy, more impact, and more trust with outcomes — not just outputs.

What Not to Do

• Don’t wait passively. It rarely gets better without a conversation.

• Don’t assume your manager sees the whole picture. They might not realize how much your role has evolved.

• Don’t accept endless stretch with no feedback loop. That’s not growth — it’s slow erosion.

And a Big Watch-Out

Before you push back on any ask outside your scope, take a breath.

Sometimes leaders do need to stretch someone to assess their readiness for growth. It might be a trial balloon. It might be trust in action. And in the right environment, a temporary stretch can lead to a meaningful leap.

This is where judgment matters.

• Is this a one-off ask or an ongoing pattern?

• Is there feedback, support, or visibility tied to this responsibility?

• Has your manager shown follow-through on other growth conversations?

Not every stretch is exploitation. Some are stepping stones. What matters is whether the ask is paired with intention, support, and a clear path forward.

Final Thought

Saying yes can be a powerful accelerator. But if every yes turns into permanent role creep, you’re not being promoted — you’re being absorbed.

If you’re in an invisible promotion, name it. Clarify it. Advocate for what comes next.

Because growth should feel rewarding — not invisible.

Enjoyed this piece?

I write weekly articles for designers and design leaders who want to grow their impact, lead with clarity, and build careers that actually feel sustainable.

If you’re new here, welcome — and thanks for reading.

Before I started writing weekly about career growth and leadership in design, I went through plenty of doubt, dead ends, and moments that didn’t feel like progress at the time.

Over the course of three posts, I told the full story of how I went from getting my graphic design degree to holding executive-level design roles…and eventually, to becoming a career coach for designers ready to lead.

The series isn’t just about titles. It’s about how we grow — through momentum, but also through moments of humility, reinvention, and choosing to keep going.

Next week I’ll be back to posting new material. If you missed it the first time around, here’s the full journey:

Sometimes staying put is the most powerful move you can make.

Not because you're loyal to a company.
Not because they "took a chance on you."
Not because you owe them for that raise, that title, or that flexibility last year.

But because you're devoted to your own growth — and, for now, this is the right environment to support it.

I talk a lot about how staying too long can stagnate your career. That happens. But there's another side. Stability can lead to mastery. Familiarity can unlock influence. Staying in one place, for the right reasons, can accelerate your development in ways that job-hopping never will.

This isn’t about loyalty for loyalty’s sake. It’s about staying when you know you’re still becoming.

This is the fourth piece in a series exploring loyalty at work from multiple angles — the harm of outdated expectations, why transparency is more powerful than blind commitment, and what it feels like to get burned by staying too long. This one is about reframing loyalty altogether.

Devotion to Your Own Development

Loyalty implies obligation. Devotion implies purpose.

The healthiest reason to stay in a role or company long-term is because it’s actively helping you grow. That might look like:

• Owning work that expands your skills

• Building relationships that unlock collaboration at a higher level

• Leading initiatives that stretch your problem-solving muscles

• Gaining business context that strengthens your design instinct

In these moments, you’re not serving the company at your own expense. You’re building something — within yourself. Your patience isn’t passive. It’s purposeful.

Depth Over Novelty

Bouncing between companies can expose you to new systems, industries, and leaders — all valuable. But depth creates a different kind of strength.

When you stay long enough to see a design system evolve, or a brand reposition, or a product strategy pivot, you gain something you can’t pick up in a 12-month sprint: strategic memory.

You start to:

• Anticipate objections before they happen

• Mentor others through changes you’ve already weathered

• Spot patterns that newcomers miss

This isn’t just retention. It’s rootedness. And it becomes part of your leadership DNA.

Influence Is Earned Over Time

At most companies, influence isn’t granted with your title. It’s earned through consistency, perspective, and trust.

When you stick around and keep showing up with insight, with calm, with clarity — people listen differently.

Sometimes, the magic of staying is that you become the person others look to. Not because you’ve been there the longest, but because your understanding runs deeper than the surface. You’ve done the work. You’ve watched it change. You have context, not just opinions.

That influence follows you, wherever you go next.

When It Works: A Personal Prompt

If you’re in a long-term role now, ask yourself:

• Am I still learning?

• Do I have more agency than I did a year ago?

• Can I point to something I’ve helped improve or evolve?

If yes: that’s not coasting. That’s compound growth. And it may be smarter to keep investing than to pull out too soon.

I did stretches at two dysfunctional agencies for the same reason: growth. Wearing many hats, launching new disciplines, and sharpening my business acumen were just a few of the upsides — even under chaotic, insecure, and micromanaging leadership.

There were positives outside the purely selfish too: doing meaningful work for non-profits, mentoring team members, and collaborating with some great — and smart — people who I hope to work with again someday.

Staying for Meaningstones, Not Just Milestones

Not every decision to stay has to be career-optimized. Sometimes you’re lucky enough to land in a place where the overall mission matters. You believe in the work, the team, or the impact you're helping to create — even if the pace of personal growth isn’t always perfect.

That kind of long-term commitment can be deeply fulfilling when it’s a conscious choice. If you know the "why" behind your decision to stay, and it aligns with your values, it is a form of growth. Purpose-driven work feeds your integrity, your resilience, and your leadership.

Just be sure you're not sacrificing your development in the name of a cause that no longer makes space for you to thrive. Purpose and growth don’t have to be in tension. The right role will give you both.

Final Thought

Loyalty to a company is misguided and fragile. It ends with reorgs, with budget cuts, with leadership changes.

But devotion to your own growth is durable. And when a company becomes the right partner in that pursuit, staying isn’t playing it safe. It’s playing it smart.

Stay for you. Not for them. And watch how far you can go.

Enjoyed this piece?

I write weekly articles for designers and design leaders who want to grow their impact, lead with clarity, and build careers that actually feel sustainable.

You gave them your best work. Your best ideas. Your nights and weekends. Maybe even your trust.

And then you were reorganized out. Or passed over. Or let go.

The job moved on without you, and the loyalty you thought you had? It wasn’t mutual.

This is the third piece in a series on workplace loyalty. In Loyalty Is Overrated, I wrote about how the term gets used to keep people stuck. In Transparency Isn’t Optional I wrote about how design leadership is built on trust. But what happens when you’ve already stayed too long — and it burned you?

The Emotional Fallout

Being burned by loyalty hits you harder than a bad job or a poor fit. This one hurts because it feels personal (it’s not, but we’ll get to that in a minute).

Maybe the team felt like family. Maybe you believed the growth path you were on was real. Maybe there were stock options — so you kept trying to believe.

When loyalty goes one-way for too long, the exit doesn’t just bruise your resume. It messes with your sense of judgment.

Did I miss the signs?
Did I stay too long?
Did I make it harder on myself?

Probably. That doesn’t mean you were wrong to care. It means you’re human.

It Feels Personal — But It’s (Usually) Not

Layoffs almost always feel like a judgment about your value. But most of the time — it’s not personal at all. It’s survival math.

Leaders are responsible for keeping the company alive, not keeping every promise they ever made.

Even when layoffs happen because of earlier leadership missteps (missed market signals, poor resourcing decisions, strategy mistakes), once the business hits a certain point, leadership has a duty to protect the whole system — the clients, the remaining teams, the investors, the brand itself.

It doesn’t make it hurt less, and it doesn’t erase the emotional breach.

But seeing the layoff as a business triage decision rather than a personal betrayal can help you carry less invisible weight afterward.

You didn’t fail. You didn’t get cut because you weren’t good enough.

You were part of a system that hit turbulence — and you deserve to keep moving forward.

What To Use As A Guidepost (Even When You Feel Lost)

It’s easy to walk away from a one-sided experience feeling like you lost time. But in reality, you didn’t walk away with nothing.

You likely gained:

• Strong, transferrable skills you didn’t even realize you had while doing the work

• Insight into (good or bad) leadership that will shape how you show up later

• A deeper sense of your values — because you saw what happens when they’re ignored

• A clearer BS meter for future red flags

Sometimes your clearest learning comes after the fact.

How to Rebuild Your Confidence and Career Narrative

Start with the story you tell yourself. Not every exit needs to be spun into gold, but it does need to be owned.

• What did you learn that you wouldn’t have learned otherwise?

• What new clarity do you have now about what you want and won’t tolerate?

• What strengths did you build that you weren’t giving yourself credit for?

Then start rebuilding the story you tell others:

• Focus on outcomes, contributions, and growth — not just the ending

• Be honest about lessons learned without sounding bitter

• Share what you’re looking for next with confidence

How to Lead — and Choose — Differently After Being Burned

When you’ve been on the receiving end of broken loyalty, you don’t walk away unchanged.

• You become sharper about the organizations you join.

• You start looking not just at the job title or salary, but at the leadership culture.

• You ask better questions in interviews.

• You notice how a company talks about its people — and how its leaders behave when things get hard.

This experience reshapes how you lead, too.

If you move into management or leadership, your own history becomes part of your MO.

• You understand that promises matter — and so does honesty about what you can and can’t promise.

• You recognize that transparency builds more loyalty than vague reassurance ever could.

• You remember what it feels like to be left out of decisions that impact your future — and you work to include your team in the realities they deserve to know.

In Transparency Isn’t Optional, I laid out why leading with clarity matters more than ever.

But when you’ve experienced a breach of loyalty firsthand, you don’t just believe it — you embody it.

You can be the kind of leader who doesn’t demand loyalty — you can build it the right way: through trust, honesty, and mutual respect.

That’s how we fix the culture.

One decision, one team, one honest conversation at a time.

Final Thought: Loyalty Burnout Isn’t the End

It might take a while to trust again. But that doesn’t mean you stop caring. It means you care smarter.

You know your value now. And you know how to protect it.

Let that be the start of what comes next.

Enjoyed this piece?

I write weekly articles for designers and design leaders who want to grow their impact, lead with clarity, and build careers that actually feel sustainable.