Workshop Guide — Benchmark Time-to-Value

Time-to-value milestones + adoption narrative for your #1 service from Challenge 1.

Challenge 2: Prove milestones in Elastic Serverless, then run prompts 1 → 3 in your AI assistant.

Serverless — prove TTV (do this first)

1. Metrics Explorer — filter service.name:horizon-* on metrics-generic.otel-default
2. Week 1 proof — cite a live series (e.g. http.server.requests) as ingest milestone
3. Week 3 proof (optional) — ☰ → Dashboards → one chart for exec readout, or note alert rule gap

Time-to-value framing (buyer language)

POV / pilot — first value in 2–4 weeks (ingest + one dashboard + one alert)
Production cutover — 90-day phased migration with measurable MTTR / toil reduction
Executive benchmark — compare tool-switch time in Sev-1 vs unified platform

1. Service snapshot

Run first
Horizon Media — Challenge 2 — my #1 at-risk or stalled **service** from Challenge 1.

Using Serverless facts from our chat only (no invented metrics):
- Service snapshot: key metrics, trends, velocity signal
- What the pattern implies for the POV
- What changed since kickoff?

One short paragraph + bullet facts.

2. Time-to-value benchmark

Main exercise — part A
Same #1 service — build a **time-to-value benchmark** your platform leads can take to leadership.

You explored **Elastic Serverless** in this lab. Use live observations as proof.

Output:
1. **Current state** — what does a stalled POV imply? (cite Serverless trends)
2. **Credible TTV table**:

| Milestone | Target week | Buyer-visible outcome | Serverless proof |
|-----------|-------------|----------------------|------------------|

Include at least:
- **Week 1–2:** OTel ingest live (cite metric you saw)
- **Week 3–4:** Executive dashboard + alert/runbook
- **Day 90:** Production cutover decision

3. **One benchmark sentence** for leadership: "Teams like yours typically see X by week Y."

Use ranges, not fake precision.

3. Adoption momentum narrative

Main exercise — part B
Same #1 service — draft an **adoption momentum narrative** that creates urgency without pressure.

Structure (≤250 words):
1. **Insight opener** — pattern in their metrics or industry
2. **Cost of delay** — one quarter of stalled POV (toil, blind spots, renewal risk)
3. **Serverless-backed next step** — concrete workshop/POV ask with date
4. **Leadership enablement** — 3 bullets they can forward internally

Tone: consultative, not FUD. Cite Serverless observations for technical claims.
End with: "Suggested next workshop agenda (30 min)" — 4 bullets.