As an IT leader, what strategies are you trying to achieve? Don’t say modernization.
I overheard this statement a few months ago: "Management won't upgrade our systems because our systems aren't modern and aren't worth the investment...because management won't upgrade our systems."
A year and a half ago, I moved from working for an IBM i customer to working for an IBM Business Partner. Since then, I’ve done many IBM i upgrades. In one particular month, I probably did more upgrades in my new job than in my entire career previously. In fact, I’ve been toying with the idea of getting C9002967 (applying PTFs) tattooed on my arm because I see it so often. Most of the upgrades have been from 7.1 to 7.3, but a few went to 7.2 because some application vendors didn’t receive the memo that Java 6 has been unsupported since December 31, 2017.
While a lot of progress is being made in getting people to move to a supported operating system release, I have to say that there’s still a need for a major mentality shift in the way companies approach modernization.
How many businesses are still running System/36 environments? Trust me; they’re out there. I see old RPG code, flat files, green-screens...they all can make that step into the world of free-form RPG, open source, and SQL tables. Bit by bit, program by program, interface by interface. Moving applications into the future can and should be thought of as imperative, rather than special projects.
Yes, applications can be modernized. Processes can be modernized. But to modernize a business? That’s far trickier but not out of the ordinary. The opportunity is there, but we may not see it as IT people.
I’ll get to that shortly.
The saying “you’re only as old as you feel” is the result of a mentality shift. It’s looking in the mirror and seeing experience rather than age. One of my daughters asked me once what my graying hair meant. I told her, “It means I know what I’m doing.” I’m getting older, but I don’t feel old. I don’t think I ever will. My body is showing signs of age, and I could use some more cardio work, but I can do an upgrade, have dinner, and then put down some deck joists or repaint the bathroom.
It’s all in how you look at things. Your house, job, family, car…they all need work. You can be a better homeowner and keep up your property value by continually performing maintenance and upgrades. You put oil in the car and check the tires. When the car gets too expensive to maintain, you trade it in for something more efficient. You try to talk through problems with your family and coworkers without letting your emotions get the better of you. You self-reflect. You reassess. You keep building and improving. If something doesn’t work, you try again. Then you try something totally different or just a different approach. You talk to your partners about how things could be better if you just worked on them.
And, yes, you do see the same in business…usually as a manager of quality and continual improvement. Here are a few bullet points from a job advertisement that spells out some of the common responsibilities.
- Facilitate the development of a plan to deliver long- and short-term business objectives through system deployment and capability building focused on alignment, the elimination of waste, and 100% employee engagement
- Establish monthly, quarterly, and annual deployment strategies, plans, and tactics
- Own the identification, facilitation, and tracking of functional cost improvement projects
- Coach and facilitate the leadership team
- Build capability and deploy systems to optimize value streams and work processes
- Assure integration of all PACS (Processes, Applications, Capabilities, and Systems) and effective governance to standards and master plan priorities
- Implement corporate loss analysis, idea generation, and promotion process
- Ensure that objectives are passed down and understood
I worked for 15 years in manufacturing companies, and this type of position is nothing new. However, one thing that I find looking back is that those positions were never really involved with systems discussions. Nor were systems people really given much time to help facilitate any continual improvement. Perhaps other people have had different experiences. But in my time as a customer, IT has always been on the outside looking in: an entity not aligned with the company, more like an afterthought once a decision has been made. “We’re doing this project. Make it work. It shouldn’t be too hard or take much time.”
A manager of continual improvement can certainly use Information Technology to help achieve goals. I would go one step further. I would look at this position as an Information Technology position or one at least closely aligned with it. This is exactly where IT needs to be as it’s exactly what IT does. And the position already exists; it just needs to be slightly altered to include IT. Or maybe IT needs to alter to fit the business. Or maybe the business needs to alter in order to properly utilize IT as a partner in order to achieve real continual improvement. That means proper budget allocations for projects, training and staff, plus a seat at the table to advise other business leaders how technology can work for them—rather than the other way around.
A company’s culture is the hardest to change. It’s like turning an aircraft carrier. You’re not going to do it by putting a paddle on one side of her. That direction needs to come from the bridge.
So when we talk about modernization, are we thinking tactically or strategically? Converting DDS to SQL is tactical. Converting to free-form RPG is tactical. Graphical interfaces, open-source tools, Linux partitions, upgrading to 7.2 or 7.3, converting System i Access for Windows to Access Client Solutions? Tactical, tactical, tactical, tactical, and tactical. They’re all tactical. And there must be an overall strategy that these tactics aim to support.
So as an IT leader, what strategies are you trying to achieve? Don’t say modernization. The strategy must be aligned with and supported by the business.