Would you think that the 1989 movie “Field of Dreams” has just as much to do with IT operations as it does with baseball. Remember the backstory?field_of_dreams_poster

The movie’s protagonist, Ray Kinsella, is an average and unsuccessful farmer, with regrets about his past. Like many on an IT team who gets struck with a bolt of inspiration – an idea for an IT-related project (a new application or service, probably along the lines of “what if we had a way to…” or “what if we did this:”) – Ray listens to a voice in the night telling him “If you build it, he will come.” He proceeds to plow under his crop, and construct a baseball field in the middle of his Iowa cornfield

Then Ray’s “project” develops its own momentum – the seemingly now-corporeal ghost of Chicago White Sox outfielder Shoeless Joe Jackson walks out of the cornfield bordering the newly built baseball field, admires everything, thanks Ray for what he’s done, and asks to come back – with “friends.”

Now Ray on an IT team would have had a similar experience: Someone gets wind he’s been working on a Skunk Works project that, although radical, could be something amazing. Shoeless Joe is like that first test user that becomes the unintentional evangelist, and quickly starts to build a critical mass among users.

At this stage in the IT project, things are going well: The user base has grown, the old guard (shown in the movie as 1960s anti-establishment author Thomas Mann) at first grudgingly agrees to take a look at the project, then likes what it sees, becomes a strong advocate, and things evolve quickly (maybe even moving to formal alpha testing). In the movie, Shoeless Joe has brought a throng of other now-corporeal ghosts to play baseball once again on Ray’s field (more users, all of whom love the work Ray’s done). And Ray’s wife Annie stands by her man, despite a wave of criticism coming from her brother Mark, the financial advisor and antagonist who absolutely cannot see or understand Ray’s vision, and what he’s done.

Mark personifies the non-IT finance person who absolutely cannot see any value in an IT project. The premise makes no sense. It’s not about economic optimization. Losses need to be cut and risk averted. (Sound familiar?) Even the testimonies of others can’t budge this person from his position. And without the ability to secure funding, that IT project isn’t ever going to go anywhere and become something big.

Getting past this immoveable object requires an “ah-ha” moment, where the clouds part and insight illuminates the closed-minded. For Mark, it was seeing the “project” in a context that mattered to him. (In the movie, Mark could finally see the ballplayers after one of them, Moonlight Graham, willingly chose to step off the safe environment of the field to help Ray’s daughter Karen, who had fallen from the bleachers.)

So now Ray’s IT project has its financing. It’s gone from a germ of an idea, been incubated, grown, overcome hurdles, proven, and spread among users. It’s been promoted. (Thomas confidently predicts that people will come.) In IT project terms, it’s ready to go live.

In the movie, that go-live moment is represented by Ray finally getting his reward for all his efforts: The newest player to arrive at this field is no other than his father, with whom, from a soliloquy early in the movie, Ray had significant, gnawing regret from their long, unresolved estrangement. The movie delivers its biggest tear-jerker moment when Ray, who, as a rebellious teen, steadfastly refused to throw a baseball around with his father, was now able to fix that by asking his father to have a catch.

And they did. And the credits to the movie rolled, showing a fade-to scene of miles and miles of cars driving toward Ray’s field. And you might think that would be the end of the IT analogies here as well. But it’s not.

Although the biggest IT lesson of all came from the end of the movie, it had nothing to do with Ray and his father playing catch. Just before that sequence, the most level-headed character in the movie, Ray’s wife Annie, simply and succinctly proved to be the voice of reason in one sentence: “If all these people are going to come, we’ve got a lot of work to do.”

Annie represents IT operations. She supported Ray’s idea (the IT project) from the beginning. (Many I’ve spoken to in IT operations say “Do we ever really have a choice of not supporting it?”) As IT operations does, she kept things running smoothly despite the chaos unfolding. And, as the voice of reason to any IT project, IT operations provides the view that starts to answer the question “What happens now that we’ve gone live?”

And Annie’s insight provides the biggest unstated IT lesson from the movie: Although the IT project and the way it unfolds is important (and makes for a good story, in this case), you can’t neglect the IT operations view of the world: Things need to happen after the go-live date to ensure IT service delivery environment (i.e., infrastructure) keeps running smoothly and performs as expected. And consider the long-term impact of what’s now changed in the environment. In IT terms, the project’s success has created a performance bottleneck in the environment (the traffic jam of people trying to get to the field). And that’s just for starters: Where will all these people eat, sleep, and bathe? And is there a wi-fi hotspot nearby?

Good IT projects can be a tremendous experience. They can overcome obstacles to create new value, change things for the better, and get people to see things in a whole new light. But a key takeaway to keep in mind is that they, like a movie, tend to have a story arc: a perceived beginning, middle, and end.

And it’s really that “end” that needs to be thought of as the beginning – the start of the usage lifecycle of that application or service. That’s when you have to address everything that needs to be done, from an IT operations monitoring and management perspective, to keep that new application or service available and performing the way it should to meet (or exceed) user expectations. And that’s exactly what EMC Service Assurance Suite and EMC ViPR SRM do – provide IT operations teams with the insights necessary to ensure that IT service delivery environment functions they way that they should, as well as the ability to easily absorb changes in the IT environment.

If I were producing this as a short movie, I’d now call out “fade to black, cut, and roll credits.” But IT operations would still keep a light on, behind the scenes, to help keep an eye on things.

Tags: , , , ,

Leave a Comment

Comments are moderated. Dell EMC reserves the right to remove any content it deems inappropriate, including but not limited to spam, promotional and offensive comments.

You must be logged in to post a comment.

Categories

Archives

Connect with us on Twitter