Daniel did not meet the required CORI threshold this cycle and moved one step back.
Early positive signals. Reliability is forming, but it has not yet been demonstrated consistently across cycles.
Next strong assessment moves to Consistent. Next weak assessment moves to Inconsistent.
The current CORI pattern does not yet support greater reliance, autonomy, or independent ownership. This team member may contribute in parts, but the pattern shows consistency gaps that require close leadership attention. At this stage, the assessment supports keeping responsibility contained until stronger reliability signals appear.
This read reflects the Ownership and Relationships ratings — see “What’s driving this read” under Operating Pattern.
This is not a rejection of the person. It is a clear signal that their current operating pattern is not yet dependable enough for increased autonomy.
This person may be useful, but they are not yet leverageable. A useful person can complete tasks in the right conditions. A leverageable person reduces leadership load. Right now, the assessment indicates that leadership energy is still required to ensure consistency, follow-through, or independent movement.
Readiness for more responsibility requires more than contribution. It requires consistent reliability without repeated chasing. The current pattern shows one or more CORI pillars not yet strong enough to indicate readiness for increased autonomy.
Competence (9/9) and Initiative (7/9) are current strengths, but Ownership (2/9) and Relationships (2/9) are in the Needs Work range. Because Ownership and Relationships are currently what most limits reliability, the read below follows from this specific pattern of ratings — not a general judgment about Daniel.
Capability is real, but neither accountability nor collaboration support it. This combination is operationally dangerous — strong output without ownership produces unpredictable delivery; strong output without collaboration produces a team-tax. The talent is present; the reliability foundation isn't.
This assessment does not yet support promotion or people-leadership responsibility. Close support and a contained scope are likely to be needed for now, with attention to how ownership behaviour holds up under pressure before scope is extended.
The current pattern does not support allocating additional reliance, responsibility, or development investment at this stage. The immediate priority is improvement, not expansion.
Show visible improvement before additional responsibility is considered.
Delegation confidence is reduced
Leadership follow-up overhead increases
Commitment reliability limits autonomy
This is the most serious constraint because ownership is the foundation of reliability.
Current pattern may create follow-up load, missed commitments, delayed escalation, and reduced confidence in delegation.
Weak ownership and weak collaboration both attack reliability from different angles. The combined effect is that this person is currently neither dependable on output nor easy to work with — strengths elsewhere cannot fully recover this.
Strong individual capability with weak collaboration creates disproportionate cultural cost. Output may be high, but team reliability, peer hesitation, and emotional drag accumulate quietly until they show up as attrition or escalation reluctance.
Each pillar score is the sum of three behavioural items. Every rating is anchored to a captured example and translated into a leadership interpretation and business impact.
Capability is currently a strength. This person appears able to understand work, improve, and deliver with acceptable quality.
“Ships production-grade work; his pull requests clear review with minimal rework and rarely reopen after merge.”
Supports reliance and delegation at current scope.
Low management overhead.
“Reframes vague tickets around the real business outcome before writing a line of code — he solves the problem, not the literal request.”
Supports reliance and delegation at current scope.
Low management overhead.
“Absorbs technical feedback fast; the same review note almost never has to be made twice.”
Supports reliance and delegation at current scope.
Low management overhead.
Ownership is the most serious risk signal. Without ownership, competence and relationships cannot fully convert into reliability.
“When the Q2 launch slipped he opened with external blockers and team dependencies before acknowledging his own missed handoff.”
Reduces delegation confidence.
Creates management overhead.
“Commitments routinely need a reminder; two of the last three deadlines moved without a proactive heads-up.”
Reduces delegation confidence.
Creates management overhead.
“Flagged a minor API risk early but sat on the larger data-migration risk until it forced a weekend rollback.”
Reliable in parts; not yet consistent.
Periodic oversight required.
Working with this person currently creates friction or resistance. This is a structural risk for scale, leadership exposure, and team culture — strong individual output does not offset relationship instability. The cost compounds quietly across the organisation in ways that surface as attrition, escalation reluctance, or quiet avoidance.
“Peers have started routing design reviews around him to avoid the friction his comments create in the room.”
Reduces delegation confidence.
Creates management overhead.
“Feedback lands intellectually but behaviour change is inconsistent — improves for a sprint, then reverts.”
Reliable in parts; not yet consistent.
Periodic oversight required.
“In architecture debates he defends his position well past the point the decision has already been settled.”
Reduces delegation confidence.
Creates management overhead.
Initiative is currently a strength. This person shows signs of creating movement without always needing pressure or instruction.
“Moves confidently on well-scoped gaps but stalls and waits for direction the moment requirements turn ambiguous.”
Reliable in parts; not yet consistent.
Periodic oversight required.
“Rebuilt the CI pipeline unprompted and cut build times by half — a clear, unsolicited systems improvement.”
Supports reliance and delegation at current scope.
Low management overhead.
“Output stays sharp under deadline pressure but visibly dips during quieter, unmonitored stretches.”
Reliable in parts; not yet consistent.
Periodic oversight required.
Commitment & follow-through discipline
Early risk communication
Accountability without reminders
This assessment does not yet support scaling responsibility. The most useful focus now is stabilising the weakest operating behaviours first.
Honour commitments without reminders, communicate risks early, and take responsibility before defending circumstances.
You are not being written off, but the current pattern needs to change. The next stage is not about proving intention. It is about proving consistency. For the next 90 days, the focus should be on creating visible evidence that reliability can increase.
CORI Score = the sum of all four pillar scores (0–36). Each pillar = three behavioural items rated Mostly True (3), Sometimes True (2), or Rarely True (0). An assessment meets the CORI standard when the score is at least 28 / 36 with no pillar in the “needs work” range — meeting it moves the person up one reliability band, missing it moves them down one. Reliability is earned over repeated cycles, not declared from a single assessment. Scoring is deterministic — the same answers always produce the same report. CORI measures business reliability and readiness for responsibility; it is not a personality test, a psychological diagnosis, or an AI prediction.