0% found this document useful (0 votes)
32 views

BA Tools and Techniques

The document provides examples of 100 business analysis tools and techniques used to gather requirements, model processes, identify risks, and support decision-making. Some of the techniques described include stakeholder analysis, process mapping, prototyping, surveys, cost-benefit analysis, and data visualization. For each technique, an example is given to illustrate how it can be applied in a business analysis context.

Uploaded by

armaan
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
32 views

BA Tools and Techniques

The document provides examples of 100 business analysis tools and techniques used to gather requirements, model processes, identify risks, and support decision-making. Some of the techniques described include stakeholder analysis, process mapping, prototyping, surveys, cost-benefit analysis, and data visualization. For each technique, an example is given to illustrate how it can be applied in a business analysis context.

Uploaded by

armaan
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 27

List of 100 Business Analyst Tools and

Techniques – Explained When and Where


to use them using Examples

Created By – Diwakar Kumar Singh


Stakeholder Analysis: Identifies and analyzes individuals or groups
affected by a project to understand their needs, expectations, and
influence. It helps in effective stakeholder engagement.
Example: A Business Analyst conducts stakeholder analysis to
understand the requirements and concerns of different departments
within an organization for a process improvement initiative.

Business Process Modeling: Graphically represents processes,


workflows, and activities within an organization using techniques like
flowcharts or BPMN (Business Process Model and Notation).

Example: Creating a process flow diagram to map the order-to-cash


process in a company, identifying bottlenecks and areas for
optimization.

Use Case Diagrams: Visual representations of system behavior and


interactions with external actors. They depict how users or systems
interact with a product or service.

Example: Creating a use case diagram for an e-commerce platform to


illustrate interactions between customers, products, and payment
gateways.

Data Flow Diagrams (DFD): Illustrates the flow of data within a system,
showing inputs, outputs, processes, and data stores. It helps in
understanding information flow.
Example: Creating a DFD to represent the flow of data between
different modules of an inventory management system.
Entity Relationship Diagrams (ERD): Represents the logical
relationships between entities in a database. It helps in designing
databases and understanding data relationships.

Example: Creating an ERD to define the relationships between


customers, orders, and products in a retail management system.

User Stories: Describes requirements from an end-user perspective.


User stories are concise, independent, and actionable.

Example: Writing user stories for an agile software development


project, such as "As a customer, I want to be able to track my order
status."

Acceptance Criteria: Defines the conditions that must be met for a


feature or user story to be considered complete and accepted.

Example: Documenting acceptance criteria for a payment gateway


integration, specifying expected response times, error handling, and
security requirements.

Business Rules Analysis: Identifies and documents the rules that govern
how a business operates. These rules guide decision-making and ensure
consistency.

Example: Analyzing business rules for an insurance company to define


eligibility criteria for claims processing.
Gap Analysis: Compares the current state of a process or system with
the desired future state to identify gaps and areas for improvement.
Example: Performing a gap analysis to assess the differences between
the existing customer service process and the desired state defined in
the business requirements.

Root Cause Analysis: Investigates the underlying causes of a problem


or an issue, aiming to identify the fundamental source rather than just
addressing symptoms.

Example: Conducting a root cause analysis to determine why a


company's website experienced a significant increase in page load
times.

Impact Analysis: Assesses the potential effects of a proposed change


on various aspects of a project or organization, such as cost, schedule,
resources, and stakeholders.

Example: Performing an impact analysis to understand the effects of


implementing a new software system on different departments and
processes within an organization.

Process Mapping: Visual representation of a process from start to


finish, capturing steps, decision points, inputs, and outputs. It helps in
identifying inefficiencies and bottlenecks.

Example: Creating a process map to document the steps involved in


employee onboarding, including HR paperwork, IT setup, and
orientation sessions.
Requirements Elicitation: Techniques used to gather requirements
from stakeholders, such as interviews, workshops, surveys, and
observations.

Example: Conducting interviews with key stakeholders to understand


their needs and expectations for a new customer relationship
management (CRM) system.

Prototyping: Building an early version of a product or system to


validate requirements, gather feedback, and refine the design before
full-scale development.

Example: Creating a clickable prototype of a mobile app to allow users


to provide feedback on the user interface and navigation.

Wireframing: Creating visual representations of screens or pages, often


