# Positioning for observability software > Explain why a team operating a distributed production service should consider a different way to diagnose service behavior using relevant telemetry. A practical procedure with a worked scenario, category-specific checks and an editable worksheet. Source: https://saas-marketing.net/industries/observability/positioning/ Topic: SaaS Product Marketing Type: field-guide Published: 2026-09-17 Last updated: 2026-09-17 Publisher: SaaS Marketing (saas-marketing.net) License: CC BY 4.0. Quote or republish with attribution and a link to https://saas-marketing.net/industries/observability/positioning/ ## Short answer A useful positioning brief for observability software starts when incidents take too long to explain across distributed services. That event gives the platform engineering director a reason to reconsider the current process. ## Key takeaways - Start with the change that creates a buying conversation. - Name the alternative without caricaturing it. - Separate the purchase argument from the daily-use argument. - A polished message can still fail if it ignores this constraint: more telemetry can add cost without improving diagnosis. --- This field guide uses a team operating a distributed production service as its working context. The buying conversation involves the platform engineering director, while the site reliability engineer needs to diagnose service behavior using relevant telemetry. Adapt the scope when those roles, dependencies or operating conditions differ. ## Start with the change that creates a buying conversation A useful positioning brief for observability software starts when incidents take too long to explain across distributed services. That event gives the platform engineering director a reason to reconsider the current process. A broad claim about efficiency does not explain why a purchase belongs on this quarter's agenda. Interview someone who recently faced the trigger and reconstruct what happened before a vendor was contacted. Record the work that became unacceptable, the people affected and the consequence of leaving it unchanged. Keep that account separate from a salesperson's interpretation of it. ## Name the alternative without caricaturing it The working alternative here is separate logs, metrics and manual queries. It may be inexpensive, familiar and adequate for a smaller team. Explain the condition under which it stops serving the customer rather than pretending it never worked. A comparison should acknowledge what the customer would lose by moving, including familiarity, flexibility and historical information. If the product cannot improve a material part of the workflow, a more forceful headline will not create a durable position. Use the customer's current process as the comparison baseline even when it has no commercial brand. ## Separate the purchase argument from the daily-use argument The platform engineering director needs confidence that the change is worth approving. The site reliability engineer needs a workable way to diagnose service behavior using relevant telemetry. These are connected concerns, but the proof differs. A purchase narrative might show ownership and control; a user narrative should show the actual sequence of work. Write one sentence for each audience and test whether they contradict each other. Promising stronger control while hiding additional data entry is a common way to win approval and lose adoption. ## Build a claim that can survive a demonstration Use a known failure investigated with bounded telemetry and cost estimates as a candidate proof exercise. The demonstration should reveal the mechanism behind the claim: what information enters, what the product changes, who acts and what can be inspected afterward. Avoid superlatives that have no defined comparison set. An honest limitation can strengthen the evaluation by identifying an unsuitable use case early. Keep a claim register with an owner and a link to evidence so sales copy does not drift beyond what the demonstration establishes. ## Test comprehension before preference Show a draft message to people in a team operating a distributed production service. Ask what they think the product does, who it is for and what would need to be true for them to evaluate it. Do not ask whether they like the wording before learning whether they understood it. A respondent who repeats the headline has not necessarily connected it with their work. Ask them to describe a recent situation in which it would matter. Preserve confusing responses verbatim in the internal research notes, then revise the underlying explanation. ## Use objections to define the boundary The objection "Data volume will create unpredictable costs" belongs in the positioning brief. Decide whether it points to a product limitation, an implementation requirement or missing evidence. Each answer changes the public claim differently. A product limitation needs a qualification; an implementation requirement needs a clear plan; missing evidence needs a test. Do not turn a legitimate objection into an aggressive rebuttal. The useful output is a more accurate buying decision, including a clear reason some prospects should not proceed. ## Category-specific review Telemetry should support a diagnostic question, not merely accumulate volume. Logs, traces and metrics can provide different evidence about one incident. Ask what an engineer needs to connect the customer-facing symptom with the relevant service behavior and what data collection costs. Introduce a known test failure and trace the investigation across the required signals. Record what could not be observed and why. The proof should show a useful diagnosis under stated conditions rather than imply that more telemetry guarantees faster incident resolution. ## Worked situation Imagine the platform engineering director evaluating a change after incidents take too long to explain across distributed services. In the first message test, a prospect describes the offer as "another system for administration." That response shows category recognition but no reason to change. Revise the proof around a known failure investigated with bounded telemetry and cost estimates, then ask the prospect to explain which step differs from separate logs, metrics and manual queries. The useful evidence is a specific explanation, not a higher preference score. If the prospect still cannot connect the difference with the work needed to diagnose service behavior using relevant telemetry, investigate the offer before running a larger messaging test. ## Working worksheet | Working item | Category-specific starting point | Question to resolve | | --- | --- | --- | | Audience | a team operating a distributed production service | Which recent customer matches this scope? | | Buying trigger | incidents take too long to explain across distributed services | What happened immediately before evaluation? | | Current alternative | separate logs, metrics and manual queries | Where is it still adequate? | | Demonstrable difference | a known failure investigated with bounded telemetry and cost estimates | What evidence supports the claim? | | Boundary | Data volume will create unpredictable costs | When should the prospect decline? | Add your evidence, owner and next action to each row. Read the [worksheet instructions](/resources/#using-worksheets) before completing the file. ## Run the review with the people who do the work Bring the site reliability engineer into the review of a known failure investigated with bounded telemetry and cost estimates. Ask them to identify the input they would actually have, the exception they expect to encounter and the person who receives the output. Then ask the platform engineering director which unresolved issue could change the decision. Keep the two answers separate until the team understands whether the obstacle is workflow fit, implementation readiness or commercial priority. Record any dependency on application instrumentation and incident response system beside the affected worksheet row. A dependency should have an owner and an observable completion condition. If it changes the scope of the offer, revise the public description before the next campaign. This prevents a useful planning exercise from turning into a promise the delivery team cannot meet. ## When to change the plan A polished message can still fail if it ignores this constraint: more telemetry can add cost without improving diagnosis. If new evidence changes the audience, required workflow or acceptance conditions, update the brief and explain why. Compare later results against the version of the plan that was actually used. ## Continue with the next decision Use the [ideal customer profile guide](/industries/observability/ideal-customer-profile/) when that is the next unresolved task, or return to the [observability software marketing overview](/industries/observability/) to choose a different route. The [saas product marketing hub](/saas-product-marketing/) provides the broader method. ## Reference and scope The [primary category reference](https://docs.datadoghq.com/) is a starting point for checking product terminology and current capabilities. This page provides an original planning framework. It does not imply a vendor endorsement, firsthand product test, original market survey or guaranteed commercial result. ## Frequently asked questions ### Where should positioning for observability software start? Explain why a team operating a distributed production service should consider a different way to diagnose service behavior using relevant telemetry. Confirm the customer situation and the evidence needed for the next decision before selecting a channel, format or tool. ### What category-specific concern should the team investigate? The concern "Data volume will create unpredictable costs" needs an observable test or a clear limitation. Also account for the dependency on application instrumentation and incident response system; do not assume it is already resolved. ### What does the worksheet include? It contains the working items and category-specific starting points shown on this page. Add your own evidence, owner, status and next review decision. The examples are constructed, not reported results or industry benchmarks. ### How does this connect to customer value? The customer needs to diagnose service behavior using relevant telemetry. A meaningful first checkpoint is to instrument a sample service and trace a known request or failure; the ongoing condition is that engineers use connected telemetry to investigate meaningful incidents. Choose the stage appropriate to this piece of work rather than combining all three into one metric.