Todos os vídeos

Create an onboarding stack in Dropbox Dash

Transcrição

Create an onboarding stack in Dropbox Dash

Putting myself in the perspective of an HR manager who needs to build a better onboarding path for new employees, I need to start by gathering all of my information. Luckily, my organization has Dash and my admin has connected all of our tools where we store the information, which means instead of tool switching and running the same query over and over again, I can run one single query in Dash for the relevant material. So I'll do just that.

Once Dash has surfaced the relevant information, I can start by selecting docs, keeping a few things in mind.

Anything with this blue check mark means that an admin has verified it as accurate and up to date.

And if I need clarity on any of the information, I can click summarize and ask.

So as I select all of my relevant docs, my suspicions are confirmed that all of these documents are held across tools like Dropbox, Microsoft, and Google Drive.

So once I've pulled everything together, I'll hit save stack and create stack. Just to save a little bit of time, I'll show you what it looks like after I've edited a little Since I put all of my documents together in one place, it was pretty helpful enough, but I wanted to add some structure to it. So I added some branding at the top to make it look more professional, as well as a title that conveys the purpose of the stack.

Then I added a description to give the reader an understanding of what they can expect from this collection. And next, I grouped everything into sections with a sub description under each. This makes it more a curated experience for my new employee to walk through. And if I had a lot of visual assets to give them, I would toggle from list to grid view.

But since everything is pretty straightforward, I'll stick with the list view. Once I've made the stack the resource I want it to be, I've got three final considerations. The first is how much I want to customize this stack to make it for one employee versus organization wide. I have an option to duplicate and add more one employee specific resource like a personalized checklist or perhaps a personal welcome email.

The second consideration is how this will be shared. If I chose to make it a duplicate and share direct to this one employee, I would toggle to only those invited and consider giving them edit access so they could continue to customize this asset for themselves. But if I choose to keep this more general for the company, I would put the access at anyone at my company and keep it on can view, so only my team controls the stack.

The last consideration is how I send. I can invite anyone direct through the stack itself, or I can choose to copy the link and paste it into a company message or an email for their first day.