Bundle any two guides and save up to €8 · See the deal →

21 July 2026

·

How to Work With a Designer Who Has a Very Different Style

Design teams are rarely full of people who think alike. Here's how to collaborate well with someone whose approach is nothing like yours.

Every design team has at least one pairing that shouldn't work on paper but somehow does, or should work on paper but somehow doesn't. The difference is rarely about talent. It's almost always about how two people navigate their differences.

Designers with very different styles can produce excellent work together. They can also spend most of their time in low-grade friction, producing something neither of them is fully proud of.

Here's how to make the first thing happen instead of the second.

Name the difference early

The most common mistake is assuming you'll figure it out as you go. Two designers with different approaches start working together, and gradually small frictions accumulate into a real problem. By the time it's addressed, there's resentment built in on both sides.

The better approach is to name it early and directly. "I tend to be more structured in how I approach problems, I like to define the question before I start sketching. I get the sense you work differently. How do you usually like to start?"

This isn't confrontational. It's just honest. And it starts the relationship with the assumption that you're both going to have to adjust, rather than that one of you will eventually convert the other.

Separate style from quality

One of the harder things in design collaboration is separating "different from how I'd do it" from "worse." They're not the same thing.

A designer who starts with aesthetics before nailing down the structure is working in a way that would drive some people mad. It might also produce outcomes that are more visually interesting than they would have been otherwise. A designer who spends three days on discovery before touching Figma might seem slow. They might also be solving the right problem because of it.

When you're evaluating a collaborator's work, ask yourself honestly: am I reacting to the approach or to the outcome? If the outcome is good, the approach might just be different, not wrong.

Find the handoffs that work

Not every collaboration needs to be fully joint. Sometimes the best structure is to identify where your strengths complement each other and divide the work accordingly.

If one designer is stronger at the ambiguous early phase and the other is stronger at detailed execution, that's a natural split. If one of you is better at stakeholder communication and the other at user research, structure the project so each person does more of what they're good at.

This isn't avoidance. It's efficiency. And it usually produces better work than both people trying to do everything in the same way.

Have a tiebreaker system

At some point you're going to disagree on something that matters. The question isn't whether that happens but what you do when it does.

If you haven't agreed upfront on how you'll resolve disagreements, you'll default to whoever is louder, more senior, or more persistent. None of those are great selection criteria for design decisions.

A simple approach: agree that the person who is most responsible for a given part of the work gets the deciding vote, and they're required to hear the other person's concern and respond to it specifically rather than overriding it. That's not perfect, but it's fairer than the alternative.

Take the disagreements to the work, not the person

The most productive design collaborations are ones where disagreements are about the work rather than about the people involved.

"This doesn't solve the problem we said we were solving" is a design disagreement. "I always have to redo everything you touch" is a personal one. Keep your critiques in the first category.

When things are getting personal, even slightly, it usually means the process has broken down somewhere. Not enough alignment at the start, not enough shared understanding of what good looks like. Fix the process problem rather than trying to fix the person.

Some combinations don't work regardless

It's worth acknowledging that some collaborations are genuinely not a good fit. Not because either person is a bad designer or a bad person, but because the specific combination of approaches, personalities, and working styles creates too much friction for the output to justify.

If you've tried the above things and a collaboration is still consistently producing more friction than work, that's useful information. It might mean structuring things so you work more independently and review each other's work rather than co-designing. It might mean involving a third person as a tiebreaker. It might mean escalating to a manager.

Not every pairing works. Knowing that early and acting on it constructively is better than grinding through months of low-grade misery.

Found this useful?Share on LinkedInPost on X

Get the free Promotion Readiness Checklist

A one-page self-assessment used by designers 3–7 years in.

Want to go further?

The guides go deep on everything covered here, with practical frameworks and checklists you can use straight away.

See the guides →

30-day money-back guarantee

← Back to blog