Course 3 - Module 4 - Lesson 2
Scenario cards for solo workers, teams, educators, and builders
Best Practices Without the Lecture Voice
The same helper needs different boundaries
A scenario card records the user, task, input, allowed action, reviewer, and stop condition. It helps you adapt a workflow to its setting. A solo worker and a large team may draft similar text but need different ownership, access, and handoff arrangements.
For a solo worker preparing a project proposal, the card can allow drafting from their own approved notes, with the worker checking prices and commitments before sending. The stop condition is missing scope or an unconfirmed amount. The draft remains private until review.
Consider teams and educators
For a team producing a weekly update, name one owner who approves the combined draft. Include links to approved project notes and require uncertain items to appear as questions. Stop if two sources disagree about whether a milestone is complete.
For an educator making a practice quiz, use public or invented material and check the answer key against the learning objective. Avoid uploading identifiable student work to an unapproved service. A fluent question can still be ambiguous, too advanced, or unrelated to the intended lesson.
Give builders an explicit test boundary
A builder testing a document-sorting helper can use fictional files in an isolated practice folder. The card allows reading and proposing categories, then asks for review before moving anything. A missing category or unexpected file type should stop the dependent action.
Compare these cards before copying a workflow into a new setting. Ask who bears the cost of an error and who has authority to approve. If those answers change, revise the card, permissions, and checks instead of assuming the original design transfers unchanged.
Tiny experiment
Write two scenario cards for a quiz helper: one for your private study and one for a teacher. Identify a different reviewer or data boundary for each.
Confidence check
Whose responsibility or privacy changes when a personal helper becomes something used by a group?