Skip to main content

The Art of CTO 1:1 Meeting Assistant provides structured meeting templates with suggested talking points per meeting type, running notes, and action item tracking that carries unfinished items into the next meeting.

How do I run 1:1s that actually help?

Structured 1:1s with template talking points, notes and action items that carry over.

Planner · Pro

About this toolWhy it matters, common mistakes, FAQ

Are Your 1:1s Worth The Hour?

The 1:1 is the main instrument you have for hearing about problems before they become resignations. Run as a status update, it is a meeting both people would rather cancel.

The manager arrives with the agenda, so the conversation covers what the manager already knows about. The value is in what you would not otherwise hear, which requires the other person to set most of it.

Questions CTOs ask

How often should engineering managers hold 1:1 meetings?
Weekly 30-minute 1:1s are the gold standard for engineering managers, with the option to extend to 45-60 minutes for direct reports who need more support (new hires, underperformers, or employees going through difficult periods). Biweekly 1:1s can work for very senior, autonomous reports but should never be less frequent than every two weeks. Skip-level 1:1s (with your reports' reports) should happen monthly or quarterly to maintain organizational awareness and provide an alternate feedback channel.
What should you discuss in a 1:1 meeting with engineers?
Effective 1:1s follow a three-part structure: their agenda first (blockers, concerns, career development, feedback — this should take 60-70% of the time), your agenda second (context sharing, project updates, organizational changes), and action items to close (clear owners and deadlines). Avoid using 1:1s for status updates — those belong in standups or async tools. Instead, focus on coaching, career growth, interpersonal challenges, and building trust. Keep a running document of discussion topics and action items between meetings.

Related Reading