How to Onboard New Team Members When Your Agency Uses 4 Different PM Tools

You've hired a new designer. It's their first day. You need to get them productive in a week.

But before they can start designing, they need access to: Asana (client project tracking), Figma (design files), Slack (team communication), your shared folder (brand assets), the client's Jira (where some requirements live), and two documentation wikis.

That's nine systems to explain on day one. Most onboarding goes sideways here.

Better approach: structured process that makes multi-tool onboarding clear instead of overwhelming.

The Pre-Onboarding Checklist

Before the hire's first day, you've prepared:

Accounts created in all tools (Asana, Linear, Jira, ClickUp, Figma, Slack, docs)
Permissions configured (team access, client access, read-only vs. edit)
One-page tool guide: "Here's which tool is for what"
Their manager identified and briefed
Project assignment decided
30-minute onboarding slot scheduled day one

This takes 30 minutes of prep work. It prevents hours of confusion during onboarding.

The One-Page Tool Guide

Create a simple one-page guide for your agency. Something like:

Project Management

Asana: Client project tracking, timelines, deliverables
Linear: Engineering work, code-related issues
Jira: Legacy client requirements (Client X only)
ClickUp: Internal operations and team projects

Design & Collaboration

Figma: All design work, active files
Slack: Quick communication, decisions, questions
Google Drive: Shared assets, templates, archives

Documentation

Wiki (Confluence/Notion): Processes and standards
GitHub: Code and technical documentation

Communication

Email: Client communication and formalities
Slack: Day-to-day team chat

Print this one-pager. Laminate it. Give it to every new hire day one.

This takes the mystery out of the question "where is X?" They have the answer immediately.

Day One Onboarding (2 hours)

Hour 1: Systems and Access (30 minutes)

Walk through:

Show them the tool guide
Open each account in their presence, confirm access
Spend 2 minutes on each tool: "Here's what this tool is for, here's where your work lives, here's how you get help"

You're not teaching them how to use each tool. You're showing them what exists and where to find help.

Hour 1: Their Project and Role (30 minutes)

Show them their project (the thing they'll be working on)
Show them who's on the team
Show them the project timeline
Answer: "What am I doing this week?"

Don't overwhelm them with detail. Just orientation.

Hour 2: Daily Workflow (1 hour)

Walk through a typical day:

"When you arrive, you check [tool]. You see what's assigned to you. You work on whatever's due soon.

If you get blocked, you ask in Slack. We meet at 10 AM daily standup.

You report what you're working on. End of day you update your status in [tool]."

This is the concrete workflow. It's how they'll spend their time.

Day Two - Tool Close look (by role)

By the new hire's role, do one longer session on the primary tool they'll use.

For a designer:

Close look on Figma (30 mins)
How to find your projects
How to give and receive feedback
How design files are organized

For an engineer:

Close look on Linear (30 mins)
How to pick tasks
How to move work through the pipeline
How to unblock yourself

For a PM:

Close look on Asana (30 mins)
How to manage projects
How to report status
How to communicate across tools

This is where they learn the actual mechanics. But they only dive deep on their primary tool day two.

Day Three - Async Training

Instead of more meetings, send async resources:

Video walkthrough of each secondary tool (5-minute clips)
Written FAQ: "How do I... in [tool]?"
Links to official help documentation

Let them learn at their own pace. They don't need to become experts in Linear if they're a designer.

The Buddy System

Assign a buddy (peer, not manager) to answer day-to-day questions. This buddy is:

Someone who works in the same tool(s)
Patient and good at explaining
Available for 15-minute coffee talks this week

This prevents them from having to escalate every small question to their manager.

The One-Week Review

Friday of week one, sit down with the new hire:

"How's it going? Any tools that are confusing?

Any access issues? What do you need to be more productive?"

Fix any problems immediately. Maybe they need better documentation.

Maybe a tool is confusing. Maybe you misconfigured access.

This feedback loop makes onboarding better for everyone.

Common Mistakes in Multi-Tool Onboarding

Teaching instead of orienting - Don't teach them how to use Asana on day one. Show them it exists, show them where their work lives, tell them where help is. They'll learn by doing.

Too much detail too fast - "Here are all the statuses in Asana and how to use each one..." STOP. They need to know: how to see their assigned tasks. That's it.

No one-page reference - If they have to remember everything you said, they won't. Give them something to reference.

Skipping manager prep - Managers should be briefed: "Your new hire is coming. Here's their first project. Here's their first week's priorities." Managers shouldn't be surprised.

Assuming they'll figure it out - They won't. Structured onboarding is faster than hoping they eventually understand.

Making It Self-Service

As you onboard more people, create self-service materials:

Video tour of each tool (5 mins each)
Typed FAQ for common questions
Loom recordings of common workflows
Slack bot that answers "where is X?" automatically

This lets new hires be more self-sufficient and reduces onboarding burden on your team.

For Distributed Teams

If your team is remote:

Async-friendly one-pager (especially important)
Recorded video walkthrough (better than live calls)
Async buddy system (can answer questions via Slack, not requiring sync time)
Weekly check-in instead of daily (respect time zones)

FAQ

How long should onboarding take?

One week to be minimally productive. One month to be fully independent. If it takes longer, your tool structure is too complex.

Should we test that they understand?

Not formally. Just observe: are they asking where things are?

That's a signal something in your guide is unclear. Update the guide.

What if we add new tools?

Update the one-pager. Tell existing team members about the change. It's not a big deal if you're intentional about it.

Should new hires train on every tool?

No. They should train on their primary tool and understand that others exist. Secondary tools they learn as needed.

What's the cost of bad onboarding?

Someone doesn't know which tool to use for work. They put it in the wrong place. It gets lost.

Or duplicated. Or done twice. Bad onboarding costs hours.

How often should we update our tool guide?

Quarterly minimum. If you add a tool, immediately. If you change a process, update it.