One-on-Ones and Career Conversations
One-on-ones are recurring private meetings between a manager and a direct report. Career conversations are the planned discussions inside that rhythm that cover growth goals, skill gaps, and next roles. Together they give engineers a private channel for concerns, feedback, and development that does not fit a team status meeting.
itEngineering leadership and delivery management | OpenSkills.info
Course pathWalk it in order
Look it upDip in anytime
Go furtherLeaves this page
Don't Panic
Don't Panic: One-on-Ones and Career Conversations
A one-on-one is a recurring private meeting with one direct report. That is the whole invention. No special software required, though plenty will sell you some. The hard part is treating the hour as the report's channel instead of a quieter status meeting with snacks optional.
The problem it solves is awkward and ancient: most useful information about conflict, confusion, motivation, and growth never appears on the team board. Before organizations named this practice, that information arrived as hallway ambushes, exit interviews, and surprise review tears. The one-on-one is the scheduled place those topics are allowed to show up early.
Three ideas carry the rest.
First, the agenda is a living private document both people feed during the week, and the report should own most of the items. If your manager handwriting fills the page every time, the calendar still looks healthy while the channel is already broken.
Second, protect the slot. Canceling for "more important" delivery work teaches the real priority order faster than any values slide. Feedback still belongs near the event when you can give it; the meeting is for the sensitive, the bi-directional, and the follow-up that needs a face.
Third, career conversations are the slower zoom-out on the same channel. The report owns the goal. The manager supplies honesty, contacts, and real practice. The organization supplies frameworks. Development builds skill; mobility changes role or scope. Wanting depth where you are is allowed. A promotion date without a skill path is a negotiation wearing a growth costume.
The surprise for many new managers: an empty agenda is not proof that everything is fine. It is often proof that nobody trusts what happens to topics that appear there, or that status has colonized the hour so thoroughly that private topics stopped trying.
If you want the mechanics, use the Cheatsheet and Practice Reference for tags, prompts, and prep lists. If you want judgment about what teams get wrong, open Field Notes. If you want the narrative map, start with Intro and Slides. The Quiz checks whether you can still tell a one-on-one from a board readout when the calendar is on fire.
Where this skill leads
Relevant careers
See how this topic contributes to broader role-level skill maps.
Sources
- https://handbook.gitlab.com/handbook/leadership/1-1/
Supports
- Shared private agendas and report-led topic ownership
- Cadence, listening norms, feedback timing, and canceling guidance
- Career topics inside the 1-1 and Grove task-relevant maturity framing
- Manager-majority agenda as a warning signal
- Transition and shadowed 1-1 context referenced from the same page family
- https://handbook.gitlab.com/handbook/leadership/1-1/suggested-agenda-format/
Supports
- Suggested section headers and hallway tag vocabulary
- Living-list agenda mechanics (last-to-first, one document)
- https://handbook.gitlab.com/handbook/people-group/learning-and-development/career-development/
Supports
- Report, manager, and organization role split
- 70-20-10 development mix and development versus mobility
- Individual growth plans and career conversation responsibilities
- Inclusive growth checks for stretch allocation and who starts conversations
- https://handbook.gitlab.com/handbook/leadership/
Supports
- Broader leadership context surrounding one-on-ones
- https://handbook.gitlab.com/handbook/leadership/underperformance/
Supports
- Boundary between private development talk and formal performance process
- https://randsinrepose.com/archives/the-update-the-vent-and-the-disaster/
Supports
- Practitioner taxonomy of update, vent, and serious-concern conversations
- Field note on keeping private time free of routine status
- https://www.engineeringladders.com/
Supports
- Open ladder language for career conversations
- https://progression.fyi/
Supports
- Public progression frameworks for career vocabulary
- https://career-ladders.dev/
Supports
- Role and responsibility examples used in awesome links
- https://themanagershandbook.com/coaching-and-feedback/running-one-on-ones
Supports
- Awesome-link rationale for a second practitioner framing of one-on-ones
- https://github.com/kdeldycke/awesome-engineering-team-management
Supports
- Discovery source for curated one-on-one and career resources
- https://github.com/sindresorhus/awesome
Supports
- Discovery of the Engineering Team Management awesome list
- https://randsinrepose.com/welcome-to-rands-leadership-slack/
Supports
- Awesome-link rationale for peer leadership community
- https://lattice.com/
Supports
- Lattice landscape placement for one-on-one and growth workflows
- https://www.15five.com/
Supports
- 15Five landscape placement for check-ins and one-to-ones
- https://www.cultureamp.com/
Supports
- Culture Amp landscape placement for development conversations
- https://www.leapsome.com/
Supports
- Leapsome landscape placement for agendas and learning goals
- https://www.betterworks.com/
Supports
- Betterworks landscape placement for goals linked to conversations
- https://www.bamboohr.com/
Supports
- BambooHR landscape placement for smaller-org development records
- https://www.personio.com/
Supports
- Personio landscape placement for HRIS-linked meeting records
- https://www.workday.com/
Supports
- Workday landscape placement for enterprise growth plans
- https://www.saplingapp.com/
Supports
- Sapling landscape placement for people-ops check-ins
- https://fellow.app/
Supports
- Fellow landscape placement for shared meeting agendas
