Practice worksheet / Fictional example
Content preview. The Word download contains the same 17 fields in an editable document, with a fictional-demo notice.
Practice Lab Studio / Try what I built
Turn a how-to guide into a training worksheet. Give learners a goal, something to practise, and a way to check their work. Then hand the trainer an editable Word document—not another chat transcript.
A public adaptation of a real solution I built at Microsoft. Fictional examples, real editing and downloads. No sign-in needed.
Your turn
You’re the training author, not the learner. Pick a fictional guide, see it as a practice worksheet, and change a step to make it your own. Your takeaway is an editable Word document.
No live AI is running here. Creating a worksheet loads a prepared example for that guide, not a new AI response. Editing, review, and Word / JSON downloads really work. Nothing you type is uploaded or saved in the browser.
This is where the blank page ends
Create an example to see the guide reshaped into a readable worksheet. You’ll review the learning goals, practice steps, and completion checks before downloading it.
Change a field, then choose Apply field. Turn off Edit worksheet to see your changes in the preview. Edits are manual, not AI-generated, and require a new review.
Practice worksheet / Fictional example
Content preview. The Word download contains the same 17 fields in an editable document, with a fictional-demo notice.
3 / You have the final word
Compare the worksheet with the original guide. Check your changes and anything marked TBD, then confirm your review.
Approval is required before exporting. Any content change requires a new review.
Word: the editable training worksheet. JSON: the same 17 fields for a technical handoff.
The decisions behind the demo
The workflow stops when the source is unavailable. Missing facts stay TBD. Open “What if the guide is missing?” to try the failure path yourself.
Editing one field preserves the others. A preview shows applied changes, not unfinished typing, and every change clears the previous approval.
A draft is not a finished lesson. Downloads stay locked until a person reviews the current version. Pending edits cannot slip into an approved handoff.
The same 17 fields carry through to the Word document and JSON file. No extra generation happens during export, and this public demo works offline.
The case study covers the real authoring problem, what I built, the tradeoffs, and how I would measure success.