From Asking to Structuring: Designing AI Interaction
Participants compare a direct request with a supplied five-phase collaboration process. They learn to shape context, make decisions and judge results through evidence.
Literacy perspective
How request structure, exchange design, examples, clarification, and feedback shape behaviour.
What lecturers should notice
Look at how the exchange is framed and revised: goals, context, constraints, examples, questions, feedback, and criteria.
Related units
The role may be primary, secondary, supporting, integrated, or part of the attack surface; consult each unit’s metadata for the exact relationship.
Participants compare a direct request with a supplied five-phase collaboration process. They learn to shape context, make decisions and judge results through evidence.
Participants clarify a task before execution and keep accepted decisions in files. They move from a virtual Markdown workspace to local Python analysis, then use verified results to prepare a report across fresh contexts.
Participants turn a single request into an inspectable process with consequential human decisions. Four cumulative exercises use the same equipment-loan case: introduce three process cuts, make the intermediate artefacts and checkpoints explicit, add reviewing perspectives and roles, then evaluate quality, control and effort. PDCA brings these elements together. A live demonstration shows how project folders, Markdown files and skills support continuity and reuse.
Participants organise critique, evidence and human decisions into workflows. In the Arena they first improve a judge, then keep the selected judge fixed while testing a generator change.
This final Friday makes security concrete as a control problem. Participants integrate learning from the preceding units to recognize where an AI-supported office task can lose control and to redesign the collaboration so that data, instructions, permissions, actions, and human responsibility remain appropriately separated.