Connect mobile-growth findings to creative and app work

Why use this

1. A mobile team may identify acquisition changes in one tool and product friction in another, then lose the connection when writing creative briefs or engineering requests. A promising correlation can become an unjustified explanation during that handoff.

2. This job could turn approved analysis into traceable test ideas and implementation questions. Each proposal can retain the evidence, competing explanations and measurement needs that a human team should review before spending or changing the product.

Why an agent / simpler alternative

Useful judgment

Connect acquisition and product signals, distinguish hypotheses from causes and adapt findings to creative versus engineering decisions.

Simpler alternative

Use a shared experiment template when the analysis and next action are already clear.

Unsuitable when

The workflow would optimize spending or ship product changes without approved objectives and human review.

Proposed inputs

1. Name

   Analytics extracts

   Owner

   Authorized growth owner

   Minimum scope

   Aggregate acquisition and product metrics for aligned periods

   Quality check

   Check attribution windows, definitions and missing events

2. Name

   Test brief

   Owner

   Product/growth lead

   Minimum scope

   Goals, constraints and approved evidence boundaries

   Quality check

   Separate target outcomes from observed results

Access and setup — proposed or unknown

Proposed minimum

1. Read scoped exports and draft handoffs; no advertising-account writes, production access or campaign spend.

Compatibility unknowns

1. Current connector access, cross-tool attribution consistency and exact runtime compatibility are unknown.

External actions requiring approval

1. Spending, campaign changes, sharing customer data, assigning engineering work or publishing creative requires approval.

Expected deliverable and review checks

Proposed artifact

Evidence-linked creative concepts and engineering specifications with assumptions and proposed measurement checks.

Critical checks

1. Trace recommendations to signals; align time windows; distinguish creative hypotheses from verified product defects.

Missing output evidence

This overlay adds no new output inspection, execution or validation; consult the referenced canonical source outcome limits.

Failure signals and proposed responses

1. Signal

   An attribution-window change looks like performance growth

   Why it matters

   The proposed action rests on measurement drift

   Proposed response

   Reconcile definitions before forming a test.

2. Signal

   A crash signal is generalized to all users

   Why it matters

   A narrow segment drives an oversized product conclusion

   Proposed response

   Bound the affected population and preserve uncertainty.

Effort and cost — unknown

Setup work

1. Define metric relationships and handoff standards.

Ongoing review

1. Review test hypotheses and observed results before further action.

Unknowns

1. Data quality, attribution limits, experiment effort and operating costs are unknown.

First check — proposed, unexecuted

Status

proposed_unexecuted

Synthetic fixture

Invent channel summaries and a product funnel with one changed event definition and one segment-specific error; draft two bounded test ideas.

Acceptance checks

1. Flag measurement changes; specify audience scope; keep causal claims tentative; authorize no spend or release.

Stop conditions

1. Stop if a handoff requires unapproved user data or unsupported causal conclusions.

Limits

1. A coordinated handoff does not establish campaign lift, product impact or a valid causal explanation.