The first thirty days: how to welcome a dedicated team member
The first month of a dedicated team member sets the tone for everything after it. People who are welcomed well become productive faster, ask better questions and stay longer. People who are left to figure it out alone often become quietly discouraged. Here is a simple plan we use, with examples from ServiceNow and AI work.
Before day one Decide who will introduce the person, what access they need and what they will work on first. Access delays are the most common reason a new person spends their first days waiting. For a ServiceNow developer, that means accounts on the right instances and the right roles. For an AI engineer, it means access to the data they will work with, approved in advance.
Week one: learn the landscape Spend the first week on understanding, not delivery. A new ServiceNow administrator should sit with the service desk for a while, see how requests arrive, look at how the change process works and read the documentation that exists. A new AI engineer should learn what decision the feature supports, who uses it and what the review rules are. Give them one small, real task by the end of the week, so they have something concrete to finish.
Week two: do real work, with support Assign a modest piece of real work and pair the person with a colleague. For a ServiceNow developer that might be a small catalog item or a portal change. For an evaluation specialist it might be building a set of test examples for an existing feature. Encourage questions and answer them without impatience.
Week three: widen the scope Increase the size and independence of the work. Review it together and talk about what went well and what did not. Introduce the person to more of the team, including those who use what they build.
Week four: agree what good looks like At the end of the first month, sit down and agree how things are going. Ask the team member what would help. Ask yourself whether their role, their workload and their tools are right. Decide the next month’s goals.
Things that help throughout
- A named buddy who is not the manager.
- A short document explaining how your team works, including unwritten rules.
- Regular check-ins that ask how the person is, not only what they have done.
- Clear expectations about how AI tools may be used and who checks the results.
Things that hurt
- No access for the first week.
- Vague tasks with no owner.
- Silence, which the new person may read as disapproval.
A good first thirty days does not need much time. It needs attention, a plan and a little patience.