Support a developer customer story with evidence

Hi,

A developer-tool customer story can explain several different outcomes: the integration worked, a team adopted the workflow, or a business result changed. Keep the evidence for each outcome visible.

For an illustrative observability SDK, an inspectable trace demonstrates an integration result. A customer's account of using traces during incidents adds context about operational use. A claim about reduced investigation time needs a baseline, observation period and definition of the work measured.

Use the case study kit to record the customer's situation, actual workflow, supporting records and approval for publication. Include constraints or implementation effort that matter to a reader deciding whether the story applies to their team.

The customer evidence organizer helps keep observations, objections and proof together. Its output depends on the records you supply.

This week, choose one proposed claim. Write its source, what it establishes and the scope within which you can publish it. If the evidence supports a narrower statement, use that statement.

Jon