01
Record the assignment
Write down the project name, customer, project owner, what was authorized, what you are responsible for, and any date already discussed. Mark anything not yet verified as an assumption.
Your first project starts with what you know.
You do not need every answer before you begin. Establish the project record, separate facts from assumptions, identify the missing information, and create the next controlled action.
YOUR FIRST SIX MOVES
Build control before the project builds pressure.
Complete these in order. Each step creates information needed by the next one.
02
Build the project workspace
Create the portfolio or project-system record, shared project folder, and email folder. Confirm that the people who need access can open the current records.
03
Define the outcome
State what the project must deliver, how completion will be accepted, what is inside the scope, and what is not yet clear enough to plan.
04
Identify the project network
List the customer lead, sponsor, decision-makers, contractors, suppliers, site contacts, internal team members, and every person needed for an approval or handoff.
05
Request evidence and inspect the site
Ask for available plans, drawings, sketches, schedules, photographs, surveys, and prior records. If the information is missing or cannot confirm conditions, schedule a site visit.
06
Set the first working dates
Enter a supportable tentative delivery forecast, separate dates for long-lead third-party items, and the first coordination meeting. Record the assumptions and revise the dates when verified information changes.
INITIAL CONTROL ESTABLISHEDYou now have a visible project, a working record, a known project network, documented unknowns, and a dated next move.
YOUR FIRST 30 DAYS
Do not try to look experienced. Make the project understandable.
A new PM builds credibility by asking complete questions, separating facts from assumptions, documenting commitments, and following through. The timing will vary, but the control sequence remains useful.
Understand the assignment
Confirm the requested outcome, authority, customer, sponsor, boundaries, known dates, and what is still only an assumption.
Create visibility
Establish the project record, working folders, contact network, open-question list, immediate actions, and first coordination rhythm.
Verify before committing
Gather current evidence, confirm requirements, inspect the working environment when needed, and identify the people who control approvals and handoffs.
Build the controllable plan
Define scope, acceptance, activities, owners, dates, dependencies, risks, decisions, and the evidence required to demonstrate progress.
WHEN YOU DO NOT KNOW THE REQUIREMENTS
Do not guess. Build a starting point you can verify.
Describe the project in plain language. FYE360 can help identify the next questions or create an editable draft. Proposed content must still be checked against the real project, governing requirements, and authorized stakeholders.
Text questions only. FYE360 does not accept PDFs, drawings, photographs, site-visit files, or other attachments. Do not include confidential company, customer, employee, or project information.