cancel
Showing results for 
Search instead for 
Did you mean: 
Create Post

Bimodal IT vs. Hybrid IT: What’s the Best Approach?

IT departments have always been an important part of the business. Critical business models rely on systems managed by IT. Businesses have been using IT for years, but IT is now finding a seat at the table and is helping to lead businesses into a new digital era. As the business puts more pressure on IT to deliver, we're having to re-structure our IT departments. One path that has been drawn up is the Gartner Bimodal IT model.

What Is Bimodal IT?

Gartner released their bimodal IT model back in 2014. It was their attempt to help guide enterprises through the new era of digital transformation. Gartner broke down IT into two different styles of work, defined as "The practice of managing two separate, coherent modes of IT delivery, one focused on stability and the other on exploration."

  1. 1. Mode 1 "focuses on what is known while renovating the legacy environment fit for the digital world."
  2. 2. Mode 2 is "exploratory and experimental to areas of uncertainty."

Mode 1 is focused on legacy applications with a focus on strict recordkeeping. When I first read about Mode 1, I thought of mainframes and legacy code base. These technologies are still very important, but traditionally are hard to add new features and functionality.

Mode 2 is focused on new applications and greenfield deployments, which led me to think about mobile applications and web-based apps.

This might have been a good starting point for enterprises to lead their IT departments into the next wave of technologies and into the digital era, but with the rise of DevOps and hybrid IT, there are gaps in the bimodal model. Gartner's model doesn't really talk about culture and the people needed to interact with each other to support these systems. Bimodal IT doubles the processes because you've created two separate pipelines and you're only as fast as your slowest link. Lastly, new technology practices can be applied using a DevOps and Agile development approach.

What Does Bimodal IT Mean for People?

People are a company's greatest asset, and making people choose between Mode 1 and Mode 2, two distinctly different development paths, is not a good idea.

Mode 1 gives people who are less inclined to learn a place to hide, be comfortable, and not innovate in an area that needs it more than ever. It gives people an excuse to not have to learn new methods or a reason for not knowing because they weren't sent to training or to a conference. Natural silos get built up in all departments of a business and management struggles with trying to have different teams communicate with each other. Now we're encouraging these walls to be built up. Mode 1 might be legacy, but it holds a lot of the critical data that needs to be fed into the newer front-end systems maintained by the Mode 2 group. We need to blend these two groups together to encourage better communication because the systems they interact with are linked.

Process for DevOps

DevOps is about combining processes and tools to help an organization deliver quality applications at a high speed. I normally see groups from Mode 2 and operations referenced when talking about DevOps. We get excited about the new shiny toys in IT and lose sight of the existing infrastructure. Not all deployments are greenfield—they’re normally brownfields. There's already a piece of technology or a process we need to incorporate with our new process. It’s the same with DevOps.

We need to include both Modes 1 and 2 under DevOps and use the same model of development for both modes. Both will benefit when the teams can be merged into a single team and the range of skills can be developed instead of limited to a single practice.

The Interaction of Technologies

When I first read about the Gartner Mode 1, it threw me back to when I worked for a manufacturing company that had a fleet of COBOL programmers who administered the IBM Z-series mainframe. These administrators and this system basically ran the entire organization because they contained the most critical data for the business. But rolling out any new change took a lot of effort. Making the system run faster usually required a hardware refresh. It took months of planning to add new features, and there wasn't an easy way to roll out into production. We maintained two separate pipelines of work. We had two distinctly different groups of people with different skillsets. One side didn't really understand the level of effort of the other side.

I don't think companies are looking at releasing multiple versions of code to their legacy systems. Instead, businesses are looking for their legacy systems to be more flexible and agile in nature—to be able to change when the business changes, pivot when the business needs to pivot. We can learn from each other by working closely with each other. Continuous integration and continuous deployment are a key component of DevOps. CI/CD allows for automated testing using technology to track code versions for quick delivery, stable releases, and quality. Instead of allowing one group benefiting from these new technologies, we need to borrow similar tools and apply to all systems so the business can benefit.

Conclusion

The introduction of the public cloud disrupted enterprise businesses and introduced new models to quickly deliver applications. A new management approach was needed to maintain new applications while supporting legacy systems, and Gartner was one of the first to put out a new model. Since then, new approaches to software development and system management have evolved and become the preferred method. Research has shown it's better for different teams to communicate with one another and share ideas instead of building silos. We've learned that it's good to merge teams from the development side as well as the operations team. Now it's time to include the legacy team.

10 Comments
Level 14

Thanks for the article.  I'd actually never heard it put this way before.

Level 13

Interesting way of looking at the problem.  Hadn't heard of Bimodal IT before, although I've definitely experienced it.  Thanks for the writeup.

Level 12

I know a lot of people will find this harsh, but...

"Mode 1 gives people who are less inclined to learn a place to hide, be comfortable, and not innovate in an area that needs it more than ever."

People who don't want to learn new technologies, particularly with regards to security, need to either be persuaded to change or lose their jobs. I am probably not the only one who has dealt with problems by people who didn't feel any need to learn how to use their workstations.

One of my favorites: management would not let us set a policy to blank out the username so users were accustomed to only entering their password. Some would need to be reminded of their usernames when they got a new workstation! One person came into my office, even though the door was closed, and literally yelled at me. I screwed up her computer so it won't let her log in. She tried her password five times and it wouldn't work, and she knows it was me because it's got my name in the username window.  THANK YOU for locking me out of my own account!

MVP
MVP

Thanks for the article.

Level 16

Thanks for the write up.

Level 13

Thanks for the article

Level 15

From my days of Industrial Engineering,  People don't want change, but IT is all about change.  We grow, we adopt, we learn, we develop, we implement, we research, and we repeat.  The concept of silos is what I would consider the biggest limiting factor.  When sub-departments or people create solutions and don't take into account the efforts required to implement those solutions, it is generally the biggest pushback for change.  And when there is the repeated steps on each solution, it continues to push people into those silos.

Thanks for the posting!

Level 14

The biggest problem I face is that I'm the SysAdmin for a company that has evolved and grown rapidly over the years.  There's about 130 companies in the group.  I have a mixture of old, not quite so old, middle aged, youngish, young and new systems.  They are all required.  I'm trying to create a new infrastructure which will give the core systems to everyone whilst still giving the users access to the applications they need.  It is hybrid and Bimodal at the same time.  That's pretty much the same everywhere I have ever worked.  I don't think you can get away from that.  Unfortunately the Mode 2 (Devops) stuff never gets finished.  It's great until the next shiny thing comes along and the previous shiny thing gets forgotten.  Then the legacy (Mode 1) people have to pick it up, get it to work properly and support it.  Mode 1 people tend to be very good at what they do and have years of experience.  It's rare to find one that meets your description.  We are the people that actually allow the business to make money whilst the Mode 2 people just cost money and rarely deliver what they promise.

I am slightly biased    

Perhaps part of the solution is to avoid not training people how to do the tasks a new environment requires.  Treating their observations that they've not received training as a weakness on their part is a mistake--it's a shortcoming on the company's side.

When old dogs have proven they can learn new tricks, providing training is the right solution for the company AND the employees.

Level 11

Thanks for the post, good read.