Sequence access, relationships, learning, supervised practice, and evidence of readiness without assuming instant productivity. 제공할 내용: Role and readiness outcomes, New employee context, Organizational resources. 예상 결과: A dated onboarding plan with owners, prerequisites, milestones, safeguards, feedback loops, and contingency paths.
1
맥락 추가
텍스트는 이 브라우저에 유지됩니다. AILesson Prompts는 이를 모델이나 서버로 보내지 않습니다.
2
프롬프트
채워지지 않은 필드는 플레이스홀더로 표시되므로 프롬프트를 복사하고 편집할 수 있습니다
Build a realistic onboarding plan using only confirmed role, employee, and organizational information.
Start date, duties, decision rights, systems, data, stakeholders, readiness evidence, and prohibited independent work:
[role]
Prior knowledge, location, timezone, pattern, language, accommodations, equipment, and consented preferences:
[person]
Manager, buddy, trainers, access owners, policies, training, meetings, reviews, dependencies, compliance, and capacity:
[organization]
Start with prerequisites that must be complete before day one and flag owners or dates that are missing. Sequence orientation, relationships, system and data access, policy and security learning, role knowledge, observation, guided practice, feedback, increasingly independent work, and milestone review. For each dated activity state outcome, owner, learner action, prerequisite, artifact or observable evidence, expected effort, and contingency. Grant least privilege and never invent access, completion, policy, training requirement, manager, meeting, deadline, or employee need. Separate exposure, practice, demonstrated competence, and authorization; attendance alone is not readiness. Protect focus time and avoid overloading the first days with passive meetings. Provide 1-week, 30/60/90-day milestones only where the role warrants them, with mutual feedback and adjustment questions. Include absence, delayed equipment/access, remote, accommodation, and failed-readiness paths without penalizing the employee for organizational delay.
기본적으로 비공개프롬프트 구성은 브라우저에서 로컬로 이루어집니다. 조직에서 허용하지 않는 한 기밀 정보를 AI 서비스에 입력하지 마세요.
입력에서 결과까지
적용 예시
구체적인 맥락이 이 레시피를 바로 사용할 수 있는 결과로 바꾸는 방법을 확인하세요
실제 입력
Role and readiness outcomes
Operations Coordinator starts Sep 7 2026. Duties: triage requests, confirm owner and acceptance criteria, maintain Linear, prepare twice-weekly reviews, document process changes. May not change product priority, approve spend, manage staff, or access production credentials. First-week evidence: correctly classify five fictional requests and identify missing owners. Day-30: run one supervised review. Day-60: manage routine queue with sampled checks. Day-90: propose one evidence-backed process improvement; manager retains approval.
New employee context
UK remote, UTC+1 in September, core overlap 13:00-17:00 UTC. Confirmed strong spreadsheet experience, no Linear experience. Company laptop shipping confirmed but delivery date not provided. English working language. No accommodation information supplied; manager should provide private request route rather than infer needs.
Organizational resources
Manager Sam, buddy Lina, IT owns accounts, Security runs required data-handling module, Support Lead explains request taxonomy, Product Ops owns Linear training. Manager has 45 minutes/day in week one; buddy 30 minutes/day. Access policy: email and HR portal before day one; Linear read-only first, edit after supervised practice; no production access. Reviews with manager end of days 3 and 5, then weekly. Exact account provisioning dates and laptop delivery unknown.
예시 출력
Before Sep 7 — organizational prerequisites
IT: confirm laptop delivery and email/HR-portal provisioning dates; both are currently missing. Manager Sam: send first-week schedule, role boundaries, core-hour expectation, and private accommodation-request route. Product Ops: prepare read-only Linear account but do not enable edit access. If equipment is late, the employee is not marked behind; Sam provides accessible, non-sensitive orientation material and reschedules system practice.
Day 1 — purpose and safe access
Sam covers role outcomes, prohibited decisions, escalation, and how success will be evidenced, not a full calendar of meetings. IT verifies approved access; no production credentials. Security assigns the confirmed data-handling module. Evidence: employee can identify what data and decisions are outside scope. Lina runs a 30-minute team-and-help-path orientation. Preserve at least two focus blocks.
Day 2 — request taxonomy and observation
Support Lead models three fictional requests. Employee classifies two with explanation. Product Ops demonstrates Linear read-only. Evidence is reasoning, not attendance. If access is missing, use exported fictional screens; do not use live customer data.
Day 3 — guided practice and review
Employee classifies all five fictional requests, identifies missing owners/acceptance criteria, and drafts questions without changing priority. Product Ops observes. Sam's end-day review compares evidence to the week-one criterion and asks what remains unclear.
Days 4-5 — supervised workflow
Employee shadows one handoff review, then prepares a fictional review packet. Edit access is considered only after the supervised task is accurate and the authorized owner confirms; it is not automatic. Day-5 review records ready, needs more practice, and organizational blockers separately.
Day 30: lead one real review with Sam present; evidence includes accurate owners, unknowns, and escalation. Day 60: manage routine queue with a predeclared sample review; no priority decisions. Day 90: present one process hypothesis with baseline evidence, risk, and test; Sam decides approval. Weekly two-way check asks what support, scope, access, or plan should change.
효과가 있는 이유
1
Readiness evidence prevents calendar attendance from being mistaken for competence or authorization.
2
Dependency ownership exposes organizational blockers before they become employee performance problems.
결과 확인
Does every activity have an outcome, owner, prerequisite, evidence, and contingency?
Are access, competence, and authorization separate under least privilege?
Are organizational delays prevented from counting against the employee?
안심하고 사용하세요
자주 묻는 질문
이 레시피를 언제 사용해야 하는지, 무엇을 제공해야 하는지, 그리고 어떤 부분에서 사람의 검토가 여전히 중요한지에 대한 실용적인 답변
What should I prepare before using “Build a new-employee onboarding plan”?
For “Build a new-employee onboarding plan,” prepare Role and readiness outcomes, New employee context, and Organizational resources. Replace placeholders only with information you can verify. If a detail is unknown, preserve that uncertainty explicitly instead of asking the model to infer it.
When is the “Build a new-employee onboarding plan” result not ready to use?
The result is not ready if it does not yet deliver the stated outcome—A dated onboarding plan with owners, prerequisites, milestones, safeguards, feedback loops, and contingency paths—from the supplied evidence, or if it relies on unresolved assumptions, missing approvals, or invented details. Use the checks as release gates: revise the source inputs or assign a named, authorized reviewer instead of polishing an unsupported output.
Which AI tools have recorded tests for “Build a new-employee onboarding plan”?
The published test record for “Build a new-employee onboarding plan” lists ChatGPT as of 2026-08-28. This confirms recorded runs, not guaranteed compatibility or identical results in later product versions. For another tool or version, keep every constraint visible and repeat the result checks before use.
ChatGPT
