Unit 2 Study Guide

Unit 2: Analyzing and Designing Automation Workflows
2a. Analyze work processes to identify repetitive, error-prone, and high-impact automation opportunities.
Which parts of a work process happen again and again, and which parts are different each time?
Where do mistakes, delays, or extra effort appear in the process?
Which task would save the most time or reduce the most errors if you automated it first?
To find good automation opportunities, start by looking for work that repeats often, takes a lot of time, or causes errors. The unit materials ask you to spot three main signs: repetition, error-proneness, and high impact. A task is repetitive when you do it many times in the same way. It is error-prone when people often make mistakes while doing it. It is high impact when improving it would help the work process in a big way. Can you see why a task can be easy to automate but still not be the best one to start with? The best first choice is often the task that combines repetition, clear rules, and important results.
You should also look at the full work process, not just one step. A small task may not matter much by itself, but it may sit inside a larger flow that slows down many other tasks. In that case, automation can have a bigger effect. Students often focus only on the most annoying task, but the better choice is the one that gives the best mix of time saved, fewer errors, and business value. For example, if one step is repeated many times and also causes many mistakes, that step is a strong automation candidate.
To review, see:
[2.1 Spotting Repetitive Tasks in Your Work]
2b. Create process maps that document current and future workflow states.
How do you show the current workflow from start to finish?
What should change in the future workflow after automation?
Which steps, handoffs, or decision points must you include so the map is useful?
How would you decide whether the future map is better than the current one?
A process map is a visual description of a workflow that shows the steps in order, so you can see how work moves from start to finish. A current-state map shows how the process works now. A future-state map shows how you want the process to work after improvement or automation. The point is not only to draw boxes and arrows. The point is to make the work clear enough that you can compare the current and future states and decide what should change.
When you build the map, include the main steps, the order of the steps, and the points where a person must decide what happens next. If a step moves work to another person or system, show that handoff too. This helps you answer whether the current process has extra steps, delays, or repeated work. The future-state map should remove or improve those weak points. For example, if the current workflow requires a person to copy the same information into two places, the future workflow should show only one entry point if the materials support that change. The common mistake is to map too much detail or to leave out important decision points, which makes the map less useful for automation planning.
To review, see:
[2.2 Creating Visual Process Maps]
2c. Define triggers, actions, conditions, and data requirements for an automation.
What event should start the automation?
What action should the automation take after it starts?
When should the automation run, and when should it stop or wait?
What information must be available for the automation to work correctly?
A trigger is the event that starts an automation. An action is the task the automation performs after the trigger happens. A condition is a rule that controls whether the automation should continue, wait, or stop. Data requirements are the pieces of information the automation must receive or use to complete the task correctly. These four parts work together, so you need to define each one clearly before building the workflow.
A simple way to apply this is to think through one workflow from beginning to end. First, identify the trigger, such as a new event in a process. Next, define the action the automation should take. Then ask what conditions change the result. Finally, list the data the automation must have, because missing data can break the workflow or lead to the wrong result. Students often confuse a trigger with a condition, but they are not the same: the trigger starts the automation, while the condition tests whether a step should happen. If the materials give you a workflow with a clear start point, a decision point, and a needed input, you should be able to label all four parts.
To review, see:
[2.3 Defining Triggers, Actions, and Conditions]
2d. Prioritize automation ideas using impact, effort, and feasibility criteria.
Which automation idea gives the biggest result for the least work?
How do you compare ideas that look useful but require different levels of effort?
Which idea should you do first if one is high impact but another is easier to build?
What evidence would make you choose one idea over another?
To prioritize means to rank automation ideas so you can choose the best one to work on first. The unit materials use three main criteria: impact, effort, and feasibility. Impact is the size of the benefit the automation would create. Effort is the amount of work needed to build it. Feasibility is how realistic the idea is with the tools, time, and information you have. You are not choosing the most interesting idea; you are choosing the one that is most worth doing now.
A strong automation idea has high impact, low effort, and high feasibility. A weak one may have high impact but be too hard to build soon, or it may be easy to build but not help much. A common mistake is to choose based on excitement alone. Instead, compare ideas side by side and ask which one gives the best return for the time and resources required. For example, if two ideas both reduce errors, but one needs much less setup and uses the tools you already have, that one is often the better first choice. This is why you should connect the priority decision back to the process analysis in 2a: the best ideas usually come from the work that is both repetitive and important.
To review, see:
[2.4 Prioritizing Automation Ideas]
Unit 2 Vocabulary
This vocabulary list includes terms you will need to know to successfully complete the final exam.
action
condition
data requirements
effort
feasibility
impact
prioritize
trigger