New job, unclear expectations? Build your first-month agreement

Separate access from understanding

Account setup and orientation matter, but they are not the same as knowing how to work effectively in the organisation. The US Office of Personnel Management^[1] describes onboarding as a longer transition than initial orientation. UC Davis guidance for managers^[2] also emphasises clear expectations and regular check-ins during the first months.

For you, the practical distinction is simple. Being able to open a system does not mean you understand which record is authoritative, who approves a change or how an error is handled.

Keep an access-and-support list separate from your work outcomes. If you cannot do a task without a permission, training session or introduction, name that dependency. A missing account should not become a private reason to work around a control.

Ask what useful progress would look like

Try: “By the end of my first month, what would tell you that I am getting established well? Which piece of work would be useful for me to own, and what should I still be learning?”

The answer should fit the role. A new specialist in a complex or regulated setting may need a longer learning period. A month is a planning window for this exercise, not a universal deadline for independence.

If the answer is “just get stuck in”, propose a modest outcome and invite correction. “Would it help if I learned the reporting process, completed one cycle with review, and documented any questions before the month ends?”

You are not asking your manager to predict everything. You are creating a shared starting point that can change as you both learn more.

Make the first promise small enough to check

Consider a fictional analyst joining a service team. “Improve reporting” is too broad to guide their first weeks. “Produce the next weekly service report from the agreed data source, have it checked by the current owner and explain two limitations in the figures” is clearer.

It identifies a deliverable, a source, a reviewer and a boundary. It also avoids promising an improvement before understanding how the report is used.

Agree what completion means. Is a draft enough, or does it need approval? Who will use it? Is the priority accuracy, turnaround time, a decision it supports or something else? Which checks cannot be skipped?

Write a short agreement in the team's normal channel: “My first outcome is one reviewed reporting cycle. Jordan will show me the source data. I will shadow the first run, draft the next and check the result before it is shared. We will review progress at our next one-to-one.”

This is a working note, not a substitute for your formal objectives or employment terms.

Learn the decisions around the work

You do not need a complete map of the organisation to start. Identify the people who give you inputs, use your output and approve important changes.

Ask each person a question connected to their work: “What do you rely on this report for?” or “What tends to arrive too late for your team to use?” You will learn more than from asking everyone for general advice about success.

When two people describe conflicting processes, do not quietly choose the one you prefer. Bring the difference to the relevant owner: “I have heard two versions of the approval step. Which applies to this report?”

Keep your notes in an approved place and avoid turning early impressions into permanent judgements about colleagues. A workaround that looks odd may exist because of a constraint you have not discovered yet.

Show unfinished work while changes are still cheap

Ask when your manager or reviewer wants to see a first version. “Would a rough draft on Wednesday help us check the direction before I finish it?” is often more useful than disappearing until Friday with a polished document.

Make feedback specific: “Is this the right level of detail for the audience?” “Have I used the correct definition?” “Which part should I change first?” The question “Am I doing well?” may matter emotionally, but it does not always produce an actionable answer.

When you receive a correction, record what you will do differently and check that you understood it. You do not need to defend every early decision to show competence. Equally, ask for an example if the feedback is too vague to use.

If there is no manager available to guide you

Ask who can provide day-to-day clarification and who still owns formal priorities. A helpful colleague can explain a process without having authority to approve your workload.

Send a proposed small plan to the appropriate manager and request correction. Do not present silence as agreement, particularly for spending, access, external commitments or consequential decisions. Stay within established permissions while waiting.

If expectations keep changing, maintain a simple record of the current priority and what changed. This makes the next conversation concrete without requiring you to reconstruct every instruction from memory.

Your next move

Write four lines: the first outcome, how it will be checked, the support you need and the next review point. Take them to your manager as a proposal.

Your first month does not have to prove that hiring you solved every problem. It should give you and the team a clearer basis for doing useful work together.

If another request competes with the agreed outcome, ask what should move when your manager adds more work. If feedback is too vague to act on, ask for the decision behind the feedback.

About this guide

US Office of Personnel Management: The difference between orientation and onboarding. Supports the distinction between initial orientation and a longer transition.

UC Davis Human Resources: The First 90 Days: From Learning through Executing. Supports clear expectations, regular check-ins and continuing manager support. These are US institutional resources; the first-month agreement and analyst example are CareerFood adaptations, not universal employment requirements.