How-to: Introduce Yourself to the Team

Sep 30, 2026 | First 90 Days, How-tos

Your team intro is not a personal brand launch. It is a clarity gift: who you are at work, what you own, how to reach you, and that you intend to learn how work already moves. A tight intro lowers the cost of the first collaboration and prevents people from inventing a story about you from your LinkedIn headline alone.

Time box: 45–60 minutes total (10 minutes to draft, 5 minutes live if there is a standup, 10 minutes to post, plus light replies the same day).

Home base: New hire hub and the early arc of your first 90 days. Pair with day-one checklist and later pick an early win. ICs can borrow tone from the Individual Contributor hub; new managers introducing themselves to reports should also skim the New Manager hub.

When to use / when not

Use when:
– You joined in the last few days and not everyone has met you
– The team is distributed and will not bump into you in a hallway
– You changed roles internally and need a reset with stakeholders
– Cross-functional partners will work with you soon

Do not use when:
– You are mid-sensitive investigation or restricted from broad communication
– Leadership asked for a sequenced rollout (exec first, then team)
– You are replacing someone who just exited under painful circumstances and timing needs manager guidance
– You plan a long manifesto about “how I work” before you have listened

A good intro is short, kind, and operational. Save philosophy for week four.

Prep

Confirm channel norms with your manager: Slack channel, email list, standup, or all-hands
Get the correct team name, your title as HR lists it, and start date
List closest collaborators outside the team (support, sales, design, finance partners)
Draft two versions: 60-second live and 120–180 word written
Decide one hobby or human detail that is safe and light (optional, not mandatory)

If your work sits on revenue or handoffs, a light nod toward how sales works or how departments work together can wait until you have a real ask. Do not lecture the org chart in your hello.

Steps

Align with your manager (5–10 min). Ask where intros usually land and whether anyone needs a private heads-up first (for example, a peer who covered the role).
Draft the written note (15 min). Role, scope boundaries you know, how to contact you, what you are optimizing for in week one (listening), and a simple ask (“tell me how you prefer handoffs”).
Deliver a live hello if a forum exists (2–3 min speaking time). Standup or team meeting. Smile, keep hands out of your pockets or off three devices, then stop.
Post the written intro the same day (5 min). Same facts as live. Pin if the channel allows and culture supports it.
Send three targeted hellos (15–20 min). Buddy, key partner, and one quiet stakeholder who is easy to miss. Personal beats broadcast-only.
Reply to welcomes within a day (10 min). Accept coffee chats selectively; do not fill the week with thirty intros and no learning time.
Log names and context in your people map from day one.

Directors entering a wider surface area can stage intros: team first, then peer leaders, using patterns in the Director / VP hub.

Script (what to say / send)

Live (60 seconds):

“Hi, I am [name]. I joined as [role] on [team]. I will spend the first weeks learning how work moves and where I can help without breaking what already works. Best reach: [Slack/email]. Glad to be here. I will drop a short note in [channel] with details.”

Written team note:

Hello [team]!

I am [name], [title], starting [date]. I will focus on [one-line scope]. In my first weeks I am here to listen: how requests come in, what “done” looks like, and where handoffs get painful.

How to reach me: [Slack handle], [email], timezone [X]. For urgent flags, [preferred path].

Before here I [one neutral line of background]. Outside work I [optional light detail].

If you have a preferred way to collaborate or a doc I should read first, send it my way. Thanks for the welcome.

Targeted partner ping:

Hi [name]: I just joined as [role]. I expect we will collaborate on [surface]. Would love a 15-minute context chat in the next two weeks, or your favorite doc if async is better. No rush on day one.

If you are an internal transfer:

Same human, new seat: I moved from [old team] to [new role] on [date]. What changed for you: [routing / owners]. What did not: [how to reach me]. Thanks for patience during the handoff window.

If the prior role holder is still around:

Grateful to [name] for coverage and context. I will shadow and transition in stages rather than flipping every ownership overnight.

Output artifact

Intro kit:

Live script (bullet card)
Written channel post (final text)
List of 5–10 targeted follow-ups with dates
Updated people map entries
Optional: pinned “about me / how to work with me” doc linked once, kept short

Keep a copy for your 30/60/90 notes so you remember what you signaled. For HR-sensitive transitions (leave coverage, role elimination aftermath), confirm messaging with your manager and, when needed, guidance aligned with how HR works.

Watch-outs

Writing a novel. If people need scrolling stamina, they will skim and miss how to reach you.
Overclaiming ownership before you understand boundaries. Tentative scope plus listening beats a turf speech.
Joke-heavy intros that age poorly in text search forever.
Ignoring time zones and response expectations. State them once.
Skipping the quiet teammates. Broadcast plus three intentional pings beats broadcast alone.
Turning intro chats into complaint sessions about your last employer. Stay forward.

Done looks like: the team can spell your name, know your role, know how to reach you, and believe you will learn before you rearrange their world. That is enough social capital to start.