‹ Back to the directory

New Hire Context Pack

Assemble a first-week context pack for a new hire: role charter, people map, systems by day needed, glossary, and a checkable 30-60-90.

by Pelican Point Consulting·0 installs
onboardingnew-hiresdocumentationramp-up
G

Create a free shareskills account to install New Hire Context Pack into Claude.

Create a free account

New Hire Context Pack

Assemble the context pack that lets a new hire be useful in week one instead of week six. Most onboarding fails by omission-through-familiarity: the team no longer notices what a newcomer cannot know — who decides what, what the acronyms mean, which meetings matter. This skill mines that invisible context out of the team and packages it into something a nervous person can absorb in forty-five minutes and keep referencing for months.

When to use this skill

  • A signed offer means someone starts in the next few weeks and nothing is written down
  • Onboarding exists as a stack of system invites and a welcome lunch, and not much else
  • Previous hires took months to ramp and nobody can quite say why
  • A manager asks for an onboarding plan, a 30-60-90, or a "starter pack" for a role
  • A role is being backfilled and the leaver's knowledge needs capturing on the way out

Sources to mine

  • The role description as practiced, not as advertised — what this person will actually do
  • The team's recent artifacts: last quarter's goals, recent reports, current project docs
  • The org chart plus the informal map of who actually decides and who knows things
  • The systems the role touches, with who grants access to each
  • The recurring meetings the hire will attend, with each one's real purpose
  • The vocabulary: internal terms, acronyms, and project codenames used without explanation

Workflow

  1. Write the role charter first, three parts: the mission of the role in three sentences, the top three outcomes for year one, and — just as important — what this role does not own. Boundary clarity prevents month-three turf confusion.
  2. Build the people map: eight to twelve people the hire will work with, each with name, role, what they will work on together, and one honest conversation-starter. Mark five as week-one meetings and say why each matters.
  3. Compile the systems and access list sorted by the day access is needed, with the granting owner named — so requests go out before day one instead of trickling through week two.
  4. Write the how-we-work notes: meeting rhythm, where decisions get made, communication channels and their expected response times, working hours and time zones, and how to ask for help without feeling like a burden.
  5. Build the glossary: ten to twenty internal terms, acronyms, and codenames the hire will hit in week one. Every organization underestimates this list; collect it by skimming a week of real team messages.
  6. Draft the 30-60-90 with checkable items, three to five per phase: 30 days to learn (meetings held, systems mastered, one small thing shipped), 60 to contribute (owned tasks with support), 90 to own (first solo outcome). Each phase ends with a named check-in conversation, not a survey.
  7. Review the pack with the manager and cut a third. The pack must be readable in forty-five minutes; completeness that nobody reads is a form of failure. Page one answers the only question that matters on day one: "what should I do right now?"

Pack structure

1. Start here          what to do in your first two hours
2. Role charter        mission, year-one outcomes, what you do NOT own
3. People map          12 people, 5 starred for week one
4. Systems & access    sorted by day needed, granting owner named
5. How we work         meetings, decisions, channels, response norms
6. Glossary            the words we forgot we invented
7. 30-60-90            checkable, with named check-ins

Worked example: people map entry

Maya R. — platform lead                       (week-one meeting)
works with you on:  release cadence, anything touching deploys
why she matters:    owns the systems your first ship passes through
opener:             ask for the deploy-freeze story — she tells it well
timezone:           two hours ahead — mornings overlap best

Five lines per person is enough. A people map is a set of door-openers, not a stack of dossiers.

Quality bar

  • Every item is actionable or checkable; no aspirational filler like "build relationships"
  • Every link, owner, and meeting named in the pack was verified current this month
  • No unexplained acronym anywhere in the pack — the glossary covers or the sentence changes
  • The five starred people know they are starred and expect the meeting
  • A manager can hand this pack over with no verbal preamble, and day one still works
  • The pack names one buddy the hire can ask anything, however small
New Hire Context Pack — AI skill by Pelican Point Consulting | shareskills