Phase 1:
Generating Distinct Courses of Action

The foundation of effective Course of Action (COA) development lies in creating genuinely different approaches to accomplishing your objective. This critical first phase determines whether you will have real strategic choices or merely superficial variations of a single idea. Quality COA generation requires discipline, creativity, and systematic process to ensure you explore the full range of viable options rather than gravitating toward the familiar or obvious.

Understanding the Challenge of Genuine Alternatives

Most organizations struggle with generating truly distinct alternatives. The natural tendency is to develop a preferred approach, then create minor variations that differ only in implementation details rather than fundamental strategy. This happens because familiarity feels safe, because advocating for genuinely different approaches requires defending unpopular positions, and because generating creative alternatives demands more cognitive effort than refining a single plan.

Military planners address this challenge through structured processes that force consideration of fundamentally different approaches. The discipline of COA development requires that each option be distinguishable. This means someone can immediately articulate how it differs from other options in philosophy, method, timing, risk profile, or resource requirements. Without this discipline, organizations waste analytical effort comparing options that are not actually different enough to matter.

The goal of Phase 1 is to develop two to four distinct COAs that represent genuinely different strategic choices. Each must be viable (could actually work), suitable (would accomplish the objective), and distinguishable (fundamentally different from the others). This foundation enables meaningful analysis and comparison in subsequent phases.

Prerequisites: Setting the Stage for Success

Before beginning COA generation, leaders must establish clear parameters that focus creative thinking while preventing wasted effort on non-viable options.

Define the Decision Requirement Clearly

Every COA development effort begins with a precise decision statement that clarifies exactly what needs to be decided and why. Vague decision statements like “improve operations” or “grow the business” provide insufficient focus for generating meaningful alternatives. Effective decision statements specify the objective to be accomplished, the timeline for decision and implementation, and the key constraints that limit options.

A well-crafted decision statement completes this sentence: “We need to decide how to [specific objective] by [timeline] given [key constraints].” For example: “We need to decide how to expand into the European market by Q3 2026 given capital constraints of five million dollars and current staffing limitations.”

This clarity focuses COA generation on relevant approaches rather than exploring options that are interesting but do not address the actual decision requirement. It also prevents the common mistake of generating COAs that solve different problems than the one requiring decision.

Document the decision requirement in writing and share it with everyone involved in COA development. This shared understanding prevents confusion and ensures all participants are generating options for the same decision.

Identify Key Stakeholders and Decision Criteria

Understanding who will be affected by the decision and what criteria will be used to evaluate options shapes COA generation by revealing which approaches are likely to gain support and which face implementation obstacles.

Map all stakeholders who will be affected by or have input into the decision. Identify whose approval or support is required for successful implementation. This stakeholder analysis reveals political realities that make some approaches more viable than others, even if they appear equal on technical merit.

Determine what criteria will be used to evaluate different options. Common criteria include: how completely the COA accomplishes the objective, resource requirements (people, budget, time), risk profile, timeline to results, flexibility for future adaptation, and stakeholder acceptance. Assign relative weights to different criteria based on their importance to organizational priorities.

This early clarification of evaluation criteria guides COA generation toward options that will perform well against what actually matters rather than generating interesting approaches that fail on critical dimensions.

Assemble the Right Team for Development

The quality of COAs generated depends heavily on who participates in the development process. Effective COA generation requires diverse perspectives, relevant expertise, creative thinking, and willingness to advocate for different approaches.

Identify individuals with expertise relevant to the decision. Include people who understand the technical aspects, those who know the organizational context, and those who will be responsible for implementation. Diversity of perspective generates more creative alternatives than homogeneous groups.

Ensure representation from functions that will implement the decision. People closest to implementation often identify approaches that those further removed might miss, and their involvement builds commitment to whichever COA is ultimately selected.

Designate specific roles for the COA development process: someone to facilitate discussions and keep the process on track, someone to document ideas and decisions, and someone with authority to make final decisions when the team cannot reach consensus. Clear roles prevent process breakdown and ensure productive sessions.

