EchoBY BIOQUANT IQ|HR portal · Tarrowby Group cohortDEMO DATA · SAMPLE PEOPLE
Development with a number behind it. Cohorts practise real decision moments; you see who moved, on which behaviour, against their own baseline.
People & journeys
Click a person to open their journey. Locked rows have not shared consent: they appear in aggregates only.
Person
Module
Best-practised skill
Runs
Score /10
Movement
Consent
How the score forms (the Echo rule): n=0 shows the person's own claim, labelled as a claim · n=1–2 blends claim and observed runs (50%, then 25% claim) · n=3 sets the baseline (mean of first three; the claim drops out) · n≥4 each new run gets half the say. Movement exists only from run 4, measured against the baseline. Bands: 70+ strong pattern · 48–69 pattern forming · <48 attention zone.
Skill × team: cohort aggregates
Average practice score /100 with people count. Aggregates include everyone, consented or not. Team cells with fewer than 3 people stay hidden; the cohort column always shows, with its count.
User management ECHO FOR LEARNING
Licenses, profiles, skills and reminders: the admin side of the same cohort. Buttons act on this demo page.
User
Status
License
Skills assigned
Last run
Actions
Also available on the platform: bulk import from HRIS, SSO, role-based admin rights, scheduled reminder rules, and automatic license recycling when a user is deactivated.
← Select a consented person to see their journey.
Ask Echo · People SCRIPTED DEMO
Ask questions about this cohort in plain words.
Answers are computed live from this page's cohort data by fixed rules: no AI model, in line with Echo's no-chatbot-near-scores design. Individual answers respect consent.
Privacy model, enforced by the product: individual journeys and individual answers appear only where the person has shared consent, agreed in writing before their first run. Everyone else contributes to aggregates only, and small groups are suppressed. No personality profiling, no protected traits, no hire/fire verdicts. Every completed run is confirmed server-side and counts exactly once.
Same room, three finalists. Each candidate ran the identical scenario: a vendor pushing to sign with vetting incomplete. You compare observed decisions, not interview polish. Candidates consent as part of the process. ILLUSTRATIVE DEMO VIEW
Role: Partnerships Manager: Indonesia expansion
Scenario given to all three: "The Vendor Sign Call" (Commercial Acumen, difficulty D3). One run each · single run = early signal, not a verdict.
The boundary, by design: Echo describes what each candidate did in the same situation. It does not rank them and it does not decide. Your panel does: now with one more piece of evidence than an interview gives you. A wrong hire costs at least 30% of first-year earnings (US Dept. of Labor).
Run the next level's room before the title changes. Candidates for the Q4 Team Lead window practise next-level situations now, while there is still time to build what is missing. ILLUSTRATIVE DEMO VIEW
Team Lead window: Q4 readiness
Readiness = observed evidence against the target role's three core skills. People decide the promotion; Echo shows what has actually been seen.
Why this matters: CEB research puts new-manager failure near 60% within two years. Most of that failure is discovered after the title. This view moves the discovery before it.
Succession evidence built over quarters, not in the panic week. For each key role: who is on the bench, and how much observed behaviour stands behind each name. ILLUSTRATIVE DEMO VIEW
Key roles & bench depth
Evidence depth = skills observed × runs × quarters of history, from the same journeys as the Learning view.
Key role
Bench candidate
Evidence so far
What it shows
Bench strength
Reading it: a thin bench is not a crisis: it is a practice plan. Each name's next quarter of scenarios is generated against the key role's decision nodes, so the bench builds itself in the normal flow of development.