For Enterprises
Know what your people can do. Not only what they have completed.
Organisations can describe what their people have completed. Very few can describe what their people can do. Zynaut Pathways gives an organisation a view of capability built from evidence — in aggregate, with every record still owned by the person it describes.
People.Capability.Evidence.
The person who could already do the job is invisible while the search goes outside. The record exists to make them visible — when they choose to be.
- Your workforce, in aggregateCapability described, never named
- Each record owned by the personNot by the organisation
- Work counts as evidenceNot only certificates
- No ranking of peopleNo index, no league table
- Designed for India's DPDP ActPurpose-limited by design
From completion records to capability
How Zynaut Pathways works inside an organisation
Five steps. The organisation sees the whole; each person keeps their own record.
1. Describe roles in capability terms
What a role needs, described in the same words a person's evidence is described in — so the two can be read together.
2. People build their own records
Each person holds a record of what they can do. Work they have already done counts as evidence, attested by whoever was in a position to say so.
3. See the whole, in aggregate
Where the workforce stands against what its roles need, built as aggregates rather than from any one person.
4. Close the gaps that matter
The smallest meaningful gap, for the organisation and for each person — with learning from anywhere counting as evidence.
5. Let people reach inward
When a role opens, a person who can already do it shows you — by their own act, with a view they chose to share.
Everything an organisation needs, honestly stated
What an organisation gets, and what it does not
Stated the way every door on this site is stated: the offer, then the boundary.
- Roles in capability termsWhat each role needs, described so a person's evidence can be read against it.Learn more
- Aggregate workforce viewsWhere your people stand as a whole, against what your roles need.
- Gaps that can be closedThe smallest meaningful gap, for a team and for a person, with learning from anywhere counting.Learn more
- No search over your peopleYou cannot browse, filter or rank the individuals who hold records. A person reaches you; you do not reach into their record.
- No succession list, no scoreNothing produces a rating, a readiness figure or a ranked list of people. Confidence is stated about evidence, claim by claim.
- Nothing the organisation ownsEach record is the person's and travels with them. When someone leaves, your aggregate view was bounded to begin with.
Turn potential into performance
Your people. Their records. One honest picture.
Give your people a record that is theirs, and your organisation a view of capability it can actually plan with.
Built this way
- Aggregates only
- Evidence keeps its issuer
- Fairness under review
StrongerPeople.StrongerOrganisations.
- For the organisationAggregate views of what your people can do, in the vocabulary your roles use — for planning, not for picking anyone out.
- For each personA record that is theirs, that grows with their work, and that leaves with them. Nothing here is held by the organisation on their behalf.
- Improvement over standingThe design counts progress for more than where a person stands today, so a workforce view is about direction, not a snapshot.
- What the organisation never seesAn individual's record outside a permission that person granted. No drill-down, no sorting, no shortlist.
Illustrative journeys
What capability looks like from inside
Three journeys the design is built around — the organisation, a person in it, and the person who plans its learning.
Illustrative journeyA head of people at a mid-sized firm
Needs to know whether the organisation can staff a new line of work before hiring outside. She reads the workforce as an aggregate, in the terms the roles use, and sees the gap is smaller than the completion records suggested.
Illustrative journeyAn engineer who taught herself the job
Has done the work for a year without the title. Her record holds it as evidence, attested by the colleagues who reviewed it. When the role opens, she sends one view — and is visible because she chose to be.
Illustrative journeyA learning lead
Stops buying by catalogue. He sees the smallest gaps that matter across a team, with what would close each, and learning from anywhere — a project, a secondment, a course — counts by the same mechanism.
Illustrative journeys, written to show what the design is for. Zynaut Pathways is in development and no customer story, testimonial or measured outcome is published yet.
Whose record this is
Aggregates for the organisation. The record for the person.
Institutional views in Zynaut Pathways are bounded and permissioned. An organisation sees its people as a whole — never any one of them without that person's permission — and the record each person holds stays theirs after they leave. That boundary is not a setting; it is how the thing is built.
- Views built as aggregates, not from any one person
- No drill-down outside a permission the person granted
- No ranking of people against each other
- A role opening is reached by a person's own act
- Each record leaves with the person who holds it
A person's record is held for that person, and travels with them.
You cannot search, browse, filter or rank people. Comparing candidates remains your judgement.
Questions enterprises ask
Before the first conversation
Does the organisation own its employees' records?
No. Each record is held for the person it describes and travels with them when they leave. The organisation's view is an aggregate, bounded and permissioned from the start. What you keep is what the organisation learned about itself as a whole.
Can a manager open someone's record?
Only under a permission that person granted — for example, by sending a view when applying for an internal role, or by choosing the manager as an adviser. There is no drill-down from an aggregate to a name.
Can we rank people for succession or promotion?
No. Nothing produces a score, a readiness rating or a ranked list. Confidence is stated about the evidence behind each claim, claim by claim, and is never compared between people. Who is promoted stays a decision people make, on evidence they can read.
Does it connect to the systems we already run?
Integration belongs to each deployment and is not claimed here. Zynaut Pathways is designed to sit above the records you already hold, not to replace them. What a particular organisation connects, and how, is agreed with that deployment.
Status: In development
Active implementation exists. General availability is not claimed.
What is not claimed. No customer, adoption figure, outcome, partnership or certification is published anywhere on this site, because none has been verified. Every design fact here is a commitment about how the record is built, not a report of results.
What it rests on
- What it rests on
- An implementation exists and is being built against. It is not generally available, and no date for that is claimed.
