The Lean Startup is the way most innovators build startups and innovate inside of existing companies. As a formal method, the lean startup consists of three parts:

• The Business Model Canvas – to frame hypotheses
• Customer Development – to test those hypotheses in front of customers
• Agile Engineering – to build Minimum Viable Products to maximize learning.

The Business Model Canvas has been a great invention for everyone from startups to large companies. Unlike an org chart, which describes how a company executes to deliver known products to known customers, the business model canvas illustrates the search for the unknowns that most new ventures face. The 9 boxes of the canvas let you visualize all the components needed to turn customer needs/problems into a profitable company.

From revenue streams to mission achievement

‍The business model canvas has served all of us well in thinking about building businesses and therein lies the problem. In a business the aim is to earn more money than you spend. What if you’re a government or a military organization or part of the intelligence community? In these cases you don’t earn money, but you mobilize resources and a budget to solve a particular problem and create value for a set of beneficiaries (customers, support organizations, warfighters, congress, the country, etc.)

For these organizations, the canvas box labeled Revenue Streams doesn’t make sense. In a mission-driven organization such as the defense and intelligence community, there is no revenue to measure. So the first step in building a canvas for mission-driven organizations is to change the Revenue Stream box in the canvas and come up with a counterpart that would provide a measure success.

We’re calling this alternative Mission Achievement. Later in this post we’ll explain how we’ll measure and describe Mission Achievement, but first our Mission Model Canvas needs four more tweaks.

• Customer Segments is changed to Beneficiaries
• Cost Structure is changed to Mission Cost/Budget
• Channel is changed to Deployment
• Customer Relationships is changed to Buy-in/Support

Customer Segments change to Beneficiaries

‍At first glance, when developing a new technology for use in the defense and intelligence community, the customer appears obvious – it’s the ultimate war fighter. They will articulate pains in terms of size, weight, form fit, complexity and durability. But there are other key players involved.  Requirement writers and acquisition folks look at systems integration across the battlefield system while contracting officers, yet another segment, will count beans, measure the degree of competition and assess the quality of market research involved. The support organizations need to worry about maintainability of code or hardware. Does legal need to sign off for cyber operations?  So yes, war fighters are one customer segment, but others need to be involved before the war fighter can ever see the product.

So the first insight is that in the defense and intelligence community mission models are always multi-sided markets.  With the goal of not just building a great demo but getting the product adopted and deployed.

Second, in the defense and intelligence communities almost all of the mission models look like that of an OEM supplier meaning there are multiple layers of customers in the value chain. Your product/service is just part of someone else’s larger system.

So to differentiate “customers” from the standard business model canvas we’ll call all the different customer segments and the layers in the defense and intelligence value chain beneficiaries.

The Value Proposition Canvas

‍Of all the nine boxes of the canvas, two important parts of the model are the relationship between the Value Proposition (what you’re building) and the beneficiaries. These two components of the business model are so important we give them their own name, Product/Market Fit.

Because of the complexity of multiple beneficiaries and to get more detail about their gains and pains, Osterwalder added an additional canvas called the Value Proposition Canvas.  This functions like a plug-in to the Mission Model Canvas, zooming in to the value proposition to describe the interactions among these beneficiaries, war fighters, etc. and the product/service in more detail. Using the Value Proposition Canvas with the Mission Model Canvas lets you see both the big picture at the mission model level and the detailed picture of each beneficiary at the “product/market fit” level.

In the defense and intelligence community business models, there will always be multiple beneficiaries.  It’s important that each beneficiary gets its own separate Value Proposition Canvas.

Distribution Channel changes to Deployment

‍In the commercial world we ask, “What type of distribution channel (direct sales, app store, system integrator, etc.) do we use to get the product/service from our company to the customer segments?”  For the Department of Defense or Intelligence organizations, we ask instead:

• “What will it take to deploy the product/service from our current Minimum Viable Product to widespread use among people who need it?” (What architecture components can they innovate on and what can’t they?)
• “What constitutes a successful deployment? (number of users, units in the field, time to get it into the field, success in the field, etc.)”
• “How do we turn a Horizon 3 innovation into something that gets adopted by a Horizon 1 organization?”

Customer Relationships changes to Buy-In/Support

‍In an existing business, Customer Relationships is defined as establishing and maintaining a relationship to support existing customers.  In a startup we redefined Customer Relationships to answer the question:  How does a company get, keep and grow customers?

For the defense and intelligence communities, we have modified Customer Relationships to mean, “For each beneficiary (customer segment), how does the team get “Buy-In” from all the beneficiaries?”

Customer discovery helps you understand whose buy-in is needed in order to deploy the product/service (legal, policy, procurement, etc.) and how to get those beneficiaries to buy-in? (Funding? Mandates? User requested? etc.) In addition, the long term support and maintenance of new projects need to be articulated, understood and bought-into by the support organizations.

At the Pentagon a favorite way to kill something is to coordinate it to death by requiring buy-in from too many people too early. How to determine who are the critical people to get buy-in from and  then who are the next set required to first sustain the iterative development of future MVP’s is one of the arts of entrepreneurship in the defense and intelligence community.  

Revenue Streams changes to Mission Achievement

Mission Achievement is the value you are creating for the sum of all of the beneficiaries/the greater good.

It’s important to distinguish between the value for individual beneficiaries (on the Value Proposition Canvas) and overall Mission Achievement. For example, Mission Achievement could be measured in a variety of ways: the number of refugees housed and fed, the number of soldiers saved from roadside bombs, the number of cyberattacks prevented, the increased target surveillance of sensor fusion, etc.  None of these are measured in dollars and cents. Keep in mind, there is only mission achievement if it delivers value to the end beneficiary.  

Lessons learned

• In the defense and intelligence community the metrics of success are not revenue but mission achievement
• We’ve modified the Business Model Canvas into a Mission Model Canvas
• Changed Revenue Streams to Mission Achievement
• Changed Customer Segments to Beneficiaries
• Change Cost Structure to Mission Cost/Budget
• Change Channel to Deployment
• Change Customer Relationships to Buy-in/Support
• Organizations without specific revenue goals can now use a version of the business model canvas