In an office, you learn how a team works by watching it. Remotely, there is nothing to watch. Decisions happen in threads you were not tagged in, norms live in people's heads, and silence is easy to mistake for approval. The first month sets how your new team sees you for a long time, so it is worth planning.
Here is a week-by-week plan that works whether you are an engineer, a designer, in support or in sales.
Day one: send the message
Before lunch on your first day, post a short note in your team channel. Something like:
Hi all, I'm Kwame, joining as a backend engineer. I'm in Accra (UTC+0) and usually online 8:00–17:00 UTC. This week I'm setting up and reading through the payments service. If there's one thing you think I should read first, I'd love to hear it.
It tells people who you are, when to reach you, what you are doing, and invites them to help. Most new remote hires never send it, and they spend their first weeks invisible.
Week 1: set up and listen
- Get every account working: email, chat, code or design tools, the HR and payroll system, password manager, two-factor authentication.
- Find the written stuff: handbook, onboarding docs, team wiki, recent planning documents. Read more than you think you need to.
- Ask your manager three questions: what does a great first 30, 60 and 90 days look like; how do they prefer updates; and who else you should meet.
- Book short intro calls with the people you will work with most. Fifteen minutes each is enough.
Keep a running document of things you do not understand. You will answer most of them yourself by Friday, and the rest become good questions.
Week 2: ship something small
Pick, or ask for, a task you can finish in a few days. A bug fix, a small design change, a set of support macros, a list of prospects researched. The aim is not impact. It is to walk the whole path once: how work is assigned, reviewed, approved and shipped.
Write down every step that confused you. If the team's onboarding docs are missing it, offer to add it. Improving onboarding in your second week is one of the fastest ways to earn trust.
Week 3: make your work visible
Remote teams judge by what they can see. Start a simple weekly update and send it on the same day every week:
- What I did this week
- What I am doing next week
- Where I am blocked or need a decision
Three bullets each. Post it where your manager and close teammates will see it. When you finish something, say so in the thread where it was requested, with a link.
Week 4: agree on expectations
Ask your manager for a 30-day check-in if one is not already booked. Bring your running document, your weekly updates and two questions: what should I do more of, and what should I do differently?
Then agree on your core hours in writing, if you have not already. Predictable availability matters more than long availability. Being reliably online for your agreed overlap beats being online all day and slow to reply.
Habits worth keeping
- Write in full sentences. Assume the reader is in another timezone and will act on your message without asking a follow-up.
- Put decisions in writing, even if they were made on a call.
- Reply to direct questions within your working hours, even if only to say when you will have an answer.
- Protect your evenings. A remote job that slowly takes over your nights is not sustainable.
Our first 30 days guide turns this plan into a checklist you can tick off as you go.