Purely technical problems are as rare as unicorns.

“To my surprise, most of the team was quite motivated to improve things but they didn't really know how.”

The hardest problems to solve are cultural problems.

Many software development teams seem stuck in the imitative stage, when it comes to business practices.

If your project were in an RPG, would your mainline quests be delivering value? Or do you have to do that on side quests?

The concept of servant leadership is heavily watered down, compared to our original examples.

"New physists need to learn about earth, wind, and fire first, then we'll teach them about the periodic table."

What is the role of team "maturity"?

When I learn about a new architectural principle, I like to extrapolate the larger truth, and see if it applies to other domains.

Is your team closer to the few-rules/high-context, or the many-rules/low-context end of the spectrum?

Five books I recommend for followers of mine