A discussion with the producers and directors of the HBO Documentary - Time Bomb Y2K

An Interview with Vincent Balouet - the former Y2K leader in France. If you wanted to know WHY the situation in France was so very different than in the rest of the world? This is the Interview to listen to. Vincent is a French consultant, he specialized in computer science and risk management (ESIEE Master); He  started his career with Y2k, as a computer science expert and wrote most of the French reports and publications between 92 and 99. He was successively called and appointed by computer security associations, CIO associations, French business associations and the French Government. He founded in 2013 maitrisedescrises.com, a French digital consulting online service to large businesses, addressing large systemic economic risks.You can view this and all the other premium content at: www.vimeo.com/ondemand/y2k

Fascinating interview with the Sheriff of London... who was deeply involved with Y2K Efforts in the UK

This is an Interview with Chuck Sevola - one of the leaders within the Prudential Insurance Y2K Project - He was involved in the Offshore Outsourcing to Tata Consultancy Services

Final Episode of the Audio part of this PodcastThere are additional episodes available at: www.vimeo.com/ondemand/Y2KPlease send your feedback on the series to Pdejager@technobility.com

In this episode we explore the big question - Why? Given that we believed that Italy (and others) did very little Y2K remediation did they experience no Y2K problems in the Year 2000? and? James Lauber will talk about a problem potentially larger than Y2K - and one we can do little to mitigate. A Carrington Event. 

The former editor-in-chief of CIO magazine and Computerworld, Maryfran is highly respected throughout the IT leadership community nationwide for her engaging stage presence, deep understanding of business technology issues and extensive network of Chief Information and Digital Officers.  In addition to her previous editorial leadership roles with IDG publications, Maryfran also served in 2016-2017 as an adjunct researcher for International Data Corp.’s IT Executive Programs. She holds a Master of Arts in Journalism from The Ohio State University's Kiplinger Program and a B.S. in Journalism from the University of Florida. Prior to joining IDG, she spent 10 years as a reporter at daily newspapers in Florida, Washington State and Ohio.

Three articles this episode1998 Dec 14th - An UNreal Question - report from the UN1999 Apr 14th - How Bad, How Long, How Likely - a look at Y2K Preparations1999 Dec 20th - A Best Kept Secret - A look at the HTC - High Tech Consortium And James Lauber explores how computers fail in Strange ways

In this episode I look back at a few important articles that appeared on the year2000.com website - My Testimony to the US House of Representatives, Doomsday Avoided - and my responses to the responses to that somewhat controversial article. In addition? We're introducing a new feature - Tangential IT Issues with James Lauber - where we start exploring the 2038 problem in some detail

This is the entire keynote I gave at this conference --- it was one I called 'The Two by Four' talk. An uncompromising, unrelenting talk designed to get the listener to either take action and start fixing the problem, or storm off in a huff determined to prove I was wrong (and then contact me later to say I was correct)Enjoy. 

If you'd like to view the video version of this interview? Head to: www.vimeo.com/technobility/bonusRobert Sawyer is a SF Writer with dozens of books to his credit - and both Hugo and a Nebula awards as bookends to his work. One of his novels, "Flash Forward" was made into a TV series, so it's more than likely you know some of his work already.I'm pushing the next regular episode of the podcast out to July 7th 2020 as I take a small holiday in the midst of the lockdownEnjoy, spread the word and leave some feedback please.

Covid-19 resulted in Lockdowns, which resulted in Unemployment levels that exceeded all past expectations, which resulted in Unemployment systems - usually in the legacy category - bursting at the seams which resulted in call outs to COBOL programmers which highlighted a flaw in how we view 'Legacy Systems' It's not about old code - it's about old systems designs. Since Y2K involved many of these same systems, the question arises did we miss an opportunity? This episode takes a look at one area where Y2K remediation failed miserably. 

What was the Embedded system problem? How we know it was real, what we imagined and what we worried about. If you want to receive a copy of 'A Crock of Clocks'?Email me at pdejager@technobility.com

A Look at the commonalities that people have been discussing... why they occur and why they are normal human behaviours.    

A look at a small subset of the many conferences that were held around the world during the 1990s. The topics presented, how the story changed as we moved from Innovators to Early Adopters, from Early Majority to Late Majority and to save time? We ignored the laggards.

We treated it as a Change Initiative, here's how we did that. 

I thought it would be useful to give you a taste of the interviews that are in the Ondemand section of this Podcast series. Join me as I have a conversation with Murray Campbell who was once a Journalist with The Globe and Mail and who was brave enough to fly with me from Chicago, IL to Heathrow London that fateful night.Spoiler... we survived. p.s. I will continue with 'It was a Change Problem' April 6th - my schedule is a bit up in the air, as is everyone else's these days. 

While Y2K was a technical problem for those who worked directly on it, for myself and a few others who were attempting to create awareness - it was first and foremost a Change Management Problem. I've wrestled with how to present this particular aspect of the project. I could just talk about what I did through the 1990s, but that would only highlight the results of my thoughts and not how I decided what to do. So, I've decided to do this in two parts;- In the first? I'll focus on why it was a change project and what 'Change Concepts' I used to frame the 'awareness' project.In many ways this session is a template for any real world problem where a change is desired, but can't be commanded to happen.I'll spend time on explaining WHAT the template is attempting to achieve and why each component is important.This is what I'll present this friday In the second part, episode #7 - with the framework in place - I'll fill in the Y2K particulars. Together They'll provide a 'theoretical framework' and then a real world example of how to use that framework. Hopefully? You'll be able to take these two as a framework for your future Change initiatives. Note? Episode #6, while it will touch on Y2K - it'll be primarily about 'Change' - and less about Y2KEpisode #7 will highlight exactly how things like, the Y2K cartoon book, the NY Stock Exchange 'de Jager' index, and putting year2000 website up on eBayserved an agenda other than what was visible to anyone other than myself. In more than 2,000 Y2K interviews - none of the above was ever discussed. Join me as I explore the strategy behind much of what was visible.

A quick update on the Y2K Interviews available in the ondemand sections of this podcast You can find the interviews here; www.vimeo.com/ondemand/y2k

Y2K isn't one story - there was a technical side and there was the hyperbole. We went from Y2K - an 'acronym' for 'Year 2000' - a purely technical issue about a field overflow problem to? TEOTWAWKI --- another acronym for THE END OF THE WORLD AS WE KNOW IT!!! ... caps and exclamation points are used deliberately to convey what can only be described as unfettered hysteria. Join Peter as he explores how the message of this technical issue was almost destined to spin out of control. And... his look back on how he was involved on both sides of the final perception of Y2K CheersPeter de Jagerp.s. This podcast is meant to be a lookback at Y2K and those who were involved - IF you were involved? Contact me - your story should be a part of this archive.