Posts

Showing posts with the label process improvement

Your Team's Junk Drawer: Why Process Without Context Creates Organizational Friction

Image
  TL;DR: In 7 minutes, you'll learn how to identify which processes are organizational junk drawers and how to replace rigid checklists with clear context, so your team moves faster and delivers better results. Research by Gary Hamel and Michele Zanini found that the U.S. economy loses approximately $3 trillion annually (nearly 17% of GDP) due to excessive bureaucracy and process bloat. Your organization is likely contributing to that number without realizing it. The problem is not that you have processes. The problem is you keep adding processes "just in case" without ever removing the ones that no longer serve you. Like a junk drawer filled with items you might need someday, your processes accumulate rules created for problems that happened once years ago and will never happen again. The Seven-Dumpster Wake-Up Call I learned this lesson the hard way when my manager decided our team needed a cleaner work environment. Once a quarter, we stopped everything and cleaned...

Stop Optimizing for The Past

Image
I have had the fortune of learning a lot about development processes and how people approach work. It is always amazing to understand what excites people about work and how they see their role in creating our products. I find great pride in helping people evolve their practices to improve how products come together. Let's explore some observations I have made about what drive people to optimize, and some ideas on how to move to a different way of thinking. What drives optimization? I have noticed a typical driver in how many groups and companies define their development practices. These practices start by working to prevent pains the team has encountered in the past. We build our documentation, processes, and automation around avoiding things that have happened to us before.  “This happened once, three years ago, and in response, we implemented a rule to prevent it from happening again.”  I will share a scenario from my experience.  One of the teams I work closely w...