January 23, 2024
In today’s episode, Highlight’s James Eselgroth will take a look at digital transformation from 40,000 feet. He will make broad observations about innovation and change in federal technology.
Normally, one would think about solutions to problems. Traditionally, develop a list of changes, check each off the list, and move on. That may be a fantastic way to build a house, not that it simply does not work in today’s dynamic software environment.
In today’s fast-moving technical climate, one approach is to use something called an MVP. No, not the National Football League kind of MVP, not “Most Valuable Player,” but a “Minimal Viable Product.”
A “Minimal Viable Product” is a concept that originated in agile software development. The idea was not to submit a complete, finished product but to present the essence, framework, or basics of a product and get feedback.
"What's a business problem that we think we can solve partner with the right vendor or partner and build out and get to that MVP in about two to four weeks"
James Eselgroth, Highlight Tweet
This initial offering has to include working elements but omits many of the details like user interface concerns and complex integration dependencies.
During the interview, Jim explains how this concept applies to the federal audience. He references a quote from Federal CTO Clare Martorana who said “Demos, not memos.”
This iterative solution would be presented to stakeholders and see if it was a good fit. Alterations are made and the next iteration is presented.
Listen to the interview to hear how Jim provides an overview of his innovation lab. This results in the MVP approach allowing for solutions to be built in two to four weeks.
He concludes the interview by mentioning a new initiative from Highlight called “Edgewerx.”
If you enjoyed this episode, then you may want to listen to Ep. 119 CMMC & the Defense Industrial Base – Are You Ready?

Leave a Reply