A practical first-month checklist for project managers taking over a customer-portal rollout, with staged evidence, stakeholder conversations, planning checks and a day-30 decision.
Follow days 1-3 through days 28-30 to clarify the mandate, establish delivery facts, test readiness and agree the next commitment. Each stage produces a concrete record you can adapt.
Start with a thirty-day outcome
Your first month should leave the project easier to understand and act on. Understand the result and your authority before changing commitments. Build a working map of interests, influence and practical knowledge. Create a dated baseline of what is known about delivery today.
Two of five customer journeys pass agreed tests. Three remain incomplete. Describe that evidence directly; two of five is not proof of 40% of total effort or value.
Days 8-9: align scope and success
Make the promised result specific enough to plan and accept. Surface the decisions that are holding the project in place. Turn the remaining scope into a credible sequence of work. Separate possible future events from problems already happening.
A missing test environment is an issue if it is already blocking testing. Possible late security approval is a risk until the condition actually occurs.
Days 15-17: establish a delivery rhythm
Use a small number of routines that help people finish work. A plan needs both available people and evidence that the result works. Report the decisions and trends that matter for the next period. Make a small change whose effect you can observe.
For the portal, reserve two review slots per week and name a backup reviewer. Observe whether waiting for review falls without creating a new queue elsewhere.
Days 26-27: rehearse the next milestone
Test the handoffs before the project reaches a critical date. Close the month with a shared assessment and a practical next plan. Use evidence of completion instead of ticking off conversations alone. The month creates a working foundation, not a permanent management system.
Record missing documents and unavailable people, explain the resulting uncertainty and plan an alternative evidence source. Do not fill gaps with assumed certainty.
Contents
- Start with a thirty-day outcome
- Days 1-3: clarify the mandate
- Days 4-5: meet the people
- Days 6-7: establish the facts
- Days 8-9: align scope and success
- Day 10: check commitments and authority
- Days 11-12: rebuild the delivery view
- Days 13-14: inspect risks and issues
- Days 15-17: establish a delivery rhythm
- Days 18-20: test resources and quality
- Days 21-23: build a useful status report
- Days 24-25: improve one real bottleneck
- Days 26-27: rehearse the next milestone
- Days 28-30: agree the next commitment
- Your thirty-day checklist
- Keep adapting after day thirty
Using the PDF
Each numbered page contains an explanation, an original worked situation and a practical action. The bookmarks navigate the learning pages. A templates advertisement follows content page 5 and a Coursera Plus advertisement follows content page 15. The entire advertisement image is linked. Promotional links may earn Coursya a commission. A purchase is optional.
Frequently asked questions
Who is this guide for?
A practical first-month checklist for project managers taking over a customer-portal rollout, with staged evidence, stakeholder conversations, planning checks and a day-30 decision.
How can I practise the ideas?
Follow the running case, work through the page actions and use the PDF bookmarks to revisit a topic. The final learning pages help you apply the decisions to your own project.
What does the download contain?
The PDF contains 19 pages, including 16 numbered learning pages, a cover and two linked advertisements. The book is written in English.


