The Accidental PM> Start-here

Somebody just said, “Can you take this on?” and now you are the project manager. Nobody trained you, and the deadline is already on someone’s calendar. That is normal. Most project managers started exactly this way.

This page is a simple 30-day plan. It skips theory and tells you what to do each week. Do the steps in order and you will have a clear goal, a map of your people, a plan, and a weekly rhythm your stakeholders can rely on.

First, the four things that decide whether projects succeed

After more than 20 years of running projects and programs, and being called in when they went wrong, I see the same four things behind most successes and failures:

1. The right process: a method that fits this project, not the fanciest one.
2. The right tools: software that supports how the work really happens.
3. The right team: people who know what is expected and are motivated to deliver.
4. The right communication: stakeholders who hear the correct information on time.

Your first 30 days set up all four. Here is how.

Week 1: Understand what you were actually asked to do

Most early trouble comes from a vague starting point. Before you plan anything, get clear.

• Write the goal in one sentence. Then ask the person who gave you the project, “Is this what you expect?”
• Find out who the sponsor is: the person who wants this done and can make decisions about it.
• Ask what “done” looks like. What will be different when this project is finished?
• Note the hard limits: deadline, budget, people, and anything that cannot change.
• Ask what has already been decided, and what has already gone wrong.

Week 2: Map your people and your scope

• List your stakeholders: everyone who is affected by the project or can affect it. Note what each person wants and how much influence they have.
• List the deliverables: the things the project must produce.
• Write what is out of scope. This one line will save you many arguments later.
• Draft a one-page project charter: goal, scope, deadline, budget, sponsor, and main risks. Get the sponsor to agree to it.

Week 3: Build a plan you can actually follow

• Break the work into tasks small enough to finish in a few days each.
• Ask the people doing the work how long each task will take. Do not guess for them.
• Start a RAID log: a simple list of Risks, Assumptions, Issues, and Dependencies. Review it every week.
• Choose a simple way of working. Some projects fit a step-by-step plan, and others fit short cycles with regular check-ins. Many fit a mix of both.
• Pick one tool to hold the plan. A spreadsheet is fine to start.

Week 4: Set the rhythm and keep everyone informed

• Hold a kickoff meeting. Cover the goal, who does what, key dates, and how you will communicate.
• Send a short weekly status report to the sponsor and key stakeholders: what was done, what is next, what is at risk, and what you need from them.
• Hold a short weekly check-in with your team to find blockers early.
• Never surprise your sponsor. Bad news is manageable when it arrives early and comes with a suggested fix.

Three mistakes to avoid

• Starting to work before the goal is clear. You will build the wrong thing efficiently.
• Saying yes to every request. Every extra request affects time, cost, or quality. Use your out-of-scope list.
• Going quiet when things slip. Silence damages trust more than the delay itself.

What to read next

• Waterfall vs Agile: which fits your project? (coming soon)
• How to write a project charter, with a template (coming soon)
• How to run your first kickoff meeting (coming soon)