1:1 Meeting Template for Managers (CTO Guide)

1:1 meeting template for managers: a CTO companion guide to the 1:1 Meeting Assistant

In a 60-engineer org, weekly 30-minute 1:1s add up to 30 hours of manager time every week. That’s close to a full-time job spent in conversations. If those 1:1s slide into status updates, you burn the time and still miss the signals that matter: burnout, misalignment, and quiet attrition.

Here’s the thesis: a one-on-one meeting tool only earns its keep when it turns talk into trust and follow-through. The 1:1 Meeting Assistant is built for exactly that.

What is the 1:1 Meeting Assistant (one-on-one meeting tool) and what it replaces

The Art of CTO 1:1 Meeting Assistant is a structured system for engineering managers to run repeatable one-on-ones. It combines templates, suggested talking points, and action item tracking. It replaces the messy mix of private docs, half-written notes, and “we’ll talk next week” promises that never quite land.

I’ve seen it work best in orgs with 10 to 100 engineers, especially when you’ve promoted a few strong ICs into first-time managers. That’s the Series A and early Series B reality.

Core parts of the tool

Structured templates: weekly check-ins, career growth, feedback, and tough conversations.
AI-suggested talking points: prompts based on prior notes and open items.
One-on-one action item tracker: owners, due dates, and carry-over between meetings.
Shared agenda: the report adds topics before the meeting.
History: a running record that survives reorgs and manager changes.

Spotify’s engineering write-up on 1:1s frames the meeting as a place for trust, sensitive topics, and career plans, not a project update channel. That’s the right mental model, and it’s what this tool is trying to support across lots of managers without turning it into bureaucracy: Spotify Engineering on 1:1s.

The framing statement: treat 1:1s as an internal operating system for leadership, not a calendar habit.

How often should engineering managers hold 1:1 meetings

Most CTOs I talk to see the same failure mode after headcount jumps from 20 to 60. Managers start canceling 1:1s to “make room for delivery.” Then delivery slows anyway because people problems sit and rot.

Weekly 30-minute 1:1s are the default for engineering managers. Weekly cadence keeps the loop tight and makes it easier to catch blockers early, before they turn into disengagement. Quantum Workplace’s research reports that employees prefer weekly one-on-ones, and it calls out monthly as the next best option when weekly isn’t possible: Quantum Workplace on 1:1 frequency.

A practical cadence model for 10 to 100 engineers:

Weekly 30 minutes: most engineers, most managers.
Weekly 45 to 60 minutes: new hires in first 90 days, performance recovery plans, or personal stress periods.
Biweekly 30 minutes: staff and principal engineers with stable scope and strong self-direction.
Skip-level monthly or quarterly: CTO or VP with second-line reports to keep signal quality high.

One question comes up in every scaling org: should a CTO mandate weekly 1:1s? Yes. Set the baseline and audit cancellations. Then let managers extend time when it’s warranted.

What to measure as a CTO

Cancellation rate: target under 10% per quarter per manager.
Carry-over rate: action items that roll more than 2 meetings need escalation.
Time-to-first-1:1 for new hires: target within 5 business days.

Use Command Center to track these as leadership hygiene metrics alongside incidents and delivery risk: our guide to tech portfolio and risk tracking in Command Center.

What to discuss in a 1:1 meeting with engineers (manager 1:1 talking points)

A good 1:1 has a shape. Without one, it turns into either a mood check or a Jira review. Neither is great.

The best default structure is a three-part flow:

Their agenda first: blockers, relationships, career, feedback.
Your agenda second: context, decisions, expectations.
Close with action items: owners and dates.

Jellyfish makes a blunt point that matches what works in practice: don’t turn 1:1s into status meetings. Put status somewhere else, then use 1:1 time for context and growth: Jellyfish on impactful 1:1s.

Pluralsight emphasizes active listening as the trust engine. Ask clarifying questions, don’t interrupt, and keep the space judgment-free: Pluralsight on 1:1 best practices.

The 60 30 10 agenda rule (a link-worthy definition)

