
What actually counts as a project, and what is just work
The four stages a project moves through
The role of the project manager and the main difficulties of the job
An overview of the PMBOK 7 principles and performance domains
Collecting the ideas and turning them into a proposal
Building the business case and the project charter
Cost-benefit analysis and the documentation that goes with it
Choosing which project to actually run
Stewardship, ethics and stakeholder interests as selection criteria
Who your stakeholders are, including the ones nobody named
Compiling and prioritising the list
Assessing influence and interest
Ways of engaging, and the Stakeholders performance domain
Establishing that the project is needed at all
Defining where the project starts and where it ends
Setting the boundaries and documenting assumptions
The development approach and life cycle domain
Breaking the project into parts and labelling them
Describing the plan as a diagram
Identifying risks at the planning stage
Time planning and the network diagram
Planning and measurement domains, with adaptability built in
Time planning methods and determining activity durations
Displaying the schedule, including the Gantt chart
Identifying participants and using a human resources matrix
Applying the Team performance domain
Project cost and the different types of it
The three stages of a project budget
Identifying risk factors and assessing them
Risk management, and the Uncertainty domain
Building the structure for the project
Working in a matrix environment, where nobody reports to you
Defining roles and responsibilities, and allocating tasks
Kicking off and then running the team
What project control actually means
The progress reporting system and monitoring spend
Handling deviations before they become the status update
Communicating progress, running meetings, the communications plan
Planning closure rather than letting a project fade out
Handling the administrative matters
Surveying the results with the people who received them
Bringing the PMBOK 7 principles together at the end
Three environments that shape how it feels to work somewhere
The key differences from office work
What changes in every process once the team is distributed
The checklist for moving, and the security part nobody plans for
The rules of the job when there is no office to define them
Sleep, nutrition, and why they belong in a management course
Organising the workplace, and rules with family and pets
Communication tools and the rules for using them
How to organise supervision of a distributed team
The control tools available, and what each actually tells you
Organising work so people control their own output
Tools for communication and for organising work
The types of meetings a distributed team needs
Tools for document storage
Deciding what belongs in a meeting and what does not
Why motivation behaves differently without a shared room
Working with engagement deliberately
Socialisation, and what happens when it is left to chance
Team building for people who have never met
The benefits that are actually used
Security for remote employees
Support for mental health
Physical health care at a distance
Time management and independence as job requirements
Working in isolation without losing output
Technical confidence and written communication
Automation as a personal skill
Which candidates work well remotely and which do not
Where to look for them
Adapting the hiring process for distance
Onboarding someone who will never visit an office
Working with retention before someone is already leaving
The real reasons people leave distributed teams
Handling low performance you cannot observe directly
Dismissing a remote employee
Describing the culture explicitly, since it is no longer absorbed
Supporting it in daily practice
Business security with a distributed team
Dealing with force majeure
Why an announcement nobody read was not communication
How communication helps delivery when it is designed
Running a communications audit
Surveying people about how they actually receive information
Aiming communication at a problem rather than at coverage
Helping decision-makers decide
Influencing behaviour instead of informing
Whether you actually know who your stakeholders are
Segmenting them and building personas
Where the data for that comes from
Building the message, and a template for an effective one
Choosing channels and what each is suited to
A real channel mix from a company that got it right
Getting attention in a saturated environment
Managers as a channel, and preparing them for it
Building the communication process
Managing change through it
Delivering news nobody wants, including slipped deadlines
Communicating culture
Why evaluation is the step everyone drops
Communication KPIs
Gathering the information for them
Preparing the report for management
This course contains the use of artificial intelligence.
A project plan that worked in an office quietly stops working when the team is spread across four time zones. Nothing dramatic happens. The status just becomes less true every week.
In a room you notice trouble without being told. Remotely you find out at the deadline.
What actually breaks at distance
The reporting still arrives, and it is optimistic. The daily meeting turns into eight people reading their tasks aloud to a muted call. Risks that someone spotted in week two never travel upward, because raising them requires an act of initiative rather than a hallway. And the manager compensates by asking people how it is going, more often, which produces more reassurance and no more information.
This is not a communication problem you can fix with a better tool. It is a project management problem that the office used to hide.
How the course is built
Thirty-eight lessons in five parts. Ten lessons on project management by PMBOK 7 first, because remote work does not replace the discipline, it removes the slack that was covering its absence. Business case, charter, stakeholder map, scope boundaries, work breakdown, network diagram, Gantt, three-stage budget, risk register, team structure in a matrix, progress control, and a closure that actually happens.
Then ten lessons on distributed teams: what changes in every process, supervision that does not require watching people, the tool and meeting stack, engagement, hiring and onboarding someone who will never see an office, low performance you cannot observe, and culture that now has to be written down because nobody absorbs it by sitting nearby.
Communication, Agile and your own week
Then six lessons treating communication as a designed process — audit, goals, audience segments, channel mix, delivering slipped deadlines, and measuring whether behaviour changed. Then six on Agile delivery without a physical board: product vision, MVP, backlog, story points, sprint planning, daily meetings, and reviews that are honest.
And six on your own week, because a distributed project manager has no office to separate work from everything else. SMART, the Eisenhower matrix, 4D, Pomodoro, GTD, time-blocking, delegation, and the procrastination problem underneath all of it.
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 — distributed companies, where every process had to survive without a shared room.
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
Start with this
Take your current project and write down how you would know, this week, if it were three weeks behind. If the answer is that someone would tell you, that is the gap. Enrol now and start the first lesson today.