Outcomes Over Infrastructure: Ensuring Successful Mission with as-a-Service (S1E34)

The “as-a-service” model has proven to improve reliability, speed up compliance, and give flexibility. If that is the case, why is there a resistance to that environment in the federal government?  This is a discussion from experts from within the federal government and technology professionals from the partner community to bring to light some of the challenges to digital transformation involving “as-a-service.”

Jeffrey Lush is the CIO of the Air Force Air University and surprises the audience with his approach to this modernization effort.  He suggests that a business-like “return on investment” review would resonate with high level federal leaders.  Further, he cautions that this cannot be done in a gargantuan eight-hour PowerPoint presentation; he recommends taking each step into increments that can be digested.

Also, success with Jeffrey Lush’s projects highlights inclusion and transparent messaging to allow federal leaders to understand the benefits of a new system.

Both Dave Kushner and Cameron Chehreh have managed to see the successful transition to the “as-a-service” model. The trap federal leaders can fall into is the close comparison of the technical aspects of a transition.  Commonly called a “bake-off,” these details fall nicely into an Excel spreadsheet where one can make a numerical comparison. Sometimes, this misses the point.

Both Dave and Cameron think that the idea of educating decision-makers involves a focus on outcomes, not technical details.  A preferred approach is to re-orient the discussion to value. Cameron Chehreh states that this change is not minor, it is almost a cultural transition that takes time.

What to focus on? When a leader emphasizes outcomes, then they can take advantage of systems that allow for rapid scaling, and not worry about the technology.

Cameron Chehreh shares that the real focus should be on three areas:  data sovereignty, critical assets, and compliance.  Many cloud systems allow for easy entry, but a difficult exit; Cameron is adamant that the federal user should not be charged to pull data out of an environment. Having close familiarity with critical data will allow managers to assign assets in a prioritized manner.  Federal compliance can be so difficult that a new environment will allow initial compliance as well as adaption to future changes in regulations.

The overall theme of the discussion is leaders must tie the user experience to the outcome, not the technology.

To view this webinar: Outcomes Over Infrastructure: Ensuring Successful Mission with as-a-Service 2.

Featured Speakers: