A team intro deck is the new hire's first sense of the team. Build it to compress months of context into thirty minutes.
The team intro is the new hire's map of the territory
The first day of any new role is overwhelming because the new hire has to absorb dozens of names, projects, processes, and political subtleties without a map. A great team intro deck is that map. It compresses what would otherwise take three months of one-on-ones into a single thirty-minute session, which is the single highest-leverage onboarding investment a manager can make. The structure that works is people first, projects second, process third, and politics never explicit but always implied through the choice of what to highlight.
The people section: photos, names, what they actually do
The people section should include every team member's photo, name, role, and a one-sentence description of what they actually work on day to day — not their job title. Job titles are abstract; daily work is concrete. The new hire needs to know who to ask about what, and the daily-work description is what answers that question. Include reporting relationships visually with a small org chart so the new hire can place every name within the team's structure.
The projects section: what is shipping, what is blocked
The projects section should list the team's current active projects with a one-sentence status for each: what is shipping this quarter, what is blocked, what is exploratory. The status should be honest, including the projects that are not going well. New hires read the honesty of this section as the truest signal of the team's culture, and the trust earned by being honest pays back in faster ramp time and earlier productive contribution.
For a deeper companion read on this topic, see our recommended editorial guide.
The process section: rituals, tools, decision rights
The process section should cover the team's core rituals — standup, planning, retro, demos — with the day, time, and purpose of each. It should also cover the primary tools the team uses and where to find access. Most importantly, it should cover the decision-rights model: which decisions does the team make autonomously, which require manager approval, which require cross-team alignment. Decision rights are the single most underexplained element of most onboardings, and explicit clarity here saves weeks of confusion.
The first-30-days section: concrete deliverables, not vague exploration
The team intro deck should end with a slide laying out the new hire's first thirty days — the people they should meet, the documents they should read, the small concrete deliverable they should ship, and the manager check-in cadence. Concrete deliverables in the first month are what create early wins and confidence; vague 'get to know the team' instructions create anxiety and drift. The DeckForge AI team intro templates include a structured first-30-days layout for exactly this.
Working through this with your team? Our recommended workshop facilitation guide has a battle-tested run-of-show.
Templates that pair with this guide
The templates below are pre-structured around the playbook in this guide. Each one ships in both Google Slides and PowerPoint, and the master grid is set up for the slide-by-slide pacing the guide recommends.