People Practice

Hold a private one-to-one from a shared agenda

Let both people surface work, support, and feedback needs, then record only agreed actions.

Preparation
Until both people review the agenda and agree any actions
Steps
3
Difficulty
Moderate
Task
Run a private one-to-one

Requires: Agree the purpose, cadence, privacy boundary, note access, retention, and escalation route. Give both people access to add agenda items before the conversation.

Uses: GitLab People Handbook

Back to the Task: Run a private one-to-one

Before you start

Prepare

  • Agree the purpose, cadence, privacy boundary, note access, retention, and escalation route.
  • Give both people access to add agenda items before the conversation.

Steps

Work through the method

Use the listed inputs and tools. Check the evidence when you need to verify a step.

  1. Prepare the shared agenda

    Let both people add priorities, blockers, feedback, support requests, development topics, and decisions needed.

    Step details and sources

    Why it matters: The agenda gives both people influence over a conversation that contains power differences.

    Input
    A restricted shared agenda and current agreed work.
    Output
    A prioritised agenda visible to both people.
    Tools in this stepGitLab People Handbook

    Evidence for this step

  2. Hold the two-way review

    Review each chosen topic, ask what support or decision is needed, and let either person correct assumptions or defer sensitive items.

    Step details and sources

    Why it matters: A one-to-one should surface support and disagreement without turning notes into inferred sentiment.

    Input
    The shared agenda and agreed privacy boundary.
    Output
    Agreed actions, explicit no-action outcomes, and separately routed sensitive concerns.
    Tools in this stepGitLab People Handbook

    Evidence for this step

  3. Close and restrict the notes

    Confirm actions and owners together, remove unnecessary sensitive detail, apply retention, and set the next useful check.

    Step details and sources

    Why it matters: A private conversation needs an accurate, minimal record and a known correction route.

    Input
    The conversation notes and agreed actions.
    Output
    A restricted action record or explicit no-action outcome.
    Tools in this stepGitLab People Handbook

    Evidence for this step

Success checks

Check the result

  • Both people can correct the record and see each agreed action and owner.
  • Sensitive concerns follow the approved HR, safety, or legal route.

Failure modes

What could go wrong

  • Remove inferred morale, health, intent, or performance claims from the notes.
  • Change the cadence when the current rhythm adds little value or harms safety.

Tools

Choose tools

GitLab People Handbook

A public company handbook with concrete onboarding-checklist and shared one-to-one agenda patterns.

Check fit, limits and pricing

Sources

Check the sources

Check what each source supports and where the advice has limits.