using low-fidelity sketches or digital tools, to demonstrate layout and
functionality.

Example: Developing wireframes for a website redesign, showcasing


the arrangement of elements and content placement.

Decision Matrix: A structured approach for evaluating multiple options


against predefined criteria to support decision-making.

Example: Using a decision matrix to evaluate different software


vendors based on factors like cost, features, support, and scalability.

Cost-Benefit Analysis: Compares the costs and benefits of a proposed


project or investment to determine its economic viability.
Example: Conducting a cost-benefit analysis to assess whether
implementing a new customer support system will yield greater cost
savings than maintaining the current system.

Feasibility Study: Evaluates the technical, operational, and economic


feasibility of a proposed project to determine if it is achievable and
advisable.

Example: Performing a feasibility study to assess whether migrating an


on-premises system to the cloud is technically and financially viable.

Interviews: Conducting one-on-one or group interviews with


stakeholders to gather information, elicit requirements, and gain
insights.

Example: Interviewing subject matter experts and users to understand


pain points and gather requirements for a new inventory management
system.

Surveys: Collecting data and opinions from many stakeholders using


questionnaires or online surveys to gather quantitative and qualitative
insights.

Example: Distributing a survey to customers to gather feedback on


their satisfaction with an existing product and identify areas for
improvement.

Workshops: Facilitating collaborative sessions with stakeholders to


brainstorm ideas, gather requirements, and achieve consensus on
project objectives.
Example: Conducting a requirement gathering workshop with cross-
functional teams to define and prioritize features for a new mobile
application.

Observations: Actively observing users or processes in their natural


environment to understand behaviors, pain points, and opportunities
for improvement.

Example: Observing call center agents in action to identify pain points


and areas where technology solutions could streamline their workflow.

Focus Groups: Organizing moderated group discussions with


representative stakeholders to gain insights into their preferences,
opinions, and experiences.

Example: Hosting a focus group with target customers to gather


feedback on a new product's design, features, and pricing.

Document Analysis: Reviewing existing documentation, such as


business plans, project charters, policies, or reports, to extract relevant
information and identify gaps.

Example: Analyzing product specifications and technical documentation


to understand the functionality and requirements of a legacy system.

Mind Mapping: Visualizing ideas, concepts, and relationships using a


hierarchical structure to generate and organize thoughts during
brainstorming sessions or requirements gathering.
Example: Creating a mind map to explore potential product features
and functionalities for a new software application.

Benchmarking: Comparing performance, processes, or practices against


industry standards or best-in-class organizations to identify
improvement opportunities.

Example: Conducting benchmarking to assess how a company's


customer service metrics and processes compare to its competitors.

Data Analysis: Examining and interpreting data to uncover patterns,


trends, and insights that can inform decision-making and identify areas
for improvement.

Example: Analyzing sales data to identify customer preferences, buying


patterns, and market trends to guide product development and
marketing strategies.

Data Visualization: Presenting data in visual formats such as charts,


graphs, or dashboards to facilitate understanding and identify trends or
patterns.

Example: Creating a sales dashboard with interactive visualizations to


provide stakeholders with real-time insights on revenue, sales pipeline,
and market segments.

Decision Trees: Graphical representation of decision-making processes


that outline the possible choices, potential outcomes, and associated
probabilities.
Example: Building a decision tree to guide customer service
representatives in troubleshooting common product issues based on
user-reported symptoms.

Gap-Fit Analysis: Comparing existing capabilities or resources with


desired requirements to identify gaps and determine the level of effort
required to bridge them.

Example: Performing a gap-fit analysis to evaluate how well an off-the-


shelf software package meets the specific requirements of a company's
supply chain management process.

Process Improvement Techniques: Methods such as Lean, Six Sigma, or


Kaizen that focus on identifying and eliminating waste, improving
efficiency, and enhancing quality.

Example: Applying Lean principles to streamline the order fulfillment


process by eliminating non-value-added steps and reducing cycle time.

Decision Support Systems: Software tools or models that assist in


decision-making by providing relevant information, analysis, and
recommendations.

Example: Using a decision support system to evaluate different project


management software options based on predefined criteria and
generate a recommendation.

Risk Assessment and Management: Identifying and assessing potential