Managers need something they can remember on a bad day.

The 60 30 10 rule

60% report-led: their topics, their risks, their growth.
30% manager-led: context, feedback, expectations.
10% close: action items, owners, dates, and next check.

Why it works: it protects the scarce part of the meeting. The scarce part isn’t information. It’s psychological safety.

A manager 1:1 talking points bank that scales past 50 engineers

Managers need prompts that fit engineering work, not generic HR scripts. The tool’s suggested talking points should pull from these categories.

Delivery and friction

Blockers: “What is slowing you down that you can’t fix alone?”
Dependencies: “Which team is hardest to work with right now, and why?”
Quality: “Where are we paying interest in tests, CI, or review time?”

Growth and scope

Next scope: “What do you want to own in the next 8 weeks?”
Skill gap: “What skill would make your job easier by 20%?”
Feedback request: “What should be different about how we work together?”

Team health

Energy: “What part of work drained you this week?”
Conflict: “Any tension with a person or process we should address?”
Workload: “What are you carrying that we should drop?”

DevDynamics calls out active listening and SMART goals as a way to align expectations and track progress. That maps cleanly to action items and follow-ups: DevDynamics on effective 1:1s.

Use metrics as prompts, not as a weapon

Metrics belong in 1:1s, but only with the right posture. Jellyfish suggests using metrics like cycle time, PR reviews, and docs contributions as conversation starters, with a focus on trends: Jellyfish on metrics in 1:1s.

A practical pattern for managers:

Bring one trend per month, not a dashboard.
Ask for context first, then offer help.
Tie the trend to system fixes, not personal blame.

If the org already tracks DORA, connect the conversation to the Engineering Metrics Dashboard and keep the 1:1 focused on what the engineer experiences day to day: our guide to DORA and team throughput in the Engineering Metrics Dashboard.

How to use a 1:1 meeting template for managers without making it robotic

Templates fail when managers treat them like scripts. Templates work when they protect the hard topics and reduce the “what should we talk about?” tax.

Lattice’s template library makes a good point: different 1:1 types need different prompts, like wellbeing, feedback, and remote work. That beats the one mega-template that tries to do everything: Lattice 1:1 templates.

Candost adds a detail that sounds small until you’ve watched it play out: write agenda items as short sentences, not vague labels. “Salary adjustment” spikes anxiety. A sentence with context lowers the temperature and saves time: Candost on 1:1 templates.

The template stack for Series A and early Series B

Use four templates and rotate them. It keeps weekly meetings from feeling stale, while still staying consistent.

Weekly check-in template

Wins since last 1:1
Blockers and friction
Workload and focus
One piece of feedback, both directions
Action items

Career growth template (monthly)

Scope changes in last 30 days
Skills to build this quarter
A project to stretch on
Sponsorship asks, like visibility or cross-team work

Feedback template (as needed)

Specific example
Impact
What “good” looks like next time
Support needed
Follow-up date

Wellbeing template (quarterly or during stress)

Energy and sleep patterns (only what they want to share)
Work boundaries
On-call load and recovery
Support options

This is where a engineering manager meeting assistant helps. It keeps the rotation steady and keeps the notes and action items in one place.

A decision matrix: template depth vs team maturity

Use this matrix to decide how structured the 1:1 should be.

Team situation	Template depth	Meeting length	Tool features to lean on
New manager, 3 to 6 reports	High	30 to 45 min weekly	Templates, talking points, action tracker
New hire in first 90 days	High	45 to 60 min weekly	Action tracker, history, follow-ups
Staff engineer, stable scope	Medium	30 min biweekly	Shared agenda, lightweight notes
Performance recovery plan	High	45 min weekly	Action tracker with dates, recap history
Team under incident load	Medium	30 min weekly	Blocker prompts, wellbeing check

For org design work, connect this to our internal guidance on manager span of control and team topology choices. See our posts on how to scale engineering org structure without breaking ownership, platform team charters that teams actually use, and career ladders for engineers that reduce title churn.

One-on-one action item tracker: the part that changes outcomes

