Strategy Brainstorming Assistant
1. Overview
The Strategy Brainstorming Assistant helps a consultant produce a set of strategic options and the associated risk factors for a client‑driven business challenge. It uses well‑known strategic frameworks to ensure the ideas are thorough, balanced, and documented in a ready‑to‑share format.
2. Business Value
- Accelerates ideation – provides a structured way to generate multiple options quickly.
- Ensures coverage – applying proven frameworks reduces the chance of overlooking important dimensions.
- Highlights risk – each option includes identified risk factors, helping the consultant anticipate challenges early.
- Delivers clear output – a concise report that can be shared directly with the client or internal team.
3. Operational Context
| Situation | Who Uses It | Frequency |
|---|
| When a consulting engagement is at the problem‑definition or early‑strategy stage – the client has presented a challenge (e.g., entering a new market, increasing revenue, or reducing costs). | Consulting analysts, senior consultants, and strategy leads. | Typically once per project phase or whenever a new strategic question arises. |
4. Inputs
4.1 Problem Statement
- Type: Text
- Details Provided: A clear, concise description of the business challenge, opportunity, or decision that requires strategic options.
4.2 Context Summary
- Type: Text
- Details Provided: Any relevant background such as industry trends, company size, recent changes, competitive landscape, or constraints that affect the decision.
4.3 Desired Frameworks (Optional)
- Type: List of text strings
- Details Provided: Names of strategic frameworks to be applied (e.g., “SWOT”, “PESTLE”, “Porter’s Five Forces”). If none are provided, the default set SWOT, PESTLE, and Porter’s Five Forces will be used.
4.4 Stakeholder List (Optional)
- Type: List of stakeholder entries
| Name | Role |
|---|
| [Stakeholder Name] | [Stakeholder Role] |
(Add one row for each stakeholder you wish the assistant to consider when identifying risks.)
4.5 Desired Output Format (Optional)
- Type: Text
- Possible Values: “Table” or “Bullet List”.
- Default: “Table”.
5. Outputs
5.1 Strategic Options Report
-
Name/Label: Strategic Options Report
-
Contents: For each strategic option generated, the report includes:
- Option Name – a short, descriptive title.
- Framework Used – the strategic framework that produced the option.
- Rationale – why the option addresses the problem.
- Advantages – key benefits of pursuing the option.
- Disadvantages – key downsides or constraints.
- Key Risks – a list of risk factors identified (each risk includes a brief description).
-
Formatting Rules: Present each option as a row in a table (see “Table format” in Appendix C).
| Option Name | Framework | Rationale | Advantages | Disadvantages | Key Risks |
|---|
| e.g., Launch Subscription Delivery Service | PESTLE | Meets growing demand for convenience and creates recurring revenue. | Predictable cash flow; differentiates brand. | Requires new logistics and IT platform. | • High upfront technology cost – Financial. |
| • Delivery reliability – Operational. | | | | | |
| […] | … | … | … | … | … |
5.2 Risk Summary
-
Name/Label: Risk Summary
-
Contents: Consolidated list of the most significant risks across all options, grouped by risk category.
-
Formatting Rules: Use a table with one row per risk category.
| Risk Category | Example Risk | Impact (High/Medium/Low) | Suggested Mitigation |
|---|
| Financial | Large upfront capital outlay. | High | Stage investment; seek partner financing. |
| Operational | Supply‑chain disruptions for new product lines. | Medium | Identify alternate suppliers, build buffer inventory. |
| Market | Consumer adoption slower than expected. | Medium | Pilot program before full launch. |
| Regulatory | New health‑safety regulations may affect product rollout. | Low | Monitor regulatory updates; adapt compliance plan. |
| [Add more as needed] | | | |
6. Detailed Plan & Execution Steps
-
Receive all inputs. Verify the presence of a Problem Statement. If missing, stop and flag for manual review.
-
Determine the framework set:
a. If a Desired Frameworks list is provided, use those.
b. If the list is empty or missing, default to SWOT, PESTLE, and Porter’s Five Forces.
-
Perform framework analysis (use the step‑by‑step guides in Appendix C):
a. SWOT – list internal Strengths / Weaknesses and external Opportunities / Threats.
b. PESTLE – examine Political, Economic, Social, Technological, Legal, and Environmental factors.
c. Porter’s Five Forces – evaluate Supplier Power, Buyer Power, Threat of New entrants, Threat of Substitutes, and Competitive Rivalry.
-
Generate strategic options for each framework:
a. Draft up to three (3) distinct options per framework (max nine total).
b. For each option, write a concise Rationale, list Advantages and Disadvantages, and note Key Risks.
c. Reference the Stakeholder List when identifying risks (e.g., “Finance” stakeholder is concerned about cash‑flow).
-
Consolidate and de‑duplicate:
a. Combine all options into a single list.
b. If two options are essentially the same (e.g., “Launch mobile app” vs. “Develop a mobile app”), merge them and keep the richer description.
-
Prioritize options (simple scoring):
- Alignment with Problem Statement (High/Medium/Low).
- Resource intensity (High/Medium/Low).
- Risk level (sum of impact scores).
Provide a ranking (1‑N) based on the highest alignment and lowest combined risk and resource intensity.
-
Create the Risk Summary:
a. Review all Key Risks across options.
b. Group them into the categories shown in the Risk Summary table.
c. Assign an Impact rating (High/Medium/Low) based on the potential effect on the client’s goals.
d. Suggest one mitigation for each.
-
Format output:
-
If Desired Output Format is “Table”, produce the tables exactly as shown in sections 5.1 and 5.2.
-
If “Bullet List”, convert each row into a bullet‑point block with the same information.
-
Deliver the Strategic Options Report and Risk Summary to the requesting consultant.
7. Validation & Quality Checks
| Check | Description | Pass/Fail Criteria |
|---|
| Problem Statement Presence | Verify the problem statement is not blank. | Must contain at least one sentence. |
| Framework Selection | Confirm that at least one framework is used. | At least one of SWOT, PESTLE, Porter’s Five Forces is applied. |
| Option Completeness | Each option has: name, framework, rationale, advantages, disadvantages, and at least one risk. | All fields non‑empty. |
| Risk Identification | Each risk includes a brief description and belongs to a risk category. | Every risk listed in the Risk Summary matches a risk from an option. |
| Duplication Check | No two options have identical names (case‑insensitive). | Duplicate rows are merged. |
| Output Format | The final output matches the requested format. | Table or Bullet List as requested. |
| Impact Rating | All risks have an Impact rating (High/Medium/Low). | No missing ratings. |
| Overall Consistency | The report follows the template layout. | No missing sections or tables. |
If any check fails, mark the entire output as “Error – Validation Failure” and provide a brief description of the failing condition. No further output should be generated until the issue is resolved.
8. Special Rules / Edge Cases
| Situation | Action |
|---|
| Missing Problem Statement | Halt the process. Return a “Missing Problem Statement” error and flag for manual review. |
| Empty Desired Frameworks | Use the default set (SWOT, PESTLE, Porter’s Five Forces). |
| Unrecognised Framework name | Skip the unrecognised framework. Add a note in the report: “The framework ‘X’ was not recognized and was omitted.” |
| No Stakeholder List | Use generic stakeholder categories: Executive, Operations, Finance, Marketing. |
| No Strategic Options Generated (e.g., problem too narrow) | Return a “No viable strategic options identified” message and stop. |
| Output Format Unrecognised | Default to “Table”. |
| Excessive Options (more than 9) | Keep only the top 9 based on the prioritization scoring. |
| Risk Impact Unknown | Set Impact to “Medium” by default and include a note to review. |
| Duplicate Risks across options | Keep the risk entry once in the Risk Summary and note all options it applies to. |
| Inconsistent Capitalization (e.g., “SWOT” vs “Swot”) | Treat as the same framework; normalise to capital letters. |
| Failure to generate report due to system error | Return an “Error – System Failure” status. No partial output should be sent. |
9. Example
Input
-
Problem Statement: Our client, a regional coffee chain with 10 stores, wants to increase market share by 15 % within the next 24 months.
-
Context Summary: The chain operates in mid‑size towns, faces rising competition from specialty coffee shops, has moderate cash reserves, and is considering a digital transformation.
-
Desired Frameworks: SWOT, PESTLE
-
Stakeholder List:
| Name | Role |
|---|
| Alice Johnson | Owner / Executive |
| Carlos Ramirez | Store Operations Manager |
| Priya Patel | Finance Director |
| Maya Liu | Marketing Lead |
-
Desired Output Format: Table
Output
Strategic Options Report
| Option Name | Framework | Rationale | Advantages | Disadvantages | Key Risks |
|---|
| Launch Subscription‑Based Coffee Delivery | PESTLE – Technological & Social Trends | Meets growing consumer demand for convenient, home‑delivered coffee; creates recurring revenue. | Predictable cash flow; enhances brand loyalty; leverages existing supply chain. | Requires investment in logistics, mobile app development; requires new delivery partnerships. | • Financial – High upfront technology cost (High). |
| • Operational – Delivery logistics reliability (Medium). | | | | | |
| Introduce Premium Specialty Coffee Line | SWOT – Opportunities | Differentiates brand, captures high‑margin segment; aligns with coffee‑culture trend. | Higher profit margins per unit; attracts new customer segment. | Requires new sourcing, staff training, potential supply‑chain risk for exotic beans. | • Supply – Sourcing specialty beans (Medium). |
| • Financial – Higher cost of goods (Medium). | | | | | |
| Open Two New Urban Locations | Porter’s Five Forces – Competitive Rivalry | Expands physical presence where competitor density is high; captures new market share. | Increased market coverage; economies of scale. | Significant capital investment; risk of cannibalizing existing stores. | • Financial – Capital‑intensive (High). |
| • Market – Uncertain foot‑traffic (Medium). | | | | | |
| Launch Loyalty Program with Mobile App | PESTLE – Social & Technological | Improves customer retention, provides data for targeted marketing. | Low‑cost digital channel; can drive upsell. | Requires app development; data‑privacy compliance required. | • Technical – App development timeline (Medium). |
| • Regulatory – Data‑privacy compliance (Medium). | | | | | |
| Partner with Local Bakeries for Co‑branded Products | SWOT – Strengths | Leverages existing bakery partners to expand product offering with minimal capital. | Shared marketing; low incremental cost. | Dependency on partner quality; brand alignment risk. | • Operational – Coordination with partners (Medium). |
| Roll Out Mobile Ordering & In‑Store Pickup | PESTLE – Technological | Meets consumer demand for speed & convenience; leverages existing stores. | Increases store traffic; data collection for inventory. | Requires POS system upgrade, staff training. | • Technical – System integration (Medium). |
| • Operational – Staff adaptation (Low). | | | | | |
Risk Summary
| Category | Example Risk | Impact | Suggested Mitigation |
|---|
| Financial | High upfront technology cost for subscription delivery. | High | Phase rollout; seek external financing; pilot in limited area. |
| Operational | Delivery logistics may cause delays. | Medium | Partner with reputable delivery service; build buffer inventory. |
| Supply | Sourcing exotic beans could be disrupted. | Medium | Identify multiple suppliers; keep safety stock. |
| Regulatory | Data‑privacy compliance for mobile app. | Low | Conduct privacy impact assessment; adopt best‑practice data handling. |
| Market | New locations may not attract enough foot‑traffic. | Medium | Conduct market research before site selection; test with pop‑up stores. |
| Technical | App development timeline may slip. | Medium | Use agile development; set realistic milestones. |
Appendix A – FAQ
Q1: What if the client wants more than three options per framework?
A: The SOP caps at three per framework to keep the output digestible. If more options are needed, run the process again with a different focus (e.g., “focus on cost‑reduction” or “focus on growth”).
Q2: How do I handle a missing stakeholder list?
A: The assistant will use generic stakeholder categories (Executive, Operations, Finance, Marketing) and note that the list is assumed. You can later replace the generic entries with actual names.
Q3: What if the client wants a “Bullet List” instead of a table?
A: The assistant will re‑format each row as a bullet‑point block but retain all fields (option name, rationale, etc.) in the same order.
Q4: The client wants to prioritize “low‑risk” options. How should I interpret the “Impact” rating?
A: Use the “Impact” column in the Risk Summary. Options with only Low or Medium impact across most categories can be flagged as “low‑risk”.
Q5: The client asks for a timeline for each option.
A: The SOP does not generate a timeline. Add a “Timeline” column manually after receiving the report if needed.
Q6: What if a framework produces duplicate options?
A: The SOP merges duplicates during Step 5. The merged entry retains the most comprehensive rationale and risk list.
Q7: How are the impact ratings decided?
A: The assistant follows the guidelines in Appendix C (Risk Impact Guidelines). Use the scale: High (potential to derail the project), Medium (manageable but needs mitigation), Low (minimal effect).
Q8: I need the report in a PDF for the client.
A: The SOP produces a table (or bullet list) as plain text. Convert it to a PDF using your standard document‑creation tool; the SOP does not generate files directly.
Q9: What if the problem statement is too vague?
A: The assistant will flag it as “Insufficient detail” and request clarification before proceeding.
Q10: Can I add a new framework (e.g., “Blue Ocean”) to the process?
A: Yes. Add the framework name to Desired Frameworks. The assistant will treat it as a “custom” framework and generate options using the generic approach described in Appendix C (Step‑by‑Step Guidance). If the framework is not recognized, it will be omitted and noted.
Appendix B – Glossary
- Strategic Option: A distinct course of action that could help the client achieve a goal or address a problem.
- Risk Factor: A condition or event that could negatively affect the success of an option (e.g., financial loss, operational disruption).
- Framework: A structured method for analyzing a situation (e.g., SWOT, PESTLE).
- SWOT: Analysis of Strengths, Weaknesses, Opportunities, Threats.
- PESTLE: Evaluation of Political, Economic, Social, Technological, Legal, and Environmental factors.
- Porter’s Five Forces: Assessment of Supplier Power, Buyer Power, Threat of New Entrants, Threat of Substitutes, and Competitive Rivalry.
- Impact Rating: A qualitative rating (High, Medium, Low) indicating the potential severity of a risk.
- Stakeholder: Any person or group who can influence or be impacted by the strategic options.
Appendix C – Reference Material
C1. Framework Summaries
| Framework | Purpose | Typical Questions to Ask | How to Generate Options |
|---|
| SWOT | Identify internal and external factors affecting the problem. | Strengths: What does the client do well? | |
| Weaknesses: Where does the client struggle? | | | |
| Opportunities: What external trends could be leveraged? | | | |
| Threats: What external forces could hinder the plan? | For each quadrant, brainstorm 1–2 actions that leverage strengths/opportunities, mitigate weaknesses/threats. | | |
| PESTLE | Scan macro‑environmental influences. | Political: Regulations, tax policies? | |
| Economic: Market growth, inflation? | | | |
| Social: Consumer habits, demographics? | | | |
| Technological: Emerging tech, digital adoption? | | | |
| Legal: Compliance, labor laws? | | | |
| Environmental: Sustainability, climate impact? | Identify how each factor creates opportunities or threats. Turn each insight into a potential action (e.g., “Adopt eco‑friendly packaging” from Environmental). | | |
| Porter’s Five Forces | Assess industry competitiveness. | Supplier Power: Supplier concentration? | |
| Buyer Power: Customer bargaining? | | | |
| Threat of New Entrants: Barriers? | | | |
| Threat of Substitutes: Alternative solutions? | | | |
| Rivalry: Number/strength of competitors? | For each force, note a strategic lever (e.g., “Negotiate long‑term contracts to reduce supplier power”). Combine related levers into a single option where possible. | | |
C2. Step‑by‑Step Guidance for Each Framework
1. SWOT
-
List Strengths (e.g., strong brand, loyal customers).
-
List Weaknesses (e.g., limited digital presence).
-
List Opportunities (e.g., growing demand for specialty coffee).
-
List Threats (e.g., new competitor entering).
-
Generate options:
- Leverage Strength + Opportunity → New option.
- Mitigate Weakness → improvement option.
- Counter Threat → defensive option.
2. PESTLE
-
Capture Political (e.g., upcoming regulation).
-
Capture Economic (e.g., recession risk).
-
Capture Social (e.g., rising health consciousness).
-
Capture Technological (e.g., rise of mobile ordering).
-
Capture Legal (e.g., new food safety laws).
-
Capture Environmental (e.g., sustainability expectations).
-
Generate options: For each factor that offers an opportunity, create an action; for each threat, create a mitigation or adaptation option.
3. Porter’s Five Forces
-
Supplier Power: Evaluate supplier concentration, switching cost.
-
Buyer Power: Evaluate customer price sensitivity.
-
Threat of New Entrants: Examine barriers (capital, regulation).
-
Threat of Substitutes: Identify alternative solutions.
-
Competitive Rivalry: Assess number and intensity of competitors.
-
Generate options:
- Reduce Supplier Power → “Diversify supplier base”.
- Increase Buyer Power → “Loyalty program”.
- Mitigate New Entrants → “Strengthen brand”.
- Counter Substitutes → “Innovate product”.
C3. Risk Identification Guidelines
| Risk Category | Typical Source | Example Risk | Typical Mitigation |
|---|
| Financial | Capital investment, cash‑flow | High upfront cost for new tech. | Staged rollout, financing options. |
| Operational | Process, supply‑chain, staff | Delivery delays. | Partner with reliable logistics, buffer inventory. |
| Market | Customer demand, competition | Low adoption of new product. | Pilot test, gather feedback. |
| Regulatory | Legal compliance, permits | New health regulations. | Monitor regulator updates, compliance plan. |
| Technological | IT system, data security | App security breach. | Implement security protocols, penetration testing. |
| Environmental | Sustainability, climate | Supply‑chain disruptions due to climate events. | Diversify suppliers, risk‑sharing contracts. |
How to assign Impact rating
| Impact Level | Definition | Example |
|---|
| High | Potential to cause project failure or major loss. | Investment > 30 % of cash reserves. |
| Medium | Could cause delay or moderate loss. | New process requires training. |
| Low | Minor inconvenience, easy to remediate. | Minor UI bug in app. |
C4. Output Formatting Guidelines
- Table Format: Use plain‑text tables with vertical bars (
|) as shown in the examples. Ensure each column header appears exactly once and is separated by a row of hyphens (---).
- Bullet List Format: Use hyphens (
-) for each bullet. Indent sub‑items with two spaces.
- Styling: Keep language neutral, professional, and concise. Avoid marketing hyperbole.
- Length: Aim for 3‑5 strategic options and 4‑6 risk entries, unless the problem scope explicitly requires more.
C5. Example Template for Report (Table)
| Option Name | Framework | Rationale | Advantages | Disadvantages | Key Risks |
|---|
| Your Option | Framework | Brief description why it works | Key benefits | Potential drawbacks | Risk 1 (Impact) – Mitigation |
| Risk 2 (Impact) – Mitigation | | | | | |
| … | … | … | … | … | … |
C6. Example Template for Risk Summary (Table)
| Category | Risk Description | Impact | Suggested Mitigation |
|---|
| Financial | Description | High/Medium/Low | Mitigation step |
| Operational | … | … | … |
C7. Frequently Used Phrases (for consistency)
- “Potential” – used to denote a possible but not guaranteed effect.
- “Mitigation” – recommended action to reduce risk severity.
- “Rationale” – why an option is considered relevant.
- “Key” – indicates the most important element of a list (e.g., “Key Risks”).
- “Leverage” – to use an asset or advantage.
- “Address**” – to confront or solve a problem.