Skip to main content

Builder Bella - JTBD Statements

Master JTBD Statement​

When building or updating features in a distributed system,
I want to instrument my code easily and confirm that telemetry is complete and accurate,
so I can debug issues quickly and deliver reliable features to production.

JTBD-1: Instrument Code with Minimal Effort​

When adding or updating code paths,
I want to apply standard logging, metrics, and tracing patterns quickly,
so I can maintain observability without spending hours learning tooling.

JTBD-2: Understand How My Code Behaves in Production​

When a feature is deployed or a bug is reported,
I want to see how my code performs and where it fails,
so I can diagnose issues efficiently and prevent customer impact.

JTBD-3: Validate That Telemetry Is Flowing​

When I push new code or refactor instrumentation,
I want to verify that logs, metrics, and traces are emitted correctly,
so I can avoid silent failures and incomplete data during incidents.

JTBD-4: Debug Issues Faster​

When investigating performance or functional defects,
I want to use clear, correlated signals to pinpoint root cause,
so I can resolve issues quickly and avoid relying on SREs.

JTBD-5: Use Consistent, Repeatable Patterns​

When joining new services or collaborating across teams,
I want to leverage templates, examples, and conventions,
so I can reduce cognitive load and achieve consistent outcomes.

Emotional Jobs​

EJ-1: Confidence in Code Quality​

When shipping new features,
I want to feel confident I’m not introducing hidden reliability risks,
so I can deliver at speed without anxiety.

EJ-2: Reduce Debugging Frustration​

When dealing with production issues,
I want to avoid noisy, scattered tools and missing data,
so I can stay focused, efficient, and calm.

Social Jobs​

SJ-1: Demonstrate Engineering Excellence​

When working with peers and leads,
I want to show that my code is well-instrumented and observable,
so I can build trust and credibility.

SJ-2: Collaborate Smoothly with SRE & Service Owners​

When incidents occur or changes are released,
I want to provide clear telemetry others can rely on,
so I can help the team troubleshoot effectively.