Facilitator guide and answer key

Use this guide after learners attempt the workbook. Grade the quality of the reasoning as well as the state displayed in the application. A learner who obtains green badges by inventing agreement has not passed the exercise.

Preparation

Ask the operator to verify the app, database and current build. Run npm run training once if the reference Northstar company or example files are missing. Each run creates another clearly named company, so avoid repeated runs during the workshop.

Prepare separate advisor and participant browser profiles. Use fictional addresses unique to each group. Do not give learners a shared real-client account. Provide Exhibit A and Exhibit B from the workbook and set the expectation that they must not infer permissions, causation or coverage beyond the evidence.

Exercise 1 answers

The output is a released standard order; the time metric is one measurement of the flow. Jamie is accountable for the work, while Alex sponsors the engagement. Payments, credit-limit changes, production credentials and automatic release are excluded. Four roster participants do not establish representation of all 24 fictional employees.

Visibility, engagement retention and timezone planning fields record intended policy. They do not implement fine-grained evidence ACLs, legal hold, a different server-audio retention period or automated scheduling. Learners should identify this distinction without assuming that a saved policy text enforces itself.

Exercise 2 answers

The response retains the request, person, original content and submission identity; acceptance creates a source linked to that original. Acceptance does not confirm task cards. Issuing a link does not send email. A participant already enrolled should sign in; an unused expired or rotated link needs replacement by the advisor.

The local session and bearer invitation provide local account assurance only. Do not describe the flow as verified corporate identity or enterprise MFA. A good learner includes the limitation without dismissing the value of preserving exact local responses.

Exercise 3 answers

The original decision shows the real disagreement in the exercise and explains why the work changed. New confirmations apply to the revised version and hash. Jamie’s previous response does not automatically endorse new wording. Human confirmed establishes that the named people accepted the description; it does not grant permission to an agent or alter customer-system access.

Expected progression: proposed card, reviewed card, request returned, accepted objection creates conflict, revised card, review, current owner/performer requests, accepted correct responses, Human confirmed. The exact version count depends on how many edits the learner made; assess the linkage, not an arbitrary number.

Exercise 4 answers

Connected plus the inspector is appropriate for evidence relationships. Reporting chart is appropriate for manager relationships. Missing managers should remain unlinked with a clear explanation; team membership and senior titles do not justify invented lines. Truncation means the displayed graph is a bounded subset and must not be presented as the whole company.

Check arrow direction with the inspector: an owner is accountable for the task; a task is supported by evidence. A selected card can have incoming and outgoing relationships. The text labels should make the direction understandable without guessing from layout.

Exercise 5 answers

TRAIN-002 has no completed intake and therefore lacks the receiving input for credit review. After a passing credit result, select the handoff to release only if the documented condition is met. An expired ready step needs attention and cannot be completed through the normal action until a permitted retry resets the deadline. Retry limits prevent endless repeated attempts.

Case controls record human observations; no external order is changed. A changed pinned definition blocks progress. Review the revised work and workflow, then close/restart the obsolete case when appropriate. Do not use retries to bypass a stale-definition error.

The handoff record’s timeout/retry fields describe the contract; case enforcement uses workflow step settings. Learners should set them coherently and understand that this version does not execute handoff-specific background timers.

Exercise 6 answers

The invented median is two hours lower, a 20% arithmetic reduction relative to ten. It misses the at-most-seven target. That arithmetic is not evidence of a real client improvement. Different product mix, missing staffing information, small cohorts, and no source-level matched dataset limit interpretation.

A useful next test measures intake correction waiting and credit-review waiting in comparable order groups while recording staffing and error rates. A capacity explanation needs observations that distinguish it from missing-input rework. The original prediction remains unchanged so later reviewers can evaluate the intervention honestly.

Inconclusive is an acceptable and expected outcome. Do not reward a confident “supported” result based only on the attractive before/after number.

Exercise 7 answers

Approval binds to the frozen report, exact version/hash, selected records and named audience. A changed source requires a fresh packet and review. An executive or weekly report is the usual sponsor-facing document; an internal confirmed-work or agent packet is for implementation/review audiences. Download alone is not a delivery record.

A training distribution log should say no message was sent. For an accepted engagement, the advisor records recipient, packet/version, date, approved channel and any acknowledgement in the agreed system. The application does not revoke copies that have already left the installation.

Scoring rubric

Suggested pass threshold is 80/100, with no critical reasoning error. Critical errors include inventing participant agreement, treating a title or task as a permission grant, claiming a real measured improvement from the synthetic data, concealing a material source conflict, or distributing unreviewed sensitive content. Revisit the relevant module before retesting.

Debrief prompts

• Which missing fact changed your next action most?
• Which apparent process disagreement was really a difference in vocabulary?
• What did the graph help you see that the register did not?
• Where was the register clearer than the graph?
• What would make the outcome supported or falsified rather than inconclusive?
• Which integration would need separate acceptance before this engagement used real customer systems?

Record product defects separately from learner mistakes. Include a minimal synthetic reproduction and visible error code. Never paste credentials, private invitations, or real source material into public issues.