Establish ground rules for collaborative work. The most important ground rule for COA generation is separating idea generation from idea evaluation. During initial brainstorming, all ideas are captured without critique. Evaluation happens later, after diverse options have been fully explored.

Step 1: Conduct a Planning Session to Generate Initial Ideas

The first step in Phase 1 brings the team together for focused idea generation. This session typically requires two to four hours for significant decisions, with more complex decisions warranting additional time.

Structure the Session for Maximum Creativity

Begin with individual brainstorming where each participant generates two to three fundamentally different approaches to accomplishing the objective. Provide 15-20 minutes of quiet time for individual thinking before group discussion. This individual work prevents groupthink and ensures that quieter team members develop their ideas before dominant voices shape the conversation.

Encourage participants to think creatively within realistic constraints. The goal is not to generate fantasy solutions that could never be implemented, but rather to explore the full range of viable approaches that might work given actual resources and constraints. Ask participants to consider how different combinations of timing, methods, resources, and sequencing might achieve the desired objective.

After individual brainstorming, conduct a round-robin sharing session where each person presents one approach without critique or discussion. Record all ideas on a whiteboard or digital collaboration space where everyone can see them. This prevents premature evaluation and ensures quieter voices are heard before the group begins analysis.

Continue the round-robin until all ideas have been shared. The facilitator’s role is to ensure ideas are captured accurately and that no evaluation or critique occurs during this initial sharing. Questions for clarification are appropriate; questions that challenge viability or effectiveness are not.

After all ideas have been shared, facilitate discussion to explore each approach more fully. Ask probing questions that help the group understand what each approach would actually entail: “How would this actually work?” “What would be required to implement this?” “What assumptions are we making?” “What conditions would need to be true for this to succeed?”

This exploration phase often reveals that some ideas are more similar than they initially appeared, while others are more different. The goal is to understand each approach well enough to group similar ideas and identify genuinely distinct alternatives.

Use Effective Brainstorming Tools

Several tools enhance the quality of COA generation sessions:

A whiteboard or digital collaboration space allows visual capture of ideas where everyone can see them simultaneously. This visibility helps participants build on others’ ideas and see connections between different approaches.

A timer keeps brainstorming focused and prevents excessive analysis during the generation phase. Time-boxing forces decisions and prevents the group from getting stuck analyzing a single idea.

A parking lot captures important issues that arise but are tangential to COA generation. When someone raises an important point about implementation challenges or stakeholder concerns, acknowledge it and place it in the parking lot for later consideration rather than derailing the current discussion.

Prompt questions stimulate thinking when the group gets stuck. Examples include: “What would we do if budget were unlimited?” “What would we do if we had only half the time?” “What approach would our main competitor take?” “What would a completely risk-averse approach look like?” “What would an aggressive, fast-moving approach entail?”

Avoid Common Pitfalls

Several common mistakes undermine COA generation sessions:

Dismissing ideas too quickly without exploration prevents the group from understanding potentially valuable approaches. Even ideas that initially seem unrealistic may contain elements that inform viable COAs. Maintain the discipline of capturing all ideas first, evaluating later.

Allowing senior voices to dominate suppresses alternatives and leads to groupthink. The facilitator must ensure that all participants contribute and that ideas are evaluated on merit rather than on the status of their advocate.

Generating minor variations rather than fundamentally different approaches wastes analytical effort. If proposed COAs differ only in implementation details but follow the same basic strategy, they are variations rather than alternatives. Push the group to identify approaches that differ in philosophy, timing, risk, or method.

Focusing on obstacles rather than possibilities during initial generation shuts down creativity before alternatives have been fully explored. Concerns about feasibility are important but belong in the analysis phase, not the generation phase. During generation, the focus should be on what might work, not why things will not work.

Step 2: Consolidate and Refine to 2-4 Distinct COAs

With a full range of ideas generated, the next step is consolidating similar approaches and developing two to four distinct COAs that represent genuinely different strategic choices.

Identify Themes and Patterns

Review all generated ideas and identify themes representing fundamentally different approaches. Look for options that vary along key dimensions:

