onboarding-guide-creator について
人事チームやマネージャー向けに、職種、期間、評価ポイントに沿った従業員のオンボーディングを設計するための枠組みです。歓迎資料、関係構築の計画、評価表、品質チェックリストをまとめています。
主な機能
- 01職種別オンボーディングテンプレート
- 02入社前から90日までのタイムライン
- 03歓迎ガイドの構成案
- 04バディと交流のスケジュール
- 0530・60・90日評価フレームワーク
- 06オンボーディング品質チェックリスト
活用シーン
- 01エンジニア新入社員の最初の数週間の計画
- 02営業やデザイン職の研修計画の作成
- 03マネージャーと従業員の30・60・90日目標の設定
- 04入社日までの準備状況の確認
インストール
コマンドをコピーしてターミナルで実行します。
$
npx skills add https:/ / github.com/ travisjneuman/ .claude --skill onboarding-guide-creatorインストール後、Claude Code で/onboarding-guide-creatorを入力して読み込まれたか確認します。
詳細
オンボーディングガイド作成ツール
役割に応じたコンテンツ、タイムライン、成功指標を含む包括的な従業員オンボーディングプログラムを作成するための構造化フレームワークです。
オンボーディングのタイムラインフレームワーク
マスタータイムライン
ONBOARDING PHASES:
PRE-DAY-1 (Offer Accepted → Start Date)
├── Welcome email with logistics
├── Equipment ordering and setup
├── Account provisioning (email, Slack, tools)
├── Pre-reading materials sent
├── Buddy/mentor assigned
└── First week calendar pre-populated
WEEK 1: ORIENT
├── Day 1: Welcome, setup, team introductions
├── Day 2: Company overview, culture, values
├── Day 3: Role-specific training begins
├── Day 4: Tool training and access verification
├── Day 5: Week 1 check-in with manager
└── Deliverable: "I understand my role and how the company works"
WEEKS 2-4: LEARN
├── Deep-dive into team processes and workflows
├── Shadow key meetings and customer calls
├── Complete required compliance training
├── Begin first small project or task
├── Meet cross-functional stakeholders
└── Deliverable: "I can execute core tasks with guidance"
30-DAY CHECK-IN
├── Manager 1:1 review
├── Self-assessment against 30-day goals
├── Feedback collection (new hire → company)
├── Identify knowledge gaps
└── Adjust 60-day plan if needed
DAYS 31-60: CONTRIBUTE
├── Own tasks and small projects independently
├── Contribute to team goals
├── Deeper cross-functional collaboration
├── Begin attending all recurring meetings
└── Deliverable: "I can work independently on routine tasks"
60-DAY CHECK-IN
├── Progress review against goals
├── Expanded responsibilities discussion
├── Peer feedback collection
└── Adjust 90-day plan if needed
DAYS 61-90: OWN
├── Own a meaningful workstream or project
├── Contribute to planning and strategy discussions
├── Mentor newer team members if applicable
├── Identify process improvements
└── Deliverable: "I am a fully productive team member"
90-DAY REVIEW
├── Formal performance discussion
├── Goal setting for next quarter
├── Onboarding feedback survey
├── Transition to standard performance cycle
└── Celebrate completion
役割別テンプレート
エンジニアリングのオンボーディング
ENGINEERING ONBOARDING ADDITIONS:
PRE-DAY-1:
- [ ] Dev machine ordered (spec: ___)
- [ ] GitHub/GitLab access provisioned
- [ ] VPN and SSH keys prepared
- [ ] IDE license assigned
WEEK 1:
- [ ] Dev environment setup (follow setup guide)
- [ ] Clone key repositories
- [ ] Run the application locally
- [ ] Review architecture documentation
- [ ] Pair with buddy on a small bug fix
- [ ] Understand CI/CD pipeline
- [ ] Review coding standards and PR process
WEEKS 2-4:
- [ ] Complete first PR (small, well-scoped)
- [ ] Participate in code review (as reviewer)
- [ ] Attend sprint ceremonies
- [ ] Understand on-call rotation and runbooks
- [ ] Review incident response process
- [ ] Deep-dive on owned service/module
30-DAY MILESTONE:
- [ ] Merged 3+ PRs
- [ ] Completed code review for others
- [ ] Can run and debug the application locally
- [ ] Understands deployment process
60-DAY MILESTONE:
- [ ] Owns a feature or workstream
- [ ] Can triage and fix production issues
- [ ] Contributes to technical design discussions
- [ ] Mentors on team conventions and tooling
90-DAY MILESTONE:
- [ ] Delivered a meaningful feature end-to-end
- [ ] Participated in on-call rotation
- [ ] Contributed to team process improvements
- [ ] Comfortable presenting technical work to team
営業のオンボーディング
SALES ONBOARDING ADDITIONS:
WEEK 1:
- [ ] Product overview and demo walkthrough
- [ ] ICP and buyer persona review
- [ ] CRM setup and pipeline training
- [ ] Sales methodology introduction
- [ ] Listen to 5 recorded discovery calls
- [ ] Review competitive battle cards
WEEKS 2-4:
- [ ] Shadow 10+ live calls (discovery, demo, close)
- [ ] Complete product certification
- [ ] Practice pitch delivery (recorded + feedback)
- [ ] Learn objection handling frameworks
- [ ] Understand pricing and discounting policies
- [ ] Build initial target account list
30-DAY MILESTONE:
- [ ] Pass product knowledge certification
- [ ] Deliver solo demo to internal audience
- [ ] Own 5+ accounts/opportunities
- [ ] Complete CRM hygiene training
60-DAY MILESTONE:
- [ ] Run discovery calls independently
- [ ] Pipeline meets minimum threshold ($X)
- [ ] Delivered 10+ demos
- [ ] Comfortable with pricing discussions
90-DAY MILESTONE:
- [ ] Closed first deal (or advanced to late stage)
- [ ] Pipeline at quota-pace level
- [ ] Can handle competitive objections confidently
- [ ] Contributing to team best practices
デザインのオンボーディング
DESIGN ONBOARDING ADDITIONS:
WEEK 1:
- [ ] Design tools setup (Figma, prototyping tools)
- [ ] Review design system and component library
- [ ] Brand guidelines deep-dive
- [ ] Understand design review process
- [ ] Meet key stakeholders (PM, Eng, Research)
WEEKS 2-4:
- [ ] Audit existing designs in your area
- [ ] Shadow user research sessions
- [ ] Complete first small design task
- [ ] Present work in design critique
- [ ] Understand handoff process to engineering
30-DAY MILESTONE:
- [ ] Completed first design deliverable
- [ ] Comfortable with design system usage
- [ ] Participated in design critique (giving + receiving)
- [ ] Understands user research insights for your area
60-DAY MILESTONE:
- [ ] Owns a design workstream
- [ ] Conducted or co-led user research
- [ ] Designs are passing critique with minimal revision
- [ ] Collaborating effectively with PM and engineering
90-DAY MILESTONE:
- [ ] Delivered end-to-end design for a feature
- [ ] Contributing to design system evolution
- [ ] Presenting design rationale to stakeholders confidently
- [ ] Identified and proposed design improvements
オペレーションのオンボーディング
OPERATIONS ONBOARDING ADDITIONS:
WEEK 1:
- [ ] Process documentation review
- [ ] Tool access (project management, analytics, comms)
- [ ] Org chart and RACI matrix review
- [ ] Understand key workflows and SLAs
- [ ] Meet cross-functional dependencies
WEEKS 2-4:
- [ ] Shadow key operational processes end-to-end
- [ ] Document current-state processes you'll own
- [ ] Identify quick-win improvements
- [ ] Understand reporting cadence and metrics
- [ ] Complete compliance and policy training
30-DAY MILESTONE:
- [ ] Can execute core processes independently
- [ ] Owns daily/weekly operational tasks
- [ ] Documented one process improvement
- [ ] Comfortable with reporting tools
60-DAY MILESTONE:
- [ ] Owns a workstream end-to-end
- [ ] Implemented at least one process improvement
- [ ] Managing cross-functional dependencies
- [ ] Contributing to operational metrics review
90-DAY MILESTONE:
- [ ] Fully owns operational area
- [ ] Driving efficiency improvements measurably
- [ ] Presenting operational updates to leadership
- [ ] Mentoring on processes for newer team members
ウェルカムガイドの構成
初日のウェルカムドキュメント
WELCOME GUIDE OUTLINE:
1. WELCOME MESSAGE
- Personal note from manager
- Team welcome and excitement
- What to expect on Day 1
2. COMPANY OVERVIEW
- Mission and vision (one paragraph each)
- Company history (brief timeline)
- Products and customers (who we serve)
- Business model (how we make money)
- Org structure (high-level chart)
3. CULTURE AND VALUES
- Core values with examples
- Communication norms (async vs sync, tools)
- Meeting culture (camera on/off, note-taking)
- Work schedule expectations (hours, flexibility)
- PTO and time-off culture
4. YOUR TEAM
- Team mission and current priorities
- Team members (name, role, fun fact)
- Your buddy/mentor (name, how to reach)
- Key stakeholders outside the team
5. TOOLS AND ACCESS
- Account credentials and setup guide
- Key tools checklist (with links)
- IT support contact
- Security policies (passwords, 2FA)
6. LOGISTICS
- Office location / remote setup
- Expense policy
- Benefits enrollment deadline
- HR contact for questions
7. YOUR FIRST WEEK
- Calendar overview
- Key meetings to attend
- First tasks or reading assignments
- Who to ask for help
企業文化への適応
関係構築のスケジュール
MEETING SCHEDULE (First 30 Days):
WEEK 1:
- Manager 1:1 (30 min) — expectations, questions
- Buddy coffee chat (30 min) — informal, culture
- Skip-level intro (15 min) — visibility
WEEK 2:
- 3 peer 1:1s (30 min each) — team relationships
- Cross-functional partner (30 min) — collaboration
- Buddy check-in (15 min)
WEEK 3:
- 2 peer 1:1s (30 min each) — expand network
- Manager 1:1 (30 min) — progress check
- Optional: exec coffee chat
WEEK 4:
- Cross-functional partner (30 min) — deepen
- Manager 1:1 (30 min) — 30-day check-in
- Buddy check-in (15 min) — transition to ad-hoc
SUGGESTED 1:1 QUESTIONS FOR NEW HIRES:
- "What do you wish someone told you when you started?"
- "What's the best way to get things done here?"
- "What's the team's biggest challenge right now?"
- "How do you prefer to collaborate?"
- "What should I know that's not in any document?"
バディプログラムのガイドライン
BUDDY RESPONSIBILITIES:
BEFORE START:
- Send a welcome Slack/email
- Ensure workspace/equipment is ready
- Block time in calendar for first-week support
WEEK 1:
- Office tour / virtual workspace walkthrough
- Lunch together (Day 1)
- Available for real-time questions
- Introduce to key people informally
- Share "unwritten rules" and tips
WEEKS 2-4:
- Weekly 15-min check-ins
- Available for ad-hoc questions
- Include in social events
- Flag any concerns to manager
BUDDY SELECTION CRITERIA:
- Same team or adjacent team
- Tenured enough to know the ropes (6+ months)
- Good communicator and approachable
- Willing and has capacity
- NOT the new hire's direct manager
成功指標とチェックポイント
30日/60日/90日の評価テンプレート
30-DAY SELF-ASSESSMENT:
Rate yourself 1-5 on each dimension:
KNOWLEDGE:
[ ] I understand what the company does and how it makes money
[ ] I understand my team's goals and priorities
[ ] I know who to ask for help on different topics
[ ] I understand the tools and systems I need to use
PRODUCTIVITY:
[ ] I can complete routine tasks without constant guidance
[ ] I've contributed meaningfully to at least one project
[ ] I understand our team's workflow and processes
RELATIONSHIPS:
[ ] I've met all my immediate team members
[ ] I've met key cross-functional stakeholders
[ ] I feel comfortable asking questions
[ ] I have a good working relationship with my buddy/mentor
OVERALL:
[ ] I feel welcomed and supported
[ ] I understand what success looks like in my role
[ ] I know my goals for the next 30 days
OPEN QUESTIONS:
- What do I still need to learn?
- What support do I need from my manager?
- What would have made my first 30 days better?
マネージャー評価フレームワーク
| 項目 | 30日 | 60日 | 90日 |
|---|---|---|---|
| 知識 | 役割と会社を理解している | 担当領域の深い知識がある | 担当領域のエキスパートである |
| 生産性 | ガイダンスを受けながらタスクを完了する | 自立して業務を進める | プロジェクトを最初から最後まで遂行する |
| 品質 | 基本的な基準を満たす | 一貫して質の高い仕事をする | 基準を引き上げる |
| コラボレーション | 迅速に対応し、質問する | 積極的にコミュニケーションを取る | チーム横断の業務を推進する |
| 企業文化 | 規範を学んでいる | 価値観を実践している | 行動で手本を示している |
| 主体性 | 指示に従う | 改善を提案する | 改善を推進する |
オンボーディング品質チェックリスト
| 確認項目 | 状況 |
|---|---|
| 初日までの準備が完了している(機器、アカウント、アクセス権) | [ ] |
| バディが決まり、事前説明を受けている | [ ] |
| 初週の予定が開始日前に登録されている | [ ] |
| 役割別の研修計画が文書化されている | [ ] |
| 30日/60日/90日の目標が作成され、共有されている | [ ] |
| ウェルカムガイドが開始日前に送付されている | [ ] |
| マネージャーが初週の確認面談の時間を確保している | [ ] |
| コンプライアンス研修が予定されている | [ ] |
| 30日目に実施するオンボーディングのフィードバック調査が設定されている | [ ] |
| 90日目のレビューが事前に予定されている | [ ] |
オンボーディングで避けるべき失敗パターン
COMMON ONBOARDING FAILURES:
1. INFORMATION FIREHOSE
Problem: 8 hours of presentations on Day 1
Fix: Spread learning over weeks; prioritize doing over watching
2. NO BUDDY OR MENTOR
Problem: New hire has no safe person to ask "dumb" questions
Fix: Assign buddy before start date; brief them on role
3. NO EARLY WIN
Problem: New hire doesn't contribute anything meaningful for weeks
Fix: Assign a small, completable task in Week 1
4. UNCLEAR EXPECTATIONS
Problem: New hire doesn't know what success looks like
Fix: Written 30/60/90 day goals shared on Day 1
5. MANAGER UNAVAILABLE
Problem: Manager is traveling or overbooked during first week
Fix: Block manager calendar; delay start date if necessary
6. TOOL ACCESS DELAYS
Problem: Can't log in, can't code, can't sell — for days
Fix: Provision all access before Day 1; have IT verify
関連項目
- 人事・人材
anthropic-skills:docx(Anthropic のドキュメントスキル)- プロダクトマネジメント
コメント
Markdown 対応