A bad design partner is worse than no design partner. That sounds harsh, but it is true. When you have no feedback, you rely on your own judgment and move fast. When you have feedback that is vague, contradictory, or simply wrong, you slow down, second-guess real decisions, and ship something nobody wanted.
This article gives you a framework for making the call.
What Useful Feedback Actually Looks Like
Before you can judge whether your design partner is giving you bad feedback, you need a baseline for good feedback. Good feedback is specific, tied to user behavior or business goals, and tells you what problem exists, not just what the solution should be.
An example of useful feedback: "The onboarding flow has five steps before the user sees any value. Our activation benchmark is under three minutes, and this will blow past it."
An example of bad feedback: "This feels a bit off. Can we make it more premium?"
If most of what you hear sounds like the second example, that is your first signal.
The Three Warning Signs
Feedback is consistently vague or aesthetic. If your partner keeps commenting on colors, fonts, and general "feel" without connecting any of it to user outcomes or conversion goals, they are not doing design critique. They are doing personal taste. Personal taste at the founding stage costs you weeks.
Feedback arrives too late to act on. A design partner who reviews work after decisions are already baked in is not a partner, they are a critic. If you consistently find yourself receiving notes after a sprint closes or after a handoff to engineering, the relationship is structured wrong and that rarely fixes itself on its own.
Feedback contradicts itself across sessions. One week the partner wants simplicity. The next week they want more features on the screen. This pattern usually means they are reacting to whatever reference they most recently saw, not operating from a consistent product philosophy. Inconsistent feedback creates an inconsistent product.
How to Run a Diagnostic Conversation
Before you fire anyone, give the relationship one structured test. Schedule a 45-minute working session, not a review meeting. Bring three specific open questions: one about navigation logic, one about a conversion drop-off you have identified, and one about a feature you are unsure whether to cut.
Watch what happens. Does your partner engage with the underlying problems, or do they jump straight to solutions? Do their answers connect to your users and your metrics, or do they feel borrowed from a portfolio project they did two years ago?
If you leave that session with clear direction on at least two of the three questions, the relationship has potential. If you leave more confused than when you arrived, you have your answer.
The Sunk Cost Trap
Most founders wait too long to end a design partnership because they are mentally accounting for what they already spent, whether that is money, time, or social capital from an introduction. Sunk cost is not a reason to continue a relationship that is producing bad outputs.
Ask yourself this instead: if you met this person today and saw exactly the feedback they have given you over the past two months, would you bring them on? That question cuts through the history and forces you to evaluate the actual value being delivered right now.
When the Problem Is Structural, Not Personal
Sometimes the feedback is bad not because the person is incapable, but because the engagement is set up poorly. A designer who reviews static mockups once a week cannot give you useful feedback on interaction flow. A partner who has never spoken to one of your users cannot give you useful feedback on onboarding.
Before making a final decision, ask whether a structural change, more context sharing, a user interview session together, or a different cadence, could meaningfully improve the output. If yes, try it for two weeks with a clear expectation on both sides. If the output does not improve, the structural fix was not the real problem.
How to End It Cleanly
When you decide to move on, be direct and specific. Do not say "this isn't working out." Say something like: "The feedback we have been getting is not connecting to user behavior or our product metrics, and we need to work with someone who can operate at that level."
This is not cruel. It is honest, and it gives the other person information they can actually use. Vague exits feel kinder but they leave both parties without closure and sometimes invite negotiations you do not want to have.
If the partnership was paid, honor whatever terms you agreed to. If it was advisory equity, check your vesting schedule and have a lawyer confirm your options before the conversation.
The Practical Takeaway
Audit the last ten pieces of feedback you received from your design partner. Write down how many of them you could connect to a specific user problem or a measurable product goal. If fewer than half clear that bar, you already know what to do. Set up the diagnostic session this week, give it two weeks if the structure is the problem, and if nothing changes, make the call and move on.