Paid media thread load by rep

Slack thread ownership across the partner-request channel and the internal QA channel.

Apr 15 – Jul 14, 2026  ·  91 calendar days  ·  65 workdays (weekends excluded)  ·  Prepared for Jess Parsons & Rachel Instone

The two channels are counted and reported separately. They measure different work under different ownership conventions, and the numbers are not additive.

Team leads (Jess, Rachel Instone, Rachel Bentley, Noah) and Partner Success staff are excluded from all counts. The 12 reps counted: Corey Sechrist, Tyler Beltz, Mayde Sierra, George Shaba, Aidan Tucker, Joe Blagrave, Sawyer Bergey, Tyler Barchek, Laura Ware, Erick Lopez, Daniela Huerta, Megan McInroy.

Channel one
#paid_media  ·  partner requests

Partner request threads

Partner Success posts Partner | Topic and @-tags the rep(s) who own it — usually two, one for Google and one for Meta. That tag is the assignment.

Threads
683
With an owner
626
Assignments
1,034
Threads/workday
10.5

Threads owned — 90 days

George Shaba
127
Joe Blagrave
108
Laura Ware
107
Corey Sechrist
101
Erick Lopez
97
Aidan Tucker
91
Mayde Sierra
90
Megan McInroy
80
Daniela Huerta
80
Tyler Beltz
79
Tyler Barchek
43
Sawyer Bergey
35

Full detail

RepThreadsThreads/dayRepliesReplies/dayReplies/thread
George Shaba1271.951,32120.310.4
Joe Blagrave1081.661,37221.112.7
Laura Ware1071.6586013.28.0
Corey Sechrist1011.551,79627.617.8
Erick Lopez971.491,16617.912.0
Aidan Tucker911.401,03716.011.4
Mayde Sierra901.381,01515.611.3
Megan McInroy801.2375711.69.5
Daniela Huerta801.2380312.410.0
Tyler Beltz791.2287113.411.0
Tyler Barchek430.663134.87.3
Sawyer Bergey350.545097.814.5

Insights — partner request threads

  • Load spans 3.6x across the team. George owns 127 threads; Sawyer owns 35 and Tyler Barchek 43. That is a structural gap, not week-to-week noise.
  • Reply volume reorders the top. Corey is 4th on thread count but 1st on replies by a wide margin — 1,796 replies at 17.8 per thread, 32% ahead of the next rep. George is the opposite shape: most threads, but they close fastest (10.4 replies each). George is running a high-throughput queue; Corey is absorbing the escalations. Those are different jobs and should probably be resourced differently.
  • Sawyer's low count is misleading. Lowest thread volume on the team but 2nd-highest intensity at 14.5 replies per thread. He is on fewer, heavier engagements — not underloaded.
  • Tyler Barchek is light on both axes. 0.66 threads/day and the lowest replies-per-thread on the team (7.3). He is the only rep who is low on volume and intensity — every other low-count rep is heavy somewhere else.
  • The bottom two are trending down. Month over month, Barchek went 17 → 16 → 10 and Sawyer 12 → 13 → 10. The gap is widening, not closing.

Questions this raises: Is George's volume sustainable, or is he the default assignee? Should escalation-heavy accounts (Corey's) count differently against capacity than routine-request accounts? And are Barchek and Sawyer deliberately staffed lighter here — or drifting?

Method. Ownership taken from the @-mention in the parent message; mentions after "cc" or "FYI" were not counted as ownership. Verified against a 10-thread sample: in 7 of 8 threads with a tagged rep, that rep did the work, and work was essentially never silently reassigned.

Reply counts include all thread participants, so they measure thread complexity, not a rep's own message output. Multi-rep threads credit the full reply count to both owners, which is why replies sum above the channel total.

Channel two — separate data
#paid-media-internal  ·  QA

Internal QA threads

A "QA Needed" bot posts the request. Every thread has a submitter (the rep whose work is checked) and a reviewer (the rep who checks it). Both are real load, so both are counted.

Threads
166
QA reviews done
120
Threads/workday
2.6
Workdays
65

Submitted for QA vs. QA reviews performed

Submitted for QA QA reviews performed
Laura Ware
40 / 4
Mayde Sierra
26 / 19
George Shaba
26 / 3
Megan McInroy
15 / 14
Joe Blagrave
12 / 14
Corey Sechrist
11 / 6
Erick Lopez
11 / 5
Tyler Barchek
10 / 5
Daniela Huerta
7 / 13
Aidan Tucker
7 / 16
Tyler Beltz
4 / 12
Sawyer Bergey
2 / 13

As submitter — work put up for QA

RepThreadsThreads/dayRepliesReplies/dayReplies/thread
Laura Ware400.621692.64.2
Mayde Sierra260.401081.74.2
George Shaba260.401001.53.8
Megan McInroy150.23831.35.5
Joe Blagrave120.18490.84.1
Corey Sechrist110.17621.05.6
Erick Lopez110.17450.74.1
Tyler Barchek100.15440.74.4
Daniela Huerta70.11320.54.6
Aidan Tucker70.11250.43.6
Tyler Beltz40.0630.050.8
Sawyer Bergey20.03120.26.0

As reviewer — QA actually performed

RepReviewsReviews/dayRepliesReplies/dayReplies/review
Mayde Sierra190.29741.13.9
Aidan Tucker160.25550.83.4
Megan McInroy140.22731.15.2
Joe Blagrave140.22881.46.3
Sawyer Bergey130.20691.15.3
Daniela Huerta130.20460.73.5
Tyler Beltz120.18520.84.3
Corey Sechrist60.09200.33.3
Erick Lopez50.08250.45.0
Tyler Barchek50.08210.34.2
Laura Ware40.06150.23.8
George Shaba30.05110.23.7

Insights — internal QA

  • This is a supplementary load, not a primary one. 2.6 threads/day here vs. ~10.5 in the partner channel. Nobody's week is defined by this channel — but the imbalances inside it are sharp.
  • Give-and-take is not reciprocal. Laura submits 40 items for QA and reviews 4 — a 10:1 ratio. George is 26:3. At the other end Sawyer is 2:13, Tyler Beltz 4:12, Aidan 7:16. The reps generating the most QA-able work are doing almost none of the checking, and vice versa.
  • Mayde carries both sides. 26 submitted and 19 reviewed — top of the reviewer table while still 2nd on submissions. She is the only rep heavy on both.
  • Unassigned QA is being absorbed by a volunteer. Many QA posts ping the usergroup with nobody named. Mayde picked up 9 such unclaimed requests in the last month alone. That is a routing gap currently papered over by one person's goodwill.
  • The rankings invert versus the partner channel. George is #1 on partner threads but 11th of 12 on QA reviews. Sawyer is last on partner threads but 5th on QA reviews. Judging capacity from either channel alone gives the wrong answer.

Questions this raises: Is there meant to be a QA rotation, and if so is it being followed? Should QA reviews be explicitly assigned rather than posted to the group and left to be claimed? And should reviewing count toward a rep's capacity the same way partner threads do?

Method. Reviewer = the rep who actually delivered the QA verdict in-thread (posted the QA tracker link, "QA is done", listed errors/fixes) — not merely whoever was tagged. This matters, because many QA requests are posted to the usergroup with nobody named and a rep volunteers. Because this required reading verdicts, treat reviewer counts as ±2.

Rachel Instone performed the QA in 12 threads. She is excluded from the counts per the brief, so the 120 reviews understate total QA throughput in this channel.