risks, estimating their impact and likelihood, and developing strategies
to mitigate or respond to them.
Example: Conducting a risk assessment to identify and evaluate
cybersecurity risks for an e-commerce platform and developing a plan
to address vulnerabilities.

Critical Path Analysis: Analyzing a project's schedule to identify the


sequence of activities with the longest duration and no flexibility,
determining the project's overall timeline.

Example: Performing critical path analysis to identify the activities that


have the most significant impact on the project's completion date and
ensure they are effectively managed.

Decision Modeling: Developing mathematical or logical models to


represent decision-making processes, enabling quantitative analysis
and optimization.

Example: Building a decision model to determine the optimal allocation


of marketing budget across different channels based on expected
returns and target audience reach.

Root Cause Analysis: Methodology to identify the underlying causes of


a problem or issue, aiming to address the fundamental source rather
than treating symptoms.

Example: Conducting a root cause analysis to determine why a software


application consistently crashes on a particular operating system and
devising a solution to fix the core issue.
Brainstorming: Facilitating a creative session with stakeholders to
generate a large number of ideas, solutions, or alternatives without
criticism or judgment.

Example: Organizing a brainstorming session with the development


team to explore innovative features for a new mobile application.

Affinity Diagrams: Grouping and categorizing ideas, requirements, or


issues by their natural relationships to identify patterns, common
themes, and potential solutions.

Example: Using an affinity diagram to categorize and organize user


feedback from customer interviews to identify common pain points and
prioritize improvements.

Conceptual Data Modeling: Creating a high-level representation of


data entities, their attributes, and relationships to understand the
structure and requirements of a database.

Example: Developing a conceptual data model to define the entities


(e.g., customers, orders, products) and their relationships in an e-
commerce system.

Logical Data Modeling: Building a detailed representation of the data


entities, attributes, and relationships based on business requirements
to guide database design.

Example: Creating a logical data model to define the tables, columns,


primary keys, and foreign keys for a customer relationship management
(CRM) database.
Interface Analysis: Examining the interfaces between different systems,
modules, or components to ensure compatibility, data flow, and
functional integration.

Example: Conducting an interface analysis to determine the data


exchange requirements between an e-commerce website and a
payment gateway system.

Use Case Point Analysis: A technique for estimating the size and
complexity of a software system based on the number and complexity
of its use cases.

Example: Performing a use case point analysis to estimate the effort


and resources required to develop an online banking application.

Data Mining: Extracting and analyzing large volumes of data to discover


patterns, relationships, and insights that can drive business decision-
making.

Example: Applying data mining techniques to customer transaction


data to identify cross-selling or upselling opportunities for a retail
business.

Functional Decomposition: Breaking down a complex system or


process into smaller, more manageable components or functions to
understand and analyze them individually.

Example: Decomposing an inventory management system into


functional components such as stock control, order processing, and
supplier management for detailed analysis.
Business Model Canvas: A visual framework that captures key elements
of a business model, including customer segments, value propositions,
revenue streams, and key activities.

Example: Using the Business Model Canvas to map out a new startup's
business model, identifying key partners, cost structure, and customer
acquisition channels.

Mindset Analysis: Assessing stakeholders' mindset, attitudes, and


perspectives to understand their resistance to change, acceptance of
new ideas, or readiness for innovation.

Example: Analyzing the mindset of employees before implementing a


new organizational structure to anticipate potential challenges and plan
change management strategies.

Customer Journey Mapping: Visual representation of the customer's


end-to-end experience, capturing touchpoints, emotions, and pain
points across different interactions.

Example: Creating a customer journey map to understand and improve


the experience of booking a flight, from initial research to post-flight
feedback.

User Acceptance Testing (UAT): Involving end-users in the testing


phase to validate whether a system or solution meets their
requirements and expectations.

Example: Organizing user acceptance testing sessions for a new e-


commerce website to ensure that it functions correctly, meets user
needs, and provides a positive user experience.

User Interface (UI) Design: Designing the visual and interactive


elements of a user interface, focusing on usability, accessibility, and
intuitive interaction.

Example: Collaborating with UX designers and developers to create


wireframes and mockups that showcase the layout, colors, typography,
and navigation of a mobile app.

Usability Testing: Evaluating the ease of use and user-friendliness of a


system or interface by observing users' interactions and collecting their
feedback.

Example: Conducting usability testing sessions with target users to


