Principles
Four principles, built into the product.
Yakini publishes findings about work that people did. How it does that is decided by four principles, and each is built into the product rather than left to a policy document.
Evidence, not status.
What it means
A verdict cites code at a commit, an executed test or a delivery record. Claims in tickets and comments are things to check, never evidence.
In the product
- Every citation is checked against the repository at the audited commit
- Each verdict lists its evidence, and what is still missing
- A percentage in a ticket is compared with the evidence, never confirmed as a precise figure
- Release notes, sprint updates and milestone declarations are checked as claims too
Abstain rather than guess.
What it means
When evidence is missing, inaccessible or invalid, or the budget runs out, the verdict is Unverified and says why. A contradiction is never published without an independent challenge.
In the product
- Unverified is hatched everywhere, so unknown never reads as done or as failed
- An audit that couldn’t finish says nothing against the work
- Confidence stays capped until enough outcomes have been checked
- Forecasts hold back until a team has enough completed, audited sprints
Fair to engineers.
What it means
Findings stay private to the assignee during a review window. Engineers can add context and challenge any finding, and challenges are reinvestigated with the evidence they point to.
In the product
Leaders don’t see new findings until the review window closes
Self-checks are seen only by the engineer who ran them
Nobody approves findings about their own work
Only evidence changes a verdict: a decision on a challenge can’t overrule one, a new audit can
About delivery, not people.
What it means
Yakini never ranks, scores or compares individuals. It reports on work and on how teams deliver, never on how one person measures up against another.
In the product
No individual productivity scores, leaderboards or comparisons between people
A person who leads someone can review that person’s claims from the last week at most; the reason is recorded and shown to them
Signals about one person are shown to that person, and to others only if they share them, for a limited time
Sensitive team figures, such as pulse answers, stay off until the organization turns them on, and show only for groups above a minimum size
Speed metrics always come with quality metrics, against the team’s own history
Privacy profiles, and a transparency centre where members see what is measured and who can see it
See how it treats your teams.
We’ll show you the review window, challenges and privacy settings in a sample organization, and answer your questions about rolling Yakini out fairly.
- Hosted, dedicated or self-hosted
- Your choice of models, self-hosted too
- Pricing set out in a written proposal