Commit Graph

6 Commits

Author SHA1 Message Date
Bernt 8e79e4b006 docs: Dashboard Principle + Landvex Dashboard audit prep
- DASHBOARD_PRINCIPLE.md (v1.0, LOCKED):

  - Four questions: What, Where, How serious, What now

  - Information hierarchy: Score -> Observations -> Map -> History -> Details

  - Decision Density: Dashboard = 1-3 decisions max

  - Not BI: helps user make decision, not consume statistics

  - Verification checklist

- EXPERIENCE_AUDIT_QA.md updated:

  - Screen 4: Landvex Dashboard (Phase: Manage)

  - Dashboard-specific questions: 3-second understanding, today's decision,

    80% ignorable, primary CTA

  - Dashboard Principle check: What/Where/How serious/What now

  - Decision Density target: 1-3 decisions

  - One-Sentence Test: understand area performance and what to act on

- Ready for Landvex Dashboard screen (stresstest for Foundation v1.0)
2026-07-02 11:45:07 +00:00
Bernt 70a625510b docs: Journey Principle + Mission Marketplace naming + Dashboard prep
- JOURNEY_PRINCIPLE.md (v1.0, LOCKED):

  - Five phases: Discover, Capture, Process, Outcome, Manage

  - Maps to both quiXzoom and Landvex

  - Screen mapping table

  - Balance check reveals Capture/Process/Outcome are empty

  - Verification: every screen must belong to a phase

- EXPERIENCE_AUDIT_QA.md updated:

  - Screen 3 renamed: Public Map -> Mission Marketplace

  - Added Phase column: Discover

  - One-Sentence Test updated: which missions not how much

  - Added Journey Principle reference

  - Screen 4: Dashboard (Landvex) - awaiting screen

  - Screen 5: Results/Decision View (Landvex) - awaiting screen

- Next: Landvex Dashboard audit (stresstest for Foundation v1.0)

Rationale: Journey Principle prevents screens from floating without

context. Mission Marketplace better reflects the page's purpose.

Dashboard is the most complex screen - best stresstest for principles.
2026-07-02 11:42:32 +00:00
Bernt c087043408 docs: quiXzoom Web vs App Principle + Public Map audit
- WEB_APP_PRINCIPLE.md (v1.0, LOCKED):

  - Web = discover, understand, administer

  - App = execute

  - Public web: map-centric, no mission acceptance

  - Logged-in web: My pages, no mission execution

  - App: camera-first, offline, GPS, quick submission

  - Feature matrix verifying separation

- EXPERIENCE_AUDIT_QA.md updated:

  - Added Product Principle: Web vs App

  - Screen 3: quiXzoom Public Map (proposed design audited)

    - 3-Second Rule: pass

    - Three-Step Rule: pass

    - Primary Decision: pass

    - Information Hierarchy: pass

    - Call to Action: pass

    - One-Sentence Test: I can see how many missions are near me

    - Issues: income estimate needs disclaimer, add real-time activity

  - Updated priority order: Dashboard -> Results -> Search -> Settings
2026-07-02 11:39:37 +00:00
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