American Extractions — Google Ads Campaign Accountability

Overview

During the September 30 ops sync, the American Extractions account surfaced as a concrete example of a recurring accountability problem: a client with an explicit, repeated need (lead generation) had ads that were not running — and remained not running for over a week after the issue was identified and escalated. The incident prompted a broader discussion about task follow-through, escalation responsibility, and consequences for non-delivery.

This article captures the incident, the root cause analysis discussed, and the process expectations that were reaffirmed as a result.

The Incident

Client need: American Extractions had been consistently communicating for weeks that they needed leads.
Issue identified: Mark reviewed the account and found the ads were not running. He flagged this and directed the team to get the ads live.
One week later: The ads were still not running. No update had been provided. The client sent a complaint ("nasty gram") on Friday.
Result: A client relationship was put at risk due to internal inaction, not a lack of clarity about what needed to be done.

"American Extractions has said continually for weeks, we need leads. We need leads. Then I go in there last week and the ads aren't running. And I said, well, you need to get these ads on. I come back a week later, the ads are still not running."
— Mark Hope

Root Cause Analysis

1. Task ownership was unclear or unenforceable

The ads not running was identified by Mark, not by the account team. Gilbert (the assigned resource) had not flagged the issue proactively, and no one had confirmed resolution after the initial directive.

2. No verification loop

After a task is assigned, there was no mechanism to confirm it was completed — or to escalate if it wasn't. The expectation that account managers would "go in and make sure things are running" was not being met consistently.

3. Accountability without consequences

The team acknowledged that tasks were being assigned but not completed, and that this pattern had been discussed before without meaningful change. Mark explicitly raised the need for consequences:

"They need to understand there's consequences to not doing your freaking job. If you tell somebody to do something, they don't do it — that's the same thing as not doing your job."

Process Expectations Reaffirmed

The following expectations were made explicit during the meeting:

Expectation	Owner
When a task is assigned, it must be completed — not acknowledged and deferred	All team members
Account managers are responsible for verifying that work is actually live/running, not just assigned	Account managers
Specialists (e.g., Gilbert) must proactively flag when something isn't working or isn't live	Specialists
Urgent client-facing issues (ads not running, deliverables missing) are not deferrable	All team members

Broader Pattern

This incident is not isolated. The same ops sync surfaced a parallel example: landing pages being marked done by Ben without being moved to internal review, making them invisible to Melissa and the broader team. The common thread is task completion theater — work being nominally "done" without the downstream steps that make it actually useful.

The ClickUp implementation (currently delayed) is intended to create visibility into task status and reduce these gaps. See ^[1] for current progress.

^[2] — Source meeting; also covers ClickUp delays, account coordinator roles, and AI tool best practices
^[1] — Workflow tooling intended to address task visibility gaps
^[3] — Proactive health monitoring sent to account managers the same week

Key Takeaway

When a client has a clearly stated, urgent need and the internal team has been explicitly directed to act, failure to complete and confirm that action within a reasonable timeframe is a client relationship risk — not a minor process miss. The American Extractions situation illustrates that accountability requires both clear ownership and a verification step to confirm completion.