How to diagnose a stalled agency engagement
By Joel Andren · Published by PressFriendly, a PR agency · Reviewed July 15, 2026 · 2 of 5 in this section
Treat underperformance as a system diagnosis before assigning fault. Audit the objective, company inputs, strategy, execution, staffing, measurement, and external conditions against the signed scope. The same method works when the operator is a founder, internal team, freelancer, or agency, although contractual responsibility changes the available remedy.
Ownership follows control and evidence
| Area | Evidence to inspect | Typical owner |
|---|---|---|
| Business priority and communication objective | Current plan, baseline, target, and decision history | Company, developed with the operator |
| Facts and access | Approved claims, data, customers, experts, spokespeople, and response times | Company |
| Strategy | Audience choice, narrative, channel mix, timing, assumptions, and changes | Operator and company together |
| Execution | Research, drafts, targeting, outreach, preparation, follow-up, and corrections | Operator named in the scope |
| Staffing and governance | Named roles, review, availability, approvals, backup, and escalation | Both sides within their commitments |
| External conditions | Editorial decisions, news cycle, regulation, market events, and third-party delays | Neither side controls them |
| Measurement | Definitions, instrumentation, reports, causal limits, and learning | Named measurement owners on both sides |
Do not assign a shared area to one side merely because the outcome was weak. Use the artifact and commitment that establish who controlled the failed step.
Inspect quality before counting activity
Review representative work, not only a summary total. Ask:
- Did the target rationale match the objective and audience?
- Were messages accurate, specific, and supported by proof?
- Did the team tailor the work to the channel and recipient?
- What qualified responses or audience signals appeared?
- What did the team learn, and how did the next version change?
- Did either side miss a dependency or service level in the scope?
A full activity log with weak results can indicate a story, targeting, quality, timing, or measurement problem. A thin log can reflect missing capacity, an agreed narrow strategy, blocked client inputs, or incomplete reporting.
Write one root-cause statement
Use this format:
[Evidence] indicates that [step in the result chain] is underperforming because [supported cause]. [Owner] will test [change] by [date], using [measure].
If the evidence supports several causes, rank them and test the least expensive reversible change first. Examples include clarifying the objective, supplying proof, changing an approval path, revising the story, narrowing the audience, replacing a team member, or fixing instrumentation.
Set a corrective review with a real decision
The review period should match the work cycle and external lead time. Define the work, quality threshold, owner, company dependency, evidence, and decision at the end. Do not require guaranteed coverage as the recovery target.
Move directly to contractual or specialist advice when the issue involves deception, confidentiality, safety, security, discrimination, harassment, an undisclosed conflict, or another material breach of trust. For performance problems that remain recoverable, decide whether to pause, renegotiate, or end the engagement after the corrective review.