“Let's go around and introduce ourselves.”
You know your name and your job. The awkward part is deciding how much of your history the room needs.
Start with your name, your work, and your connection to this meeting:
Hi, I'm Maya. I work on customer support, and I'm here to share the questions people ask during setup.
That gives the group something to remember and a reason to listen when you contribute.
The eight examples below are written for a quick introduction round, roughly 15 seconds at a comfortable pace. Follow the host's instructions if they ask for something longer. You can adapt every example to your own work.
For what comes after the introduction, see our guide to speaking up in meetings.
A Simple Meeting Introduction Template
Hi, I'm [name]. I [describe your work]. I'm here to [contribution, question, or purpose].
The final part changes with the room:
- Contribution: “I'll share what we heard in customer interviews.”
- Question: “I'm here to understand which deadlines depend on our team.”
- Purpose: “I'll be coordinating the launch once we agree on the scope.”
Use the words a colleague would use to describe your work. “I help new customers get set up” can tell an unfamiliar team more than an internal job title.
A longer networking pitch has a different setting; MIT's career toolkit covers introductions of 30–60 seconds. For a quick meeting round, the short examples here give you a starting point.
Jump to: eight introduction examples, shortening an introduction, or a two-minute rehearsal.
Eight Short Meeting Introduction Examples
1. Your First Team Meeting
Hi, I'm Noor. I joined the design team this week, and I'll be working on account setup. Today, I'd like to learn where people are getting stuck.
This says what you will work on and gives colleagues a useful opening. Replace the final sentence with a real question you have about the team's work.
You do not need to apologize for being new. If the host asks for a personal detail, add one you are comfortable sharing.
2. A Meeting With Another Department
I'm Luis from finance. I help teams plan project spending. I'm here to understand the proposed timeline so we can agree on a budget that fits it.
Describe the connection between your work and theirs. An unfamiliar acronym or internal team name may not explain why you are attending.
For a technical role, translate the responsibility into plain language: “I work on keeping checkout reliable” or “I help the team find errors before a release.” Our technical explanation guide goes further into this.
3. Your First Client Call
Hi, I'm Erin. I'll be your main contact during setup. Today, I want to understand your team's priorities and agree on the first steps together.
Tell the client what they can expect from you. “Main contact during setup” is useful because it explains when they should come to you.
If someone else owns the relationship, be specific about your part instead: “I'll handle the data transfer” or “I'm joining to answer questions about training.”
4. A Project Kickoff
I'm Dev, and I'll coordinate the website launch. I'll track the shared dates and dependencies. Today, I need to confirm who owns each part of the work.
This introduction names a responsibility and the information needed to carry it out. It gives you a natural way to contribute during the discussion.
Save the full timeline for the relevant agenda item. Once the project is underway, use a concise project status update to report progress.
5. A Large Online Meeting
Hi, I'm Hana from the London support team. I review customer feedback, and I'm here to share the issues people raise most often after a new release.
In a large call, your location or team can help place you when it matters to the discussion. You can leave it out when it adds nothing.
Check that your display name is recognizable. If your microphone fails, put the same short introduction in the chat instead of trying to deliver a longer explanation over broken audio.
6. A Senior Leader Joining a Working Session
I'm Morgan, and I lead operations. I'm here to understand the rollout risks and help resolve decisions the team cannot make alone.
Say what you can contribute without taking over the introduction round. If you are attending to listen, say so plainly.
Avoid making a broad promise such as “I can solve anything you need.” Name the decisions or resources you actually control.
7. Someone Attending as a Specialist
I'm Amara, the accessibility specialist on this project. I'll review how the proposed design works with assistive technology and flag questions we should resolve before testing.
Give people a clear idea of when your expertise is relevant. There is no need to list every qualification unless the context calls for it.
If you have been invited for one agenda item, name that item. It explains your presence and makes the handoff easier.
8. A Meeting Where People Already Know You
You know me from customer support. For this launch, I'm collecting the training questions and turning them into a short guide. I'll share the first draft on Friday.
You can skip the repeated biography and introduce your role in this piece of work.
If the host does not ask for introductions and everyone already knows the relevant roles, you may not need one at all. Join the discussion when you have something useful to add.
How to Shorten an Introduction That Runs Long
A long introduction often contains several useful facts. Choose the ones that matter to this group today.
Before:
Hi, I'm Alex. I've been here for about three years. I started in support and moved into product last year. Before that, I worked at two smaller companies, mostly doing customer research and some project work. At the moment, I'm involved in a few things, including checkout, which is why I'm here.
After:
Hi, I'm Alex. I work on the checkout experience. I'm here to share what customers found confusing in our latest interviews.
The shorter version keeps the current work and the contribution. The career history can wait for a conversation where it is relevant.
Try cutting these first:
| Detail | Keep it when… |
|---|---|
| Previous jobs | They explain experience the group needs to understand |
| Years at the company | The host asks, or the history matters to the discussion |
| A personal interest | The introduction round is social or explicitly asks for one |
| An internal title | People in the room know what it means |
| A project summary | It is needed to explain your role; save the full update for later |
If trimming is difficult because you keep adding context, try the exercises in how to stop rambling.
How to Sound Natural Without Memorizing Every Word
Write three notes: name, work, purpose. Say the introduction once from those notes, then again with slightly different wording.
Keep the facts steady. Let the connecting words change.
Pause briefly after your name if you tend to run straight through it. Finish the final sentence, then give the next person room to speak. You do not need a closing line such as “And that's everything about me.”
Use a normal speaking pace. If the introduction takes longer than the host allows, remove a detail before trying to say every word faster.
If people ask about your work afterward, you have room to add context in the answer. Our guide to workplace small talk offers ways to continue that conversation.
What If You Join Late or the Host Skips Introductions?
If you arrive while someone is speaking, wait for a natural opening. Where chat is available, a short message can supply your name and role without interrupting:
Hi, I'm Alex from the checkout team. I'm joining for the customer research discussion.
If you need to speak before the host introduces you, use a brief lead-in:
I'm Alex, the designer working on checkout. Could I clarify one point about the test?
When you host, tell people what you want from the round: “Please share your name, your role in this project, and one question you want us to answer.”
Stanford's meeting guidance from Matt Abrahams emphasizes defining the purpose and helping people participate. A specific introduction request is one practical way to apply that approach.
A Two-Minute Rehearsal Before the Meeting
- Write your name, work, and purpose as three short notes.
- Record one introduction without reading a full script.
- Listen once: can you hear your name, understand your work, and tell why you are attending?
- Remove one unnecessary detail and record it again.
- Imagine someone asks, “What are you working on first?” Give a short answer.
Practice aloud at the pace you expect to use. Toastmasters' rehearsal advice recommends speaking aloud and making feedback specific.
Articulated is another way to practice a spoken answer and review AI feedback before trying again. Premium app practice requires a subscription; the examples and phone-recording exercise here are free.
Keep Reading
Frequently asked questions
How do you introduce yourself in a meeting?
Say your name, describe the work you do, and connect it to the meeting. For example: 'I'm Alex, the designer working on checkout. I'm here to understand what customers find confusing before we change the form.'
How long should a meeting introduction be?
Follow the organizer's instructions. For a quick introduction round, aim for one or two sentences, often around 15 seconds at your normal pace. Allow more time when the group asks for background or the meeting is specifically about getting to know one another.
What should I say when I am new to the team?
Share your name, what you will work on, and something specific you want to learn from the group. You can be friendly without giving your full work history or apologizing for being new.
How do I introduce myself when everyone knows my name?
If an introduction is still needed, explain your role in this particular discussion. State what you are bringing, what you need to understand, or which part of the work you own.
Should I introduce myself if I join a meeting late?
Avoid interrupting someone mid-sentence. Use the chat to give your name and role if appropriate, then wait for a natural opening or the host's invitation. A brief introduction is usually enough.
Before your next meeting
Make your next introduction easier to follow
Use Articulated's speaking drills to practice getting to the point. Review feedback on clarity and structure, then bring one adjustment to your introduction. Premium app practice requires a subscription.
Learn more →More in Workplace Communication and Interviews
Keep building this skill
How to Sound Confident in Job Interviews
Evidence-based techniques to project confidence, structure your answers clearly, and stop freezing under pressure during job interviews.
Communication Skills for Engineers
Why technically brilliant engineers get lost in meetings, and research-backed frameworks to explain complex ideas clearly.
How to Explain Technical Work to a Nontechnical Audience
Use a five-level translation ladder, analogy test, decision-first structure, and worked engineering example to explain technical work clearly without dumbing it down.