# Your first 30 days at Instfy

<p class="lead">Your onboarding roadmap at Instfy: what happens before your first day, during your first week and through the end of your first project cycle.</p>

Welcome to Instfy. This guide is for people who have just joined the team. It organizes your first 30 days into short stages, with what we expect from you and what you can expect from us at each point. The idea is simple: apply with you the same logic we apply with clients. First understand, then take part and then deliver.

!image[The team welcoming a new colleague in the first days](/assets/img/pessoas/team-onboarding.webp)

## Before your first day

Between accepting the offer and your first day, your area lead prepares for your arrival.

<ol class="steps">
<li><strong>Paperwork:</strong> you receive guidance on the documents and formalities for your type of engagement, which vary by country and role.</li>
<li><strong>Access:</strong> we create your company email and your user in <strong>ERP Instfy</strong> and in the other tools your role uses, with the necessary permissions.</li>
<li><strong>Point person:</strong> we name the person who will support you during your first weeks and answer day-to-day questions.</li>
<li><strong>First-week schedule:</strong> you receive the plan for your first days, with conversations, reading and introductions.</li>
</ol>

:::warn
Your credentials are personal. Never share passwords, and turn on the security features the team recommends. If any access is missing, tell your point person instead of using someone else's access.
:::

## Week 1: understand

Your first week is your **Understand** stage. The goal is not to produce, it is to build context.

### Culture and way of thinking

Read, in this order:

1. [Who we are](#/instfy): the story of Instfy and where our way of working comes from.
2. [How we think](#/how-we-think): the logic behind every decision.
3. [Culture and principles](#/culture): the behaviors we expect.
4. [Instfy methodology](#/methodology): the eight stages we use in every project.
5. [How we work](#/how-we-work): the core, the network of skills, cycles and the six questions.

### Ecosystem and services

Learn what Instfy offers, even if your role does not work directly with every product. Clients ask questions, and you will understand projects better.

- The [product ecosystem](#/ecosystem) and the overviews of [ERP Instfy](#/introduction), [Instfy AI](#/instfy-ai), [Instfy Data](#/instfy-data), [Instfy Rewards](#/instfy-rewards) and [Carbon by Instfy](#/carbon).
- The [service charter](#/services) and [Assessments by segment](#/assessments).
- [I just hired Instfy](#/instfy-onboarding): the journey our clients go through.

### Tools

We use **ERP Instfy** itself for internal management. During your first week, log in for the first time and get to know the modules that are part of your routine:

| What for | Where in the ERP | Guide |
|---|---|---|
| Your employee data, attendance and leave | *HRM* | [HR, attendance, leave and payroll](#/hrm) |
| Projects and tasks you work on | *Project > Projects* | [Projects](#/project) |
| Logging hours by project and task | *Timesheet* | [Timesheet](#/timesheet) |
| First access and navigation | Login screen and side menu | [First access](#/first-access) and [Interface](#/interface) |

:::tip
Instfy Docs is your first place to look things up. Press the **/** key on any page to search. If you find something outdated or confusing, let us know: improving the documentation is also work.
:::

### First-week conversations

- A welcome conversation with your area lead to align expectations and goals for your first 30 days.
- Introductions to the people in the core you will work with most closely.
- An overview of the ongoing projects you will work on.

## Weeks 2 to 4: take part and deliver

### Week 2: shadow closely

You follow the work on an ongoing project alongside your point person: you attend meetings, read the decision records and see how the six questions are applied in practice. This is the time to ask a lot of questions.

### Week 3: first deliverable

You take on a first deliverable with a defined scope. It follows the same standard as any Instfy initiative: **goal, owner, deadline, metric and expected result**. Its size is designed so you can finish it with quality, not to test your limits.

### Week 4: first full cycle

You take part in a project cycle from start to finish, including the decision point. At the end, have a 30-day conversation with your lead: what worked, what was hard, what you learned and what the goals are for the coming months. See how we continue from there in [Development and career](#/career-growth).

## The rituals you will encounter

| Ritual | What it is | Why it matters |
|---|---|---|
| Work cycles | Work moves forward in short cycles, with deliverables validated at the end of each one. | Keeps focus and allows course corrections early. |
| Decision points | Formal moments to decide whether to continue, adjust or stop an initiative. | Prevents decisions from happening by inertia. |
| Six questions | What, why, who is responsible, when, how much it costs and how we will know it worked. | Ensures every initiative has direction and an owner. |
| Decision records | Decisions, hypotheses, changes of direction and lessons learned are documented. | Anyone can understand what was decided and why. |
| Time logging | Hours for each project and task are logged in the ERP's *Timesheet*. | Shows the real effort and helps plan future projects. |

## First 30 days checklist

| Item | When | Done |
|---|---|---|
| Hiring paperwork submitted | Before day 1 | ☐ |
| Company email and ERP Instfy accessed | Day 1 | ☐ |
| Data checked in the *HRM* module | Week 1 | ☐ |
| Culture and methodology reading completed | Week 1 | ☐ |
| Welcome conversation with leadership | Week 1 | ☐ |
| Product ecosystem and service charter read | Week 1 | ☐ |
| Shadowing on an ongoing project | Week 2 | ☐ |
| First hours logged in *Timesheet* | Week 2 | ☐ |
| First deliverable completed | Week 3 | ☐ |
| Participation in a decision point | Week 4 | ☐ |
| 30-day conversation with leadership | Week 4 | ☐ |

## Who to ask

| Topic | Talk to |
|---|---|
| Day-to-day questions, routines and tools | Your point person |
| Priorities, goals and expectations | Your area lead |
| Scope, deadlines and decisions on a project | The project lead |
| Access and permissions | Your area lead, who contacts the person in charge |
| Personal data and privacy | dpo@instfy.com |

## Frequently asked questions

### What happens during my first week at Instfy?

Your first week is dedicated to building context: reading about culture, methodology and the ecosystem, first access to the tools, a welcome conversation with leadership and introductions to the people and projects you will work with.

### What tools will I use day to day?

We use ERP Instfy for internal management, with the HR, Projects and Timesheet modules, plus the tools specific to your role, which are set up before your first day or right at the start.

### When do I make my first deliverable?

Usually in the third week, after shadowing an ongoing project. Your first deliverable has a defined scope, with a goal, deadline and metric, and is sized so it can be completed with quality.

### What if I have questions that are not in the documentation?

Ask your point person or your area lead. Asking early is part of our culture, and if the answer should be in Instfy Docs, suggest adding it.

### How do I know if I am doing well in my first month?

In the fourth week there is a 30-day conversation with your lead to review what worked, what was hard and the goals for the coming months. You do not need to wait for it to ask for feedback.

## Next steps

See how people grow at Instfy after the first 30 days.

:::related
career-growth, culture, methodology, how-we-work, hrm, timesheet
:::