Scrape Result 2236
Id 2,661,942
Active 1
Created Epoch 1,736,381,702
Modified Epoch 1,753,252,565
Original Ad Id 0
Collationcount 0
Collationid 0
Enddate 0
Hasuserreported 0
Hiddensafetydata 0
Impressionsindex 0
Isaaaeligible 0
Isactive 0
Isprofilepage 0
Pageisdeleted 0
Creation Time 0
Page Id 542,112,098,974,863
Page Is Profile Page 0
Is Reshared 0
Version 0
Page Like Count 9
Page Is Deleted 0
Spend 0
Startdate 0
Created 1/8/25, 6:15 PM
Modified 7/23/25, 1:36 AM
Status

active

Notes
Adarchiveid
Currency
Entitytype
Fevinfo
Gatedtype
Hidedatastatus
Impressionstext
Pageid
Pageinfo
Pagename
Reachestimate
Reportcount
Ad Creative Id
Byline
Caption

kenlentzcoaching.com

Cta Text

Learn more

Dynamic Versions
Effective Authorization Category
Display Format

IMAGE

Title

Home

Link Description

Fast-track your career as an IT managerwith a service designed to help you make the transition from being technically skilled to understanding the core business skills necessary to succeed as an upwardly mobile IT manager. These comprehensive resources from Ken Lentz IT Management Coaching equip you...

Link Url

http://kenlentzcoaching.com/

Page Welcome Message
Page Name

Ken Lentz CIO Management Coaching

Page Profile Picture Url

https://scontent-iad3-2.xx.fbcdn.net/v/t39.35426-6/473114687_587773584107993_4994754837716044199_n.jpg?stp=dst-jpg_s60x60_tt6&_nc_cat=111&ccb=1-7&_nc_sid=c53f8f&_nc_ohc=lQ60FShwG4kQ7kNvgGDF-an&_nc_zt=14&_nc_ht=scontent-iad3-2.xx&_nc_gid=AUuE5tO7sdwDPC3_L9F-VY7&oh=00_AYDsGJeSodQkBsO2S1QTKFARjm1mgP3VPW2JXXRlvA9DmQ&oe=6784F6AE

Page Entity Type

PERSON_PROFILE

Instagram Actor Name
Instagram Profile Pic Url
Instagram Url
Instagram Handle
Body

’ll never forget the day our mission-critical software went live. It was supposed to be a defining moment for my IT department—a testament to our capability to deliver tailored solutions for the business. Instead, it turned into one of the most humbling experiences of my career.

The name of the software was going to be “Catalyst”. But, as you will read, it should have been named “Catastrophe”.

The software had been in development for months, designed to handle a core function of our operations. It wasn’t just a tool; it was the tool. The project was driven by the needs of a particular business unit, and I worked closely with their manager, Kelly, to ensure it met every requirement. Kelly was sharp and confident—a natural leader. When she assured me that her team had thoroughly tested the software in their environment, I believed her. After all, she had as much at stake as I did, if not more.

Looking back, I realize I wanted to believe her. The deadlines were tight, and our resources were stretched thin. Her reassurance meant I could avoid delaying the launch. The thought of holding things up for additional testing felt like an overstep. I was the IT Director, not the gatekeeper of their processes—or so I thought.

Launch day arrived with an air of cautious optimism. The initial rollout seemed smooth enough, but within hours, the cracks began to show. Reports didn’t reconcile. Transactions were failing. Users were locked out of key features. What was supposed to streamline operations instead ground them to a halt. My phone was blowing up with calls from executives demanding answers.

As it turned out, Kelly’s team hadn’t done any meaningful testing. They had assumed we would catch everything on our end. We, in turn, had trusted their assurances. It was a perfect storm of misplaced confidence and miscommunication, and the result was catastrophic.

The next 72 hours were a blur. My team and I didn’t leave the office, fueled by stale coffee and sheer determination. We tore through the codebase, patching what we could and rewriting entire sections when necessary. Kelly’s team was suddenly very available to validate changes, a little too late for my taste. Every fix felt like triage on a sinking ship.

In the end, we managed to stabilize the system enough to keep the business running, but the fallout was unavoidable. Trust was damaged—not just between IT and the business unit, but across the organization. The blame game started almost immediately, with fingers pointed in every direction. I took full responsibility, publicly and privately. It was the right thing to do. I had made the call to trust Kelly’s word without verifying it myself, and that decision cost us all.

The experience changed the way I lead. From that point on, I implemented a policy: no system goes live without an independent review and verification of user testing. Trust is vital, but so is accountability. I also made it a priority to build stronger relationships with business units, ensuring clear communication and mutual understanding of roles in every project.

The rewrite eventually turned into a success story, but the scars from that launch remain a constant reminder. Leadership isn’t about trusting blindly—it’s about ensuring everyone is rowing in the same direction, with the same level of commitment. It was a painful lesson, but one I’m grateful for. It made me a better leader, and our team, a stronger unit.

Branded Content
Current Page Name

Ken Lentz CIO Management Coaching

Disclaimer Label
Page Profile Uri

https://www.facebook.com/KenLentz59/

Root Reshared Post
Cta Type

LEARN_MORE

Additional Info
Ec Certificates
Country Iso Code
Instagram Branded Content
Statemediarunlabel