Target product, positioning, and experience principles

Product definition

Capablio is an adaptive feedback and development platform that helps organizations run short, relevant feedback programs, combine recurring signals with structured 180/360 reviews, and convert evidence into personal development actions.

The core promise is:

Product pillars

1. Adaptive programs — Daily, weekly, monthly, quarterly, annual, and event-triggered packs with cooldown, quota, coverage, and fatigue controls.
2. Multi-rater feedback — Self, manager, peer, direct report, customer, and tenant-defined relationships with minimum group thresholds.
3. Development loop — Results, reflection, PDP goals, action follow-up, evidence, and recurrence overrides in one lifecycle.
4. Enterprise governance — Tenant isolation, scoped roles, content versioning, audit, retention, authentication, integrations, and controlled platform operations.
5. Modern leadership content — General leadership, engineering leadership, customer leadership, AI/data leadership, and tenant-specific packs.
6. Import and interoperability — Thomas and other external reports as source-attributed evidence, plus CSV, HRIS, SSO/SCIM, API, and warehouse integrations by plan.

Primary audiences and jobs to be done

HR and people teams

• Create programs that are short enough to complete and broad enough to cover the intended framework over time.
• Select global packs, apply tenant overlays, define audience and cadence, and forecast coverage.
• Manage nominations, reminders, completion, anonymity, exceptions, and report release.
• See program health without reading private individual content they are not authorized to view.
• Prove governance, fairness, retention, and auditability.

Executives and people managers

• Understand the current development priorities of a team without turning the product into employee surveillance.
• Request feedback, nominate raters, discuss results, agree actions, and follow through.
• See only the PDP information explicitly shared with them or permitted by tenant policy.
• Receive actionable prompts rather than dense HR reports.

Individuals

• Understand what is due and why.
• Complete feedback quickly with confidence in anonymity and use.
• Review strengths, gaps, differing perspectives, and supporting evidence.
• Create a private or selectively shared development plan.
• Track actions and see whether perception changes over time.

Tenant administrators

• Configure identity, domains, roles, scopes, organization data, integrations, billing, branding, security, retention, and tenant content.
• Know which settings are inherited, overridden, or plan-gated.
• Preview the user impact of changes before publishing.

Global platform operators

• Provision and support tenants without casually accessing tenant content.
• Monitor platform, delivery, integration, and billing health.
• Manage global catalog content, entitlements, release channels, regions, incidents, and audited support access.

External raters

• Understand why they were invited, what will be visible, how anonymity works, and how long the survey will take.
• Complete a focused survey without needing a paid seat.
• Save and resume securely where policy allows.

Experience principles

Goal language over system language

Use “Programs,” “Feedback,” “Results,” “Development,” and “Organization” rather than “wrapped surveys,” “envelopes,” “state transitions,” or “consoles.” System terms may appear in internal documentation and diagnostics only.

One role-aware product, not disconnected admin tools

Use a consistent shell and a workspace switcher. Each workspace has its own navigation and scope indicator, but shared concepts—people, programs, tasks, results, and help—behave consistently.

Progressive disclosure

Show the next decision and its consequences. Advanced coverage weights, encryption modes, and integration mappings belong behind expert controls with documentation, previews, and safe defaults.

Evidence before interpretation

Results must show sample size, relationship group, observation period, source, Not Observed rate, and anonymity suppression. AI summaries must link to source evidence and clearly identify uncertainty.

Development before judgment

Default language and flows should support reflection, coaching, and action. Do not introduce leaderboards, employee ranking, or automatic employment decisions.

Privacy is a visible product feature

Explain who can see completion, ratings, comments, goals, and shared actions at the point of collection and sharing. Avoid vague claims such as “fully anonymous” when a manager group contains one person.

Enterprise administration must be reversible and auditable

Provide preview, validation, diff, staged publish, archive, rollback where feasible, and immutable history for high-impact configuration.

Short instances, complete programs

A single recurring survey is intentionally partial. The program UI must show anchors, rotating content, PDP items, coverage progress, projected completion, and infeasible configurations.

Non-goals

• Replacing payroll, compensation, case management, or a full HRIS.
• Diagnosing personality, mental health, or protected characteristics.
• Claiming psychometric adaptivity without formal calibration and validation.
• Ranking engineers using delivery telemetry.
• Automatically creating high-stakes PDP or performance actions from one low score.
• Allowing platform operators to treat tenant data access as routine support.