5 MONTHS AGO • 5 MIN READ

How to survive when you’re the only designer on your team

profile

Join 40,000+ designers moving from execution to influence

Biweekly strategies for product designers ready to move from execution to influence. Learn frameworks for stakeholder management, getting ideas approved, and advancing to senior roles.

Hey Reader

This week is packed with ways to work smarter, grow your influence, and level up your design career.

In today's email:

  • Lean design teams: Feeling stretched across multiple projects? Learn four tactics to work strategically, stay focused, and unblock yourself without burning out.
  • AI Product Design Career Coach: Get personalized guidance from a GPT trained on Garron Engstrom’s mentorship frameworks—perfect for navigating career growth, IC vs. management decisions, and promotion planning.
  • Strategic Designers Guild: Enrolment opens Jan 2nd! A curated program for mid–senior UX designers to sharpen clarity, influence, and leadership muscles through monthly prompts, peer feedback, and guided reflection.

🎟️ Get your ticket to our next live event with Chris Abad as we explore how to turn creative pitches into strategic stories using the VISION Framework, so your ideas get funded and make real impact.


Design gems of the week

If you didn't catch my latest post on IG, I'm expecting my second baby early next year and will be taking a break form mentoring for a bit 💗

This article below is a recap of our recent livestream with Florian Bölter. The conversation was full of super useful, real-life advice for designers juggling way too many teams — enjoy the main takeaways and RSVP to our next event with Chris Abad here.

How to stop drowning when you're the only designer (or one of very few)

Most designers aren’t working in well-staffed teams anymore. You’re supporting multiple product streams, fielding requests from marketing, and watching your backlog grow faster than you can work through it.

The reality: You can do many things, but you cannot do all of them at once.

This isn’t about working harder or being more efficient. It’s about fundamentally changing how you operate as a designer when resources are limited. Here are four tactical frameworks that actually work when you’re stretched thin.

Distribute the decision surface

When you’re splitting time across multiple teams, you can’t be in every meeting or available for every question. Your teams need to keep moving when you’re working elsewhere.

The problem isn’t that you’re unavailable—it’s that teams don’t have what they need to make decisions without you.

How to do this:

  • Provide decision-making context alongside your designs. Explain why you made certain choices so engineers can handle edge cases without pulling you into Slack.
  • Bring engineering and PM leads into decisions early. When they participate in the thinking, they can unblock themselves later.
  • Establish predictable check-ins. Turn your standup into office hours where people bring design questions instead of interrupting you randomly throughout the day.
  • Set boundaries on “quick look” requests. When someone asks for a fast review, redirect them to your next check-in. This protects your focus time and trains people to batch their questions.

Get into a rhythmic focus

Context-switching kills productivity. The fix isn’t managing switches better—it’s switching less often.

How to do this:

  • Give one team 70-80% of your attention for several days before switching to another team. This creates predictable blocks of deep work and builds up a buffer.
  • Attend all team rituals, but focus your actual design work on one team at a time.
  • Let Team A work through what you’ve already delivered while you’re heads-down on Team B. The longer you maintain this rhythm, the fewer urgent collisions you’ll face.

Some weeks both teams will need you simultaneously. When that happens, fall back on your other tactics. But this rhythm prevents those situations from becoming your default.

Ship in stages, not all at once

You don’t always need to deliver polished UI before engineering can start. This might feel uncomfortable if you’re used to shipping complete designs, but it’s one of the most effective ways to unblock teams when you’re stretched.

How to do this:

  • Start with flow charts or user flows. These let backend teams begin work while you’re still figuring out UI details.
  • Provide sketches next if they need clarity on the exact flow.
  • Deliver polished UI last, when it becomes relevant for implementation.

A flow chart might unlock 50% of backend work and takes an hour to create. Twenty polished screens take much longer. Do the math on what unblocks your team fastest.

The pitfall: Sometimes during the UI phase you’ll discover you need more backend work than planned. It happens, but it’s rarely catastrophic. The time you save by unblocking teams early is usually worth it.

Only use this when you’re genuinely stretched thin. It’s emergency relief, not a permanent working style.

Manage your calendar like your design time depends on it

Because it does.

How to do this:

  • Decline non-essential meetings without explanation. If someone really needs you there, they’ll follow up.
  • Avoid fragmented meeting slots. If someone books 2:00-2:30pm and another meeting lands at 3:00-3:30pm, you’ve got a useless gap. Ask to reschedule or pull yourself out.
  • Block protected deep work time and set it to auto-decline meeting invites. Do this during your most productive hours.
  • Make people justify overriding your blocked time. Most won’t bother.

One more thing: AI isn’t replacing you, but it can help you move faster

AI won’t design your product for you. But it can keep you moving when you’d otherwise be stuck.

How to use it:

  • Bounce ideas off ChatGPT or Claude when you can’t grab time with your PM. Use it as a thinking partner to get a first pass when you’re blocked.
  • Let it make sense of data quickly. Designers often avoid data work, but AI handles it well.
  • Use meeting note tools like Granola to auto-summarize conversations so you’re not scrambling to remember what was said.

The goal isn’t to replace collaboration—it’s to eliminate the friction that stops you from making progress.

The reality

Working as a lean design team is hard. There’s no sugar-coating that.

But you’re not failing if you can’t do everything at once. You’re just in a situation that requires different tactics than the “one designer per team” setup you might have been trained for.

Start with one framework. Try distributing decision-making context this week. See what changes. Then layer in the others as you build momentum.


Looking for more? Here's how I can help:

Have a topic you'd like me to write about? Reply to this email and let me know! I read every reply.

🖼️

Follow me on Instagram

Get a daily dose →

🎥

Subscribe on YouTube

See it in action →

📘

Follow me on LinkedIn

Never miss a post →

Join 40,000+ designers moving from execution to influence

Biweekly strategies for product designers ready to move from execution to influence. Learn frameworks for stakeholder management, getting ideas approved, and advancing to senior roles.