🎖️US Army's Intelligence battlefield operating system (BOS) is one of the best playbooks for competitive info gathering for product dev. It consists of the following functions:
1 Plan
2 Prepare
3 Collect
4 Process
5 Produce
Analyze, disseminate and assess occur throughout.
👇
Intelligence BOS is one of seven operating systems-Intelligence, maneuver, fire support, air defense, mobility/countermobility/survivability, combat service support (CSS), & command & control⎯that enable commanders to build, employ, direct & sustain combat power
1 Plan - includes assessing the situation, envisioning a desired outcome, identifying pertinent info & intel requirements, developing a strategy for intel, surveillance & reconnaissance (ISR) ops to satisfy those requirements, directing intel ops, and sync the ISR effort.
1.1 Commander’s intent, planning guidance, and commander’s critical info requirements (CCIRs) drive the planning of intel ops. Planning, managing, and coordinating these ops are continuous activities necessary to obtain info and produce intel essential to decision making
📓Ex
Assign a person to run point & define:
Goal → Study the mid career education & training industry
Info → Pricing, process, options, friction & ease
Intel channels → Sign up on all platforms, reach out to gurus, interview customers & analyze landscape
2 Prepare - This step includes those staff and leader activities that take place upon receiving the ops plan (OPLAN), ops order (OPORD), warning order (WARNO), or commander’s intent to improve the unit’s ability to execute tasks or missions and survive on the battlefield.
📓OPORD
Situation → There is a gap in the mid career edu mkt. X has already started bldg partnerships
Mission → PM, UXR & PMM will look for optys in the mkt to identify synergies
Execution → Research will be done by D/M & findings will be used for the coming planning cycle
3 Collect - Focus ISR on CCIR but also enable the quick re-tasking of units & assets as the situation changes. The enemy situation, not just OPLAN drives ISR ops. Well-developed proc to support emerging targets, changing reqs & the need to support combat assessment are critical
📓Let’s say we find out that Competitor X is working on MOOCs for product strategy whereas the majority of users are looking for in-person interactions with experts and peers. We should focus our efforts towards p2p opportunities that are aligned with our ops capabilities.
4 Process - Convert relevant info into a form suitable for analysis, production, or immediate use by the commander. Processing also includes sorting through large amounts of collected info and intel.
5 Produce - Integrate evaluated, analyzed, & interpreted info from single or multiple sources & disciplines into finished intel products. Ensure the unit’s info processing and intel production are prioritized & sync to support answering the collection reqs
📓The finished product will be a summarized deck for exec decision making and a detailed doc for the content and ops team to get a head start on planning.
The example over simplifies the process & masks the organizational complexity for executing & responding to situations.
Working on democratizing experimentation? Here are the resources that I used to 10x volume of experiments at Yelp
1 Good experimentation strategy
2 Focus on people over tech
3 Avoid common gotchas
4 Prioritize for impact
5 Building your own platform
6 Build safeguards
👇
1. Good experimentation strategy
- Furthers understanding of users not just metrics
- Has a strong well reasoned hypothesis
- Ensures you can learn why it didn’t & did work
- Instruments & defines metrics upfront