Timing: Some approaches emphasize speed and rapid implementation, while others prioritize careful phased rollouts that minimize disruption. A fast approach and a phased approach represent genuinely different COAs even if they use similar methods.

Risk profile: Some approaches accept higher risk in pursuit of higher returns or faster results, while others prioritize risk minimization even at the cost of slower progress or higher resource requirements. Conservative and aggressive approaches to the same objective are distinct COAs.

Resource intensity: Some approaches use minimal resources by focusing on essential elements only, while others employ comprehensive resources to maximize success probability or speed. Minimal and comprehensive approaches differ fundamentally in their philosophy.

Method: Some approaches emphasize evolutionary change that builds incrementally on existing systems, while others pursue revolutionary transformation that replaces current approaches entirely. Evolutionary and revolutionary methods represent distinct strategic choices.

The goal is not to force artificial distinctions, but rather to identify where the generated ideas naturally cluster around different philosophies or approaches. Often, multiple participants will have suggested similar ideas using different language, and consolidation reveals that you have three or four distinct themes rather than fifteen unique approaches.

Group similar ideas together under descriptive theme names. For example, multiple ideas about gradual market entry might group under “Phased Expansion COA,” while ideas about rapid comprehensive entry group under “Full-Scale Launch COA.”

Develop 2-4 Distinct COAs

From the identified themes, develop two to four distinct COAs. Two COAs is the minimum for meaningful choice; more than four often creates unnecessary complexity without adding sufficient value to justify the analytical burden.

For each COA, create a clear description that captures its fundamental approach and distinguishes it from alternatives. The description should be concrete enough to enable analysis but high-level enough to avoid getting lost in implementation details at this stage.

Use the COA template to structure each option:

COA Title: Create a descriptive name that captures the essential nature of the approach. Good titles immediately communicate the key characteristic: “Rapid Deployment COA,” “Partnership-Based Entry COA,” “Phased Implementation COA.” Avoid generic titles like “Option A” that provide no information about the approach.

Core Concept: Write two to three sentences describing the fundamental approach. What is the basic strategy? How does this COA propose to accomplish the objective? What makes this approach distinct from the others?

Example: “The Rapid Deployment COA accomplishes market entry through comprehensive immediate launch across all target segments. This approach accepts higher initial risk in exchange for faster market penetration and first-mover advantage. All capabilities are deployed simultaneously rather than sequentially, requiring significant upfront resource commitment but achieving full operational status within six months.”

Key Features: Identify three to five distinctive characteristics that define this approach. What are the essential elements that must be present for this to be the COA described? Features might include specific methods, resource allocations, timeline elements, or structural approaches.

Primary Advantage: Articulate the main reason this COA is attractive. What does this approach do better than the alternatives? Every viable COA must have at least one significant advantage or there would be no reason to consider it.

Primary Risk: Identify the main concern or vulnerability of this approach. What could cause this COA to fail? Being honest about risks during development prevents surprises during implementation and enables realistic comparison between options.

Apply Quality Check Questions

Before finalizing your COAs, test whether they meet the standard for genuine alternatives:

Can someone clearly articulate how each COA differs from the others? If you have to explain subtle distinctions, your COAs are probably too similar. Genuine alternatives should have obvious, easily stated differences.

Does each COA represent a fundamentally different philosophy or approach? If COAs differ only in implementation details but share the same basic strategy, they are variations rather than alternatives. Push for approaches that differ in their core assumptions about how to succeed.

Would different stakeholders prefer different COAs for legitimate reasons? If all reasonable stakeholders would obviously prefer the same COA, your alternatives are not genuinely different enough. Distinct COAs create legitimate disagreement because they optimize for different priorities.

Do the COAs span the realistic range of possible approaches? Have you explored the spectrum of viable options, or have all your COAs clustered around a similar middle ground? Effective COA development includes at least one relatively conservative and one relatively aggressive option.

If your COAs fail these tests, return to the generated ideas and look for more fundamental differences. Better to develop two genuinely distinct COAs than four variations of the same approach.

Step 3: Develop Initial COA Outlines