Most 1:1s don’t fail in the meeting. They fail after. Notes sit in a doc. Promises fade. The same topic comes back for six weeks straight.

Action tracking fixes that, but only if you’re strict about it.

Atlassian’s guidance on follow-up is clear: recap what was discussed, document action items, and keep check-ins consistent. It also points out that tools can extract action items and turn them into tasks, which is exactly what busy managers need: Atlassian on running 1:1s.

The “3D” action item rule: Date, Doer, Definition

This rule is simple enough to enforce across 20 managers.

Date: a due date or a review date.
Doer: one owner, even if others help.
Definition: what “done” means in one sentence.

Examples that work:

“Doer: manager. Date: 2026-06-07. Definition: share promotion rubric and map current level to next.”
“Doer: engineer. Date: 2026-06-14. Definition: draft design doc for cache invalidation plan and ask for review.”
“Doer: manager. Date: 2026-06-03. Definition: talk to Product about scope cut and report back with decision.”

Examples that fail:

“Follow up on promotion.”
“Fix on-call.”
“Talk to Product.”

CTO-level guardrails for action items

A CTO should not read 1:1 notes. That breaks trust fast. But a CTO can set system rules.

Managers keep action items in the tool, not in private notebooks.
Managers close action items in the next 1:1 or re-date them.
Managers escalate cross-team blockers after 2 missed dates.

When action items touch incidents or reliability work, connect them to the same workflow used for outages. That keeps the org honest about operational debt. See our guide to blameless reviews in the Incident Postmortem tool.

Enterprise implications for Series A and early Series B CTOs

Manager quality becomes a scaling limit at 40 to 80 engineers. You add managers fast, and many have never run coaching-style 1:1s. A shared one-on-one meeting tool sets a baseline without turning managers into robots.
Shadow performance problems get expensive fast. A missed expectation in March becomes a PIP in September. Regular 1:1s with tracked action items pull that timeline forward, while the fix is still cheap.
Reorgs break context, and 1:1 history is the glue. Series B orgs reorg every 6 to 12 months. A structured record helps new managers pick up coaching threads without forcing the report to retell their story.
Burnout shows up first in private conversations. Weekly cadence and active listening surface on-call fatigue and workload drift before it hits attrition. Pluralsight’s point about judgment-free space isn’t soft advice. It’s a retention control: Pluralsight on trust in 1:1s.

CTO recommendations for rolling out the 1:1 Meeting Assistant

Immediate actions

Set a cadence standard. Default to weekly 30 minutes. Track cancellations by manager.
Ship four templates. Weekly, career, feedback, wellbeing. Keep them short.
Adopt the 60 30 10 rule. Coach managers to protect report-led time.
Turn on action tracking. Require Date, Doer, Definition for every action.
Run a manager calibration. One 45-minute session per month to share what prompts work.

Policy framework

Confidentiality. Notes stay between manager and report, except explicit escalation.
No status in 1:1s. Status lives in standups, Jira, and async updates.
No surprise reviews. Feedback shows up in 1:1s before it shows up in a cycle.

Architecture principles (yes, for a people tool)

Single source of truth. One place for agenda, notes, and action items.
Low friction capture. If it takes more than 60 seconds, managers stop doing it.
Portable history. Reorgs and manager changes should not erase context.

For build vs buy decisions around people tooling, use our Build vs Buy Matrix. The common trap is building a custom 1:1 system in Notion, then losing consistency across teams.

Bigger picture: 1:1s are a control loop for change

Series A and early Series B companies live in change. Roadmaps shift, funding changes, teams split. You need a control loop that catches drift early. Weekly 1:1s can be that loop, as long as managers listen well and close the loop with action items.

Tools don’t create trust. They create consistency. Consistency gives managers enough breathing room to do the human part well.

So the real question is simple: does your org treat 1:1s as optional meetings, or as the place where problems get named while they’re still small?

Use the tool

1:1 Meeting Template for Managers: A CTO Companion Guide to the 1:1 Meeting Assistant