New short just went up on what prompt engineering actually means once you take it out of the hype and into a real workplace context. It's not a special technical skill, it's just being clear and specific about what you want, the same way you'd brief a new staff member. Three things covered in the video: - Why "prompt engineering" sounds more complicated than it is - What actually separates a weak prompt from a strong one - How this applies directly to the kind of AI work we talk about in this community, drafting, admin, lesson prep and more Worth thinking about: if you've been putting off using AI tools because "prompt engineering" sounded technical, this might change your mind. Let us know your thoughts in the comments once you've watched it.

Quick one on something that trips a lot of people up: the quality of what you get out of an AI tool comes straight from the quality of what you put in. Vague question in, vague answer out. This matters more in RTO and training work than most people realise. If you ask an AI tool to "write a session plan" you'll get something generic. If you give it the unit code, the cohort, the delivery mode and the length of the session, you'll get something you can actually use. Watch it here: https://youtube.com/shorts/xTs_OyhH9Fo What's one thing you've learned about getting better output from AI tools?