In a recent interaction, I showcased the potential of OpenAI's ChatGPT in assisting educators to refine their course structures. My experiment began by predefining a context using a comprehensive list of Business Analysis Techniques. Following this preprompt, I presented a current undergraduate course structure that needed modification. The goal? To identify and recommend new Business Analysis techniques appropriate for each chapter of the course.
This post has been cowritten with ChatGPT. Please beware that AI is fascinating and can catch your full attention for hours. Get the balance right! > more?
The Experiment
Teacher:
ChatGPT
Sure, I will suggest 3 additional Business Analysis techniques from your provided list for each chapter from 2 to 10. Here are my suggestions along with a brief explanation of each technique and why they would be suitable for each respective chapter:
Chapter 2 – Context
Business Domain Model
- Summary: This technique involves creating a representation of the organizational context in which the business problem or opportunity exists. It helps in identifying the entities in a business and their relationships.
- Justification: Understanding the business domain at a granular level can provide insights into how external factors identified by PESTEL, SWOT, and Porter's 5 forces can influence various elements in the business domain.
STEEP Analysis
- Summary: This method is similar to PESTEL but focuses on Socio-cultural, Technological, Economic, Environmental, and Political factors that influence the business environment.
- Justification: STEEP analysis complements PESTEL analysis and provides a broader view of the external factors affecting the business context.
Balanced Scorecard
- Summary: This technique allows businesses to monitor and measure the effectiveness of processes and strategies.
- Justification: Including this in the context chapter helps in setting up a framework which allows measuring the impacts of various contextual elements on business strategies.
Chapter 3 – Stakeholders
Stakeholder List, Map or Personas
- Summary: This technique involves identifying and analyzing stakeholders and creating visual representations or detailed profiles to understand their interests, influence, and needs better.
- Justification: Enhances stakeholder management by creating a clear representation of stakeholder groups which complements the existing techniques in the chapter.
Jobs to be Done (JTBD)
- Summary: This method focuses on understanding the jobs that stakeholders are trying to accomplish.
- Justification: Incorporating this technique can provide a more in-depth insight into stakeholder needs and preferences which would assist in effective stakeholder management.
Interviews
- Summary: This technique involves conducting interviews with stakeholders to gather qualitative data and insights.
- Justification: Helps in acquiring direct insights from stakeholders, providing an opportunity to uncover trends and perspectives that might not be captured through diagrams and matrices.
Chapter 4 – Opportunities & Risks
Risk Analysis and Management
- Summary: It involves the identification, assessment, and prioritization of risks followed by coordinated efforts to minimize and control the probability of unfortunate events.
- Justification: Directly contributes to managing and mitigating risks identified in the opportunity-risk matrix.
SWOT Analysis
- Summary: SWOT analysis helps in identifying Strengths, Weaknesses, Opportunities, and Threats related to business competition or project planning.
- Justification: This technique can aid in identifying opportunities and risks from a broader perspective, complementing the existing techniques in the chapter.
Benchmarking and Market Analysis
- Summary: It involves comparing business processes and performance metrics to industry bests or best practices from other companies.
- Justification: Helps in identifying opportunities and risks in the market, facilitating better decision-making based on market trends and standards.
Chapter 5 – Scenarios
Use Case and Scenarios
- Summary: This technique helps in identifying, clarifying, and organizing system requirements, particularly in system developments.
- Justification: Can be used to develop potential scenarios in business planning, providing a structured approach to scenario development.
User Stories
- Summary: These are simple descriptions of a feature, told from the perspective of a person who desires the new capability.
- Justification: Can be used to build stakeholder stories, helping in understanding various perspectives in different scenarios.
Prototyping
- Summary: This technique involves creating prototypes of systems or features to visualize and test concepts before full-scale implementation.
- Justification: Helps in visualizing scenarios and understanding potential issues before implementation, aiding in better planning.
Chapter 6 – Gaps
Gap Analysis
- Summary: It is a technique to identify the differences between current processes and desired goals.
- Justification: Directly relates to identifying gaps in current business strategies and operations, aiding in effective planning for improvements.
As-Is Process Analysis
- Summary: This technique involves analyzing current processes to understand their effectiveness and identify areas for improvement.
- Justification: Complements gap analysis by providing a detailed view of current processes, helping in identifying gaps effectively.
To Be Process Analysis
- Summary: This technique involves analyzing and defining future processes that would help in bridging identified gaps.
- Justification: Helps in creating a roadmap for bridging identified gaps, complementing the POPIT and McKinsey 7-S models.
Chapter 7 – Priorities
MoSCoW Prioritisation
- Summary: This technique helps in prioritizing requirements by categorizing them into Must-haves, Should-haves, Could-haves, and Won't-haves.
- Justification: Complements the existing techniques in the chapter by providing a structured approach to prioritizing requirements and tasks.
Kano Model
- Summary: This technique involves categorizing features or requirements based on how they are perceived by users and their effect on user satisfaction.
- Justification: Provides a different perspective on prioritization, focusing on user satisfaction which can be an essential factor in determining priorities.
Weighted Decision Matrix
- Summary: It is a tool used to compare alternatives with respect to various criteria of different weights.
- Justification: Can be used to make informed decisions based on different criteria, helping in prioritizing tasks effectively.
Chapter 8 – Processes
Business Process Modelling Notation (BPMN)
- Summary: This technique involves using graphical notation to visualize the steps and activities in a business process.
- Justification: Complements the existing techniques in the chapter by providing a standardized method for mapping and visualizing business processes.
Functional Decomposition
- Summary: This technique involves breaking down complex processes or projects into simpler, manageable parts.
- Justification: Helps in understanding and managing complex processes better, facilitating effective process management.
Six Thinking Hats
- Summary: This method involves looking at decisions from multiple perspectives to ensure comprehensive thinking.
- Justification: Can be used to evaluate processes from different perspectives, helping in identifying potential issues and improvements.
Chapter 9 – Planning & Budget
Financial Analysis
- Summary: This technique involves analyzing financial data to assess the business's stability, performance, and liquidity.
- Justification: Critical for budget planning as it provides insights into financial health, aiding in informed budget planning and management.
Metrics and Key Performance Indicators (KPIs)
- Summary: Involves setting up metrics and KPIs to monitor and measure the performance of various aspects of the business.
- Justification: Helps in tracking the performance of implemented plans and budgets, facilitating effective management and adjustments.
Resource Audit
- Summary: This technique involves assessing the current resources of the organization, including financial, human, and material resources.
- Justification: Provides insights into available resources, aiding in effective planning and budget allocation.
Chapter 10 – Business case document
Business Cases
- Summary: This technique involves creating a structured document that argues why a particular business decision or project is the right course of action.
- Justification: Directly relates to building a strong business case, supporting the existing techniques in the chapter.
Benefits Dependency Network (Benefits Map)
- Summary: This technique involves mapping out the relationship between project deliverables and the benefits they are expected to deliver.
- Justification: Helps in showcasing the potential benefits of a proposed business case, enhancing its credibility.
Vendor Assessment
- Summary: This technique involves assessing and evaluating potential vendors based on various criteria.
- Justification: Can be essential if the business case involves acquiring products or services from external vendors, ensuring the best vendors are selected for optimal results.
These suggestions incorporate a range of techniques to provide a holistic approach to business analysis across different chapters.
Analysis
The majority of the suggestions are interesting. ChatGPT sticks to the list of 96 techniques. These are sensibly assigned to the chapters of my course. Discussing whether the rationale in each case is defensible is beyond the scope of this post. Although the majority of the suggestions are helpful, we also see clear limits to the LLM model in the solution: • In Chapter 4, ChatGPT suggests SWOT Analysis even though the course chapter already includes SWOT. It seems that SWOT and SWOT Analysis are not equal here. • In chapter 5 ChatGPT proposes User Stories, although the course chapter contains Stakeholder Stories. Users belong to Stakeholders, of course, but LLM cannot make this derivation. • In Chapter 6, ChatGPT proposes a Gap Analysis, which is consistent with the title of the entire course chapter. • In Chapter 7, ChatGPT proposes a MoSCow Prioritization and surprises me with an otherwise uncommon Case Sensitiveness, because MOSCOW is already in the course chapter. • Finally, in the closing chapter 10, ChatGPT proposes business cases, which again matches the title of the course chapter. These difficulties aside, I found the experiment exciting. I will adopt the suggested in-depth topics in my next year's course structure. Thus, the answer to the in-depth question is: Yes, to some extent ChatGPT can help me refine my course structure.