I got a degree from Douglas College in programming and business management. I understood the business side more and was better at that than at being a coder.
To successfully repair after a mistake, you need to acknowledge and name the mistake, validate the other person's feelings and viewpoint, and create a plan for the specific actions you will take to prevent this mistake from occurring again.
Well, our guest today argues that the best way is by moving to a more project-driven model of work, up and down the organization from the corporate level to individual teams. He wants us to both ruthlessly prioritize as well as stay fluid so that we're identifying strategic goals, assembling teams to go after them, evaluating as we go, and then either continuing, shifting, or disbanding based on our outcomes.
I see this daily in veterinary medicine, where high burnout rates cost the sector upwards of $2 billion per year. It's a challenging environment with long hours, stressful workloads and patients that can't even tell you what's wrong. But I've found that the best way to boost performance and even increase capacity with maxed-out teams is to address the underlying operational issues.
Scrum has a bad reputation in some organizations. In many cases, this is because teams did something they called Scrum, it didn't work, and Scrum took the blame. To counter this, when working with organizations, we like to define a small set of rules a team must follow if they want to say they're doing Scrum. Enforcing this policy helps prevent Scrum from being blamed for Scrum-like failures.
Your AI pilot showed 94% accuracy improvements. The LLM is yielding solid results. You're getting defunded anyway. The reason? You solved a problem AI can solve. Your budget-holder needed you to solve theirs. Companies launch AI pilots that produce results, then stall at scale. The team's diagnosis: "They don't get it." What's really going on: These projects never earned budget-holder buy-in.