Your working notes

Use these ten tools with your learning, engineering, and community colleagues. Choose a decision, write a concrete answer, and return to the chapter when you need an example.

• Save notes stores that tool’s text in this browser on this device. Your note text is not sent to Kabakoo or Google Analytics. Other people using the same browser can read saved notes.
• Copy notes lets you paste the tool into a shared document. Clearing browser data removes saved work.

Use project decisions and anonymized observations; keep participant records in your organization’s own system.

1. Frame the problem · 2. Trace the change · 3. Decide what the pilot needs · 4. Design one learning sequence · 5. Rehearse the failure paths · 6. Review a mentor response · 7. Investigate a first action

8. Plan a route back · 9. Design useful peer help · 10. Plan an experiment

1. Frame the problem

Read the chapter

What work is the person already doing? What specific obstacle did you observe? Who supplies information, whom does the person trust, and what already helps? What useful action could the application support, and what must the person control? What evidence would change this brief?

Not saved yet.

2. Trace the change

Read the chapter

What does the program offer? What will the learner do with it? Who else contributes, and how can the learner choose that connection? Which livelihood outcome could follow? Which response behavior tests the mechanism, and what alternative explanation will you examine? What evidence belongs at Model, Product, User, and Impact levels?

Not saved yet.

3. Decide what the pilot needs

Read the chapter

Who will participate, including people who never began, stopped, or use a borrowed device? What realistic task will they attempt? What happened, what did the person say, and how was the logged event recorded? What blocks the pilot or needs investigation? What will change, who owns it, and how will you check it?

Not saved yet.

4. Design one learning sequence

Read the chapter

What will the learner produce, with which instructions and accepted formats? How will the system acknowledge receipt? What feedback and next action follow validation or a request to revise? What will a peer contribute? How can the learner find the task again, revise it, or ask for help? Which task, submission, and feedback versions remain linked?

Not saved yet.

5. Rehearse the failure paths

Read the chapter

What carries the message from the phone to the system and back? Where do task state, media, and delivery status live? What happens after a duplicate, timeout, late response, or incorrect conversation route? How does the worker check conversation scope, ownership, opt-out, and messaging eligibility? What did the phone, database, and operator each show in the rehearsal?

Not saved yet.

6. Review a mentor response

Read the chapter

What task and submission does the response address? Which prompt, model, retrieval collection, and product versions were tested? Which criteria and cases did reviewers test, and what remains uncovered? What failed in meaning, format, speech, or human connection, and where did reviewers disagree? What correction or human escalation is needed? What did the learner do next, including if they stopped?

Not saved yet.

7. Investigate a first action

Read the chapter

Which population and dates are included, including people who did not finish the baseline? What exactly counts as the first response or useful action? What is unknown about delivery, baseline access, or the reasons people stopped? Where did people stop, and what did follow-up reveal? What explanation and alternative will the next change test? How will you retain assignment, exposure, and later-action records?

Not saved yet.

8. Plan a route back

Read the chapter

What interrupted participation, and how do you know? What task, submission, feedback, and contact state must be preserved? What next step addresses the obstacle, and who owns it? How can the learner pause, return, or decline contact? What will show that the learner could continue from their work?

Not saved yet.

9. Design useful peer help

Read the chapter

What concrete contribution will one peer make to another? Which compatibility criteria matter, and who might the matcher exclude? How will each person accept or decline the connection? Who handles unanswered requests and obstacles to the shared task? How will you distinguish a first reply, reciprocal exchange, and useful help?

Not saved yet.

10. Plan an experiment

Read the chapter

What decision, mechanism, and alternative explanation will you test? Who is eligible, what is the assignment unit, and how is assignment retained? What does each arm receive, and how will you verify delivery on a phone? What is the primary outcome, denominator, window, and missing-data rule? What effect matters, what sample is feasible, and what stopping rule is agreed? How will you report uncertainty, delivery failures, and changes during the run? What result would lead you to adopt, revise, stop, or test again?

Not saved yet.