Training workbook
Use this workbook to demonstrate that you can operate the application and reason about its evidence correctly. Complete exercises in a separate practice company. The prebuilt Northstar company is a reference answer, not a blank worksheet. All exercise data is fictional.
Workshop plan
| Module | Time | Practice |
|---|---|---|
| Orientation | 20 minutes | Explain the record types and four key distinctions |
| Scope and discovery | 40 minutes | Create engagement, roster and kickoff |
| Work and confirmation | 60 minutes | Write tasks, resolve disagreement, obtain current decisions |
| Relationships and cases | 35 minutes | Inspect org chart, define handoffs, complete and fail cases |
| Measurement and outcomes | 35 minutes | Test the explanation and preserve uncertainty |
| Client delivery | 30 minutes | Draft, review and inspect a package |
| Review and discussion | 20 minutes | Compare answers and identify improvement areas |
Allow breaks between modules. Pair participants so one plays advisor and the other plays a fictional participant in a separate browser profile. Rotate roles. A facilitator can shorten the workshop by inspecting the prebuilt example instead of recreating every record.
Exhibit A: fictional order procedure
Standard orders need an item, quantity and customer reference. Sam checks intake. Robin records the credit-check result. Jamie owns the completeness and exception process. Sam records a release only when the complete order packet and passing credit result are available. Jamie reviews exceptions. This exercise excludes payments, changing credit limits and automatic release.
Alex is the executive sponsor. Jamie and Robin report to Alex. Sam reports to Jamie. These relationships are supplied as training roster facts; do not infer additional reporting lines.
Exhibit B: invented practice observations
| Measure | Baseline cohort | Practice cohort |
|---|---|---|
| Standard orders observed | 20 | 20 |
| Median intake-to-release duration | 10 hours | 8 hours |
| Credit review duration | Under one hour | Under one hour |
| Product mix | Mostly established items | More small, simple orders |
| Staffing comparison | Not recorded | Not recorded |
| Intended target | At most 7 hours | At most 7 hours |
These are invented aggregate values, not an empirical dataset. They are sufficient to practice recording observations and limitations, but do not establish an effect or provide source-level statistical verification.
Exercise 1: bound the engagement
Create a company and engagement plan. Use the goal of understanding standard order delays without weakening credit controls. Record the exclusions in Exhibit A, four roster people, optional total headcount 24, source policy, audience and weekly cadence.
Write your answers before proceeding:
- What is the output unit?
- Who is accountable for the work and who sponsors the engagement?
- What belongs outside the scope?
- Does a roster of four establish coverage of all 24 employees?
- Which policy fields are descriptive in this version rather than technically enforced?
Submit: engagement record and screenshot or written summary of coverage.
Exercise 2: preserve an account
Create a kickoff request for Alex using five relevant questions. Issue and open the link in the participant profile. Submit the fictional account, inspect it as advisor, and accept it.
- What proves the source’s origin in the application?
- Does accepting the response confirm the tasks?
- Was an email sent?
- What must you do if the invitation is already used?
Submit: request, response and resulting source IDs. Do not include the invitation URL or password.
Exercise 3: resolve disagreement
Draft the intake task with Jamie as owner and Sam as performer, but deliberately say that Sam can change customer credit limits. Review and request confirmation. Have Sam choose Needs change and explain the error. Accept that response as advisor.
Revise the denied actions and instructions. Review the new task and issue current confirmation requests to Jamie and Sam. Inspect the history after accepting their responses.
- Why must the first disagreement remain visible?
- Which version do the new responses apply to?
- Can the previous correct response from Jamie confirm the revised text?
- Does the final Human confirmed state authorize an agent to act?
Submit: task version history, final state, and a two-sentence explanation of the authorization limit.
Exercise 4: make the graph useful
Create the remaining two tasks and supplied manager relationships. Open Connected and select Jamie. Open Org & duties, compare By team with Reporting chart, and inspect Sam’s responsibilities.
- Which view best answers “What evidence supports this task?”
- Which view best answers “Who reports to Jamie?”
- What should appear when no manager is recorded?
- What does a truncation notice mean?
Submit: a written explanation of two arrows and one reporting relationship. Use the record inspector to verify the relationship direction.
Exercise 5: observe a workflow
Create and review the duty, two handoffs and a workflow. Complete TRAIN-001 through all three steps. Create TRAIN-002 and record missing information at intake.
- Why must credit review remain blocked in TRAIN-002?
- Which route should be selected after a passing credit result?
- What happens when a ready step passes its deadline?
- Do the case controls call a real order system?
- What must you do if the pinned workflow is revised before the case continues?
Submit: one complete case and one case needing attention, each with useful observer notes.
Exercise 6: interpret an outcome
Create the hypothesis that incomplete intake causes waiting, with credit capacity as the alternative. Define the metric and intervention prediction before recording Exhibit B’s observation. Create an Inconclusive outcome review.
- What does the arithmetic difference between 10 and 8 show?
- Did the practice result meet the 7-hour target?
- What confounders prevent a strong causal conclusion?
- Which new observation would help separate the two mechanisms?
- Why should the original prediction remain unchanged?
Submit: hypothesis, metric, intervention and reviewed outcome, plus a proposed next test.
Exercise 7: deliver to the right audience
Create an executive report for Alex and Jamie. Select appropriate records and write a short summary, decision, next steps and limitations. Preview the draft and attempt to download before approval. Then review the exact audience and content and download it.
Inspect the ZIP. Locate the HTML report, JSON, CSV and checksums. Confirm that raw interview text and credentials are absent. In a separate practice report, change a selected record after drafting and observe the stale-binding rejection.
- Why does approval bind to exact content and audience?
- What needs to happen before a changed report can be delivered?
- Which package is appropriate for the sponsor, and which for an implementation reviewer?
- How will you record delivery when the application does not send it?
Submit: approved synthetic client packet and a manual delivery-log entry clearly labeled “training; not sent.”
Final assessment
Explain the engagement to a fictional sponsor in five minutes. Show the work, the evidence, the strongest remaining uncertainty, and the next decision. Finish by opening a reviewed client report and identifying its audience and coverage limits.
An advisor is ready for supervised use when they can operate the flow, recover from disagreement and stale data, and explain the limits without prompting. The assessment is a training aid; it is not professional accreditation or production security acceptance.