two weeks ago i had to write the yearly reviews for my team, and i quickly realized i had two choices:
- spend an hour per colleague filling out the generic company feedback form, the same one used for every job function (the easy route), or
- spend a couple of days building a framework tailored to evaluating a software developer on an agile team (the hard route).
as always, i chose the hard route with the better long-term outlook over the short-term fix.
i have high expectations, high standards, and a comprehensive yardstick for anyone carrying a senior developer title. and since all my team members are seniors, i had to work out a set of principles that make a software team exceptional, a team that’s the 80/20 rule made flesh for our company’s development department.
the pareto principle (the 80/20 rule) says that for many outcomes, roughly 80% of the consequences come from 20% of the causes, the “vital few.”
the result? here’s how i think about an excellent developer:
in short, the things that matter most to me are:
- consistently delivering quality, timely, collective results, while sharing knowledge, collaborating, and communicating effectively with colleagues.
- demonstrating a growth-seeking mindset, personally and professionally, with an ownership attitude.
- acting like a senior: taking initiative to improve the reliability, maintainability, and scalability of the product and the system.
once i finished the framework, the next question hit me: how do i share it with the other team leads in the company so they can benefit from it without much effort?
the answer? build yet another internal app.
with some help from chatgpt i created an app, “dev excellency,” and added it to the internal toolkit i’ve built since joining censhare, called “agilekit,” which helps our development teams with agile (and even some hr) processes.
the app gives team leads (engineering managers, in some companies) an organized way to evaluate developers against the framework. you create an “assessment,” pick a team member, and the system pulls metrics from jira (epics, user stories, story points, average velocity, and more) into tables and charts, so you get an overall picture of what that person achieved across the year. then you work down a list of principles, rating performance on each. when you’re done, the assessment lands in the developer’s dashboard.
i ran it for all my devs, and the response was striking:
almost all of them said they’d never received feedback this detailed in their career. they were happy that every small thing they did over the year, to help the team and the company, was noticed, captured, and counted in their evaluation, and that they now had meaningful, actionable items to improve on.
i think the way we give feedback in the software industry is broken. this was my first attempt to fix it on my part.
what do you think of this framework? how was the last feedback you got at work? was it fair? was it detailed? i’d love to hear your thoughts.