Jump to content
Main menu
Main menu
move to sidebar
hide
Navigation
Main page
Recent changes
Random page
Help about MediaWiki
Special pages
Fullmer Wiki
Search
Search
Appearance
Create account
Log in
Personal tools
Create account
Log in
Pages for logged out editors
learn more
Contributions
Talk
Editing
Onboard
(section)
Page
Discussion
English
Read
Edit
View history
Tools
Tools
move to sidebar
hide
Actions
Read
Edit
View history
General
What links here
Related changes
Page information
Appearance
move to sidebar
hide
Warning:
You are not logged in. Your IP address will be publicly visible if you make any edits. If you
log in
or
create an account
, your edits will be attributed to your username, along with other benefits.
Anti-spam check. Do
not
fill this in!
==Treat it as a deploy, not a checklist== Most onboarding programs are a task checklist: accounts created, training scheduled, kickoff call held. None of that is a deploy β a deploy has defined success criteria set before you start, a staged rollout instead of flipping everything on at once, and a rollback or rescue plan if it doesn't go live cleanly. Onboarding should work the same way: a stated time-to-first-value target, a phased rollout across teams or use cases rather than a big-bang launch, and a named rescue path if the customer isn't live on schedule.
Summary:
Please note that all contributions to Fullmer Wiki may be edited, altered, or removed by other contributors. If you do not want your writing to be edited mercilessly, then do not submit it here.
You are also promising us that you wrote this yourself, or copied it from a public domain or similar free resource (see
Fullmer Wiki:Copyrights
for details).
Do not submit copyrighted work without permission!
Cancel
Editing help
(opens in new window)
Search
Search
Editing
Onboard
(section)
Add topic