Deckplate innovation is receiving unprecedented attention these days, as well as its fair share of sniping from the skeptical sidelines. Innovation is indeed nothing new under the sun, and its traditional obstacles are no less prohibitive than they ever have been. What is new is the unprecedented speed at which ideas can promulgate through modern social media. The controlled brainstorming or “ideation” drive has been compared to panning for gold, but the internet has allowed us to increase the size of our pan.
In his recent post about the Defense Entrepreneur’s Forum, BJ Armstrong urged us to publish and promote our ideas to those empowered to act on them; to “influence the influencers,” so to speak. Execution is, of course, the graveyard of good ideas; for our ideas to become results they must find the backing of some influential executive or “principal.” The “pitch” to a receptive principal is the most sensitive stage of an embryonic idea’s lifespan. Having made no small number of failed pitches (and a few that didn’t fail), I’ve identified a few common themes to rejection. For those potential innovators getting ready to make the pitch, please consider the following as you prepare:
Know Thyself: Hazards to Credibility
Old ideas. It’s often the case that your idea has been tried before and failed. It’s not necessary that an idea be new for it to be good—many failed innovations suffered from flawed executions, and are worth attacking again with a better plan. The important thing is that you do your homework to understand why the idea failed and what should be done differently before you try to revive it. If you don’t know until mid-pitch that your brilliant idea was tried and failed twenty years ago, then your innovation is dead on arrival.
Lacking solutions. If you’ve identified a problem but haven’t identified a potential solution, then you’ve really just filed a complaint. Unfortunately, the complete solution might be beyond your level of expertise, and it’s for this reason that many potential innovations die at this stage. Don’t let a lack of expertise paralyze you—great innovations rarely resemble their instigators’ original vision. This is a rare situation where effort can actually be more important than the immediate results—what you’re doing here is getting the process started.
Emotion. It’s rare that potential solutions are not accompanied with some degree of frustration at the original problem or the myopic organization that fails to perceive it. Frustration, skepticism, and resentment are all common sentiments among smart people in large bureaucracies—left unchecked, they can fester into bitterness, and nobody wants to listen to another bitter JO. It’s essential that you prevent emotions from bleeding into your pitch, and it can happen to either written or verbal communication. If you suspect that your passions may be too evident, it might be a good idea to run your presentation by a trusted mentor first.
What about enthusiasm? Keep it under control; remain stoical and professional if you want to be taken seriously. Principals are interested in facts. It’s good to communicate conviction, but too much enthusiasm may instead communicate naiveté, which hurts your case and calls your objectivity into question. Scott Adams beautifully dismissed the usefulness of enthusiasm in a recent editorial: “Success caused passion more than passion caused success.”
Know Thine Enemy: Obstacles to Acceptance
Admitting to the problem. Your principal is familiar with the saying, “If it ain’t broke, don’t fix it.” He or she has probably endured a career’s worth of ambitious Good Idea Fairies and gimmicks, and understands that failed executions are worse than leaving well enough alone. If a system is in place, then somebody thinks it is working, and sometimes that may be enough for your principal—effective or not, if we perform according to expectations we will be left alone to accomplish our real mission.
Finite resources. Funding is the obvious obstacle, but may not be the most difficult. Your principal has limited time and limited political capital, and must carefully budget both to do their job. You have to prove not only that your problem is indeed worth solving, but that it is more important than the other problems they’re going to have to divert resources away from. You have to prove that solving it is their job—they’re not in the business of taking on other people’s problems.
The pocket veto. This is how bureaucracies insidiously devour innovation. Rather than overtly rejecting your proposal at risk of appearing unconcerned with your problem, some principals may agree to “take it into consideration” or to “forward it along” with no real commitment to execution. Since you’re not really in a position to demand commitment, the only thing you can do is be persistent. No great idea ever caught on without a lot of hard work and follow-through.
You may have to seek the attention of other principals– be careful. It’s easy to stray into insubordination this way, but if you tailor your message carefully, your immediate chain of command may be relieved that you would seek resolution elsewhere (depending on the problem). The best way to avoid conflicts of interest is to communicate your intentions aggressively. Then there is always the option to write and publish, in fact it has never been easier.
You might be wrong.
In all of our fervor over innovation, we sometimes forget that not all new ideas are good. At any given moment there is an infinite quantity of bad ideas floating around, and yours just might be one of them. You might not realize it for years, in fact you may never become convinced, and this is why the bureaucracy isn’t always a bad thing. If the principal refuses to choose your battle, it’s not because they’re an unthinking cog in a stolid machine, it’s because they feel it’s their responsibility to “just say no.” Later on, you might even come around to their point of view.
While persistence is necessary if you ever hope for your idea to catch on, it is also necessary that you be willing to move on at some point if it really is a non-starter. As usual, brutal self-honesty is in order, with an eye to improving for the next attempt. Other battles need fighting, and we need your innovation.
If we want to get serious about putting Warfighting First and Reducing Administrative Distractions, we can start with how we assess training on ships. Our current system is process-based: superior commands issue detailed instructions for the administration of shipboard training and qualification, and then assess compliance by auditing the ships’ records. There is usually a results-based component (observed drills) of assessment which is combined with the audits to produce an overall score—commands with weak performance in drills might be saved if they exhibit fantastic recordkeeping practices.
The process-based approach suffers from two flawed assumptions:
Assumption #1: Performance is the result of directed training processes. I’ll illustrate this assumption with an anecdote from my previous command, when I had just become responsible for the Torpedo Division. I observed divisional training conducted by the Leading First, complete with a PowerPoint presentation and testable objectives in compliance with the Continuing Training and Qualification Manual. The topic, also in compliance with said manual, was the characteristics of various weapon classes, many of which were not employed by our ship.
- DEF[x] Annapolis: Encourage the Innovators
- A History of the Navy in 100 Objects #48: Models of HMS St. George (1701) and USS Missouri (1944)
- Engineering and the Humanities: The View from Patna’s Bridge…
- A History of the Navy in 100 Objects #47: British Dockyard Models
- A History of the Navy in 100 Objects #46: WWII Japanese Radio Headset