Onboarding-planer efter rolle

Brug eksemplerne som udgangspunkt

Eksemplerne nedenfor viser, hvordan rækkefølgen kan ændres efter rolle. De er generelle forslag, ikke oplysninger om jeres virksomhed. Aftal forventningerne med lederen, og brug kun de systemer, personer og dokumenter, som faktisk findes hos jer.

Salg: forstå kunden før den første samtale

Start uge ét med produktets anvendelse, kundetyper og eksempler på tidligere kundedialog. Lad medarbejderen følge en kollega, gennemgå en anonymiseret kundecase og øve en indledende samtale. Først når lederen har vurderet forståelsen og bekræftet de nødvendige adgange, går medarbejderen videre til kundekontakt. Et konkret resultat fra den første uge kan være en kort forklaring af kundens problem og de spørgsmål, der stadig skal afklares.

Udvikling: gennemfør en lille, sikker ændring

Prioritér et fungerende udviklingsmiljø, forståelse af produktet og en gennemgang af teamets proces for test og kodegennemgang. Vælg derefter en afgrænset opgave med lav risiko, som løses sammen med en erfaren kollega. Målet for uge ét kan være en testet ændring, som teamet har gennemgået. Produktionsadgang og selvstændige udgivelser kræver særskilt godkendelse; de følger ikke automatisk med, fordi opgaven er læst.

Drift og lager: sikkerhed før selvstændige opgaver

Begynd med arbejdsstedets sikkerhedsregler, kontaktpersoner og proceduren ved fejl eller uheld. Lad medarbejderen følge et normalt arbejdsforløb og derefter udføre en afgrænset opgave under opsyn. Brug arbejdsstedets egne instruktioner til at vurdere, hvornår opgaven kan udføres selvstændigt. Maskiner, særlige tilladelser og lovpligtig oplæring skal altid håndteres efter de konkrete krav på stedet.

Fra uge ét til 30, 60 og 90 dage

Efter 30 dage kan fokus være at løse kendte opgaver med støtte og kunne forklare centrale arbejdsgange. Efter 60 dage kan medarbejderen tage ansvar for et afgrænset område og vide, hvornår der skal spørges om hjælp. Efter 90 dage vurderer medarbejder og leder konkrete resultater, resterende læringsbehov og næste ansvar. Tidspunkterne er forslag: erfaring, opgavernes kompleksitet og krav til sikkerhed afgør tempoet. Brug guiden nedenfor til at gøre hvert mål målbart.

Praktiske guides

• 30/60/90-dages onboarding-plan — En 30/60/90-plan deler de første tre måneder op i lær, bidrag og tag ejerskab. Den virker bedst, når hver fase har konkrete resultater som leder og medarbejder er enige om.
• Onboarding-tjekliste til nye medarbejdere — En tjekliste, der dækker hele forløbet fra underskrevet tilbud til dag 90. Brug den som baseline, fjern det der ikke passer, og tilføj de trin der er specifikke for rollen.

Uddybende eksempler på engelsk

Disse artikler findes foreløbig på engelsk.

• Account Executive onboarding plan — An Account Executive is productive when they can qualify, run and forecast deals in your sales process on their own. Onboarding should get them from product story to their first owned opportunities without months of shadowing.
• Sales Development Representative onboarding plan — SDRs ramp fastest when they start real outreach early with tight feedback. The plan should focus on who to target, what to say and how to hand over meetings, not on the full sales cycle.
• BDR onboarding plan — Where SDRs often handle inbound and volume outreach, BDRs are usually outbound-focused on named accounts or new markets. Their onboarding needs more account research, market context and multi-threading practice.
• Sales Manager onboarding plan — A new sales manager inherits people, pipeline and a forecast at the same time. Good onboarding gives them a clear picture of all three before they start changing process.
• Customer Success Manager onboarding plan — A CSM takes over relationships that already exist. Onboarding has to cover the product, each account's history and the signals that predict churn, so handovers don't feel like a reset to customers.
• Customer Support Specialist onboarding plan — Support specialists can contribute in days if the scope is right: start with common, low-risk tickets, review responses closely and widen the scope as accuracy builds.
• Software Engineer onboarding plan — Engineers learn a codebase by changing it. Onboarding should get them to a working environment and a small shipped change fast, then widen scope through progressively larger work.
• Product Manager onboarding plan — A new PM's credibility depends on understanding customers and the team's constraints before proposing anything. Onboarding should front-load customer exposure and stakeholder context.
• Product Designer onboarding plan — Designers need to learn the design system, the product's history and how design work moves into engineering. A small shipped improvement early builds trust faster than a big redesign proposal.
• Marketing Manager onboarding plan — A marketing manager has to understand positioning, channel performance and the sales relationship before they can choose where to invest. Onboarding should give them the numbers early.
• Content Marketer onboarding plan — Content marketers depend on knowing the audience and finding subject-matter experts inside the company. Onboarding should connect them to people and voice early, with a first piece published quickly.
• Operations Manager onboarding plan — Operations managers are hired to make things run better, which tempts them to change things too early. Onboarding should first build an accurate picture of how work flows today and who owns what.
• Finance Manager onboarding plan — Finance managers usually face a month-end close within weeks of starting. Onboarding should be timed around the close calendar so they observe one close before owning the next.
• HR Manager onboarding plan — An HR manager handles sensitive information from day one. Onboarding should cover data access, open employee cases and legal obligations before process improvements.
• Recruiter onboarding plan — Recruiters are productive once they understand each open role well enough to sell it and screen for it. Onboarding should pair them with hiring managers early.
• Data Analyst onboarding plan — Analysts lose most early time figuring out which tables and definitions to trust. Onboarding should hand them the key metric definitions and a known-good report to rebuild first.
• Project Manager onboarding plan — Project managers usually inherit work in progress. Onboarding should give them the state of each project, the delivery method and who decides what, before they take over.
• Consultant onboarding plan — Consultants are measured on client work, so firms rush them onto projects. Onboarding must still cover methodology, confidentiality and client conduct, or the firm's reputation carries the risk.
• Warehouse Manager onboarding plan — In a warehouse, safety and site rules come before anything else. A warehouse manager's onboarding must cover them on day one, then the flow of goods, shifts and the people who run each area.
• Logistics Coordinator onboarding plan — Logistics coordinators handle shipments where small errors cost real money. Onboarding should teach the booking flow and exception handling with real shipments, reviewed closely at first.
• Office Manager onboarding plan — Office managers keep many small things running. Onboarding should hand over suppliers, recurring tasks and budgets explicitly, because most of this knowledge is undocumented.
• Executive Assistant onboarding plan — An executive assistant's onboarding is really about one person: the executive's priorities, preferences and relationships. Onboarding should make those explicit instead of leaving the EA to learn by mistakes.
• RevOps Manager onboarding plan — RevOps sits between sales, marketing and customer success, and inherits their data problems. Onboarding should map definitions and the CRM setup before any tool changes.
• Implementation Manager onboarding plan — Implementation managers turn a signed deal into a working customer. Onboarding should combine deep product configuration knowledge with the handover rules between sales, implementation and customer success.
• IT Support Specialist onboarding plan — IT support specialists get elevated access early, so onboarding must cover security procedures and access rules before tools. Then common tickets, with review.