liveBook · Manning

Trust

As explained in Fast by Default

Trust is a user's or customer's confidence that a product or service is reliable and worthy of continued use.

Trust is confidence that a product or service is reliable and worth continuing to use. Performance strengthens that confidence; slow experiences quietly weaken it through reduced engagement, conversion, retention, and customer satisfaction. section 1.2 section 2.6

Performance failures rarely announce themselves through crashes or visible errors. Sluggish interactions, delayed responses, and slow-loading layouts accumulate across sessions until users leave, convert less, or choose a competitor. section 2.1.4

Make trust a practical performance concern by:

  • Connecting regressions to money, time, and trust instead of reporting milliseconds alone. section 2.4
  • Identifying affected users and their business value, especially high-value or enterprise customers. section 2.4
  • Surfacing measurements, regressions, and concrete examples early enough to influence prioritization. section 2.4
  • Tracking conversion, productivity, retention, and other outcome changes to expose silent performance risk. section 2.6

When speed determines adoption

An enterprise data table failed to render customers' datasets beyond a 1024-row limit, including every dataset brought to user-testing sessions. Reframing the issue as failure affecting paying customers secured priority. Similarly, an API responding in 800 milliseconds lost against a 200-millisecond competitor because speed determined developer adoption and trust during evaluation. section 2.4 section 2.2.3

How Fast by Default covers it

How deep it goes
Explains trust erosion through observable performance patterns and outcomes, but stops short of defining a formal trust model or measurement method.
Examples
Uses slow interactions, failed large data tables, measurable conversion changes, and competing API response times as concrete trust signals.
What it assumes
Assumes familiarity with performance problems and business outcomes while teaching how to translate technical evidence into trust-related priorities.
What you can do after
Evaluate performance risk by linking measurements and regressions to user value, revenue, retention, adoption, and stakeholder priorities.
How it connects
Connects trust with performance engineering, customer satisfaction, conversion, retention, API performance, and enterprise adoption.

Also explained in

Compare how 18 books explain trust →

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Fast by Default. The section links point to the parts of the book it draws on.