Suddenly a project manager? Do these five things this week

It usually happens in a meeting you thought was about something else.

"Great, and you can look after the project side, right?"

No job title change. No training budget. No handover, because there's nothing to hand over yet. Just a delivery date someone has already mentioned to a director, and now: you.

If that's you, two things are true. First, you're what the industry calls an accidental project manager, and you're in enormous company. A substantial share of the world's projects are run by people who never planned to run one. Second, and more usefully: the difference between the accidental PMs who drown and the ones who swim isn't certification, experience, or even confidence. It's whether they do a handful of unglamorous things in the first week, before the project develops momentum in a random direction.

Here are the five, in order.

1. Get the "why" in writing, even if you have to write it yourself

Before tasks, before tools, before anything: can you state, in two sentences, why this project exists and what happens if it doesn't?

Ask your sponsor. If their answer is crisp, write it down and email it back to them: "Just confirming this is the goal we're working to." If their answer is vague, and it often is, that's not a problem, that's a discovery. You've just found the project's biggest risk on day two instead of month three.

Everything else you'll do, every scope argument, every prioritisation call, every "can we just add..." conversation, gets resolved by pointing at those two sentences.

2. Write a one-page charter, not a plan

Your instinct will be to open a spreadsheet and start listing tasks. Resist it. Tasks are easy and comforting and mostly wrong at this stage.

Instead, write a project charter: one page recording why the project exists, what "done" looks like (measurably), what's in and out of scope, who the key people are, five-to-eight milestones, the top risks, and, critically, who has the authority to decide what.

The charter isn't paperwork. It's a structured way of having the six conversations that kill projects when they're skipped. The out-of-scope box alone will save you: every painful week-twelve argument traces back to something ambiguous that a week-one charter would have surfaced.

(If you want a head start, we made a free UK charter template with guidance notes in every section.)

3. Meet the people who can hurt you

List everyone who is affected by the project, controls something it needs, or can veto it. For each: what do they care about, and how much influence do they have?

Then spend your first week having twenty-minute conversations with the top five. Not status meetings. Listening meetings. One question does most of the work: "What would make this project a success from where you sit, and what's the version of it that would annoy you?"

The stakeholders who derail projects are almost never the loudly difficult ones. They're the quietly unconsulted ones.

4. Set a weekly rhythm and never break it

Pick a day. Every week on that day, three things happen:

• A progress check. Twenty minutes, what moved, what didn't, what's stuck.
• A risk review. Scan the list, ask "what's changed?", add anything new keeping you up at night.
• A status report upwards. Three lines: what moved, what's at risk, what you need. Put the ask at the top, not buried in paragraph four.

Consistency beats sophistication here, every single week. A mediocre report that arrives every Friday builds more trust than a brilliant one that arrives when things are going well.

5. Use AI for the drafting, keep the judgement

Here's the honest 2026 advice nobody puts in the methodology guides: the drafting work of project management, charters, risk register entries, status reports, difficult-email first drafts, is now largely a solved problem. AI does it in minutes, and does it well if you give it real context and a precise format.

What AI can't do is know your sponsor is quietly sceptical, sense which risk everyone is politely not mentioning, or decide what to do with a slipping milestone. That's the actual job. The accidental PMs who thrive this decade are the ones who hand the paperwork to the machine and spend the recovered hours on judgement, relationships, and the next move.

That's precisely the gap PM101 was built for: 500+ tested prompts for real PM scenarios, templates that export board-ready documents, and an assistant that answers "what should I do next?", for £9 a month, which is less than an hour of anyone's time.

---

The takeaway: don't try to become a certified project manager by Friday. Do these five things instead: why in writing, one-page charter, stakeholder conversations, weekly rhythm, AI for the drafting. You'll be ahead of most people who've held the title for years.