Continuous Improvement: An ongoing effort to improve products, services, or processes. These efforts can seek “incremental” improvement over time or “breakthrough” improvement all at once.
If you haven’t read it, I highly recommend the book: “The Progress Principle.” The authors’ explored the question: “What really makes people happy, motivated, productive, and creative at work…?” Plot spoiler alert: the title is a dead giveaway on what makes us and our teams tick: The strongest contributing factors: …
What makes your teammates lose sleep at night? The best way to find out is simple, but not always easy: ask them!
A refresh to one of my more popular posts…
Now more than ever companies are exploring ways of measuring and visualizing how their teams are doing (KPI’s; ROV’s, NPS, etc.,)
The general idea being ya can’t improve what ya don’t measure. And without some sort of systemic approach with clear visualization – things would very much be a guessing game.
When surveyed, 80% of software developers reported they believed their skills were above average. Overestimating one’s desirable qualities relative to other people, is known as the Illusory Superiority Bias, aka the Lake Wobegon effect, one of many cognitive biases.
Bring up the topic of “technical debt” to a software engineer, a product owner, a stakeholder, or heavens above, the gold owner. What happens? Do you get frowns? Smiles? Nervous fidgeting? Technical Debt is such a loaded, misused, and misunderstood term. I imagine in most conversations when the topic comes up we probably aren’t even …
