The setting
makes software for watching how computer systems are running. is its hosted platform for collecting, searching, displaying and alerting on metrics, logs, traces and profiles, so customers do not run their own tools.
The next campaign test must be fast enough to matter and grounded enough to trust.
Campaign speed protects the follow-up window, while source-linked evidence protects the technical relevance of the next message.
Who you’d be doing this for
“I joined for the incident story, then the follow-up was about features I’m not even evaluating.”
Joko Le · Site Reliability Engineering Manager · a character in this brief
An existing customer evaluating whether to expand its observability coverage across additional services.
What is at stake
SRE leaders are registering for events but taking follow-up meetings at uneven rates. You must decide whether AI recommends the next test from linked evidence or leaves competing interpretations for strategist review.
Why it isn’t already fixed
Every obvious fix costs something else. That’s the part you’d have to decide.
- one next test vs several open questions
- follow-up depth vs registration volume
- technical relevance vs broad engagement
- reusable workflow vs campaign-specific nuance
Why Grafana
Grafana Cloud lifecycle campaigns must connect observability evidence to the SRE and platform engineering leaders evaluating broader adoption.
Written with these in mind
Not your kind of problem? 28 more at Grafana, or browse every organization.
Where the organization context comes fromThe postings this brief was written from, and the reporting read before it.
The organization context comes from public information. The situation and characters are written for the brief.
Job postings it was written from
Public descriptions of the work at Grafana. They are listed as sources, not as openings.
- Senior Product Marketing Manager | Spain | Remote (opens in a new tab)
- Principal Technical Marketing Engineer | US | Remote (opens in a new tab)
- Principal Technical Marketing Engineer | Ireland | Remote (opens in a new tab)
- Senior Product Marketing Manager | Germany | Remote (opens in a new tab)
- Principal Technical Marketing Engineer | UK | Remote (opens in a new tab)
This is the setup. The work is inside.
Running it puts you in the room: the full situation and its constraints, stakeholders who push back in their own words, and the decisions that are yours to make. What you produce becomes a Day One Plan — work you can show someone instead of describing.
Where similar work appears
Other live briefs connected to this one, and what connects them.
Similar problems at other organizations
Like this one, each of these is about people starting something and never quite finishing it.
Strong signup campaigns are producing uneven funded and payment-active accounts.
You must decide whether the system or the strategists judge if a Segment identity join is sound enough for a next-test recommendation to appear.
Agency partners need a next creative brief, yet Meta and TikTok point to different learner quality signals.
You have to decide what the system recommends and what strategists must verify before acting.
Travelers reach price details after a value message and still leave without booking.
You must decide where the system's next-test recommendation ends and the strategists' choice of message, audience and spend begins.
The same setting, from another role
Each is set around Grafana’s Grafana Cloud, written for a different role. They’re separate briefs, not the same scenario.
OpenTelemetry onboarding feedback is being interpreted as separate Beyla, Collector, and attribution issues.
You must decide who groups the comments into themes and who confirms, from the original research reads and customer conversations, that a theme is one recurring complaint.
Tenant SLO-burn alerts must reach a reviewed severity decision in under 10 minutes for 80% of the pilot.
You must decide where the system's evidence assembly for a suggested severity ends and the on-call engineer's own reading of the tenant's Mimir, Loki and Tempo signals begins.
Alert-evaluation investigations must produce engineer-confirmed causes within 20 minutes in 70% of pilot cases.
You have to decide where the trace across Prometheus, Loki, Tempo and Kubernetes hands over to the on-call engineer who names the cause and ships the fix.
Other problems with a similar purpose
In each of these, as in this one, the aim is to find the real question hiding behind incomplete evidence and choose a reversible next step instead of guessing.
Product managers read homeowner, pro and metric evidence on urgent repairs separately and reach different conclusions.
You have to decide where the AI's clustering of that evidence stops and a product manager's framing of the problem begins before a test is shaped.
A major advertiser may move $1.5 million after finance disputes whether reported sales were incremental.
You must weigh a compelling cross-format growth case against the evidence each claim can support.
A 4,000-seat business program may not renew because executives dispute what learner progress proves.
You have to weigh a fast commercial save against claims the evidence cannot support.
