#project-commitment

#project-commitment

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.

Curiosity is foundational in the arts, as demonstrated by the Menil Collection's exhibition, which transformed a gallery into an education room through public programs.

Most for-profit companies still confine nonprofit relationships to corporate philanthropy. Donations flow through foundations, annual reports highlight community contributions, and nonprofit engagement is framed as evidence of corporate responsibility.

Operational Excellence practices alone don't guarantee success; implementation quality, organizational culture, leadership commitment, and strategic alignment determine competitive outcomes. Banks implementing identical operational improvement methodologies like Lean and Six Sigma achieve vastly different results due to factors beyond the practices themselves. Success depends on how thoroughly organizations embed these approaches into their culture, the quality of implementation execution, leadership commitment to continuous improvement, and alignment with overall business strategy.

The biggest challenge is that Learning and Development is not positioned as a strategic function in many organizations. Instead, L&D often operates as a function for the sake of having a function. It is rarely used by executive leadership as a strategic support capability and is more often treated as a nice-to-have necessity rather than an integral part of business decision-making.

You must be a TalkNats Subscriber to access this content. Subscribers have access to exclusive content on the TalkNats website and can engage in discussions with other Nats fans. First two weeks are free and then you will be billed $3.99/month. Cancel anytime. Secure payments using Stripe. If you are already a subscriber, simply log in using the form below.

When you take the leap of faith to bring your vision, your idea, to life and start your company, you wear many hats and take on many tasks. You develop the business plan and deck pitch, help build a great product or service offering, create and implement the marketing strategies, make sales, handle customer service and get take-out for everyone during the late nights they're working.

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.

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.

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.

The average CEO makes over 280 times what their company's line worker earns. This is more than 10 times the ratio observed in the 1970s. Looking just at the salaries and bonuses of Fortune 500 CEOs, financial executives, top university presidents, and even some directors of the larger non-profit organizations, you would think that these leaders are performing at high levels-at least levels high enough to justify their huge compensation. Unfortunately, that's not often the case.

I'm not a runner, but I love to watch the relay.

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.