
Translating business value into a solution
Problem mindset against solution mindset
Telling a symptom from a problem
Value-driven analysis, and the Problem to Goal to Constraint to Metric framework
Stakeholder mapping and influence analysis
Elicitation techniques
Asking the business the right questions
Working with conflicting requirements, and prioritising by value against effort
Business, functional and non-functional requirements
User stories: structure, examples and anti-patterns
Acceptance criteria in Given-When-Then form
Use cases, BRD, SRS, PRD, and the definition of ready
What a business process means in practice
The AS-IS and TO-BE approach
The minimum necessary BPMN
Finding bottlenecks and waste, and proposing improvements rather than diagrams
The system context diagram
Functional decomposition
User flows, data objects and business rules
Non-functional requirements and traceability
Working in Agile, Scrum and waterfall
The backlog and requirements that keep moving
Change requests and impact analysis
Managing scope, and defending requirements to both sides
Who should own process description
What describing a process actually buys you
What a description consists of
Which processes are worth describing first, especially before automating anything
How processes are described around the world
Which methodology fits your situation
Using flowcharts
A simple BPMN diagram, and analysing what it reveals
Process description models
Templates worth reusing
The software available
A worked description using online tools
What the output actually is
Implementing a described process so people follow it
Evaluating whether it works
Adjusting it afterwards
Describing onboarding
Describing recruitment
Describing training and performance management
Describing offboarding
Creating the project team and choosing the processes
Preparing the concept and defending it with management
Launching, and reporting on the project
Closing it and monitoring what happens next
What a large language model is: capabilities and limitations
A short history, and what the alternatives are
How to formulate a prompt so the answer is usable
Working with the interface, and where the field is heading
Organising tasks and plans
Generating ideas and support for decisions
Optimising your own processes with ready prompt templates
Practical examples
Drafting business correspondence and documents
Producing reports, instructions and templates quickly
Analysing information and files
Building a custom assistant on your own documents, tuned to your role
Generating ideas, names and wording
Creating content for different formats
Rewriting, improving and adapting text to a required style
Working with generated images
Finding and structuring information
Producing summaries, lists and analytical material
Studying a new domain through questions and dialogue
Prompts for developing a skill quickly
Integrating AI into everyday processes through apps and automation
Building complex prompts for precise answers
Non-standard tasks, from wording to strategy
Services built on top of these models
The seven blocks of an advanced prompt: role, context, task, examples, constraints, format, validation
RISEN, CRISPE, CREATE and RTF, and when each applies
Why role and context account for most of the answer quality
Few-shot examples, and the validation block that makes the model check itself
Chain-of-thought and the accuracy it adds
Self-consistency: several answers, and picking the reliable one
Tree-of-thoughts for multi-criteria assessment
ReAct, and combining techniques inside a single prompt
The shift from prompt engineering to context engineering
Projects: an assistant loaded with your own policies, templates and documents
Custom instructions and system prompts: set up once, works afterwards
RAG explained without an API, and managing context across sessions
The difference between a prompt, a workflow and an agent
Prompt chains where one output becomes the next input
MCP and tool use: reading mail, calendar and spreadsheets
n8n as a no-code builder, and where a human still has to approve
The landscape: the assistant, the desktop workspace and the coding agent
Where Projects, Skills, Plugins and MCP connectors each live
Setting up a workspace and connecting Drive, mail and messaging
Building the company-wide knowledge base every other Project inherits
Building a Project with role-specific instructions and a reference knowledge base
Writing four custom Skills for one workflow
Taking apart an official command and adapting it to your own rules
Worked on a recruiting workflow: job description, search strings, screening rubric, draft offer
Customising an official command for your own process
Writing Skills that generate a pack of documents from one input
Building a self-service knowledge base for repeated questions
Worked on onboarding: welcome pack, 30-60-90 plan, day-one checklist, access list
A Skill that converts unstructured notes into a structured assessment
Loading a framework library so the output follows a known format
Preparing a calibration session in an hour instead of a day
Worked on performance review, with SBI and STAR as the frameworks
A Skill for gap analysis across a group
Generating an individual plan from the gap
Building a micro-course with text, examples and a test
Keeping generated content consistent with a defined brand voice
Adapting an official analysis command to your own framework
A Skill that ingests a system export and flags outliers against rules
Generating a document from the result and routing it for signature via a connector
Worked on compensation: pay equity, offers and variable pay
This course contains the use of artificial intelligence.
Most analysts have tried AI, received something that read well and meant little, and quietly gone back to writing everything themselves.
The output was mediocre because the input was a sentence. What produces usable work is a structure, and the structure is learnable.
Why the first attempt disappoints
You asked for a document and got a plausible one, with the specifics invented. You asked for analysis and got a summary of what you had already written. The model had no access to your policies, your definitions or your templates, so it answered from the general internet. And every time you wanted the same output again, you rebuilt the request from scratch, which means nothing accumulated.
None of that is a limitation of the technology. It is what happens when a tool designed to run on context is used without any.
What the course covers
Thirty-five lessons in three layers. The analyst's craft first, twelve lessons: framing a problem before writing a requirement, user stories with acceptance criteria, AS-IS and TO-BE modelling, impact analysis, and describing processes in BPMN — because a process nobody has described cannot be automated, only accelerated in its confusion.
Then the AI fundamentals: what these models can and cannot do, working with files, building a custom assistant on your own documents. Then prompt engineering properly — the seven blocks of a prompt, the four classic frameworks, chain-of-thought and tree-of-thoughts, ReAct, and the shift from prompting to context engineering with Projects, RAG and memory.
Building things that keep working
Then eight lessons on the operations layer, which is where this stops being about chatting. Projects with their own instructions and knowledge base, custom Skills written as plain text files so a workflow runs identically every time, connectors to your drive, mail and messaging through MCP, retrieval over your own documents, and packaging the whole set into a plugin your team installs with one command.
And finally five lessons of analysis end to end: a raw system export turned into a clean dataset, descriptive analysis without manual formulas, diagnosis of causes and anomalies, forecasting through interpretable rules rather than an unexplainable model, and a board-ready presentation defended in front of people who will push back.
A note on the examples
The AI sections are taught on people and operations data — recruiting, onboarding, reviews, pay. The methods are domain-neutral: a Skill is a Skill, a RAG setup is a RAG setup, and the PEARL analysis cycle works on any dataset. I have kept the worked examples as they were recorded rather than genericising them, because a real dataset teaches more than an invented one.
Who is teaching this
Mike, the number one HR instructor on Udemy. More than 1.6 million course enrolments, over 150,000 professionals trained, PHRi and SHRM-CP certified, HRCI representative in more than 10 countries. I built the people function of the unicorn Preply and worked at Wargaming, Alfa-Bank and iDeals.
What is included
Lifetime access to all course materials
Active instructor support in the Q&A section
Udemy Certificate of Completion
Practical assignments and real business cases
A section with additional courses, tools and resources
Take the document you write most often and build it as a Skill during the course. That single artefact usually pays back the time before you finish. Enrol now and start the first lesson today.