Skip to main content
Running 1-on-1s That Actually Change Outcomes — Anselm Fowel
Leadership

Running 1-on-1s That Actually Change Outcomes

5 min read
632 views
Share:

The one-on-one is the most powerful tool a manager has and the most commonly wasted. Done well, it is where problems surface while they are still small, where careers quietly get built, and where you earn the trust that makes everything else in management possible. Done badly, it is a recurring status meeting that both people privately resent and would cancel if either had the nerve.

This time belongs to the person, not the project.
This time belongs to the person, not the project.

I have run thousands of these over the years, badly at first and then, slowly, better. Here is what I have learned actually moves outcomes.

It is not a status update

The first and most common mistake is using the one-on-one to ask "what are you working on this week." You have other, better tools for that: a board, a standup, a chat channel, an async update. Spending this scarce, high-trust time on status is like using a scalpel to butter toast. It works, technically, and it wastes the one instrument that can do something nothing else can.

This time belongs to the person, not to the project. The moment that distinction blurs, you have lost the entire value of the meeting and turned it into a slower, more awkward version of a tool you already had.

Their agenda first

I open with a deliberately open question: what is on your mind? And then I shut up. The discomfort of the silence that follows is precisely where the real topics surface, the frustration with a teammate, the worry about a deadline they have not voiced, the half-formed idea they were not sure was worth raising. If I rush to fill that silence, I never hear any of it.

The most useful sentence in a one-on-one is almost always the one that arrives after ten seconds of awkward quiet that you resisted the urge to fill.

Learning to be comfortable with that silence took me years. It still feels slightly unnatural. It is also where most of the value lives.

The questions that earn their keep

When the open question does not unlock things, I reach for a small set of questions that reliably do.

  • What is slowing you down that I could actually remove?
  • What feedback do you have for me that you have been hesitant to give?
  • Where do you want to be in a year, and is your current work moving you there?

That second question is the hardest to ask and the most valuable to hear answered honestly. The day your reports stop giving you feedback is the day you have quietly stopped being useful to them, and they have decided it is not worth the risk of telling you so.

Enjoying this article?

Get more like it in your inbox — practical engineering leadership, fintech, and AI. No spam, unsubscribe anytime.

Close the loop or lose the trust

If someone raises a blocker in a one-on-one and then nothing happens, you have taught them, far more effectively than any words could, that the meeting is theater. They will keep showing up and keep saying nothing real, because they have learned that saying real things changes nothing.

I keep a running note for each person, and I follow up on what they raised, visibly, so they can see the line between what they told me and what then happened. That visible follow-through is the single thing that turns the one-on-one from a ritual people endure into a tool people actually use to get things done.

Adjusting to the person in front of you

There is no single correct format, because there is no single kind of person. A new engineer needs more structure and reassurance and frequent contact. A seasoned senior might need little more than a clear channel and the occasional unblock, and would find heavy structure patronizing. Some people open up immediately; some need the relationship to age before they trust you with anything real. Part of running these well is reading which person you have and meeting them where they are rather than where your template says they should be.

Protect the time fiercely

When things get busy, the one-on-one is the first thing managers cancel, which is exactly backwards. Busy and stressed is precisely when your people most need the channel kept open, when small problems are most likely to be growing into large ones unnoticed. I treat these meetings as nearly unmovable, and the cost of that discipline has, without exception, been lower than the cost of the surprises it prevented. The blow-up you did not see coming almost always had a warning that would have surfaced in a one-on-one you cancelled because you were too busy dealing with blow-ups.

Anselm Fowel, CTO and fintech architect
Anselm Fowel — CTO & fintech architect

Conclusion: the highest-leverage half hour

A well-run one-on-one is, hour for hour, the highest-leverage time a manager spends. It is where retention is quietly won, where careers are shaped, where the small problems get caught before they become the big ones that eat your week. Give it the person's agenda, get comfortable with silence, ask the hard questions, close the loop, and protect the time. Everything else in management gets easier when this one thing is done well.

Enjoyed this article? Share it with others!

Share:

Get new posts in your inbox

Occasional, practical notes on engineering leadership, fintech, and building with AI. No spam, unsubscribe anytime.

Comments (10)

Leave a Comment

Comments are moderated and will appear after review.

Akua Osei

July 27, 2026

Would add: the incentives inside the calibration room matter as much as the actual conversation with the engineer.

Ifeoma Ezeh

July 14, 2026

Junior eng, 12 months into my first fintech role. Reading this after a rough sprint — the "The questions that earn their keep" bit lands, because I spent this week in the middle of first prod incident on my team. Honestly the framing would have saved me at least a Slack DM I regret sending.

Vanessa Garcia

July 12, 2026

Small addition: this stops working the moment the promotion committee stops trusting the manager. That trust has to be earned upstream first.

Andrew Allen

July 12, 2026

Question on "It is not a status update" — how do you actually apply this across a distributed team where you cannot read the room? Struggling with that specific case on my team right now.

Femi Olowu

July 2, 2026

Refreshing to read this framed for our market rather than lifted from a Silicon Valley playbook. Specifically the "Their agenda first" piece — CBN have opinions, and that changes the design constraints in ways the US-centric literature never touches.

Adaeze Ezeh

June 28, 2026

Refreshing to read this framed for our market rather than lifted from a Silicon Valley playbook. Specifically the "Close the loop or lose the trust" piece — the licence guys write it into the audit questions, and that changes the design constraints in ways the US-centric literature never touches.

Michael Allen

June 25, 2026

EM for 5 years, was IC for 11 before that. The "Their agenda first" is what I wish someone had spelled out for me in my first year as an EM — learned it the hard way when a skip-level asked a question I could not answer.

Christopher Thompson

June 21, 2026

Does the "Protect the time fiercely" still hold on a 3-engineer team? We're at the smaller end of that and some of these patterns feel like they need a dedicated ops person to run properly.

Nicole Nelson

June 15, 2026

Does the "Adjusting to the person in front of you" still hold on a 247-service estate? We're at the smaller end of that and some of these patterns feel like they need a dedicated platform team to run properly.

Tyler Wilson

June 14, 2026

Founder-CTO, 5 engineers, 12 months post-launch. Reading this on the walk in — the "Close the loop or lose the trust" bit lands, because I spent this week in the middle of early revenue vs debt on my startup. Honestly the framing would have saved me at least a Slack DM I regret sending.

About the author

Anselm Fowel

Anselm Fowel

Chief Technology Officer & fintech architect. 16+ years leading engineering across AlliancePay, Mondu, Transalliance, Global Accelerex, and Fidelity Bank — writing here about engineering leadership, fintech architecture, and AI in production.

Read next

Subscribe to the newsletter

Practical notes on engineering leadership, fintech, and building with AI — delivered to your inbox. No spam, unsubscribe anytime.

Anselm Fowel

Chief Technology Officer | Fintech Architect | Engineering Leader

Building the future of financial technology through innovative engineering and strategic leadership.

Expertise

  • CTO Advisory
  • Fintech Architecture
  • Team Leadership
  • Technical Strategy
  • System Design

Get In Touch

[email protected]
Lagos, Nigeria

© 2026 Anselm Fowel. Crafted with passion.