EP · 011
THE SCIENTIST WHO BET HIS CAREER ON BUGS. 14 YEARS LATER, HE WAS RIGHT.
The most important thing any technology organization can do is build in-house expertise rather than outsource its thinking to vendors.
This episode hasn't dropped yet. Subscribe to get notified when it's out.
Katie Savage took the CIO job for the state of Maryland eight months pregnant. She came from Defense Digital Service, where she learned that the most important thing any technology organization can do is build in-house expertise rather than outsource its thinking to vendors. In Maryland, she found a team that managed contracts. She built a different kind of team.
Key Takeaways
In This Episode
What We Discuss
Q&A
Questions answered in this episode
Katie says you need a solid mix of IT ops, which covers networking, cybersecurity, enterprise platforms, and identity and access management, combined with product skills like design, engineering, and understanding user needs. She also increasingly emphasizes data proficiency, specifically the ability to collect, manage, analyze, and display data, as a foundation that cuts across all of it.
Katie says Maryland cannot compete on salary and she is candid about that, but she recruits on the specificity of the mission: offering cyber candidates work on live ransomware attacks, 24/7 security operations center experience, and critical infrastructure protection. She also credits Governor Moore's reputation as a forward-looking leader as doing a significant portion of the recruiting work for her.
Katie says the core problem is that government agencies think about services by agency rather than by the citizen's outcome, so a person trying to start a business gets linked out to seven different departments instead of seeing a single list of required permits. She is also working to reverse decades of fragmentation where agencies bought their own tools independently, including 13 separate Microsoft contracts she found when she arrived.
Katie describes it as diametrically opposed pressures: you are there to disrupt, but you are operating inside a culture intentionally built around discipline, chain of command, and tradition. Her approach was to spend her early time at DDS in deep listening mode while simultaneously introducing operational changes she knew were needed, rather than coming in with solutions before she understood the environment.
Katie believes the roles will not disappear but the tasks will look completely different, shifting away from coding dropdown menus toward understanding what information people need from an AI-powered interface and how to translate that into data queries. She compares it to the Estonia model where the goal is not to build a better application but to eliminate the need for one by surfacing the right data automatically.
Related Episodes
More Conversations
Every episode is a different story about the space between one chapter and the next.