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.
A discovered dependency map does not provide the same orientation as an experienced colleague.
New rotation members need a manageable route through a service, while experienced SREs do not want another guide to maintain.
Who you’d be doing this for
“I found the service, then spent half an hour asking someone which of those connections I should actually understand before Friday.”
Olumide Mensah · Backend Engineer · a character in this brief
Joining the on-call rotation for a service outside their usual area of work.
What is at stake
Six of eight engineers needed help understanding a service before on-call. You have to weigh a guided learning route against free exploration without creating another guide that experts must maintain.
Why it isn’t already fixed
Every obvious fix costs something else. That’s the part you’d have to decide.
- guided learning vs open exploration
- stable orientation vs changing dependencies
- service-specific relevance vs content upkeep
- completion rates vs demonstrated understanding
Why Grafana
Knowledge Graph discovers changing relationships from existing telemetry, so service orientation must work without a separately maintained inventory.
Written with these in mind
Not your kind of problem? 31 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 Designer, Knowledge Graph | Germany | Remote (opens in a new tab)
- Senior Product Designer, Knowledge Graph | Sweden | Remote (opens in a new tab)
- Senior Product Designer, Knowledge Graph | Ireland | Remote (opens in a new tab)
- Senior Product Designer, Knowledge Graph | Spain | Remote (opens in a new tab)
- Senior Product Designer, Knowledge Graph | Canada | 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 turns on easing someone in at the cost of understanding.
Six of eight interviewed engineers rebuild unfinished investigations through screenshots.
You have to weigh continuity inside a live session against an analyst's need for a clear, bounded starting point.
Nine of 14 replacement owners needed the tracker builder's help despite having access.
You weigh guidance that makes the first update safe against preparation that busy builders will actually finish.
Five of seven incoming benefits owners couldn't explain where member access questions belong.
You must weigh a focused handover against a broader service that prepares them to defend the benefit at annual planning.
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.
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.
Alerting customers are spending incident time reconstructing browser failures from disconnected evidence.
You must choose which browser-investigation story earns a scarce technical follow-up without overpromising the result.
Renewal-stage expansion acceptance fell from 18% to 9% after pricing conversations.
You must choose how directly the campaign addresses metered investigation costs without weakening the managed-service case.
Other problems with a similar purpose
In each of these, as in this one, the aim is to turn confusing, fragmented technical systems into something the people relying on them can understand and trust.
Health-system opportunities stall after first meetings, even when the discovery notes are complete.
You must decide where the AI's work on those notes ends and where the seller takes over what a care-management leader reads in the proposal.
Eleven producers appear complete in the dashboard, but only seven pass migration checks.
You must weigh a timely wave against publishing a readiness view people cannot trust.
Pilot sellers are rebuilding account context and taking more than an hour to reach a usable next step.
You have to decide how far the index and CRM carry an account brief toward a recommended next step before the seller steps in to judge which evidence is safe to use with a regulated buyer.
