Groundhog Day

Someone should write Groundhog Day for tech.

When Phil first arrives at his new job, he assesses its application landscape and realizes that he owns 5 redundant systems. Obviously, he should only have 1 so he brings in the 6th to take out the 5 tombstones.

Fast forward two years and a lot of hard work that retires 80% of each of the 5 systems but recognizes the complexity around retiring that final 20% and bzzzz-- the alarm clock reads 6:00 am.

When Phil first arrives at his new job, he assesses its application landscape and realizes that he owns 6 redundant systems. Obviously, he should only have 1 so he brings in the 7th to take out the 6 tombstones.

--

Don’t be like Phil. He’s why every enterprise has 12 of everything-- 13 if you wait for the executive clock to reset.

Break the cycle by investing in one of the systems that you already own; preferably the one with the most open architecture. If they’re vendor products, pick the partner that will invest alongside you in eliminating the other tombstones.

If you’re in enterprise sales (Ned Ryerson), that’s your hook: “we’ll invest in getting rid of your tombstones before your alarm clock resets.”

Just make sure they’ve seen the movie. Otherwise they’ll call security.