Cross-functional scenarios
Describe a time you had to navigate a significant disagreement between your product and marketing teams about how to position a feature.
Present both positions as reasonable, then describe how you moved the argument from opinion to customer evidence, ideally a test both teams watched. Show how the final positioning kept the valid point from each side, who made the call, and how the relationship held up.
End with what you would do sooner, which is usually getting a customer into the debate earlier.
4 min read
Free 10-minute mock
Practice “Product and marketing disagree” free
Your first mock interview is free (10 minutes). No card needed.
What the positioning-disagreement question is scoring
Positioning arguments between product and marketing are rarely about right and wrong. The product manager is usually right that the technical detail matters to someone. The marketer is usually right that it shouldn’t lead. A PMM’s contribution is a neutral way to decide, and a result both teams can live with.
On the rubric, navigating disagreement productively is part of Strong cross-functional influence. The Exceptional signal is that both teams come to you earlier the next time a positioning call is coming, because they have learned you will find a fair way to settle it.
What each side of a positioning fight wants
| Side | Their stake | What moves them |
|---|---|---|
| Product manager | Accuracy, credit for hard engineering work, and not overpromising | Seeing the technical story kept somewhere visible, and evidence from technical users |
| Marketing or brand lead | Clarity for a broad audience and consistency with the brand | Evidence that the benefit framing converts |
| Engineering | Not being misdescribed | A chance to review claims before launch |
| Leadership | A decision soon | A clear owner, a date, and a way to settle it |
Say both positions in their strongest form before you say what you did. If you can’t state the side you disagreed with fairly, the panel will assume you couldn’t in the room either.
A note-taking app example of settling a positioning fight
“We were launching offline sync for a consumer note-taking app. The PM wanted the announcement to lead with the new sync engine, rebuilt from scratch, because it had taken his team a year. Our brand lead wanted it to say your notes are on every device, even with no signal. Both were reasonable, and we had gone in circles for two meetings. I suggested we stop debating and test. We ran both versions of the in-app announcement for a week, split evenly, and I did twelve calls with heavy users. The benefit version drove about twice as many people to turn sync on. On the calls, though, the heavy users all asked what happens when two devices edit the same note, and they only trusted it after hearing how the engine handled that. So the announcement led with the benefit, and the PM and I wrote a short post on how sync works, linked from it, with his name on it. He felt his team’s work was seen. My mistake was letting two meetings pass before proposing the test.”
The final positioning avoids a compromise headline. Each side’s valid point got a place where it did its job. The benefit leads, and the technical story sits where the people who need it will look.
Where positioning-disagreement answers go wrong
The facilitator with no view
“Product and marketing had very different ideas, so I brought both sides together and facilitated a discussion. I made sure everyone felt heard, and we landed on a compromise that worked for both teams.”
Diplomacy matters, and this describes many real meetings. It never says what the disagreement was, how it was decided, or what the compromise said. Name both positions and the evidence that settled it.
Splitting the difference in the headline
Combining both ideas into one headline, such as a benefit plus the engine name, usually weakens both. Panels with positioning experience will notice. Separate the jobs instead.
Winning for marketing
A story where marketing’s framing wins and product’s concern disappears reads as partisan. Panels notice. Show where the PM’s point ended up.
Follow-ups on a positioning disagreement
| Possible follow-up | They are checking | Try this |
|---|---|---|
| What if the test had favored neither side? | Whether you have a way to decide without data | Describe falling back on the target segment and the owner’s call |
| How do you handle a PM who won’t accept customer data? | Persistence without escalation | Say you would ask what evidence they would accept and gather that |
| Who made the final call? | Clarity about ownership | Name the role, even if it wasn’t you |
| Did the relationship change afterward? | Durability | Give a later moment when the PM brought you in early |
More questions in this category
Frequently asked questions
- Should I take a side in the story?
- Only if the evidence did. It is often stronger to play the person who found the evidence, since that is the PMM’s real contribution to the argument.
- What if there was no time to run a test?
- Use existing evidence, such as sales calls, support tickets, or past campaign results, and say how you limited the risk of being wrong. A quick informal check with five customers is better than none.
- Is it a problem if my team lost the argument?
- No. Losing to better evidence and saying so plainly is a good story. Explain what the evidence showed and how you helped the other side’s version succeed.
Guides that help with this question
All guidesFree 10-minute mock
Practice “Product and marketing disagree” free
A Mokk session asks this question, follows up on your answer, and scores it on five competencies. Your first mock is 10 minutes, scored like a full interview. No card needed.
Your first mock interview is free (10 minutes). No card needed.
Practice “Product and marketing disagree” free
10 minutes · no card needed