I wrote the first of a three-part series about looking at culture when you hire people last month. I posted that Pragmatic Manager, Your Culture: What is Okay for You to Discuss? and forgot to tell you. If you are on my email list, you received today’s Pragmatic Manager about what the organization values and rewards. Next up is how people treat each other.
Many people are familiar with the build-break-build method of starting with positive feedback, then the negative, and then more positive. But is that the most effective way to convey your compliments and criticism? Recent research has been done to determine the most effective, and polite method.
Uncertainty doesn't have to be a bad thing, but many say they'd rather know there were definitely problems coming, rather than be uncertain about whether there were or not. What do you prefer? Do you spend valuable time trying to prevent uncertainty?
I’ve had several conversations in email and with clients recently that have all been about this question: “What do we do about our infrastructure?” Either the project or the program has to create/update/upgraded their architecture or automated test infrastructure, pay down technical debt, or somehow do something that’s not part of a story.