S1E915 February 2020

S1E9: PMO 2020 Predictions - By Dale (Bonus episode)

S1E9

S1E9: PMO 2020 Predictions - By Dale (Bonus episode)

0:000:00
100%

Any reference to projectlabs.co or the pmoshow has now been superseded by projectchatterpodcast.com. For more information, blogs, and contact details please visit www.projectchatterpodcast.com. Enjoy the pod… Dale spends some time reflecting on what...

Related Episodes

More conversations on similar topics

S1E17

S1E17: AIPM Presentation 'Disrupting PMO' presented by Val Matthews (bonus episode)

In this episode Val Matthews had the pleasure of presenting his views on disruptions to PMO and technology advances to the members of AIPM. (Technology), what could it mean to PMO's? A new role for PMO in projects? The Australian Institute of Project...

Listen Now
S10E228

S10E228: Shadow AI: Your Free ChatGPT Is a Data Breach with Joe Klich

Someone on your project pasted the schedule into a free ChatGPT account to get it analysed. That is a data breach, and the confidentiality clause they signed does not care that it was convenient. Joe Klich calls it shadow AI, and he thinks it is the most under-discussed risk in construction right now. Joe spent 18 years in commercial construction operations, from the field through executive leadership, before founding Klich Consulting, an operational risk advisory for construction executives. He joins Dale and Val to talk about how fast AI capability is actually doubling (the METR curve has gone from every seven months to every three), why most people cannot keep up and what that gap means for project teams, and how regulators in the US, UK and Australia are all reacting rather than leading. In this episode: why Chinese models at three cents a task will put AI everywhere and magnify the governance problem; the difference between AGI and ASI and why nobody smarter than you will design their own off switch; AI as a hammer, not a colleague; why companies get AI backwards by starting with the tool instead of their people; the cybersecurity parallel from 2010 and why insurers, not legislators, will force AI governance by refusing to pay for AI-related losses; what the jobs of the future look like when a team of ten becomes five; and Joe's closing advice for anyone using AI at work. Connect with Joe Klich on LinkedIn: https://www.linkedin.com/in/joe-klich-96020635/ Hosted by Dale Foong and Val Matthews. The Project Chatter Podcast has been running since 2018 and is free to access, always.

Listen Now
S10E227

S10E227: Your Project Is On Time. So What? with Matthieu Sors

Your project is green. Every milestone hit. And the CIO still can't tell the business what value it created. Matthieu Sors has watched that conversation play out inside banks, telcos and software companies for 20 years, and he thinks the fix is a shift most PMOs haven't made yet: stop tracking outputs, start owning outcomes. Matthieu is French, based in Sydney, and has spent his career on portfolio management: NBN, banking EPMOs, and now Planview, where he works with executive teams on what comes next. He joins Dale and Machine Gun Martin to unpack the difference between an output and an outcome, why senior executives are already ready for the outcome conversation (and why the middle layer isn't), and what OKRs look like when they are done well. In this episode: the bank that reported 10 platinum, 6 gold and 5 silver milestones and still couldn't answer "what did we deliver?"; why large programmes are being broken into waves; delegation and empowerment without blowing the budget; the asset lifecycle and the sponsor role on infrastructure projects; value streams and product operating models; why OKR rollouts fall apart after two quarters; AI, quantum and the human in the loop; and Matthieu's final thought for every project manager updating their CV in a panic: you are not going anywhere. Connect with Matthieu Sors on LinkedIn: https://www.linkedin.com/in/matthieusors/ Hosted by Dale Foong and Martin C. The Project Chatter Podcast has been running since 2018 and is free to access, always. Contains one instance of strong language.

Listen Now

Enjoyed this episode?

Subscribe to never miss a conversation with project experts