Discovering Existing Business Processes: Key Tasks and Techniques

Correct Answers: A, C, D and.

F.

Usually, there are several project phases that Solution Architect is involved in.

These phases include Presales, Initiation, Analysis and design, Implementation, Delivery, and Operation.

The Presales phase contains discovery, RFP responses, introductory customer meetings, proof of concept or demos, a solution proposal.

During the discovery phase, a Solution Architect captures and documents the organization's business process.

Architect learns about the company, their current solutions, their vision for the new applications, needs, processes, and their customers or solution users.

Several tasks can help you: Job shadowing - helps to see the processes firsthand and better understand the user's needs and expectations.

Review existing automation - helps to analyze and dissect current automation processes and identify flaws, needs, and improvements.

Looking for pain points - helps to examine the processes and understand their origin and needs.

Learn about processes directly from the customer - organize workshops with the targeted group of people involved in the project.

Ask open-ended questions using “Why?” - Why do you need this new solution? Or Why do you think the Power Platform is the best choice for your solution? These types of open-ended questions should help you understand the company's needs and expectations.

All other options are incorrect because the “Identify solution components” and “Develop proof of concept” are tasks from a solution proposal stage but not for the discovery stage.

For more information about the discovery organization's business processes, please visit the below URLs:

As a Solution Architect, during the discovery phase, it is important to capture and document the organization's business process. This helps to understand the current state of the organization's operations, identify pain points and areas for improvement, and develop a plan for implementing the proposed solution. To collect information about existing business processes, the following four tasks can be helpful:

A. Job shadowing: Job shadowing is the process of observing an individual or team as they perform their day-to-day work. As a Solution Architect, you can shadow employees in various departments and observe their work processes. This will help you gain insight into how the organization operates and how work is completed, as well as identifying bottlenecks or areas that could be streamlined.

B. Develop proof of concept: Developing a proof of concept (POC) can help you understand how the proposed solution will fit into the existing business processes. A POC is a small-scale demonstration of the solution that provides insight into how it will work in practice. This can be particularly helpful in identifying areas where the solution may need to be modified or adjusted to fit the business process.

C. Review existing automation: Reviewing existing automation processes can help you identify areas where automation is already being used to complete tasks. This can provide insight into where automation can be expanded or improved, or where manual processes could be replaced with automation.

D. Looking for pain points: Identifying pain points is critical to understanding where the proposed solution can provide the most value. Pain points are areas where the business process is inefficient or ineffective, and can include things like manual data entry or long wait times between steps in a process. Identifying pain points will help you focus your efforts on areas where the proposed solution can have the greatest impact.

E. Identify solution components: Identifying the solution components that will be used in the proposed solution is important in understanding how the solution will fit into the existing business process. This can include software, hardware, and other components that will be used to implement the solution.

F. Learn about processes directly from the customer: Learning about the processes directly from the customer is important in understanding the business process from their perspective. This can include interviewing stakeholders and end-users, gathering feedback through surveys, and observing how users interact with the existing processes.

In conclusion, during the discovery phase, a Solution Architect can use a variety of methods to collect information about the organization's business process. These methods include job shadowing, developing proof of concept, reviewing existing automation, looking for pain points, identifying solution components, and learning about processes directly from the customer. By understanding the existing business process, the Solution Architect can develop a solution that will improve efficiency, reduce costs, and provide maximum value to the organization.