Three situations, three ways to begin
These teaching examples are fictional, including their possible results. Use them to frame your own question; they are not client case studies or offers of specialist services.
Fictional example · access to a service
The steps to get help are hard to complete
You may be trying to use a service, or helping people reach it. In this example, a community program offers help with activity fees, but its instructions do not say which proof is needed or who answers questions. People return without being able to apply.
A useful result: a person can identify the next step, the information it needs and where to resolve an unanswered question. The provider can see which instruction needs correction.
How to check: with permission, walk through a fictional application using the revised instructions. Ask the person to locate the relevant requirement and explain what they would do next. Record remaining uncertainty; this checks the instructions, not eligibility or whether assistance was received.
Take away: use the document worksheet to record the task, official source, steps, unanswered questions and who keeps the instructions current. A visitor seeking help can take those questions to the program; its responsible staff must confirm actual requirements and eligibility.
Continue independently: keep the record, check unresolved requirements with the responsible source, and retest changed instructions with a willing user. See what help we can discuss.
Fictional example · recurring community activity
One person keeps chasing everyone
A neighborhood group meets regularly, but one organizer confirms attendance, arranges access and follows up on every change. Participants want to join without uncertainty; the organizer wants someone else to be able to carry the arrangements forward.
A useful result: participants know what they have agreed to do, how to report a change and who handles an unresolved task. Another willing organizer can take over the next meeting.
How to check: agree roles for one meeting, including cancellations and a fallback. Afterwards, ask participants what became easier or harder and record missed handoffs and extra coordination effort. One smoother meeting would not establish a lasting improvement.
Take away: adapt the handover worksheet for commitments, the information each person needs, the next owner and the review date. Participation and reminders need agreement; do not put private circumstances in a shared schedule.
Continue independently: ask the next organizer to explain the arrangement and handle a fictional cancellation. Keep, revise or stop it together. Discuss implementation or an unresolved question if useful.
Fictional example · a maker and the people using a product
The available solution does not fit its users
A maker’s reusable storage case is hard to open in the setting where people use it. A person using the case can describe the difficulty; the maker needs to understand the setting before assuming a new latch is the answer.
A useful result: a clear account of the task, access needs and performance requirements, followed by an appropriately reviewed option that can be tested in that setting.
How to check: with willing users, observe a safe, nonfunctional mock-up and ask what remains difficult. Compare the proposed change with existing options and record who would maintain it. A mock-up cannot establish strength, safety or suitability for other users; qualified design and testing may be needed.
Take away: use the offer worksheet to describe the person’s need, intended result, responsibilities and support burden. This is a starting record, not a product specification or safety assessment.
Continue independently: take the requirements and open questions to the responsible maker or suitable specialist. Decide which evidence is needed before making or buying a change. See the boundaries of help here.
Choose what would help next
Work independently. Use or adapt the worksheets without an account or inquiry. Organize your next step in SIA’s English planner. It organizes your notes; it does not verify requirements, decide eligibility or carry out the work.
Discuss implementation. Mina is being established in Osaka and has no Japanese client work to report yet. We can discuss whether a workflow, document or tool-related piece of work fits our current capacity. You can bring a short description of the desired result and where it gets stuck, without confidential records.
Discuss a question that needs investigation. If the cause or a suitable response is unclear, tell us the question and what evidence would help. We would first establish whether the expertise, authority and capacity are available; this is not a promise of specialist research or service delivery.
Any work needs agreement on scope, responsibilities, cost and how its result will be checked. You can use the material and leave without making an inquiry.
Contact MinaExamine a handover
Use this when work waits for information, clarification, or approval between people. Begin with a few recent instances that the people involved can describe accurately.
- Record what happened.
Choose three recent handovers of the same kind. Record when the work was ready, when it was passed on, when the information was complete, when review actually started, and when it was completed. Include returns for clarification.
- Ask both people.
Ask the sender what they believed was complete. Ask the recipient what they needed to proceed. Record the missing information or decision in their own terms. Check whether the same issue occurred in each instance.
- Locate responsibility.
Identify who supplies the information, who makes the decision, and who can approve a change. Account for privacy, safety, contractual, and operational requirements.
- Choose the next step.
If the records do not yet support a change, agree a bounded observation first: what to record, who will record it, how many instances, when to review, and when to stop. Otherwise, agree one small reversible change, such as adding a required reference to a handover note. Record the expected effect, trial period, who will maintain it, and the conditions for stopping. Participants can question the explanation, correct the records, or decline extra recording or a trial. If permission or support for the next step is missing, pause and record what needs resolving.
- Carry out the agreed next step.
For an observation, record the agreed events without changing the workflow. If a change has been agreed, try it on a small agreed set of handovers. Record waiting, clarification requests, completion, and the extra effort required from each person. Keep sensitive content in its authorized location.
- Decide from the observations.
Review the observation or trial with both people. Compare similar work and account for changes in volume or difficulty. Decide whether more observation is needed or whether to choose a trial. For a trial, keep, revise, or remove the change. Record the reason and who owns the next step.
Worked example · fictional
Fictional example: a team passes purchase requests to an approver. Three requests waited for clarification because a project reference was missing. The team agrees to include that reference in five subsequent requests.
The reference is present in all five. One request still waits because the approver is unavailable. The team keeps the reference field and separately examines approval coverage. These observations identify two issues; they do not establish a general reduction in processing time.
Reasoning
All three requests lacked a reference the recipient needed. The trial checks whether supplying it reduces clarification. Approver availability remains a separate possible cause of delay. Record clarification time and total processing time.
Check the result
Check whether the intended recipient could act, whether work was actually completed, and whether effort moved to another person. Pause if the change creates errors, exposes information, or exceeds the agreed scope. A short trial may require repetition before it supports a lasting decision.
Try the reasoning on another instance
Ask a colleague to apply the worksheet to another safe instance and explain their decision. Record what they found unclear and when they would ask for help.
Worksheet fields
- Work and trigger
- Recent instances and dates
- Sender and recipient
- Ready / sent / received / actionable / review starts / completed times
- Missing information or decision
- Decision owner and permission
- Next observation or agreed change and expected effect
- Observation or trial size, review date, and stop conditions
- Observed result and additional effort
- Decision, owner, and next review
- Explanation being tested
- Other possible explanation
- Observation that would change the decision
- What another person needed to use this method
Download worksheet (plain text)Test a working document
Use this for a procedure, shared reference, or recurring report. Test it against a real task with someone who would normally use it.
- Choose a task.
State what the reader needs to do or decide. Select a recent or safely simulated instance. Identify the source material and any information that must remain restricted.
- Find the required information.
List what the reader needs at each step. Mark which facts change, where authoritative values come from, and who can answer unresolved questions.
- Prepare a usable version.
Put the task, inputs, steps, decision points, and expected output in order. Identify the owner, version date, and update trigger. Link to authoritative information when copying it would create inconsistent versions.
- Observe someone using it.
Ask a colleague to carry out the task using the document. Record where they search, pause, ask for clarification, or choose the wrong action. Obtain consent for observation and any recording.
- Revise the specific problem.
Change the wording, ordering, or reference that caused difficulty. Repeat the affected part of the task. Check whether the revision creates a new ambiguity elsewhere.
- Assign upkeep.
Agree where the document lives, who maintains it, and what prompts a review. Make the current version easy to identify. Recheck it when the work, system, or decision authority changes.
Worked example · fictional
Fictional example: a stock-count sheet asks for “quantity” without identifying the unit. One person enters individual items and another enters boxes.
The revised sheet names the unit and includes one filled example. Two colleagues use it on a small count and compare their entries with the stock record. A later packaging change becomes a trigger to review the sheet.
Reasoning
A unit label addresses the ambiguity observed in the entries. The retest checks whether another person records the same stock consistently. If errors continue, check packaging conversions and the clarity of the example before adding further instructions.
Check the result
Check whether a reader can complete the task accurately, locate the current version, and recognize when they need help. Record unresolved cases. Keep safeguards and required approvals visible. One successful use provides evidence for that task and reader.
Try the reasoning on another instance
Ask a colleague to apply the worksheet to another safe instance and explain their decision. Record what they found unclear and when they would ask for help.
Worksheet fields
- Task and intended reader
- Required inputs and authoritative sources
- Access restrictions
- Steps and decision points
- Expected output
- Owner, date, location, and update trigger
- Observed pauses, questions, and errors
- Revision and retest result
- Remaining questions and next review
- Explanation being tested
- Other possible explanation
- Observation that would change the decision
- What another person needed to use this method
Download worksheet (plain text)
