How to Run One-to-One Meetings: What to Talk About and How to Make Them Count

When Victoria came to the throne on 20 June 1837 she had only just turned eighteen. She had lost her father at eight months old and knew nothing of the business of state. The Prime Minister, Lord Melbourne, was forty years her senior, and for the next four years he became the young queen's tutor in politics.
It was a one-to-one meeting in the sense we use today, and an extraordinarily intense one. According to his biography, the Prime Minister spent four to five hours a day visiting the Queen and writing to her. He was even given his own apartment at Windsor Castle. Victoria saw him as a father figure.
Then came May 1839. With his government weakened, Melbourne meant to resign, and the opposition leader Robert Peel was called to form a government. Peel set one condition: some of the Queen's ladies of the bedchamber had to go; many of them were the wives and relatives of leading figures in Melbourne's Whig party. Peel wanted to replace only six of the 25, but he never made that clear to the Queen. Victoria saw her ladies as close friends and refused. Melbourne backed her. Peel declined to form a government and Melbourne stayed in office. History remembers it as the Bedchamber Crisis.
Years later Victoria weighed her old tutor more coolly: she said Melbourne had been too much of a party man and had made her a "Party Queen". Five hours of one-to-one time a day had taught a young sovereign politics. But in those hours it was mostly the teacher who talked, and the pupil had learned to see through the teacher's eyes.
Whose time is the one-to-one?
The regular one-to-one a manager holds with each person on the team is now the most frequently repeated meeting in many companies' calendars. It is also the one most easily wasted. In a roundup of its pieces on these meetings, First Round Review gathers advice from six experienced managers. What they share is the thing Melbourne could not do: using the meeting to grow the other person's thinking.
Hand the meeting over
Michael Lopp, who has led engineering teams at Apple, Slack and Pinterest, recommends a 30-minute meeting every week but booking 45 minutes in the calendar in case it runs over. In his view the time belongs to the report, not the manager. Meetings tend to fall into one of three types: the update, the vent or the disaster. Someone who is venting wants to be heard, not fixed. Keep three topics ready in case you hear "there's nothing to talk about".
Ask before you advise
Julie Zhuo, who spent fourteen years building the design team at Facebook, says a coach's best tool is to ask. Her questions fall into three groups: "What's top of mind for you right now?", "What does your ideal outcome look like?" and "How can I help you?" Lenny Rachitsky, a former product lead at Airbnb, has an even shorter rule: when asked for advice, first say "Before I answer, what do you think?"
Look for the cause, not the symptom
John Milinovich, founder of URX, opens every one-to-one with "Where's your head at?" and asks in detail at which point in the day, in which meeting or with whom the stress rises. Maggie Leung, who built the content team at NerdWallet from scratch, likes a different question: "What's harder than it should be?" In Leung's words, it helps you smell smoke early. A manager who tries to fix each symptom one by one easily slides into micromanagement.
Put the career on a separate table
Rachitsky describes how, after a performance review, his report kept only vague memories of the feedback, with 95% of the message lost. So he suggests keeping the weekly meeting for projects and blockers, holding a separate monthly conversation for career development, and keeping a running note for each person that logs specific wins and misses with dates. That way, when a hard conversation comes, for example with someone whose performance is slipping, nothing comes as a surprise.

An audience: a word that comes from listening
Being received by a sovereign is called an audience in English. The word comes from the Latin audientia, "hearing", and at its root is the verb audiō, "I hear". Since the 16th century it has also meant a formal meeting with a dignitary. In other words, that meeting was named after listening, not talking.
Listening is not easy, because the other person does not tell you everything. In a study published in Sociometry in 1970, the psychologists Rosen and Tesser gave the name MUM effect to people's reluctance to pass on unwelcome information. In a team, bad news may also slow down most on its way to the manager. The weekly meeting may be the only regular door that news comes through; if the manager fills the doorway with talk, the news does not arrive.

To be consulted, to encourage, to warn
In 1867, thirty years after Victoria came to the throne, the English writer Walter Bagehot summed up the power left to a constitutional sovereign in The English Constitution as three rights:
"The right to be consulted, the right to encourage, the right to warn."
To be consulted, to encourage and to warn. Not to decide. According to Bagehot, a sovereign of real sense would want no others. A manager's role in a good one-to-one is much the same. So in this week's meeting, who made the decision: the person across the table, or you?
If you want to think about how to phrase the hard words in that meeting, How to Give Your Team Feedback is worth a read.