identify pain points, navigation issues, and areas for improvement in a
web application.

Non-Functional Requirements Analysis: Capturing and analyzing


requirements that focus on system attributes such as performance,
security, reliability, scalability, or maintainability.

Example: Gathering non-functional requirements for a cloud-based


storage solution, including data encryption, data redundancy, and 24/7
availability.

Storyboarding: Creating a visual sequence of screens or steps to


illustrate user interactions, system workflows, or user journeys.
Example: Developing storyboards to depict the user flow for a mobile
game, showcasing the main menu, gameplay screens, and end-of-level
achievements.

Quality Assurance (QA) Techniques: Methods and processes used to


ensure that a product or solution meets specified quality standards and
requirements.

Example: Performing functional and regression testing on a software


application to validate that it meets the intended requirements and
doesn't introduce new defects.

Agile Methodologies: Iterative and incremental approaches to project


management, such as Scrum or Kanban, that promote adaptive
planning, continuous improvement, and close collaboration.

Example: Applying Scrum methodology to manage the development of


a software product, organizing work into sprints, conducting daily
stand-up meetings, and prioritizing backlog items.

Change Management Techniques: Strategies and methods used to


facilitate smooth transitions and minimize resistance when
implementing changes within an organization.

Example: Applying change management techniques, such as


communication plans, training sessions, and stakeholder engagement,
when introducing a new enterprise resource planning (ERP) system.
Balanced Scorecard: A performance measurement framework that
considers financial, customer, internal process, and learning/growth
perspectives to assess organizational performance.

Example: Developing a balanced scorecard to track and measure key


performance indicators (KPIs) related to customer satisfaction,
employee training, process efficiency, and financial outcomes.

Vendor Evaluation and Selection: Assessing and comparing potential


vendors or suppliers based on criteria such as cost, quality, reputation,
service level agreements, and fit with organizational requirements.

Example: Evaluating different software vendors based on their product


features, pricing models, support capabilities, and compatibility with
existing systems.

Task Analysis: Breaking down complex tasks or processes into smaller,


detailed steps to understand the requirements, dependencies, and
potential areas for improvement.

Example: Performing a task analysis to document the steps involved in


a customer support ticket resolution process, including actions taken by
support agents and automated system interactions.

Regression Analysis: Analyzing the relationships between variables to


understand how changes in one variable impact another and make
predictions or forecasts.
Example: Using regression analysis to determine the correlation
between marketing spend and sales revenue, helping to optimize
marketing budget allocation.

Impact-Effort Matrix: A tool used to prioritize tasks, features, or


projects based on their potential impact and the effort required to
implement them.

Example: Creating an impact-effort matrix to prioritize system


enhancements based on their potential value to the business and the
estimated development effort.

Pareto Analysis: A technique that identifies the most significant factors


or issues contributing to a problem by ranking them in descending
order of importance.

Example: Conducting a Pareto analysis to identify the top customer


complaints or product defects that account for the majority of
customer dissatisfaction.

Data Validation and Verification: Processes for ensuring the accuracy,


completeness, and consistency of data through checks, tests, and
reconciliation.

Example: Implementing data validation rules and running data


verification scripts to ensure that customer records in a database are
complete, accurate, and free from errors.
Business Case Development: Building a comprehensive document that
justifies the need for a project, assesses its feasibility, and outlines the
expected costs, benefits, and risks.

Example: Developing a business case to secure funding for an


expansion project, outlining the anticipated market demand, financial
projections, and return on investment.

Ethnographic Research: Studying and analyzing the cultural, social, and


behavioral aspects of a specific group or community to gain insights and
inform business decisions.

Example: Conducting ethnographic research to understand the


preferences, behaviors, and needs of a target customer segment for a
new line of sustainable fashion products.

Cost Estimation Techniques: Methods and models used to estimate


project costs, including bottom-up estimation, analogous estimation,
and parametric estimation.

Example: Applying a bottom-up estimation technique to estimate the


costs of developing specific features or modules of a software
application based on detailed requirements.

Decision Analysis: A systematic approach for evaluating and comparing


different alternatives or scenarios, considering probabilities, risks, and
trade-offs.
Example: Using decision analysis techniques, such as decision trees or
decision matrices, to evaluate and select the most suitable software
vendor for an organization.

