Page 239 - CyberSecurityEssentialsEnglish

Review Questions
1. What is the difference between a prompt and a workflow, and why does the distinction
matter in practice?

2. Distinguish among a task, a process, a workflow, and a standard operating procedure, with
an example of each.
3. Why do we map the as-is process before designing the to-be process?

4. What are the nine elements that a workflow definition card should contain?
5. How do you decide whether a step should be deterministic, generative, or a matter of
human judgment?

6. What does a structured output guarantee, and what does it not guarantee?
7. Give two workflow patterns and state when each is appropriate and when it is not.

8. What is the difference between a transcript, minutes, decisions, and action items?
9. Why should supporting documents be derived from a single approved source?
10. What are the quality gates for a bilingual document, and why is the visual check a
separate step?

11. What should be verified before analyzing any table?
12. What is the difference between cycle time, touch time, and first-pass yield?

13. Why does a net productivity gain require measuring the whole cycle?
14. What does process mining need in order to work, and what does it reveal?

Practical Exercises
↻ Exercise 1: Draw the process as it is
Goal: Describe the work as it is actually done before proposing any change to it.
Required: A request that recurs in your work at least weekly. Allow about 40 minutes.
Steps: Mark the event that starts the work. Draw each step in the order it really happens,

not the order the written procedure claims. Put a decision point wherever the path can
change. Name the person responsible above each step. Then mark where the work waits
and where it is usually sent back.
Output: A step diagram with the delay points and the error points marked.
Assessment criterion: The trigger, the owner of each step, and at least one exception
path are visible. A diagram with no exception path describes a wish rather than a process.

↻ Exercise 2: A workflow definition card

Goal: Record a process so that another person could run it without asking you.
Required: The process from Exercise 1. Allow about 35 minutes.
Steps: Fill in every field of the card: the trigger, the acceptable inputs, the owner, the
steps, the decision rules, the exception paths, the outputs and records kept, and the
indicators. Leave no field empty, and write not yet defined where that is the truth. Then
give the card to a colleague and ask them to describe the process back to you from it

alone.
Output: One completed workflow definition card.

238