Capablio

Handbook

Current-state UX and product audit

The supplied application is a coherent functional prototype, not yet an enterprise product. It proves several important concepts—tenant context, role separation, an organization graph, survey lifecycle, third-party PDF…

Updated

Executive assessment

The supplied application is a coherent functional prototype, not yet an enterprise product. It proves several important concepts—tenant context, role separation, an organization graph, survey lifecycle, third-party PDF import, encrypted subject results, and a platform-operator view—but it exposes implementation details, relies on sparse developer-oriented screens, and does not yet communicate a complete commercial product.

The visual language is consistent enough to evolve, but the experience currently reads as an internal admin tool:

  • Nearly every screen uses the same dark shell and large empty canvas regardless of task.
  • Navigation is organized around technical “consoles,” not user goals.
  • Forms use raw browser controls and have limited validation, guidance, progress, or recovery.
  • Data-heavy flows are presented as plain lists or even raw JSON.
  • Empty states dominate but rarely explain what happens next.
  • Marketing, pricing, trust, customer documentation, onboarding, and help are absent.
  • The design does not yet demonstrate mobile behavior, accessibility, localization, auditability, or enterprise operations.

What should be preserved

  1. Clear tenant context. The shell consistently shows which organization is active.
  2. Role-gated workspaces. End-user, organization-admin, and platform-operator separation is already visible.
  3. Privacy intent. Client-side envelope encryption and restricted HR visibility are meaningful differentiators if explained and operationalized safely.
  4. Organization graph. Org units, managers, HR scopes, and users form a useful foundation for routing and reporting.
  5. External report import. Thomas and snapshot PDF import creates a practical migration path.
  6. PDP linkage. Results and personal development are treated as one flow rather than unrelated modules.
  7. Cross-tenant control plane. A distinct operator surface exists instead of overloading tenant administration.

Critical gaps by product area

Public presence and commercial clarity

There is no visible marketing site, solution packaging, pricing page, security/trust content, documentation portal, case-study structure, release notes, or demo path. Prospects cannot understand who the product is for, why it is different, how privacy works, or what each plan includes.

Information architecture

“Consoles” expose implementation architecture. A person with multiple roles should see a workspace switcher with clear scope and permissions, not a collection of technical consoles. The application needs separate navigation models for:

  • Individual work
  • Manager work
  • HR program operations
  • Tenant configuration
  • Global platform operations

Authentication and onboarding

The current sign-in screen asks invitees to import a JSON encryption key before Google sign-in, displays a tenant slug, and exposes a bearer-token path. These are developer or recovery mechanisms, not a mainstream enterprise onboarding flow. The production experience needs verified invitations, enterprise SSO, passkeys or MFA where supported, guided device registration, recovery choices, legal notices, and a development-only gate for token login.

Product home and task management

The subject home page has four equal cards but no priority, due date, completion state, recent insight, progress, or recommended next action. Enterprise users need a “Today” experience that answers:

  • What is due?
  • Why am I being asked?
  • How long will it take?
  • What changed since last time?
  • What development action should I take next?

Administration

The current tenant-admin screens lack search, filters, bulk actions, status, effective dates, audit history, import reconciliation, role preview, scope summaries, and safe destructive-action flows. HR designations are represented as a long checkbox list, and org-unit editing is a plain indented list.

Survey lifecycle

The lifecycle screen shows internal states and raw rater-assignment JSON. It needs a campaign stepper, named participants, relationship groups, anonymity thresholds, nomination and approval, delivery status, reminders, exceptions, coverage simulation, and publish/reopen/cancel controls.

Results and PDP

The PDP screen currently consists of a period field and “Load my surveys.” It does not yet present competency patterns, self-versus-others gaps, top and bottom items, role-priority differences, qualitative themes, evidence, goal creation, action tracking, follow-up questions, or sharing controls.

Platform operations

The operator tenant list proves cross-tenant management but lacks plan, seat use, region, lifecycle, health, integration status, billing, incidents, support access, audit, entitlements, feature rollout, framework publishing, or privacy-preserving diagnostics.

Accessibility and responsive behavior

The screenshots show low-contrast secondary text, small navigation labels, extensive dark surfaces, native controls with inconsistent styling, and layouts optimized only for 1280×800. No visible focus treatment, skip navigation, keyboard workflow, mobile navigation, dense-table adaptation, or reduced-motion behavior is demonstrated.

Screen-by-screen findings

