IE 11 Not Supported

For optimal browsing, we recommend Chrome, Firefox or Safari browsers.

Missouri CIO Mike Cheles Announces Retirement Date

After announcing he planned to retire earlier this year, the CIO will log his final day in the service of the state Monday, Dec. 16. Cheles said there are rumors the state is nearing a decision on who will be replacing him.

Missouri capitol
Missouri CIO Mike Cheles, who has served in the top state IT position since October of 2018, will be ending his tenure next week on Monday, Dec. 16.

Cheles had previously announced his plan to retire from the Office of Administration IT Services, citing personal reasons and calling his work with Missouri an ideal career "capstone."   

Under Cheles, the state sought a program of increased efficiency, focusing on spending, increased worker productivity, and a plan to break down the siloed nature of state leadership to advance a more unified governance approach. 

At the time that he took the position, Cheles was the state's first permanent CIO for nearly three years; he also came as a government outsider — having spent several decades in the private sector, including long stints as CIO for companies like Gibson Brands Inc, Hussmann International, and United Health Technologies. 

Speaking with Government Technology, Cheles said that entering state government for the first time had presented its own unique set of challenges.

"There are some very significant differences between government and the private sector," he said. "The whole procurement process and RFPs and bidding was completely different than what I was able to do in the private sector. I had far more leverage in business than I had in government to put together a good deal," he said.  

Cheles said he sought to shift norms around vendor relationships and procurements, looking to optimize those relationships. "I hope I opened people's eyes to [the idea] that you constantly have to look for value," he said.   

Cheles also focused on increasing worker pay by leveraging increased productivity. To do this, he launched a large workforce training program that resulted in staff logging around 2,800 more hours of training than when he first started.

"I set a goal that 5 percent of their hours I wanted spent on training and I made it clear that supervisors that get in the way of training aren't doing their jobs," he said.

Cheles also focused on fostering a more unified approach to governance through increased communication. 

"This was an extremely siloed organization. We had people within their own departments not talking to each other," he said. "I finally put my foot down and said we're not going to be that type of organization. I expect people to talk."

It is unclear who will immediately replace Cheles, said Angel Hughes, assistant to the CIO. However, Cheles commented that it seemed the state was nearing a decision. 

"I have not been part of the process," he said. "What I do hear is that they're 'close,' that it's an outside hire and that they either have made an offer or are close to finalizing one." 

Lucas Ropek is a former staff writer for Government Technology.
Special Projects
Sponsored Articles
  • How the State of Washington teamed with Deloitte to move to a Red Hat footprint within 100 days.
  • The State of Michigan’s Department of Technology, Management, and Budget (DTMB) reduced its application delivery times to get digital services to citizens faster.

  • Sponsored
    Like many governments worldwide, the City and County of Denver, Colorado, had to act quickly to respond to the COVID-19 pandemic. To support more than 15,000 employees working from home, the government sought to adapt its new collaboration tool, Microsoft Teams. By automating provisioning and scaling tasks with Red Hat Ansible Automation Platform, an agentless, human-readable automation tool, Denver supported 514% growth in Teams use and quickly launched a virtual emergency operations center (EOC) for government leaders to respond to the pandemic.
  • Sponsored
    Microsoft Teams quickly became the business application of choice as state and local governments raced to equip remote teams and maintain business continuity during the COVID-19 lockdown. But in the rush to deploy Teams, many organizations overlook, ignore or fail to anticipate some of the administrative hurdles to successful adoption. As more organizations have matured their use of Teams, a set of lessons learned has emerged to help agencies ensure a successful Teams rollout – or correct course on existing implementations.