
Workforce planning as a partnering activity rather than a form
Building the profile of who a team actually needs
Taking part in interviews and what you contribute there
Where the partner adds something the manager cannot
Preparing before the first day
The first day itself
The first month
Closing a probation period honestly
How to run these conversations
What the partner's role in them is, as distinct from the manager's
Giving feedback to the manager afterwards
Reporting, and monitoring the risk of someone leaving
The Gallup Q12 questionnaire
What to do with the results rather than what to present
Raising engagement in a specific team
What employee experience is made of, and how to survey it
The basics of burnout as distinct from stress
Diagnosing it
The causes, which are usually structural
The ways it actually gets resolved
The basics of coaching and the GROW model
Unlocking potential rather than assigning development
Working with someone's talent
When coaching is the wrong instrument
The basics of developing someone
Hard and soft skills, and why the split matters here
Creating the plan
Getting it actually implemented rather than filed
Preparing for it
The questionnaire
Conducting it so the answers are honest
Feedback, analytics and the action plan that follows
Taking part in the goal-setting process
Setting goals with a manager rather than for them
Giving feedback inside the cycle
Running the appraisal itself
The angry one and the toxic one, which are not the same
People resisting a change
Chronic lateness and chronic complaining
The conflicted person, and where the partner's mandate ends
The stages of persuasion, and AIDA and SPIN inside them
Understanding motive rather than stated requirement
FAB, and building a value proposition for an internal idea
Building trust, and using evidence from elsewhere
The channels available inside an organisation
Building a picture of the person you need to convince
BANT applied to an internal proposal
The five-touch method, and the elevator pitch
The ladder of persuasion
Active listening and open questions
Presenting through story rather than specification
Objections via LAER and Feel-Felt-Found, and two ways to close
What a project actually is, and its four stages
What project management is as a way of producing a result
The role of whoever runs it, and the main difficulties
The PMBOK 7 principles and performance domains
Collecting the ideas
Building the business case
Developing the charter, and the cost-benefit analysis
Choosing which initiative to actually run
Who your stakeholders actually are
Compiling and prioritising the list
Ways of engaging each of them
Assessing influence and interest, and planning engagement
Establishing that the work is needed at all
Defining the start and end points
Defining the boundaries
Documenting assumptions, which is where partnering usually fails
Breaking the work into parts
Describing the plan as a diagram
Identifying risks early
Time planning, and the network diagram
Methods for planning time
Determining how long things take
The Gantt chart and other displays
Identifying participants, and the responsibility matrix
Cost and budget, and the types of cost
The three stages of a budget
Identifying and assessing risk
Managing it rather than listing it
Building the structure for the work
Operating in a matrix, which is where a partner usually sits
Defining roles and allocating tasks
Starting the team properly
What control actually means
Reporting progress, and monitoring spend
Handling deviation from the plan
Running meetings, and the communications plan
Planning the closure rather than drifting into it
Handling the administrative side
Surveying the result
What a proper closure does for the next request you make
What owning a service relationship involves
The effect on experience and on results
The key indicators: net promoter, satisfaction, effort, first-contact resolution
Working across departments, and leading change from a support function
What an audit is for and what it must cover
Journey mapping applied to your own service
Collecting data: surveys, interviews, feedback
Finding the bottleneck rather than the symptom
Vision and mission for the function itself
Long-term and short-term goals
Developing policy and standards
Choosing the operating model
This course contains the use of artificial intelligence.
The difference between a business partner and a service desk is not the job title. It is whether people arrive with a task or with a problem.
How a function ends up as a service desk
Nobody decides it. It happens because every request gets accepted, so requests are what you get. You are competent, you are responsive, and you are told about decisions after they are made — because you have trained everyone that you are the person who executes, not the person who is consulted. I spent two years being extremely useful in exactly that way and could not understand why I was never in the planning meeting.
What this course actually covers
Five blocks, each one a piece of what changes that. First, the substance of the role — ten lessons on what partnering actually consists of: workforce planning, one-to-ones that surface a problem before it becomes a resignation, engagement, burnout, coaching, development plans, exit interviews and difficult people. Second, persuasion, because a partner cannot instruct anyone: the funnel, objections, and getting to a decision. Third, delivery — ten lessons of project management, because trust is built on things you promised and finished, not on good meetings. Fourth, treating an internal stakeholder as a client: auditing how your function is experienced, service standards, metrics, escalation and difficult situations. Fifth, communication, so the message survives being retold by someone else.
A note on the first block
Those ten lessons are recorded from the people-partner seat, because that is the most fully developed version of this role and the one with the clearest practice behind it. The mechanics are the same in any function. A finance partner, an IT partner and a people partner all begin the same way: by stopping waiting for the request, and by learning enough about the business unit to have an opinion worth interrupting for.
Who is teaching this
I am Mike Pritula. I built the people system at Preply as it became a unicorn, working as a partner to every function in it, 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 40 lessons
Active instructor support in the Q&A section
A Udemy Certificate of Completion
Working material: the one-to-one structure, Gallup Q12, the development plan, AIDA, SPIN, FAB, BANT, the project charter and stakeholder map, service standards and the metric set
Practical work aimed at the business unit you actually support
Where to start
Look at the last ten things your function was asked for and mark which arrived as a task and which as a problem. That ratio is your current position, and it is the only number this course is trying to change. Enrol now and start today.