Continuous Improvement (Kaizen): A philosophy and methodology


that emphasizes small, incremental changes and ongoing
improvements to processes, products, and services.

Example: Implementing a Kaizen approach to regularly review and


optimize the order fulfillment process by identifying and addressing
bottlenecks, reducing waste, and improving efficiency.

Lean Six Sigma: A combination of Lean principles and Six Sigma


methodology that aims to eliminate waste, reduce variation, and
improve process performance and quality.

Example: Applying Lean Six Sigma techniques to streamline the product


development lifecycle by reducing cycle time, eliminating non-value-
added activities, and improving defect rates.

Resource Allocation and Optimization: Allocating and managing


resources (human, financial, and technological) in an optimal way to
maximize efficiency and productivity.

Example: Using resource allocation techniques, such as resource


leveling or resource smoothing, to optimize the utilization of
development teams across multiple projects.
Business Process Reengineering (BPR): Redesigning and rethinking
existing processes to achieve significant improvements in performance,
efficiency, and customer satisfaction.

Example: Applying business process reengineering principles to


streamline the invoicing process by automating manual tasks, reducing
errors, and improving cash flow.

Feasibility Analysis: Assessing the practicality, viability, and suitability


of a proposed project or initiative in terms of technical, economic,
operational, and organizational factors.

Example: Performing a feasibility analysis to evaluate the potential


return on investment (ROI) and risks associated with developing and
launching a new software product.

Vendor Management: Establishing and maintaining relationships with


external vendors or suppliers, including contract negotiation,
performance monitoring, and issue resolution.

Example: Managing relationships with IT service providers by regularly


reviewing service level agreements, monitoring performance metrics,
and conducting vendor audits.

Logical Framework Analysis (LFA): A structured planning and


management tool that defines project goals, objectives, activities, and
indicators to ensure alignment and track progress.
Example: Using the logical framework analysis to develop a project plan
for a community development initiative, defining measurable
indicators, activities, and expected outcomes.

Capacity Planning: Estimating and managing the resources (such as


infrastructure, staff, or equipment) required to meet current and future
demands effectively.

Example: Performing capacity planning to determine the optimal


number of customer service representatives needed to handle peak call
volumes without excessive wait times.

Dependency Analysis: Identifying and analyzing the relationships,


dependencies, and interconnections between different tasks, activities,
or components in a project.

Example: Conducting a dependency analysis to understand the impact


of delaying a specific task on the overall project timeline and identifying
critical dependencies.

Data Migration Techniques: Strategies and methods used to transfer


data from one system or environment to another while ensuring data
integrity and consistency.

Example: Planning and executing a data migration process when


transitioning from an old customer database to a new CRM system,
including data mapping, transformation, and validation.
Cost-Volume-Profit Analysis (CVP): Analyzing the relationships
between costs, volume or quantity, and profit to determine the
breakeven point and assess the financial impact of different scenarios.

Example: Performing a cost-volume-profit analysis to evaluate the


profitability of introducing a new product line, considering variable
costs, fixed costs, and expected sales volumes.

Decision Matrix Analysis: A technique that uses a matrix structure to


evaluate and compare different options or alternatives based on
multiple criteria or factors.

Example: Using a decision matrix analysis to select the most suitable


software development methodology for a project, considering factors
like team size, project complexity, and client preferences.

Dependency Structure Matrix (DSM): A visual representation of


dependencies between components or activities, highlighting the
interrelationships and facilitating analysis and optimization.

Example: Creating a dependency structure matrix to analyze the


relationships between software modules, identifying potential
bottlenecks or areas of high coupling.

Business Process Modeling (BPM): Creating visual representations


(such as flowcharts or diagrams) of business processes to document,
analyze, and improve their efficiency and effectiveness.

Example: Developing a business process model to document the steps


involved in the employee onboarding process, including tasks, decision
points, and system interactions.
Force Field Analysis: A technique that assesses the driving forces and
restraining forces impacting a proposed change or decision, helping to
identify barriers and plan mitigation strategies.

Example: Applying force field analysis to assess the potential adoption


of a new project management software, considering factors like cost,
training requirements, and resistance to change.

Heatmap Analysis: A visual representation of data using colors to


highlight patterns, trends, or areas of focus, often used for risk analysis,
performance assessment, or resource allocation.

