> For the complete documentation index, see [llms.txt](https://engineering.umh.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://engineering.umh.app/product/product-standards/immediate-trust.md).

# Immediate trust

Every action in the Management Console answers immediately and says what it is doing.

Owner: Jeremy

Every action in the Management Console answers immediately and says what it is doing. Users trust what they can see happening.

## Rules

* Every action gets visible feedback within 0.1 seconds, following Jakob Nielsen's [response-time limits](#response-time-limits).
* A running operation shows the real values it changes, for example "Updating pump-03 flow: 50→75 L/min" and not "Updating configuration".
* We show a progress bar only when we know the percentage. Otherwise we show the elapsed time.

## Response-time limits

**Jakob Nielsen described** [**three response-time limits**](https://www.nngroup.com/articles/response-times-3-important-limits/) **in 1993.**

* 0.1 second is "the limit for having the user feel that the system is reacting instantaneously".
* 1.0 second is "the limit for the user's flow of thought to stay uninterrupted, even though the user will notice the delay".
* 10 seconds is "the limit for keeping the user's attention focused on the dialogue".


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://engineering.umh.app/product/product-standards/immediate-trust.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.