With distinct COAs identified, the final step in Phase 1 is developing high-level outlines that provide enough detail to enable meaningful analysis in Phase 2 without becoming burdensome.

Outline Execution Phases

For each COA, document the major phases or steps required for execution. These phases should be high-level rather than detailed task lists. The goal is to understand the general flow of implementation and identify major milestones.

Most COAs will have three to five major phases. For example, a market entry COA might include: market preparation and partnership development, initial launch in pilot markets, evaluation and adjustment, and full-scale rollout. A technology implementation COA might include: requirements and design, build and testing, pilot deployment, and enterprise rollout.

For each phase, provide a brief description of what would be accomplished and an approximate duration. This high-level timeline helps understand the overall timeframe for the COA without getting lost in detailed scheduling.

Identify major decision points where the approach might need to change based on results or changed circumstances. These decision points are critical because they represent moments when the organization might pivot to a different COA or modify the current approach based on new information.

Document Resource Requirements

Develop high-level resource estimates across relevant categories. At this stage, order-of-magnitude estimates are sufficient; detailed budgeting happens after COA selection during implementation planning.

Personnel requirements should identify key roles and approximate staffing levels. For example: “Requires dedicated project team of six to eight people including marketing, operations, and technology expertise, plus part-time support from legal and finance.” This level of detail enables comparison between COAs without requiring detailed organizational design.

Budget estimates should provide order-of-magnitude figures: thousands, tens of thousands, hundreds of thousands, or millions. The goal is to understand whether COAs are in similar cost ranges or whether some are significantly more expensive than others.

Technology or infrastructure requirements should identify major systems or capabilities needed. For example: “Requires new CRM system, payment processing integration, and customer portal development.” This helps understand whether COAs require similar or different technical investments.

Time estimates should indicate total duration from initiation to completion. Some COAs achieve results quickly but require intensive short-term effort, while others spread work over longer periods with lower intensity. Understanding these differences helps evaluate COAs against organizational capacity and urgency.

Identify Critical Success Factors

For each COA, identify three to five factors that must go right for the approach to succeed. These critical success factors reveal what each COA depends on and help assess risk in Phase 2.

Critical success factors often relate to assumptions being made: “Assumes cooperation from key partners,” “Requires securing additional budget within three months,” “Depends on market conditions remaining stable,” “Requires rapid skill development in new capabilities.”

Explicitly stating these factors forces honest assessment of what each COA needs to succeed. This transparency prevents wishful thinking during COA development and creates realistic expectations for implementation.

Use the COA Outline Template

Structure each COA outline using a consistent format:

Execution Phases: 1. Phase 1: [Description and duration] 2. Phase 2: [Description and duration] 3. Phase 3: [Description and duration]

Resource Requirements (High-Level): - Personnel: [Key roles and approximate numbers] - Budget: [Order of magnitude estimate] - Technology/Tools: [Major systems or capabilities needed] - Time: [Total duration from start to completion]

Critical Success Factors: - [Factor 1: What must go right] - [Factor 2: What must go right] - [Factor 3: What must go right]

This structured format enables easy comparison between COAs in later phases and ensures that all COAs are described with similar levels of detail.

Practical Example: Technology Platform Selection

To illustrate Phase 1 in practice, consider a mid-sized manufacturing company that needs to replace its aging enterprise resource planning system.

Prerequisites

Decision Statement: “We need to decide how to replace our ERP system by Q4 2026 given that we cannot disrupt current operations and have capital budget constraints of five million dollars.”

Key Stakeholders: Operations leadership, finance team, IT department, plant managers, executive leadership.

Evaluation Criteria: Risk to operations (40%), total cost (25%), time to full capability (20%), flexibility for future needs (15%).

Generated Ideas from Brainstorming

The team generated eight initial ideas including: complete system replacement in single implementation, phased modular replacement, running parallel systems during transition, cloud-based solution, on-premise solution, partnering with implementation consultants, training internal team for implementation, and hybrid cloud/on-premise approach.

Three Distinct COAs Developed

COA 1: Big Bang Replacement

