I’ve talked previously about technical debt. Should we stop other work to address it? What is the cost of delay? And that we should watch out for technical bankruptcy. But … Continue reading How much time should we put aside for tech debt?
Trust might seem like a nebulous thing, but it’s based on very concrete things. Some time ago I was lucky enough to be part of a workshop run by Laurence … Continue reading Trust from delivery
Having worked as both a team manager and a consultant, I find there is a common balancing act when introducing people to a new approach or idea, such as setting … Continue reading Balancing ownership and quality
In a discussion the other day about measuring the effectiveness of developers I looked for a document I’d written a while back for exactly that purpose. But when I opened … Continue reading Are we seeking to evaluate or improve?
I often hear about organisations that have tried to implement change and it’s not gone well. Sometimes those are organisations in which I’m working. Here, “not gone well” means the … Continue reading Be aware of the organisational brakes
Very technical roles require very technical skills. Information security experts, software developers, architects and others all need specialist skills as a baseline. But in general those people (like so many … Continue reading Good technical people need good non-technical skills
Some people are often advised to not solutionise—that is, don’t jump to conclusions about how to solve a problem. Instead they are urged to make sure they understand the problem … Continue reading The right time to define a solution