Engineering Manager

Conduct 1:1 meetings with direct reports

Enhances◐ 1–3 years

What You Do Today

Hold weekly 1:1s with each engineer — discuss blockers, career goals, feedback, and wellbeing. Your most important meeting of the week.

AI That Applies

1:1 preparation — AI summarizes the engineer's recent PRs, sprint contributions, and peer feedback to prepare conversation starters and development observations.

Technologies

LatticeCulture Amp15FiveFellow

How It Works

The system aggregates data from multiple operational systems into a unified analytical layer. The processing layer applies the appropriate analytical models to the structured data, generating scored outputs that surface the most actionable insights. The output is a structured view that highlights exceptions, trends, and items requiring attention — available in the existing tools without switching systems.

What Changes

You come prepared with specifics: 'You merged 3 PRs this week, including that tricky caching fix. The code reviews you gave were thorough. Let's talk about your arch lead ambitions.'

What Stays

The relationship — building trust, providing psychological safety, helping engineers navigate career decisions — that's the core of engineering management.

What To Do Next

This section won't tell you what your numbers should be. It will show you how to find them yourself. Every instruction below produces a real, verifiable result in your organization. No benchmarks, no projections — just the steps to build your own evidence.

Establish Your Baseline

Know where you are before you move

Before adopting AI tools for conduct 1:1 meetings with direct reports, understand your current state.

•

Map your current process: Document how conduct 1:1 meetings with direct reports works today — who does what, how long it takes, where the bottlenecks are. You need this baseline to measure improvement.

•

Identify the judgment points: The relationship — building trust, providing psychological safety, helping engineers navigate career decisions — that's the core of engineering management. These are the boundaries AI won't cross.

•

Assess your data readiness: AI tools for this area need data to work. Check whether your organization has the historical data, integrations, and data quality to support Lattice tools.

Without a baseline, you can't measure whether AI actually improved anything. You'll adopt tools without knowing if they're working.

Define Your Measures

What to track and how to calculate it

Time per cycle

How to calculate

Measure how long conduct 1:1 meetings with direct reports takes end-to-end today, then after AI adoption.

Why it matters

The most visible improvement is speed. If AI doesn't save time, question whether it's adding value.

Quality of output

How to calculate

Track error rates, rework frequency, or stakeholder satisfaction scores before and after.

Why it matters

Speed without quality is just faster mistakes. Measure both.

When to check: Check after 30 days of consistent use, then quarterly.

The commitment: Give new tools at least 30 days before judging. The first week is always awkward.

What NOT to measure: Don't measure AI adoption rate as a KPI. Adoption follows value — if the tool helps, people use it.

Start These Conversations

Who to talk to and what to ask

your engineering manager or VP Eng

“Which of our current reports are manually assembled, and how much time does that take each cycle?”

They're deciding which AI developer tools to adopt team-wide

your DevOps or platform team lead

“What questions do stakeholders actually ask that our current reporting doesn't answer?”

They manage the infrastructure that AI tools depend on

Check Your Prerequisites

Confirm readiness before you invest

Check items as you confirm them.

← Back to AI for Engineering Managers