
Who should own the description itself
What describing a process actually gives you
What a description consists of
Which processes to describe first, and which to leave alone
How processes are described internationally
Which methodology fits which situation
Using flowcharts properly
A simple BPMN diagram, and analysing what it shows
The description models available
Templates
The software worth using
A worked example using online tools
The actual output of the exercise
Implementing the described process rather than filing it
Evaluating how it performs afterwards
Adjusting it once reality disagrees
Describing an onboarding process end to end
Describing a hiring process
Describing a training and a performance process
Describing an exit process, and what each one exposes
Forming the project team and choosing the processes
Preparing the concept and defending it to leadership
Launching the project
Reporting, closing and monitoring afterwards
Who is responsible for the shape of an organisation
The design process itself
The five steps of organisational design
What problem you are actually solving, stated plainly
Strategic priorities and the star model
The symptoms that say ownership is unclear
Setting the goal, and the six drivers of design
Using the six drivers to choose
Organisational archetypes
Whether a matrix is the answer
The three types of matrix, and what each does to accountability
Designing for operational management
Operating models and levels of management
Matrix management, networks and boundaries
Diagnostic indicators, and how power distributes in a matrix
Designing the leadership layer
Defining accountability at the top, and the options for it
The cascade, and organisational levels
Span of control, and making good staffing decisions
Developing the implementation plan
All at once or in phases
Whether a pilot is worth it
Managing the transition and launching new workflows
What separates a redesign from a reorganisation announcement
The skills the work requires
How the project team operates
Wargaming and Vega
Parallel
Corum and ArcelorMittal
What transfers between them and what does not
What a job profile actually contains
Which sections belong in it
Why an organisation needs them at all
What job analysis is, and who should write the profile
Interviewing people who hold the role
Interviewing the manager, who will describe it differently
Questionnaires for collecting information
Observation, and how the profile fits the process system
What a competency is, precisely
What competencies add to a role profile
How to research them rather than assume them
How to describe them so two people read them the same way
An overview of existing competency libraries
Ready-made role descriptions
How to use existing material without inheriting its assumptions
Building a scorecard from the profile
Building a career ladder on it
Building a development plan
Deriving goals and indicators for the person holding the role
Why an organisation needs the process at all
What sits with managers and what sits with the function
The modern approaches
Linking the process to strategy rather than to the calendar
What a performance agreement contains
The role profile behind it
Cascading objectives to an individual
Identifying required skills and behaviours, and the development plan
A model for giving feedback, and what makes it effective
Regular one-to-ones as the main instrument
Difficult conversations, and diagnosing a drop in performance
Coaching and delegation as part of managing it
What can be automated and what should not be
The tools available
A worked example of an automated process
Where AI genuinely helps here
Assessment based on responsibilities and on objectives
Assessment based on indicators
Assessment against standards and critical incidents
Assessment derived from job analysis
Building a competency profile or model
Organising a 180-degree assessment
Organising a 360-degree assessment
Competency interviews, and running an assessment centre
The questionnaire template and the question bank
Linking goals, feedback and the review into one process
The template for a good review conversation
The manager's own self-check afterwards
Salary review and bonus decisions
The promotion decision, and revising responsibilities
Inclusion in the talent pool, and the development plan
Improvement plans, and dismissal
This course contains the use of artificial intelligence.
Ask who owns a process in your company and count the seconds before someone answers. That pause is the whole subject of this course.
Documented is not the same as governed
Plenty of organisations have process documentation. Very few have a named person who is obliged to notice when the process stops matching reality, with the authority to change it and a consequence if they do not. So the document ages quietly, everyone works around it, and the gap only surfaces during an audit or an incident. I have owned processes on paper that I had no ability to change, and I have watched a control fail in a place where three departments each assumed one of the others was watching.
What this course actually covers
Five layers, from the object to the person. First, describing a process so its boundaries and handoffs are unambiguous — methodology, tooling, worked examples, and running the project. Second, structure: the six design drivers, what a matrix does to accountability, the leadership cascade and span of control. Third, the role: what a specific job owns, the competencies it requires, and how that profile feeds hiring, development and goals. Fourth, the individual layer — the performance agreement, evidence, the review conversation and the consequence attached to it. Fifth, controls and risk: the heat map, the fraud triangle, ISO 31000, top-management risk, risk culture, the three lines of defence, and personal accountability.
A note on the material
Twenty-three of the thirty-seven lessons use people-side material: role profiles, review cycles, risks that originate with people. That is not a compromise. Governance always terminates in one named individual with an obligation and a consequence, and the mechanics of defining and evidencing that obligation are the same whatever the process contains. RACI, the three lines of defence, ISO 31000 and competency matrices do not change by department.
Who is teaching this
I am Mike Pritula. I built the people system at Preply as it became a unicorn, including its process and accountability layer, and I have worked at Wargaming, iDeals and Alfa-Bank. More than 1.6 million students have enrolled in my courses across 185 countries, and over 150,000 specialists have gone through my programmes. I hold PHRi and SHRM-CP certifications and represent HRCI in more than ten countries.
What is included
Lifetime access to all 37 lessons
Active instructor support in the Q&A section
A Udemy Certificate of Completion
Working material: BPMN mapping, the six design drivers, role profile and competency templates, the review cycle, the risk heat map, ISO 31000, the three lines of defence
Real organisational cases, including Wargaming and ArcelorMittal
Where to start
Pick your three most important processes and write a single name next to each one. If you hesitate on any of them, or if the name you wrote does not know it, you have found your first governance gap. Enrol now and start today.