Team Introduction
Introduce your team to stakeholders, new hires, or cross-functional partners. This 7-slide template covers your mission, team lead, members, what you own, how you work, and how to connect with you.
Who This Template Is For
This template is designed for team leads, department heads, and managers introducing their team. Use it when you need to:
- ✓ Present your team at a company all-hands or new hire orientation
- ✓ Help cross-functional teams understand what you do and how to work with you
- ✓ Create a reference document for your team's responsibilities and processes
- ✓ Introduce a newly formed team or reorganized department to the company
Slide-by-Slide Breakdown
- 1Title
Team name and parent organization. Clean and professional.
- 2Team Mission
What you do, why it matters, and your core principles. Gives context for everything else.
- 3Team Lead
Manager profile with background and a personal quote. Puts a face on the team.
- 4Team Members
Full team roster with roles and brief descriptions. People can see who to contact.
- 5What We Own
Infrastructure, services, and responsibilities. Defines your team's scope clearly.
- 6How We Work
Rituals, request process, and response times. Makes it easy to collaborate.
- 7Connect With Us
All channels and links in one place. Removes friction for reaching out.
Complete Markdown Template
Copy and paste into Slidepicker# Meet the Data Platform Team
## Engineering Division | Waveform Technologies
---
# Our Mission
We build and maintain the **data infrastructure** that powers every product at Waveform.
Our goal: make it possible for **any team** in the company to access, analyze, and act on data within minutes, not days.
- We own the data pipeline, warehouse, and self-service analytics tools
- We serve 14 internal teams and process 2.8 billion events per day
- We believe in reliable infrastructure, clear documentation, and fast feedback loops
---
# Team Lead
**Sophie Andersen** - Senior Engineering Manager
- 10 years in data engineering, previously at Spotify (Data Platform) and Segment
- Joined Waveform in 2022, built the team from 3 to 12 engineers
- Passionate about data democratization and reducing time-to-insight
*"The best data platform is one that nobody has to think about. It just works, and the data is always there when you need it."*
**Slack:** @sophie.andersen | **Email:** sophie@waveform.io
---
# Team Members
- **Kai Nakamura** - Staff Engineer, Pipeline Architecture (7 years, data systems expert)
- **Lena Vogt** - Senior Engineer, Real-Time Streaming (Apache Kafka, Flink)
- **Omar Hassan** - Senior Engineer, Data Warehouse (dbt, Snowflake)
- **Yuki Sato** - Engineer, Data Quality & Observability (Great Expectations, Monte Carlo)
- **Ava Chen** - Engineer, Self-Service Analytics (Metabase, internal tools)
- **Daniel Okeke** - Engineer, ETL & Integrations (Airbyte, custom connectors)
- **Marta Kowalska** - Engineer, Infrastructure & DevOps (Kubernetes, Terraform)
- **James Park** - Junior Engineer, Pipeline Development (joined October 2024)
- **Priya Sharma** - Data Analyst, Internal Analytics & Reporting
- **Tom Rivera** - Technical Writer, Documentation & Developer Education
---
# What We Own
**Infrastructure:**
- Data pipeline (ingestion, transformation, delivery) - 2.8B events/day
- Data warehouse on Snowflake (42TB, 180+ tables)
- Real-time streaming platform (Apache Kafka, 14 topics)
- Self-service analytics tools (Metabase, 300+ dashboards)
**Services we provide:**
- New data source onboarding (average: 3 business days)
- Custom dashboard creation for any team
- Data quality monitoring and alerting
- Pipeline incident response (15-minute SLA during business hours)
---
# How We Work
**Rituals:**
- **Daily async standup** at 9:30 AM in #data-platform-standup
- **Weekly team sync** every Tuesday at 11 AM (all team, 30 min)
- **Bi-weekly sprint planning** every other Monday
- **Monthly architecture review** (open to all engineers in the company)
**How to request work from us:**
- File a request in Linear under the "Data Platform" project
- Tag @data-platform in Slack for questions
- For urgent issues: page us via PagerDuty (#data-platform-oncall)
**Response times:**
- Slack questions: same business day
- New data source requests: scoped within 48 hours
- Pipeline incidents: 15-minute response during business hours
---
<!-- invert -->
# Connect With Us
- **Slack:** #data-platform (general) | #data-platform-support (requests)
- **Linear:** Data Platform project board
- **Documentation:** notion.so/waveform/data-platform
- **Office hours:** Thursdays 2-3 PM (drop-in, no agenda needed)
We are here to help you work with data.
**Don't hesitate to reach out!**Use This Template Now
Open Slidepicker, paste the Markdown above, and your team introduction is ready. Replace the sample team with your own members, mission, and processes.
Open Slidepicker - It's FreeRelated Templates
Training & Onboarding
10 slidesWelcome new hires with company overview and first-week plans.
For: HR & Team Leads
Company All-Hands
8 slidesShare company updates, wins, and roadmap with the entire team.
For: Leadership
One-on-One Review
7 slidesStructure productive performance review conversations.
For: Managers & Reports
Frequently Asked Questions
When should I present a team introduction?
Common occasions include company all-hands meetings, new hire orientations, cross-functional kickoffs, and after a team reorganization. This template also works well as a standing reference document that lives in your company wiki or internal docs.
How detailed should the team member descriptions be?
Keep it brief: name, title, area of focus, and optionally one distinguishing detail (years of experience, area of expertise). The goal is to help people know who to contact for what, not to provide full bios. Link to individual profiles in your company directory for more detail.
Should I include the "How We Work" section?
Yes, it is one of the most useful slides for other teams. Knowing how to request work, expected response times, and your team's rituals dramatically reduces friction. Without it, people resort to Slack messages and drive-by requests that disrupt your workflow.