Screen What works Enterprise uplift required
01 — Sign in / invite key Explains that encrypted content exists and distinguishes invited users Replace key-first onboarding with invitation verification and guided device setup; hide bearer tokens outside development; add SSO, recovery, privacy, support, loading/error states, and branded tenant context
02 — Subject home Clear four-task overview and tenant/user identity Replace equal cards with prioritized tasks, due dates, time estimates, progress, latest insights, PDP next step, notifications, and contextual help
03 — Account & security Exposes backup, restore, reseal, and sign-out concepts Add devices, sessions, MFA/passkeys, backup health, recovery policy, key rotation history, destructive-action confirmation, and plain-language explanations
04 — PDF import Supports Thomas and snapshot import by period Add drag-and-drop, source detection, file validation, progress, parsing preview, mapping confirmation, duplicate handling, lineage, import history, and human review
05 — HR link in subject shell Demonstrates role-aware navigation Use a labeled workspace switcher and explain active scope; avoid mixing employee tasks with admin navigation hierarchy
06 — Operator link Demonstrates operator gating Separate the platform control plane visually and by domain; add explicit privileged-session indicators and support-access guardrails
07 — Completion dashboard Correctly states managers see counts rather than answers Add KPI cards, response funnel, groups at risk, due dates, reminders, filters, trend, anonymity warnings, export, and drilldown without plaintext exposure
08 — Org units Basic hierarchy and child creation work Add tree controls, search, headcount, manager/owner, inherited settings, drag/reparent safeguards, archive rather than unsafe delete, sync status, and history
09 — Users Simple searchable-looking directory structure Add actual search, filters, status, role, manager, license, invitation state, last active, bulk actions, CSV/SCIM provenance, and detail drawer
10 — HR designations Establishes org-scoped HR administration Replace long checkboxes with searchable people picker, scope chips/tree, permission preview, inheritance, effective dates, conflict detection, and audit
11 — Invites Captures basic invitation data Add invite type, expiry, resend/revoke, bulk operations, domain rules, role preview, email template, delivery status, and secure onboarding policy
12 — CSV import Supports dry run Add downloadable template, field mapping, validation report, diff preview, conflict policy, rollback, import job history, and accessibility
13 — Survey lifecycle Shows state progression Replace raw JSON with campaign summary, participants, rater groups, assignment table, nomination/approval, reminders, exceptions, thresholds, and action history
14 — All tenants Clear cross-tenant list and status Add plan, seats, region, owner, health, billing, provisioning state, auth/integration status, last activity, risk flags, support access, and filterable columns
15 — Create tenant Minimal provisioning path Use a multi-step wizard for identity, plan, region, owner, domain, authentication, data policy, branding, integrations, seed content, and launch checklist
16 — Access denied Correctly blocks an unauthorized subject Add a branded 403 state, reason-safe explanation, return action, request-access path, correlation ID, and security-event audit without leaking permissions
17 — Results & PDP Preserves subject privacy and period selection Build a complete results narrative, evidence views, gaps, strengths, role priorities, qualitative themes, goals, actions, follow-up cadence, progress, and share controls
18 — Static export Demonstrates an offline artifact goal The export is visibly unstyled; bundle assets, preserve navigation and print styles, add version/date/source metadata, and test offline/print/PDF output

Product concepts from the 360 materials that the UI must support

The result experience should preserve the useful concepts already present in the supplied 360 materials:

  • Development conversation rather than performance judgment
  • Anonymous, aggregated relationship groups
  • Minimum response thresholds
  • Self versus others
  • Competency averages and item distributions
  • Not Observed / Not Applicable
  • Top and bottom statements
  • Role-importance differences
  • Strengths, blind spots, hidden effort, and development themes
  • Qualitative evidence
  • Two or three focused PDP objectives

These concepts should be expressed as modern, interactive workflows rather than reproduced as dense legacy report tables.

First ten changes to implement

  1. Establish the dual wiki and traceability contract.
  2. Freeze the role, scope, and data-visibility model.
  3. Replace the current shell with role-aware workspace navigation.
  4. Build a reusable light-first design system with an optional dark theme.
  5. Redesign sign-in, invite, device registration, and recovery.
  6. Build a prioritized user “Today” page.
  7. Replace the survey lifecycle JSON with a campaign workflow.
  8. Build question-library, pack, cadence, cooldown, and coverage administration.
  9. Build interactive results and PDP experiences.
  10. Build the public marketing, pricing, trust, and documentation surfaces from the external wiki.