Start your day with intelligence. Get The OODA Daily Pulse.
This is the next in our series of special reports for OODA members focused on federal business strategies for the Startup CEO (find them all here).
If you are a tech CEO building an awesome new capability that improves the ability of organizations, there is a very high likelihood that government agencies will have an interest. The government organizations that will have the most interest are those that will see your technology as critical to mission accomplishment. This makes learning government mission needs extremely important.
Here are our top tips on identifying the government mission needs most relevant to your capabilities:
The federal government is huge. Think of it as the largest customer in the world, because that is exactly what it is. It is so large no one human can understand it all. As an aid to focusing on what is important, we recommend talking to experienced professionals who know the federal government. As a member of the OODA Network we would welcome a conversation with you on this. If you give us a brief understanding of your core capabilities we can more than likely help narrow down the key sectors of the federal government that will have most interest in your capabilities and give a very high level overview of the mission needs of those organizations.
After determining which organizations you will want to focus on you can build more detailed insights. A first step we always recommend is reviewing Congressional Testimony of the leaders of the agency or organization. Congressional testimony contains key executive branch priorities and most always also includes gaps that leaders want the public to know about. If your capability fills these high priority gaps it can help shape your strategic approach to the agency.
At some point you will want to consider standing up a federal advisory board made up of seniors who have had experience in government agencies of interest to you. The right professionals can accelerate your understanding of mission needs and help you and your team grow in service to these key missions.
You will also need insights into the compliance drivers that flow from both the White House and Congress. Since this is where both guidance and money flows from, this is also critically important. You can learn these compliance drivers yourself by study of the CIO.gov website and OMB websites. But the most efficient way to do this is to have experienced former federal executives help you and your team out. So helping you understand these drivers may be another task for your federal advisory board.
Most every agency will also publish key requirements on their website, and many will also provide instructions for technology vendors who seek to provide demos of capability. If you are going to provide a demo to an agency, it is absolutely critical that you have studied up on their gaps and missions so you can put your demo in their context. We recommend having experts review your demo before giving it to the government. Otherwise you might follow their procedures, set up a demo, and have it fall flat. But, if you provide a demo in the context of agency needs you will almost certainly get feedback from government leaders on what they are really looking for. This is the best way to get deep insight into agency mission needs- directly from government leaders.
Your understanding of mission needs may now be good enough to inform your strategic approach to market. More detailed work will be required to really operationalize pursuit of federal business.
When you are ready to aggressively pursue government business you will need to equip your team with more operational insights. Some tips:
Please Contact Us Here or reply to any of our emails with your feedback.
Some other resources that can help your team understand the mission needs of government agencies include:
We also strongly recommend you and your entire team sign up for distribution of the OODA Daily Pulse for updates on issues of high interest to the entire federal technology ecosystem.
The next post in this series will dive deeper into working with federal systems integrators.