Calibration as a Continuous Practice
Most engineering teams treat performance calibration as an event that happens once or twice a year. The rest of the time, expectations and impact are left implicit. The result is familiar: surprise at review time, vague feedback, and missed opportunities for growth that were visible months earlier.
Software teams learned long ago that releasing code in large, infrequent batches is a recipe for failure. The same logic applies to people. Engineers iterate constantly — learning new skills, refining approaches, and delivering work in stages. The processes used to evaluate and support that work should match that cadence.
An always-on approach to calibration means alignment around expectations and performance is maintained throughout the review period, not reconstructed after the fact. This removes unpredictability from performance conversations and lets managers recognize impact as it happens. It also surfaces specific, just-in-time growth opportunities for each individual.
Consider some common questions about your own experience:
- When did you last receive feedback, and how specific was it?
- Do you always know how your work connects to role expectations and organizational goals?
- Have you ever been surprised by a performance evaluation?
- Could you recall all your contributions in detail when review time came?
If any answer is "no" or "I don’t know," you’re not alone. Many engineers go years without meaningful feedback. Even teams that do hold reviews often try to assemble a full picture of a year’s work in a single sitting, relying on faded memories and general statements.
Problems with Infrequent Review Cycles
Traditional performance reviews aim to capture an individual’s impact over a given period, reward them for it, provide feedback, and identify stretch opportunities. In practice, infrequent reviews undermine all three objectives.
Missed Contributions
When reviews are rare, the full scope of an individual’s work is rarely captured or recognized. Trying to reconstruct months of contributions at the end of a window introduces several issues:
- Memory fades, and specific contributions get lost.
- Descriptions of work become general statements without detail.
- Recency bias skews the view of the entire review period.
- Managers and individuals hold different or incomplete views of what was accomplished.
Without a complete view of an individual’s output, managers miss chances to reward effort and guide growth toward long-term goals.
Slower Growth
The real cost of infrequent calibration is lost growth. Frequent feedback lets engineers try new things and adjust early. Rare feedback means course corrections happen late — or not at all. Problems include:
- Little opportunity to experiment and iterate on skills with early feedback.
- Feedback arrives too late to be actionable.
- A lack of specificity about what the next level in one’s career requires.
- Individuals overstay on teams when growth opportunities exist elsewhere.
Continuous calibration keeps engineers moving forward, identifying opportunities when they’re ready and adjusting paths before small issues become blockers.
The Quarterly Calibration Document
One practical mechanism for always-on calibration is a living document updated each quarter. Shopify’s engineering teams use a quarterly objectives template with six sections:
- Intended Outcomes: what the individual plans to accomplish in the coming quarter.
- Top Accomplishments: the most impactful work completed so far.
- Other Accomplishments: additional meaningful deliverables.
- Opportunities for the Next 3–6 Months: growth opportunities not yet available but expected soon.
- Feedback: input received from coworkers.
- Quarterly Review: a table linking the individual’s specific impact to organizational expectations for their role and level.
The individual starts each quarter by drafting their intended outcomes. During the first one-on-one, the manager and individual align on those outcomes. From there, the individual updates the document weekly before each one-on-one, capturing accomplishments and feedback as they occur. Because the document is reviewed alongside role expectations, both parties always know where the individual is meeting, exceeding, or missing expectations — and what development opportunities lie ahead. Performance is calibrated every week, not just at the end of a cycle.
Weekly Review in One-on-Ones
Always-on calibration requires dedicated time within weekly one-on-ones. These meetings already provide a forum for coaching and mentorship. Adding regular calibration lets managers:
- Give feedback tied to specific work and its impact.
- Recognize contributions consistently.
- Point to growth opportunities connected to the individual’s development plan.
- Identify deviations from intended outcomes early and take corrective action.
Shared Ownership
The quarterly calibration document is driven by the individual, with the manager acting as mentor and coach. Individual ownership means the engineer sees firsthand how their objectives map to role expectations and organizational priorities. They know what they’ve done and why it matters. The manager’s role is to provide guardrails — helping shape realistic intended outcomes for the role and level, and connecting individuals to upcoming work that aligns with their growth trajectory.
Team Feedback, Incorporated Early
Waiting to gather peer feedback until review time produces vague, unhelpful commentary. Infrequent collection tends toward statements like "She did great on this project" or "They’re easy to work with" — neither of which drives improvement. Useful feedback is candid, specific, timely, and behaviour-focused, delivered from a place of care.
Discussing feedback through the quarterly document and weekly one-on-ones enables teams to:
- Capture specific, timely input from coworkers.
- Spot and act on growth opportunities quickly.
- Reinforce that feedback is part of everyone’s development.
In practice, this means discussing any peer feedback received during the previous week in each one-on-one. Managers also actively solicit input that colleagues may not have shared directly. Positive feedback is logged for future promotion and compensation conversations; constructive feedback is dissected for specifics and future application. Where relevant, new intended outcomes are folded into the quarterly document.
Addressing Performance Problems Immediately
When an individual appears off track for their intended outcomes for performance-related reasons, managers must act immediately, not wait for the next formal cycle. Difficult conversations only get harder with time; starting them early gives the individual the best chance to course correct.
The reality is that calibration sessions happen weekly, not yearly. With that cadence, engineers have ample time to address issues before they become serious — but only if managers raise them as soon as they appear.
When Outcomes Are Missed
The first step when an intended outcome isn’t met is to clarify which type of outcome it is, since the response differs for personal development goals versus role and level expectations.
Personal Development Outcomes
Beyond meeting current role expectations, individuals should be progressing toward their longer-term ambitions, typically mapped out in a development plan. These plans break down long-term aims into short-term intended outcomes. When these are missed, it slows progress toward the broader goal but does not indicate a performance problem in the current role. In this case, the right response is to reinforce why these outcomes matter, determine whether they remain appropriate, and if so, reprioritize them going forward. It’s also important to openly discuss how missing them affects the timeline for long-term goals so everyone stays aligned on development expectations.
Role or Level Outcomes
At the start of each review period, role- and level-specific intended outcomes are agreed upon. If those outcomes look like they won’t be hit, the reason needs to be identified. When shifting priorities are the cause, the work already done should be acknowledged and new outcomes set for the remainder of the period. If the problem is that the individual lacks the skills or capability to deliver, a performance improvement plan may be necessary to help them build the skills required for the expected level.
Why a Quarterly Review Cycle Works
Calibrating impact every quarter — or at least on a cycle shorter than a year but longer than a month — avoids the pitfalls of an annual review. A year is simply too long a window: too much happens to evaluate meaningfully, and there’s too much data to work through at once. Breaking the year into smaller review windows has clear benefits:
- It highlights impactful windows of contribution — a great quarter can be celebrated even if the full year is only average.
- It creates snapshots of smaller periods that can serve as a highlight reel when reviewing the whole year later.
- It provides a performance rating for each period, enabling early course correction.
Tracking and discussing work specifics, impact, and growth areas on a continuous basis is the only way to get an accurate picture of an individual’s contributions — one that genuinely reflects whether they’re meeting organizational expectations for their role and level and whether they’re getting the right growth opportunities. Relying on year-end feedback and a collected list of accomplishments is insufficient. At best the list is incomplete; more importantly, the opportunity to accelerate someone’s growth has already passed. That missed growth compounds over time, and the lost impact of not calibrating continuously with your team is significant.
