1:1 Meeting Agenda Generator

Where the 1:1 meeting came from

The regular 1:1 between a manager and each direct report was made famous by Andy Grove, who ran Intel and described the practice in High Output Management (1983)¹. He wrote that regularly scheduled one-on-ones were "highly unusual outside of Intel" at the time. The habit started when Grove, new to memory chips, asked two of his reports to give him private lessons. They prepared, and he took notes. He called the meeting's purpose "mutual teaching and exchange of information"¹.

Forty years on, 1:1s are everywhere, but they were barely studied. Organizational psychologist Steven Rogelberg estimates that 200 to 500 million 1:1 meetings happen around the world each day². A 2023 review he co-wrote in Organizational Psychology Review notes that 1:1s make up nearly half of all workplace meetings, yet had not been studied as a topic of their own³. His book Glad We Met (2024) turns that research into practical advice for managers and their reports².

The report owns the agenda

Grove put it plainly: a one-on-one "should be regarded as the subordinate's meeting, with its agenda and tone set by him"¹. His reason was practical. A manager with eight reports would have to prepare eight times; each report prepares once. Writing the list in advance also forces the report to think through what they want to raise¹.

Rogelberg's research backs this up. In his research, 1:1s with an agenda, written ahead or even at the start of the meeting, were rated as more valuable. But the key was the report taking an active part in drafting it, alone or together with the manager⁴.

Owning the agenda does not mean the manager stays quiet. The manager's job, in Grove's words, is to help the report say "what's going on and what's bothering him," and to "ask one more question" when the report seems finished¹. Rogelberg adds a simple test: the manager should not talk more than the report². The manager can add items, but after the report's.

How often, and for how long

Match frequency to the person and the job. Grove tied it to experience with the task at hand, not general seniority. Someone new to a task might need a 1:1 once a week; an experienced veteran, perhaps once every few weeks. Jobs where things change quickly need more frequent meetings¹.

Keep a fixed rhythm. Rogelberg advises against meeting only when something comes up. He weighs remote work, what the report prefers, time in the role, team size and whether the team already meets weekly when setting the cadence⁵. If a 1:1 has to move, reschedule it close to the original date rather than skip it².

Leave room for hard topics. Grove argued for an hour at minimum, because shorter meetings push people toward "simple things that can be handled quickly"¹. Many teams now use 30 minutes weekly. No study found for this page settles the right length. A fair test: if hard topics never come up, the meeting is too short or too rushed.

What to keep out, and the common mistakes

Much advice says a 1:1 should never cover status. Grove did not say that. His list started with the report's performance numbers, but with the weight on "indicators that signal trouble," then potential problems, and above all the issues that "preoccupy and nag" the report¹. Rogelberg warns that tracking the same numbers every meeting can tip into micromanagement⁴. The line to draw: a status recital belongs in writing, before the meeting. The meeting is for what the numbers do not say.

• The status readout. If the report reads out what they did all week, send it as a note instead. A weekly update covers it, and the 1:1 starts from the questions it raises.
• The manager's agenda. When the manager fills the time with their own items, the report stops bringing theirs.
• Canceling first. A 1:1 is often the first thing a busy manager drops. Each skip tells the report where they rank.
• The late surprise. Grove warned of the "zinger," a big personal issue raised in the last five minutes¹. Ask about how things are going early, while there is time to deal with it.
• No notes, no follow-up. Grove had both people take notes, so a promise is written down "like a handshake" and can be checked next time¹. Rogelberg recommends sharing the notes within two days².

A sample 1:1 agenda, weak and stronger

The person here is invented for illustration: a support team lead, three months into the role, who has been working late. The meeting is 45 minutes, weekly.

The weak version is the manager checking in. The stronger one is built from the report's list, keeps the numbers to the one that signals trouble, and ends with written commitments on both sides.

What a 1:1 does not do, and what to use next

A 1:1 is a regular conversation, not a verdict. Rogelberg describes it as able to support a company's formal review process, not replace it². Some things need their own setting:

• Formal feedback on a year's work. Use the review, and draw on 1:1 notes so nothing in it is a surprise. Performance review phrases can help with the wording.
• Decisions that involve the whole team. Take them to a team meeting with its own agenda.
• Tracking what was agreed. Turn the notes into owners and dates with the meeting action items tool, and open the next 1:1 by checking them.