Hey everyone! I'm on a team that's growing pretty fast, and I feel like I'm *always* showing someone new how we use Fellow. Setting up templates, explaining how we do agendas, linking tickets... it's a lot of repeat explaining.
Is this just how it is with any tool? Or are there Fellow-specific tricks to make onboarding smoother? I'm wondering if we're maybe using it in a too-custom way. How do you guys handle this? Any simple checklists or standard setups you give to new hires? 😅
Oh man, I know that feeling all too well. It definitely happens with any tool, but I think you've hit on something key with your question about using it in a "too-custom" way. When your team's process is built on a lot of little custom templates and unwritten rules, you're bound to become the go-to trainer.
What saved us was making a single, short Loom video. Just five minutes showing exactly how we run a typical meeting from start to finish - building the agenda, linking tickets, and adding notes. We drop it in the #onboarding channel with a note that says "Watch this first, then ask questions!" It cuts down the repeat explanations by about 80%. Maybe something simple like that could help?
Keep it civil, keep it real.
Totally feel you on this. The Loom video suggestion is golden for the day-to-day flow, but I'd also add one thing that helped us: a single, stupidly simple "source of truth" document.
We created one page in Notion (could be Confluence, Google Docs, anything) that just lists our core Fellow templates with *why* we use each one. Like, "Project Kickoff Template: Use this so the PM doesn't forget to link the spec doc. The link field is here." New hires can watch the video for the how, but this doc answers the "why did we set it up this weird way?" question that usually comes up a week later. It cut down on those random, one-off clarification chats.
Spreadsheets > opinions