Core Concept: Replace entire system in a single comprehensive implementation. All modules and capabilities launch simultaneously with intensive three-month cutover period. Highest risk but fastest time to full benefit.

Key Features: - Single implementation event rather than phased approach - Complete legacy system retirement - Intensive training and change management in compressed timeframe - Maximum implementation support from vendor and consultants

Primary Advantage: Fastest time to full operational capability and complete elimination of legacy system limitations.

Primary Risk: Significant operational disruption if implementation encounters problems during cutover period.

Resource Requirements: - Personnel: 8 FTE dedicated team plus extensive consultant support - Budget: $4.5 million - Technology: Cloud-based ERP platform - Time: 12-month planning and development, 3-month cutover, 15 months total

Critical Success Factors: - Comprehensive testing before cutover - Executive commitment to intensive change management - Vendor delivers on implementation commitments

COA 2: Phased Modular Replacement

Core Concept: Implement new system module by module over 24-month period. Each module fully operational before next module begins implementation. Lower risk through incremental rollout that maintains operations throughout transition.

Key Features: - Sequential module implementation (finance, operations, supply chain, etc.) - Maintains legacy system until all modules operational - Allows learning and adjustment between modules - Distributed training and change management

Primary Advantage: Minimizes operational risk through incremental approach that allows course correction between modules.

Primary Risk: Extended timeline maintains legacy system costs and delays full benefit realization.

Resource Requirements: - Personnel: 5 FTE dedicated team - Budget: $5.2 million (higher due to extended dual-system operations) - Technology: Cloud-based ERP platform - Time: 24 months total

Critical Success Factors: - Successful first module implementation builds confidence - Organization maintains commitment through extended timeline - Module integration works as designed

COA 3: Parallel Systems Approach

Core Concept: Implement new system while maintaining legacy system for 18 months. Run parallel operations to ensure business continuity and enable comprehensive validation before legacy retirement. Maximum safety at highest resource cost.

Key Features: - Full implementation of new system with complete legacy system backup - Extended parallel operations for validation - Gradual transition of functions from legacy to new - Maximum risk mitigation

Primary Advantage: Complete operational continuity with ability to revert to legacy system if problems arise.

Primary Risk: Highest cost due to supporting two complete systems; complexity of managing parallel operations.

Resource Requirements: - Personnel: 10 FTE dedicated team - Budget: $6.8 million (requires budget increase) - Technology: Cloud-based ERP with legacy system maintenance - Time: 24 months total including parallel operations

Critical Success Factors: - Approval for budget increase - Organizational capacity to manage dual systems - Clear criteria for legacy system retirement

These three COAs represent genuinely different approaches: aggressive fast implementation, conservative phased approach, and maximum safety through redundancy. Each has clear advantages and disadvantages that enable meaningful analysis and comparison.

Transitioning to Phase 2

With two to four distinct COAs developed and outlined, Phase 1 is complete. You now have genuine strategic alternatives rather than superficial variations, and each COA has sufficient definition to enable rigorous analysis.

The COAs developed in Phase 1 provide the foundation for all subsequent work. Phase 2 will analyze each COA’s feasibility, risks, resource requirements, and probable outcomes. Phase 3 will systematically compare the analyzed COAs to identify the superior option. Phase 4 will develop detailed implementation plans for the selected COA.

The quality of your Phase 1 work directly determines the value of subsequent analysis. Genuinely distinct COAs enable meaningful choice; superficial variations waste analytical effort without improving decision quality. Invest the time required to develop real alternatives, and the subsequent phases will produce better decisions and more successful implementations.

Before moving to Phase 2, validate that your COAs meet the standard for genuine alternatives. Each should be viable, suitable for accomplishing the objective, and distinguishably different from the others. If your COAs fail these tests, return to earlier steps in Phase 1 rather than proceeding with inadequate alternatives.

Purposeful leadership requires genuine strategic choice, not predetermined outcomes disguised as analysis. Phase 1 creates the foundation for purposeful decision-making by ensuring you have real alternatives worthy of rigorous consideration.

Phase 1: Generating Distinct Courses of Action