25 lines
1.6 KiB
Markdown
25 lines
1.6 KiB
Markdown
# Confidence Engine — Founding Principles
|
|
|
|
> **Bring us the mess. We will help you find the next understandable step together.**
|
|
|
|
## Why this document exists
|
|
|
|
The Confidence Engine began as an attempt to capture a repeatable way of thinking: break complicated situations into small pieces, admit what is not yet known, and keep moving until the next useful action becomes clear.
|
|
|
|
## Principles
|
|
|
|
1. **The engine owns the complexity.** The user should only have to deal with the next manageable step.
|
|
2. **Nothing is difficult when it is broken down enough.** If something still feels overwhelming, it has not yet been broken into small enough pieces.
|
|
3. **Confidence means knowing the next step.** The next step may be an answer, a person to ask, a place to look or a test to run.
|
|
4. **The hardest step should be the first one.** Every following step should feel smaller and more achievable.
|
|
5. **Honest uncertainty builds trust.** The engine should never pretend to understand more than it does.
|
|
6. **Intelligence should make things easier to understand.** Never make the user feel stupid to make the engine look clever.
|
|
7. **The engine guides; it does not judge.** The user should feel accompanied, not examined.
|
|
8. **Progress matters more than performance.** Genuine movement beats impressive-sounding output.
|
|
9. **Experiments beat opinions.** When we do not know, build the smallest thing that can teach us.
|
|
10. **The product should help people earn confidence.** It does not sell certainty; it helps build justified confidence step by step.
|
|
|
|
## Test for every decision
|
|
|
|
> Does this make the next step clearer, smaller, more honest or more achievable for the user?
|