Bernt
edf1e6e0d6
- FOUNDATIONS-v1.0.md updated:
- Added Landvex Core Principle and Design Constitution to frozen foundations
- Added Core Principle Rules to invariants (2.4)
- Reordered component priority: Modal, Search, Map Panel, Navigation, Table, Data Grid
- Reflects business value: search and maps are central to Landvex
- EXPERIENCE_AUDIT.md (v1.0, LOCKED):
- Four questions for every screen:
1. Can purpose be understood in 3 seconds?
2. Is 'Reality → Decision' visible?
3. Is it obvious what the user should do?
4. Does everything contribute to the decision?
- Three-second rule levels with verification method
- Audit process: select screens → apply questions → prioritize fixes → verify
- Example audit format
- Core Principle Check for RFCs: 4 questions before approval
- COMPONENT_TEMPLATE.md updated:
- Added Core Principle section to template
- Requires: decision support, cognitive load reduction, 3-second understanding
- RFC_DEFINITION_OF_DONE.md updated:
- Added Core Principle as criterion #2 (was 12 criteria, now 13)
- Exit criteria: must pass all 13
Rationale: Freeze foundation with Core Principle as highest authority.
Experience audit ensures all screens support decision-making.
Core Principle Check prevents components that don't serve the user.
Business-value prioritization: search and maps before tables.
3.7 KiB
3.7 KiB
EXPERIENCE AUDIT
Checklist for Evaluating Screens Against Landvex Core Principle
| Version | 1.0 |
| Status | LOCKED |
| Scope | All Landvex & quiXzoom screens, documentation, presentations |
The Four Questions
For every screen, view, or presentation, ask:
1. Can the purpose be understood in 3 seconds?
Check:
- Is the primary action or information immediately visible?
- Is there visual hierarchy that guides the eye?
- Are there no competing elements for attention?
Pass criteria: A new user can answer "What does this screen do?" within 3 seconds.
2. Is "Reality → Decision" visible?
Check:
- Does the screen show where reality becomes data?
- Is the decision basis clearly presented?
- Is the connection between input and output obvious?
Pass criteria: The user sees the flow from reality to decision without explanation.
3. Is it obvious what the user should do?
Check:
- Is the primary action clearly indicated?
- Are secondary actions distinguishable from primary?
- Is there no ambiguity about next steps?
Pass criteria: The user knows what to do without reading instructions.
4. Does everything contribute to the decision?
Check:
- Is every element on the screen justified?
- Are there decorative elements that don't aid comprehension?
- Is information density appropriate for the context?
Pass criteria: Removing any element would reduce the user's ability to make a decision.
Three-Second Rule Levels
| Time | Understanding | Verification |
|---|---|---|
| 3 seconds | What does the system do? | Ask 5 new users, 4/5 must answer correctly |
| 10 seconds | The process from input to decision | Ask 5 new users, 4/5 must describe the flow |
| 60 seconds | Why the result is useful for business | Ask 5 domain experts, 4/5 must articulate value |
Audit Process
Step 1: Select Screens
Priority order:
- Landing page / Dashboard
- Map view
- Search results
- Object detail
- Report view
- Settings
Step 2: Apply Four Questions
For each screen, answer all four questions. Document failures.
Step 3: Prioritize Fixes
| Severity | Criteria | Action |
|---|---|---|
| Critical | Fails question 1 or 3 | Block release |
| High | Fails question 2 | Fix before next version |
| Medium | Fails question 4 | Fix in next iteration |
| Low | Minor improvements | Backlog |
Step 4: Verify Fixes
Re-audit after fixes. Same criteria apply.
Example Audit
Screen: Dashboard
| Question | Result | Notes |
|---|---|---|
| 1. 3-second understanding | ✅ Pass | KPI cards immediately visible |
| 2. Reality → Decision | 🟡 Partial | Map shows reality, but decision basis requires scrolling |
| 3. Obvious action | ✅ Pass | Primary action button prominent |
| 4. Everything contributes | ❌ Fail | News feed does not aid decision-making |
Action: Remove news feed or move to secondary panel.
Core Principle Check for RFCs
Before an RFC is approved, it must answer:
| Question | Answer Location |
|---|---|
| How does this component support "Reality → Decision"? | Cognitive Purpose section |
| Can it be understood in 3 seconds? | User Expectation section |
| What decision does it help the user make? | Cognitive Purpose section |
| How does it reduce cognitive load? | Interaction Contract section |
ÄNDRINGSHISTORIA
| Version | Datum | Beskrivning |
|---|---|---|
| 1.0 | 2026-07-02 | Initial experience audit checklist |
STATUS
LOCKED
- Mindre revideringar: 1.x-serien
- Brytande ändringar: Kräver Architecture Review, ny major-version (2.0+)