Tell me about a time you had a mission critical disagreement with a cross-functional colleague.

Question

Anonymous · Accepted Answer

One of the harder Product disagreements I had at TikTok was around a Virtual
Try-On ads product that used AI-generated creative.

We were moving from alpha into a broader beta, and I had actually helped define
the alpha exit criteria with the Senior Global PM. So this wasn’t me coming in
from the outside and saying Product had set the wrong bar.

By the criteria we had agreed on, the alpha worked. The assets were generating
reliably, engagement and conversion performance were roughly in line with or
better than standard creative, and technically we had cleared the threshold to
expand.

Then I started hearing something in direct advertiser interviews that our
performance metrics and post-alpha surveys weren’t capturing.

Apparel advertisers were telling us that even when the ads performed, they
didn’t always feel comfortable having the creative represent their products.
They were calling out things like fabric texture, fit, and realism. The product
might have looked acceptable to a consumer in-feed, but for a brand that is
highly sensitive to how its product is represented, that was a very different
standard.

The uncomfortable part was that I had helped write the rules we had just passed.

So when I went back to the Senior PM and said I didn’t think we should expand
apparel into the broader beta yet, her pushback was completely reasonable.

We had aligned on the exit criteria. We had met them. Creative quality is
inherently subjective. The product was performing. And she didn’t want to slow
down the entire alpha-to-beta transition because one subvertical had a higher
creative-quality bar.

And honestly, I agreed with most of that.

Where I disagreed was on what the alpha had actually proven.

I wasn’t arguing that the technology had failed or that the performance data was
wrong. I was arguing that our definition of success was incomplete.

And I didn’t want to take one or two unhappy customer comments back to Product
and ask them to change course, so I treated the feedback as a hypothesis.

I immediately went back to the other apparel advertisers in the alpha and did
deeper post-test interviews to understand whether this was isolated or whether
there was a real pattern.

The pattern held.

The issue wasn’t performance. It was trust and brand acceptability.

These advertisers weren’t saying, “This ad won’t convert.” They were saying,
“I’m not comfortable letting this represent my product.”

That gave me a much stronger basis for the conversation with Product.

I went back and said, essentially: we cleared the bar we agreed on, but the
alpha taught us that we didn’t set the complete bar for this segment. Passing a
performance test isn’t necessarily the same thing as being market ready.

The breakthrough was realizing this didn’t need to be a binary launch decision.

Rather than hold the entire beta, I proposed that we preserve the learning
velocity Product wanted and move forward in lower-risk categories like beauty,
accessories, and simpler products, while holding back the more brand-sensitive
apparel use cases and giving the model team more time to improve fabric
rendering, fit, and overall product realism.

I also pushed us to add explicit creative-quality and brand-acceptability
criteria alongside the quantitative performance metrics, so we weren’t relying
only on engagement and conversion as proof of readiness.

That let us keep the broader roadmap moving without asking advertisers to absorb
a level of brand risk they weren’t comfortable with.

The model quality improved, apparel later moved into beta successfully, and it
also changed the relationship with the PM.

What built trust wasn’t that I “won” the disagreement. It was that I didn’t
bring Product an anecdote and ask them to slow down. I acknowledged the data
supporting their position, validated whether the market concern was real, and
came back with a narrower recommendation that preserved velocity while
addressing the actual risk.

The biggest lesson for me was that exit criteria are hypotheses, not contracts.

You align on the best definition of success you have at the beginning, but good
Product partnership means being willing to update that definition when the
market teaches you something you couldn’t have known beforehand.

And that changed how I think about PMM’s role with Product.

The goal isn’t to give Product more feedback. It’s to give them better context
for the decisions only they can make.

Anonymous · Answer

SITUATION

> During our hackathon, we were building Namma Voice, a citizen grievance
> reporting platform. A disagreement arose between me (focusing on product
> decisions) and one of our developers. We had limited time, and we disagreed on
> what to prioritize for the MVP.

TASK

> The developer wanted to spend time implementing advanced AI-based issue
> categorization because it was technically impressive. I believed our biggest
> risk wasn't the AI—it was whether users could quickly report an issue with
> minimal friction. Since the demo deadline was approaching, choosing the wrong
> priority could affect the success of the project.

ACTION

> Instead of debating opinions, I proposed that we evaluate both ideas based on
> user value, implementation effort, and the likelihood of improving the demo
> experience. We realized that a simple reporting flow with photo upload and
> location capture addressed the core user problem, while AI categorization
> could be added later. We agreed to build a basic rule-based categorization for
> the MVP and keep AI as a future enhancement. Throughout the discussion, I
> focused on the product goal rather than proving my idea was right.

RESULT

> We completed the MVP on time, demonstrated a smooth end-to-end user journey,
> and had a clearer roadmap for future AI enhancements. The experience taught me
> that resolving disagreements through evidence, prioritization, and shared
> goals is much more effective than arguing based on personal preferences.

Tell me about a time you had a mission critical disagreement with a cross-functional colleague.

Practice this question with AI

Go Premium

Community Answers

Unlock Full Access

Unlock Full Access

Practice More Questions