Example: Creating a heatmap to analyze website traffic data and


identify the most visited pages or sections, informing content
optimization and user experience improvements.

Procurement Analysis: Evaluating and optimizing the procurement


process, including vendor selection, contract negotiation, purchasing
efficiency, and supplier performance management.

Example: Conducting a procurement analysis to identify opportunities


for cost savings, vendor consolidation, and improved contract terms
and conditions.

Root Cause Corrective Action (RCCA): Identifying the root causes of a


problem or issue and implementing corrective actions to prevent
recurrence.
Example: Applying root cause corrective action techniques to address
recurring customer complaints by identifying the underlying issues,
implementing process improvements, and providing employee training.

Business Intelligence (BI) Tools: Software applications or platforms that


collect, analyze, and present data in a visual and interactive manner to
facilitate decision-making.

Example: Using a business intelligence tool to create dashboards and


reports that provide real-time sales data, customer analytics, and
inventory levels for retail store managers.

Capability Maturity Model Integration (CMMI): A framework that


assesses and improves an organization's capability to develop and
maintain quality software and systems.

Example: Adopting the Capability Maturity Model Integration to assess


and improve the software development processes and practices within
an organization.

Customer Relationship Management (CRM) Systems: Software


solutions that help manage and analyze customer interactions, sales
pipeline, marketing campaigns, and customer service processes.
Example: Implementing a CRM system to centralize customer data,
track customer interactions, and improve sales and customer service
processes.

Supply Chain Management (SCM) Systems: Software applications that


optimize and manage the flow of goods, services, and information
across the supply chain, from procurement to delivery.
Example: Implementing a supply chain management system to
automate inventory management, streamline order processing, and
improve supplier collaboration.

Enterprise Resource Planning (ERP) Systems: Integrated software


platforms that manage core business processes, including finance,
human resources, inventory, and production.

Example: Deploying an ERP system to consolidate financial data,


streamline procurement and inventory management, and standardize
business processes across multiple locations.

Customer Segmentation and Profiling: Dividing a customer base into


distinct groups based on characteristics, behavior, or demographics to
tailor marketing strategies and improve customer experience.

Example: Conducting customer segmentation and profiling to identify


target segments for a new fitness app, considering factors like age,
fitness goals, and preferred exercise activities.

Process Automation: Using technology to automate repetitive tasks,


workflows, or processes, reducing manual effort, improving accuracy,
and increasing efficiency.

Example: Implementing robotic process automation (RPA) to automate


data entry and validation tasks, reducing errors and freeing up
employees' time for more value-added activities.
Decision Support Systems (DSS): Interactive computer-based tools or
applications that provide information, analysis, and modeling
capabilities to support decision-making.

Example: Using a decision support system to analyze sales data, market


trends, and customer preferences when determining pricing strategies
for a product line.

Social Media Analytics: Analyzing social media data and metrics to gain
insights into customer sentiment, brand perception, market trends, and
campaign effectiveness.

Example: Using social media analytics tools to monitor and analyze


customer conversations, mentions, and sentiment related to a brand,
helping to inform marketing strategies and reputation management.

Mind Mapping: A visual technique that captures and organizes ideas,


concepts, or information in a hierarchical and interconnected manner,
aiding brainstorming, problem-solving, and knowledge representation.

Example: Creating a mind map to explore different product features


and their potential implications, facilitating idea generation and
organizing thoughts for further analysis.

Rapid Prototyping: Quickly creating a tangible or interactive model or


mockup of a product, system, or interface to gather feedback, validate
concepts, and accelerate the development process.
Example: Developing a rapid prototype of a mobile app's user interface
to solicit user feedback, refine design elements, and validate usability
before proceeding to full-scale development.

SWOT Analysis: Used to assess the strengths, weaknesses,


opportunities, and threats of a project or organization. It helps identify
areas for improvement or potential risks.

Example: A Business Analyst performs a SWOT analysis to evaluate a


company's new product launch strategy, considering internal strengths
and weaknesses, as well as external opportunities and threats.

PESTLE Analysis: Evaluates the political, economic, social, technological,


legal, and environmental factors that may impact a project or business.
It provides insights into the external environment.

Example: Conducting a PESTLE analysis to understand the impact of


regulatory changes on a business's expansion plans.

You might also like