What three rules help you write great performance feedback? Which part of your feedback is the most important?
An opinion column for developers. Brutally honest, no pulled punches.
What three rules help you write great performance feedback? Which part of your feedback is the most important?
How do you make fair choices and impose fair restrictions? Why wouldn’t you be transparent?
What subtle changes can you make to be productive working from home? How do you keep the peace with your housemates and kids?
What makes high performing teams twice as likely as low performers to exceed performance goals? Which wonderful, wasteful, and disgraceful practices do teams follow?
How can good communication save you grief? What does a communication plan look like for rollouts, reorgs, and outages?
The next column will appear in February.
When is being lazy advantageous? Why not always jump into problems, work and team assignments, and new projects?
What purpose does a root cause analysis serve for incidents? Why ask why so many times?
How will I transfer the knowledge of the departing employee? What should I do to help my team cope with the loss?
What’s wrong with designating feature work as good, bad, and ugly? How should you categorize feature work and why?