Introduce your team to Stackby

Bring everyone up to speed with a clear announcement, a simple onboarding path, and the right support. This guide gives plug‑and‑play messaging, concrete steps, and practical tips to ensure fast adoption.

Introduce your team to Stackby

Set context before granting access. Explain why Stackby is being adopted, what will improve for each role, and what happens next. Then invite collaborators with the right permissions and provide a short, focused training.

1. Draft your Stackby launch announcement

Share the “why,” the outcomes, and what to expect. Keep it short, benefit-led, and action-oriented.

Example message for introducing Stackby

Subject: We’re moving our workflow to Stackby — here’s what to expect
Hi team,
We’re excited to shift [process/project name] into Stackby to solve [top pain point(s): duplicate spreadsheets, unclear ownership, status chaos]. Stackby gives us a single source of truth, clear ownership, faster updates, and less time in status meetings.

What this enables:
- Streamlined intake and standardized data (fewer back-and-forths)
- Role-based views (see only what matters to act quickly)
- Live dashboards and automations (fewer manual nudges)

What to expect:
- Access: You’ll receive an invite to our Stackby workspace by [date].
- Training: A 30–45 min kickoff on [date/time] to show exactly how we’ll work in Stackby. Session will be recorded.
- Start using it: After training, we’ll track work in Stackby going forward.
- Questions are welcome—reply here or post in #[channel-name].
 
Thanks,
[Executive sponsor or workflow owner]

Take action: Customize your launch message

• Fill in: process name, top pain points, dates, channel for questions.

• Link to: Quick-start guide, role-based views, and training calendar invite.

Announce your Stackby launch

Make the announcement official and visible to everyone affected.

Take action: Identify the best announcement channels

• Options: All-hands, team meeting, #announcements, email + calendar invite.

• Include: Why now, training date, where to find resources, and who to contact.

Invite your team to Stackby

Invite people with the least-privilege role required to do their job. Preconfigure views so new users land in the right place.

• Add collaborators: admin/creator/editor/commenter/viewer, or interface-only access where applicable.

• Prepare role-based views: “My work,” “This week,” “Needs review,” “Leadership: Rollup.”

• Use shared view links for external stakeholders; hide sensitive/internal fields.

• Add a Collaborator field for ownership and build “Owner is me” views.

Host a kickoff training

Keep it practical and job-focused. Show the exact path each role will use daily.

• Agenda (30–45 min):
  
  

  • 10 min: The why (benefits, outcomes)

  • 15 min: Live demo (views, updating records, forms, basic automations)

  • 10 min: Hands-on (everyone updates a test record)

  • 5–10 min: Q&A and next steps

• Record the session; share the link immediately afterward.

• Provide a 1-page quick-start per role (links to their saved views).

Take action: Schedule a team training

• Send calendar invite with: agenda, workspace link, “log in before session,” and the recording link placeholder.

Support your team with additional resources

Keep help easy to find and quick to access.

• Office hours: 2–3 short sessions in the first two weeks.

• Help channel: Create #[stackby-help] for async questions.

• Resource hub: Centralize the training recording, quick-start PDF, base link, FAQs, and escalation contacts.

• Learning path: Short GIFs or Looms for common tasks (update status, add record, submit a form).

Take action: Create and share a resource hub

• Create a folder/wiki page labeled “Stackby Onboarding.”

• Add: Launch brief, training recording, role-based quick-starts, links to views/interfaces, and support contacts.