One level below?

[szamanr]

i'm having a hard time using the framework when having career conversations with entry-level developers. basically the first level (e.g. "follows process") is where they're expected to be and the higher levels are something to reach in the future. however, it makes it hard to highlight areas where attention is needed, because there is nothing below their expected level. so, while a junior developer might score 1/5 on each axis, it would be useful if there was another label for 0, so that a manager could see that they score 0 on a particular axis, therefore it's something to draw attention to in a performance review.

[jorgef]

Hi @szamanr,

Sorry for the delay.

An entry-level developer should be assessed against the D1 chart. Although the radar starts at level 1, there are clear expectations at that level that either they meet or not. For example, if they are not following the process correctly, you can highlight that and create a plan so the developer can improve in that area.

Are you saying that there is a need for a "doesn't follow the process" level?

Jorge

[szamanr]

my use case is we use a performance review tool where we created a competency corresponding to each axis. you need to give yourself a score on each competency and can also add a more detailed comment. for entry-level developers i felt it was strange / harsh to have to give the lowest score on each axis, and if somebody is underperforming in some areas, i wanted a way to highlight that.

i ended up adding a custom level on each axis below the first one. sharing it here in case someone else finds this useful:

technology:
0. Uses — is able to use the technology defined by the team, but might require support to learn or adopt it in some cases.

system:
0. Works with — is able to work with the system, but might require support in order to push new features or bug fixes.

people (added two extra levels here, since my direct reports = developers aren't expected to go above "mentors"):
-1. Interacts — interacts with team members on a regular basis but might struggle with effective communication
0. Communicates — effectively communicates with other team members

process:
0. Understands — understands the team processes, but might struggle to follow them in some cases

influence (i feel this could be better, but didn't come up with anything):
0. Limited — makes limited impact or has not been making impact yet

[mgan59]

@szamanr I like these additions, as I've been adopting the rubric into our organization I'm also noticing that my junior devs don't feel like they are represented. Not an ideal feeling for them to have so being able to give them a ranking to baseline against so that level 1 becomes the aspirational goal helps give them feel included and not an imposter.

For Influence I labeled 0. Self -- makes an effort to improve skills and learnings to begin building a halo to impact others