TattvaDocs
Use casesPerformance marketing

Product-lag RCA

"SKU-A is 30% behind target. Why?" — the most-asked weekly RCA, with a logic tree that covers most of the usual causes.

Planned

This use case needs definitions that aren't in the Library yet (product targets). Until your data analyst adds them, Tattva can't answer it as shown here.

The question: "SKU-A is 30% behind target. Last time it was 10%. What happened, and what are we doing about it? Did the winning ads stop coming, or did the agency deliver fewer creatives?"

This is the "product is behind target" RCA: every product, every week, every review. The usual causes are predictable enough that a short logic tree covers most of them.

Who asks

  • Founders or the function head
  • The performance-marketing lead, explaining the number
  • The category lead, explaining the creative pipeline

Frequency

Weekly per product; daily during sale weeks.

Data you need

  • targets: monthly or weekly target per product
  • orders and customers: actuals, with the new-vs-repeat tag
  • ads and ad_creatives: the active creatives per product
  • creator_pipeline: planned vs delivered creatives per period
  • Notes on ad-platform events (algorithm changes, account issues), if you keep them

How to ask it

  • "SKU-A is 30% behind target this week. Find the cause: winning ads, creative supply, or platform issues."
  • "For each product more than 15% behind target this week, give me the main cause."
  • "Has SKU-A's share of winning ads dropped this week vs the last four weeks? By how much, and which creators stopped winning?"

What you'll get back

A focused RCA, not a chart dump (figures made up):

Headline: SKU-A is 30% behind target. Main cause: the share of winning ads fell from 28% to 11% week on week.

Top causes, ranked:

  1. Too few winning ads (most likely, about 72% of the gap): only 2 of last week's 18 active ads cleared the NRoAS threshold, against 7 of 18 the week before. The five that stopped winning all came from one batch of creatives made six weeks ago: they've run their course.
  2. Creative supply behind plan (about 18%): the agency delivered 4 new creatives against 10 planned, leaving ad sets under-supplied.
  3. Platform issues (the rest): nothing unusual detected this week.

Next steps:

  • Pause the five tired ads (see Ad action decisions)
  • Raise the creative-supply gap with the category lead
  • Re-check mid-week

The logic tree

Product behind target by more than X%?
├── Has the share of winning ads fallen?
│   ├── Yes (by more than 20%) → main cause: winners. List the tired ads.
│   └── No → continue
├── Is creative supply behind plan?
│   ├── Yes (by more than 30%) → main cause: agency / category. Escalate.
│   └── No → continue
├── Was there an ad-platform event in the period?
│   ├── Yes → noise; give the week-on-week comparison less weight
│   └── No → continue
├── Were last week's winners over-scaled (saturating audiences)?
│   ├── Yes → expected decline; a correction is normal
│   └── No → continue
├── Did the product's landing-page conversion drop?
│   ├── Yes → not a marketing issue; route to product / web team
│   └── No → continue
└── Is the target itself ambitious vs last month's run rate?
    └── If yes → discuss the target, not the RCA

Walk the tree with follow-up questions in the same session.

How to make it recurring

  1. Click Save as tracker on the answer, then Edit the question and pick weekly.
  2. For several products, click Add Question on the tracker and add one question per product ("Is SKU-B more than 15% behind target this week? Why?"). There are no tracker templates; each product is its own question.
  3. For each question, set the Classification rule to Relative delta on your revenue metric with critical if Δ > 15. A run is Critical when revenue moved more than 15% since the previous run, in either direction. The rule compares runs, not the target, so read the narrative for the gap to target.
  4. Add destinations on the Delivery tab so the team gets the runs before the weekly review.

When a product lags again, compare with last time: reopen earlier conversations from the Sessions drawer, or check the tracker's History tab, to see whether the cause is the same.

Pitfalls

  • Mistaking a bad week for a trend. One −30% week may be a miss, not a structural problem. Read the last four weeks, not just this one.
  • Blaming the agency by default. Sometimes creative supply is the real cause; sometimes it's a convenient story. Let the figures rank the causes.
  • Ignoring the target. If a product has missed every week for two months, the target is wrong. Raise that instead.
Product-lag RCA — Tattva Docs