
In this lecture you work on the moment every requirement starts from: somebody has just told you what they want, and you have three answers available.
This course is built from six disciplines: business analysis, interviewing, facilitation, surveys, process management and critical thinking.
The map of the course
A dictionary for reading lectures written about recruitment and engagement surveys as your own requirements work
Three questions to ask after every lecture
A short self-diagnostic that shows which sections to watch first
Download the Behind the Request Card and fill it in before your next conversation.
Tools in this lecture
Files to download (1)
Translating business value into a solution
Problem mindset against solution mindset
Telling a symptom from a problem, which is where most requirements go wrong
Value-driven analysis, and the Problem to Goal to Constraint to Metric framework
Tools in this lecture
Ready to use on the slides (11)
Models and methods explained (6)
Stakeholder mapping and influence analysis
Elicitation techniques
Asking the business the right questions
Working with conflicting requirements, and prioritising by value against effort
Tools in this lecture
Files to download (4)
Ready to use on the slides (17)
Models and methods explained (2)
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
Tools in this lecture
Files to download (3)
Ready to use on the slides (15)
Models and methods explained (4)
What a business process means in practice
The AS-IS and TO-BE approach, where the gap becomes your requirements
The minimum necessary BPMN
Finding bottlenecks and waste, and proposing improvements rather than diagrams
Tools in this lecture
Files to download (3)
Ready to use on the slides (10)
Models and methods explained (2)
The system context diagram
Functional decomposition
User flows, data objects and business rules
Non-functional requirements and traceability
Tools in this lecture
Files to download (3)
Ready to use on the slides (12)
Models and methods explained (1)
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
Tools in this lecture
Files to download (3)
Ready to use on the slides (13)
Models and methods explained (8)
What an elicitation conversation is for and what it is not for
Structured, semi-structured and unstructured formats
Competency-based and case formats, and where each fits
Preparing the profile, developing questions and building a scoring sheet
Tools in this lecture
Ready to use on the slides (7)
Models and methods explained (14)
The STAR technique and behavioural questions applied to how work is done now
Competency maps, and where to find ready libraries
Active listening: clarifying questions and interpreting the answers
Reading non-verbal behaviour and creating a comfortable atmosphere
Tools in this lecture
Ready to use on the slides (7)
Models and methods explained (1)
Measuring what someone described against what they demonstrated
Designing a task and evaluating the result
Avoiding bias and stereotypes when you score
Checking with other sources, and comparing what different people told you
Tools in this lecture
Ready to use on the slides (8)
Models and methods explained (6)
Documenting results and observations while they are fresh
The matrix for comparing what you heard from different people
Giving feedback on what will and will not be included
Feedback to the team, and the confidentiality and legal side
Tools in this lecture
Ready to use on the slides (5)
How facilitation relates to decision making
The basic principles
The role of the facilitator, which is neutral by design
The single most important facilitator skill
Tools in this lecture
Ready to use on the slides (9)
Models and methods explained (1)
The main stages of preparation
Formulating the goal the workshop is meant to produce
Selecting who is in the room, which decides most of the outcome
How to open the session
Tools in this lecture
Ready to use on the slides (15)
Models and methods explained (1)
Keeping participants focused and managing the group
Taking notes without losing the thread
Gathering information and generating options
Choosing priorities as a group with different needs
Tools in this lecture
Ready to use on the slides (23)
Summing up what was actually agreed
Assigning owners so the workshop produces a list rather than notes
Evaluating the session
Force majeure and difficult participants
Tools in this lecture
Ready to use on the slides (28)
How a group actually arrives at a decision
Maintaining the atmosphere
Exercises that move a stuck room
Tools in this lecture
Ready to use on the slides (9)
Models and methods explained (2)
Building the agenda and estimating timing
Facilitating online
Facilitating large meetings
Working with an international group
Tools in this lecture
Ready to use on the slides (15)
The role of a survey when you cannot interview everyone
The most common survey types
Automation tools
Benchmarks to compare against
Tools in this lecture
Ready to use on the slides (2)
Services and apps shown in this lecture (4)
Satisfaction, loyalty and engagement surveys
Experience surveys, which map closest to requirements work
Cross-department and process surveys
Pulse surveys and the exit conversation
Tools in this lecture
Ready to use on the slides (6)
Models and methods explained (1)
Types of question and how each one biases the answer
Response options and the choice of scale
How long a questionnaire can be before quality collapses
Open questions, platforms, and a build in Google Forms
Tools in this lecture
Ready to use on the slides (3)
Services and apps shown in this lecture (3)
Models and methods explained (1)
Setting the question the survey is meant to answer
Designing the questionnaire around it
Promoting it so the response rate is worth analysing
Reminders that work without irritating people
Tools in this lecture
Ready to use on the slides (6)
Models and methods explained (3)
Report formats and which fits your audience
Chart types and what each one hides
The sections a report has to contain
Preparing recommendations, and analysing open-question text
Tools in this lecture
Files to download (4)
Ready to use on the slides (4)
What conclusions the answers actually support
Turning them into a plan with owners
Interim surveys to check whether anything moved
Tools in this lecture
Ready to use on the slides (3)
Models and methods explained (2)
Who should own process description
What describing a process actually buys you
What a description consists of
Which processes are worth describing first
Tools in this lecture
Ready to use on the slides (3)
Models and methods explained (9)
How processes are described around the world
Which methodology fits your situation
Using flowcharts
A simple BPMN diagram, and analysing what it reveals
Tools in this lecture
Ready to use on the slides (4)
Models and methods explained (3)
Process description models
Templates worth reusing
The software available
A worked description using online tools
Tools in this lecture
Services and apps shown in this lecture (1)
This course contains the use of artificial intelligence.
386 tools for requirements engineering in one course: 275 ready-to-use procedures, question lists, templates, checklists, matrices and AI prompts, 82 models and methods, 21 downloadable tool files, and 8 services and apps shown on screen.
Open a lecture, take the tool, use it on a real requirement.
Why specifications fall apart
Nobody can tell you what they want. They can tell you what they do now, what annoys them about it, and what they saw somewhere else and liked. The requirement gets written down exactly as it was said, so it records a proposed solution and not the problem behind it. The acceptance criteria say "the system should be user-friendly", which cannot be tested. Two stakeholders want opposite things and both wishes are recorded, so the conflict moves to delivery.
What changes after this course
You start from the business problem and its metric. You get requirements in three ways, because each one brings different information: one to one in an interview, in a group at a workshop, and in writing through a survey. You write them as user stories with acceptance criteria that a developer can build from. You draw the process as it is and as it should be, and the gap between them becomes the requirement set. You check a requirement for logic and evidence before the team spends time on it.
What is inside: 386 tools, counted lecture by lecture
You do not have to take this number on trust. Open any lecture and read its description: every tool inside is listed there by name.
Where the tools are
What this course is not
It is not a certification programme such as CPRE, CBAP or ECBA. You receive the Udemy Certificate of Completion and a working toolkit.
Who is teaching
I am Mike, the #1 HR instructor on Udemy, with 1,800,000+ course enrollments from 170,000 students, and the author of about 200 books on Amazon. I built the people system at Preply as it became a unicorn and worked at Wargaming, iDeals and Alfa-Bank across 20 years in HR. I hold PHRi, SHRM-CP and HCI sHRBP certifications and represent HRCI in Eastern Europe.
I have been on both sides of this work. At the STB TV channel I described and improved recruiting and onboarding myself. When personnel administration needed the same, a business optimization manager was brought in. She started by coming to the department, sitting next to an employee and watching a typical working day from start to finish. She saw a person standing in a queue, a form filled in by hand though the law did not require it, and we removed these steps one by one. I also saw what a written process gives. New recruiters read the described process and took vacancies into work on the third day. More time went to development and less to putting out fires.
How to use the course
Start with the first lecture and its card: it takes one vague request and turns it into something you can test. Watch the next two sections in order: they follow a requirement from the problem to the change request, and the lectures have files to fill in. Then open the way of eliciting you need now: interview, workshop or survey. Section and lecture titles show how many tools are inside, and each lecture description lists them by name.
What is included
Where to start
Take one request you received this week. Open the first lecture and rewrite the request as a business problem statement: what is the problem, what is the goal and how you will measure it. Enrol now and start your first lesson today.