platform-admin/boc - boc - Gitea: Git with a cup of tea

platform-admin/boc

Fork 0

Commit Graph

Author	SHA1	Message	Date
Bernt	09f3d2f39d	docs: Experience Audit updated with fixed matrix + placeholders for next screens - Updated audit framework with fixed 6-question matrix: 1. 3-Second Rule: understand purpose immediately 2. Three-Step Rule: Input → Processing → Outcome visible 3. Primary Decision: know what to do 4. Information Hierarchy: most important is largest 5. Cognitive Load: what can be removed 6. Call to Action: clear next action - Added One-Sentence Test: - Can user describe screen in one sentence? - Examples for Onboarding, Map View, Dashboard, Results - Two+ sentences = screen tries to do too much - Added placeholders for next screens: - Screen 3: Dashboard (Landvex) - Screen 4: Map View (Landvex/quiXzoom) - Screen 5: Results/Decision View (Landvex) - Priority order: Dashboard → Map View → Results → Search → Settings - Updated quiXzoom onboarding audit with new matrix format Rationale: Fixed matrix ensures consistent evaluation across all screens. One-Sentence Test reveals overloaded screens. Placeholders ready for next screens. Priority reflects user journey impact.	2026-07-02 11:36:56 +00:00
Bernt	d43d523444	docs: Three-Step Rule + quiXzoom audit improvements - EXPERIENCE_AUDIT_QA.md updated: - quiXzoom onboarding: 8 specific improvements - Headline: 'Fota. Skicka. Få betalt.' (three verbs) - First card: show payment upfront - 100% card: larger number, smaller text - Payment card: remove Stripe, add 'Få betalt varje måndag' - Flexibility: 'Jobba när du vill' - CTA: clearer pre-registration - Key numbers: 100% \| /bin/bash \| Every Monday \| 4K - Visual flow: 📷 → ✅ → 💰 - THREE_STEP_RULE.md (v1.0, LOCKED): - Universal product summary: Input → Processing → Outcome - Landvex: Reality → AI Analysis → Decision - quiXzoom: Photo → Approval → Payment - Applies to landing pages, onboarding, presentations, UX - Verification table for both products Rationale: Common language between products. Three steps = three seconds. Every product must be summarizable as Input → Processing → Outcome. This unifies Landvex and quiXzoom under the same conceptual model.	2026-07-02 11:33:50 +00:00
Bernt	8ee9965378	docs: Experience Audit + Component Maturity Model - EXPERIENCE_AUDIT_QA.md (v1.0, DRAFT): - Audit framework: 6 questions per screen - Screen 1: quiXzoom Onboarding — 3s ✅, R→D ⚠️, Decision ✅ - Issue: 'kr' used instead of USD/EUR (Valutaregel violation) - Issue: Launch date creates hesitation - Screen 2: Landvex Process — 3s ✅, R→D ✅, Decision ✅ - Issue: Technical terms in step descriptions - Action items: currency update, date removal, verb simplification - Next screens: Dashboard, Map View, Search, Mission Details, Results - COMPONENT_MATURITY.md (v1.0, LOCKED): - Three levels: Foundation → Validated → Canonical - Foundation: RFC approved, passes 13 DoD criteria - Validated: used in 3 real screens, passes Experience Audit - Canonical: used in 5 screens, 2 sprints stable, other components inherit - Promotion process with verification requirements - Current status: all 4 components at Foundation level Rationale: Observe first, standardize second. Components become Canonical only after proving value in real screens. Experience Audit identifies gaps before building components. Maturity model prevents premature standardization.	2026-07-02 11:32:25 +00:00

Author

SHA1

Message

Date

Bernt

09f3d2f39d

docs: Experience Audit updated with fixed matrix + placeholders for next screens

- Updated audit framework with fixed 6-question matrix:
  1. 3-Second Rule: understand purpose immediately
  2. Three-Step Rule: Input → Processing → Outcome visible
  3. Primary Decision: know what to do
  4. Information Hierarchy: most important is largest
  5. Cognitive Load: what can be removed
  6. Call to Action: clear next action

- Added One-Sentence Test:
  - Can user describe screen in one sentence?
  - Examples for Onboarding, Map View, Dashboard, Results
  - Two+ sentences = screen tries to do too much

- Added placeholders for next screens:
  - Screen 3: Dashboard (Landvex)
  - Screen 4: Map View (Landvex/quiXzoom)
  - Screen 5: Results/Decision View (Landvex)
  - Priority order: Dashboard → Map View → Results → Search → Settings

- Updated quiXzoom onboarding audit with new matrix format

Rationale: Fixed matrix ensures consistent evaluation across all screens.
One-Sentence Test reveals overloaded screens. Placeholders ready for
next screens. Priority reflects user journey impact.

2026-07-02 11:36:56 +00:00

Bernt

d43d523444

docs: Three-Step Rule + quiXzoom audit improvements

- EXPERIENCE_AUDIT_QA.md updated:
  - quiXzoom onboarding: 8 specific improvements
  - Headline: 'Fota. Skicka. Få betalt.' (three verbs)
  - First card: show payment upfront
  - 100% card: larger number, smaller text
  - Payment card: remove Stripe, add 'Få betalt varje måndag'
  - Flexibility: 'Jobba när du vill'
  - CTA: clearer pre-registration
  - Key numbers: 100% | /bin/bash | Every Monday | 4K
  - Visual flow: 📷 → ✅ → 💰

- THREE_STEP_RULE.md (v1.0, LOCKED):
  - Universal product summary: Input → Processing → Outcome
  - Landvex: Reality → AI Analysis → Decision
  - quiXzoom: Photo → Approval → Payment
  - Applies to landing pages, onboarding, presentations, UX
  - Verification table for both products

Rationale: Common language between products. Three steps = three seconds.
Every product must be summarizable as Input → Processing → Outcome.
This unifies Landvex and quiXzoom under the same conceptual model.

2026-07-02 11:33:50 +00:00

Bernt

8ee9965378

docs: Experience Audit + Component Maturity Model

- EXPERIENCE_AUDIT_QA.md (v1.0, DRAFT):
  - Audit framework: 6 questions per screen
  - Screen 1: quiXzoom Onboarding — 3s ✅, R→D ⚠️, Decision ✅
    - Issue: 'kr' used instead of USD/EUR (Valutaregel violation)
    - Issue: Launch date creates hesitation
  - Screen 2: Landvex Process — 3s ✅, R→D ✅, Decision ✅
    - Issue: Technical terms in step descriptions
  - Action items: currency update, date removal, verb simplification
  - Next screens: Dashboard, Map View, Search, Mission Details, Results

- COMPONENT_MATURITY.md (v1.0, LOCKED):
  - Three levels: Foundation → Validated → Canonical
  - Foundation: RFC approved, passes 13 DoD criteria
  - Validated: used in 3 real screens, passes Experience Audit
  - Canonical: used in 5 screens, 2 sprints stable, other components inherit
  - Promotion process with verification requirements
  - Current status: all 4 components at Foundation level

Rationale: Observe first, standardize second. Components become Canonical
only after proving value in real screens. Experience Audit identifies gaps
before building components. Maturity model prevents premature standardization.

2026-07-02 11:32:25 +00:00

3 Commits