Credibility
Competitive Positioning Analysts Respect vs. Dismiss: The Credibility Test
Strategy & Marketing Positioning Series
Explore why analysts dismiss unsupported competitive positioning, and how disciplined responses to difficult feedback can strengthen credibility, sharpen strategy and earn lasting respect.
Contributing Author
.avif)
Tammy Richards is a senior marketing and analyst relations leader with 25+ years of experience shaping global brands at Conga, Veeam, and Citrix. She specializes in transforming complex technology into clear, credible narratives that strengthen market position and accelerate growth. As Vice President of Operations & Delivery at Forward AR Experts, Tammy helps build a senior‑only AR firm powered by intelligence and AI—ensuring clients benefit from seasoned judgment, strategic guidance, and relationships that move the market.
Tammy Richards
VP of Operations & Delivery
Why Analysts Dismiss Competitive Positioning (and What Earns Respect Instead)
Every AR practitioner eventually delivers an analyst assessment that leadership doesn't want to hear: your product is behind on a capability, a competitor is perceived as stronger, the market has moved and your narrative hasn't.
What happens next determines whether the company's competitive positioning earns analyst respect or gets quietly dismissed. Too often, the internal reaction is to challenge the analyst's objectivity instead of examining the finding. That instinct is the single biggest barrier between an analyst relations program and real analyst credibility.
The Competitive Positioning Credibility Test: Four Tests Analysts Apply
Analysts don't dismiss competitive claims because they're inherently skeptical. They dismiss them when the positioning fails one of four tests. Positioning that passes all four earns respect. Positioning that fails any of them gets discounted.
1. The Evidence Test
Does the claim rest on proof, or on assertion? "We're the leader in X" is an assertion. "We've closed 40% more enterprise deals against Competitor Y in the last two quarters, and here's the win/loss data" is evidence. Analysts evaluate hundreds of vendors making similar claims; the ones that stand out are backed by something verifiable.
2. The Acknowledgment Test
Does the claim rest on proof, or on assertion? "We're the leader in X" is an assertion. "We've closed 40% more enterprise deals against Competitor Y in the last two quarters, and here's the win/loss data" is evidence. Analysts evaluate hundreds of vendors making similar claims; the ones that stand out are backed by something verifiable.
3. The Trajectory Test
Can the company show movement over time, not just a current-state snapshot? A gap that's been static for three years signals a company that isn't listening. A gap that's visibly closing, with specific milestones, signals one that acts on feedback. Analysts track vendors across cycles; trajectory is often more persuasive than any single data point.
4. The Translation Test
Is the AR function translating analyst feedback into internal action, or defending the existing narrative? When AR's role gets reduced to managing the relationship rather than managing what the company does with the input, the company stops improving and starts performing. Analysts can tell.
The pattern behind all four:
Analysts respect positioning that treats their assessment as a mirror, not an obstacle. Positioning that argues with the mirror is what gets dismissed.
How to Build Competitive Positioning Analysts Won't Dismiss
Separate the finding from your reaction to it.
When an assessment lands badly, the first instinct is to relitigate methodology or question objectivity. Before doing that, ask: even if the framing is imperfect, is there a signal underneath that customers might also be picking up on? Analysts are frequently a leading indicator of market perception, not a lagging one.
Build a structured feedback loop, not a one-time readout.
Translate every material finding into three categories: where you're validated, where a competitor is genuinely stronger, and what specific gap that creates. This becomes a living document product and leadership can act against, not an artifact of a single conversation.
Push for milestones, not intentions.
"We're aware of the gap" is not something AR can bring back to an analyst in six months. Attach real dates and scope to how a gap will close. Even directional milestones give AR something concrete to report, and give the analyst relationship a trajectory to track.
Bring competitive intelligence in before the assessment, not after.
Surface competitor positioning proactively so leadership hears about a competitive gap from AR before they hear it from an analyst report. This changes the dynamic from defensive to collaborative.
Run a mock evaluation before the real one.
An internal mock Wave or MQ ahead of an actual evaluation cycle surfaces gaps early enough to close them before they show up in the report customers see. It also creates a baseline: compare results against the eventual real evaluation and the gap between becomes evidence of trajectory, exactly what the Trajectory Test rewards. The exercise only pays off if leadership treats it as genuine learning rather than a rehearsal for defending the existing narrative.
Protect your credibility by not overselling.
If AR consistently packages every interaction as a win, leadership stops trusting AR's read on where the company actually stands. Calibrated reporting, genuine wins as wins, real gaps as gaps, is what earns AR the standing to be heard when a hard message needs to land.
In Practice: When the Organization Listens vs. When It Doesn't
I've seen this pattern repeat: an analyst delivers a review with substantiated critique, and the internal reaction is to label it biased or uninformed. The opportunity to close a real gap gets lost in the effort to discredit the source.
I've also seen the alternative. One organization ran a mock Wave ahead of the real cycle, inviting the same hard scrutiny on purpose. It surfaced honest gaps in a specific product and in how that product related to the broader platform story. The gaps sharpened direction rather than triggering defensiveness.
The harder part is what happens after gaps are named: whether product leadership takes action, or the findings quietly lose momentum. AR can surface where the company is strong, where competitors are stronger, and what the gap implies. AR cannot close product or narrative gaps alone. That's on product and leadership to set milestones and follow through.
Signals You're Losing Analyst Respect on Competitive Positioning
-
Internal reaction to critical findings defaults to disputing the analyst's objectivity rather than examining the substance.
-
Competitive gaps identified a year ago are described the same way today, with no visible trajectory.
-
AR's competitive positioning consists mostly of strengths, with no acknowledged weaknesses.
-
Product and leadership treat analyst feedback as AR's problem to manage, not an input to their roadmap.
-
AR finds out about a competitive gap from an analyst before having surfaced it internally.