Getting Things Done When You're Not the Project Manager

What you'll learn

---

define what "done" actually means before work begins
turn vague requests into clear objectives, outcomes, deliverables and acceptance conditions
identify scope, assumptions, dependencies and responsibility boundaries;
break work into smaller parts and estimate it more realistically
recognise when changing Requirements

---

or circumstances affect the original plan
communicate risks, delays and changes early enough for useful decisions to be made
make decisions, ownership and next actions visible so work does not stall after meetings or handovers
distinguish effort from duration and account for limited capacity and waiting time
Requirements

---

No previous project-management experience is required.
Students will get the most from it if they can relate the exercises to real situations where they have had to coordinate work, deal with unclear expectations, manage dependencies, estimate effort, or communicate changes.
Description

---

Project Manager by Accident is a practical introduction to project management for people who become responsible for getting something done, even when Project Manager is not their formal job title.
Many projects do not begin with a charter, a formal kickoff, or a dedicated project manager. They begin with a request: investigate a problem, improve a process, coordinate a change, prepare a plan, or deliver something by a certain date. What initially sounds simple can quickly involve unclear expectations, several contributors, approvals, competing priorities, changing Requirements

---

, and dependencies outside your control.
This course helps you deal with those situations more clearly.
You will learn how to turn vague requests into defined results by understanding the objective, expected outcome, deliverable, acceptance conditions, responsibility boundaries, and handover. You will practise defining what "done" actually means before committing to work.
You will also learn how to break work into smaller parts, identify dependencies and assumptions, estimate effort more responsibly, and distinguish effort from calendar duration. The course examines how available capacity, waiting time, approvals, and other people's availability affect realistic delivery dates.
Finally, you will learn how to maintain visibility when reality changes. You will practise comparing what was expected with what is true now, identifying the impact of risks and changes, and communicating consequences, options, decisions, and next actions early enough for people to respond.
The course is designed for beginners, aspiring project managers, team leaders, specialists, consultants, analysts, operations professionals, and anyone coordinating work across people or functions without necessarily managing them directly.
The focus is practical judgement rather than memorising a large methodology. Through practical lessons, exercises, personalised quizzes, and AI-supported coaching activities, you can apply the ideas to realistic situations and to the work you already do.
Who this course is for

---

The course is designed as a practical introduction for people who are new to project management, moving toward a project-management role, or already coordinating project-like work without having Project Manager as their formal title.
team leaders, specialists, product managers, business analysts, operations or office managers, consultants, technical professionals, and new or aspiring project managers
people coordinating work across several people or departments without directly managing them
people dealing with unclear requests, changing Requirements

---

, approvals, dependencies, competing priorities, or deadlines agreed before the work is fully understood
people who have finished what they thought was the task, only to discover that somebody expected something more
people whose project-like work keeps getting pushed behind normal operational work
Homepage

---