A simple project-brief structure can make workplace AI outputs clearer, safer and easier to review. You open an AI tool between meetings and type something like, “Summarise this,” “Write a project plan,” or “Help me improve this process.” The answer arrives quickly. It sounds polished. It may even be useful. But it is also a bit too broad, a bit too confident, and not quite grounded in the messy reality of your workplace. That is where many people get stuck. They treat AI like a search box or a very enthusiastic assistant, then feel disappointed when the output is generic. The better approach is simpler: use AI like you would brief a project team member. A good project brief explains the goal, context, constraints, source material and expected output. The same habit works well with AI. You do not need technical language. You need a clear working brief. Why This Matters AI is already moving into everyday knowledge work: meeting notes, project updates, service improvement...
Raf Sanga’s notes on project management, technology-enabled change, Lean Six Sigma, process improvement, analytics, and building practical systems that help teams deliver measurable results.