All posts

1:1s that aren't just status updates

Published May 2, 2026 · by Majd Ghithan, written with the help of AI

1:1s that aren't just status updates

For my first few months as a lead, my 1:1s were thirty minutes of me asking "so, what are you working on?" and nodding at answers I already knew from standup. We both left slightly bored. It took one of my engineers quietly quitting, blindsided me, gave two weeks, had a whole story I never heard, for me to realize what those meetings were supposed to be for, and that I'd been wasting every single one.

A 1:1 is the one meeting that isn't about the work. It's about the person doing the work. The moment it becomes a status update, you've replaced the only conversation you get about them with information a Jira board already has.

Status is the thing 1:1s should never be

Here's the test I use now: if the answer to a question is already on the board, I don't ask it in a 1:1. I can see the tickets. I know what shipped. Spending our thirty minutes re-narrating the sprint is the most expensive way possible to learn something I could read in ten seconds.

What the board can't tell me is the stuff that actually decides whether this person stays and grows: Are they bored? Are they stuck on something they're embarrassed to raise in public? Do they feel like their work matters? Is there a manager-shaped obstacle only I can move? None of that shows up in a commit history, and none of it comes out if I open with "so what are you working on."

Good 1:1 vs wasted 1:1

Wasted 1:1Good 1:1
Who talksI do, mostlyThey do, ~70%
TopicThis week's ticketsCareer, blockers, how they're feeling
Agenda ownerMeThem (I ask what's on their list first)
SilenceI rush to fill itI let it sit; the real thing comes after
Blockers"All good?" → "yep""What's the most frustrating part of your week?"
ResultWe both forget it by lunchThey leave with something, so do I
NotesNoneI keep a running doc per person

The single biggest lever in that table is who's talking. If I'm doing most of the talking in a 1:1, it's not a 1:1, it's a broadcast. My job is to ask a real question and then shut up long enough that the honest answer has room to arrive, which is usually a few seconds after the polite one.

The questions that actually open things up

"Everything good?" gets you "yeah, all good," every time, because it's a yes/no shaped like a door already closing. The questions that work are specific and a little harder to deflect:

  • "What's the most frustrating part of your week right now?"
  • "Is there anything you're working on that you don't find interesting? What would you rather be doing?"
  • "Six months from now, what do you want to be able to do that you can't yet?"
  • "Is there anything I'm doing, or not doing, that's making your job harder?"

That last one is the scariest to ask and the most valuable. It gives explicit permission to critique me, and the first time someone actually takes it, you learn something about yourself you'd never have found otherwise.

Cadence and notes, the boring part that makes it work

Weekly if I can, every two weeks minimum. Less than that and it stops being a relationship and becomes an occasional performance review, which is exactly the wrong energy. And I protect the slot, cancelling a 1:1 because "nothing urgent" sends the loudest possible message that the person is lower priority than whatever bumped them. If I truly must move it, I move it, I don't cancel it.

I keep a running note per person, one doc, newest at top. What we talked about, what they said they wanted, what I promised to follow up on. It does two things. It means I actually close the loop on "let me look into that" instead of quietly forgetting, which is how trust dies. And over months it shows me the pattern, the same frustration surfacing three times isn't a mood, it's a problem I've been nodding past.

The point

A 1:1 is the cheapest retention and growth tool you have, and the easiest to fumble into uselessness by treating it as a status meeting. The status you can get anywhere. The thirty minutes where someone tells you what they actually want, and what's actually in their way, you only get if you stop asking about the tickets and start asking about them.

I learned that from someone's resignation letter. You can learn it from this instead.

🤖 Heads up: this post was drafted with AI. Spot something wrong or off?Edit it on GitHub & open a PR
Majd Ghithan

Majd Ghithan

Full-Stack Engineer & Tech Lead

More posts

Laravel finally resizes images for you

Laravel finally resizes images for you

Every Laravel app I've built that takes an avatar ended the same way: composer require intervention/image, wire up a facade, write a little service class, and hope the next dev…

July 26, 2026Read more
What actually breaks at 100,000 users (that never breaks in a demo)

What actually breaks at 100,000 users (that never breaks in a demo)

The first time I shipped a dashboard to a hundred thousand active users, nothing I had tested was what broke. Everything that failed had passed every check I ran. It worked on m…

July 25, 2026Read more
Where your queue jobs go to die under load

Where your queue jobs go to die under load

The support ticket said "I never got my invoice email." I checked the logs. The job ran. It succeeded. failedjobs was empty. Everything said the email went out. It did not.

July 18, 2026Read more
The indexes you're missing (and the one that's hurting you)

The indexes you're missing (and the one that's hurting you)

A client sent me a query that took 4.2 seconds. One WHERE, one ORDER BY, a table with three million rows. I added a single index and it dropped to 11 milliseconds. They asked if…

July 11, 2026Read more
Caching in Laravel without the stampede

Caching in Laravel without the stampede

We cached the homepage's "trending products" query for five minutes. It was our slowest query — about 900ms, a big aggregation across orders. Caching it took the homepage from s…

July 4, 2026Read more
Taking one endpoint from 800ms to 80ms

Taking one endpoint from 800ms to 80ms

The order-details endpoint took 800 milliseconds. Not broken, just slow enough that the app felt heavy everywhere it was used. The team's instinct was "the server needs more mem…

June 27, 2026Read more
The N+1 you can't see (it's hiding in your accessors)

The N+1 you can't see (it's hiding in your accessors)

I've fixed hundreds of N+1 queries. The easy ones are right there in the controller — a foreach with $order-customer inside it, obvious the moment you read the code. Those aren'…

June 20, 2026Read more
The Friday deploy that charged customers twice

The Friday deploy that charged customers twice

It was 4:40 on a Friday. The change was tiny — a one-line tweak to how we called the payment provider, plus a bump to the queue worker's timeout. Small, tested, reviewed. I depl…

June 13, 2026Read more
Code review people don't dread

Code review people don't dread

I once left forty-one comments on a junior's pull request. I was proud of it. Thorough, I told myself. The next day he barely made eye contact, and his next PR sat open for a we…

June 6, 2026Read more
Hiring a mid-level Laravel dev: the signals that actually matter

Hiring a mid-level Laravel dev: the signals that actually matter

The best hire I ever made failed my first question. I asked him to explain service containers and he stumbled, went quiet, then said "honestly I use them every day but I've neve…

May 30, 2026Read more
Saying no to a feature without being the 'no' person

Saying no to a feature without being the 'no' person

For about a year I was the engineer everyone learned to route around. Not because I was wrong, I was usually right, but because my answer to new ideas was a flat "no, that'll br…

May 23, 2026Read more
My first 90 days as a tech lead (and the habit I had to break)

My first 90 days as a tech lead (and the habit I had to break)

Three weeks into leading my first team, I stayed late to "help" by rewriting a junior's feature myself. It was faster my way. I pushed it, felt productive, went home. The next m…

May 16, 2026Read more
Breaking down the task that scares you

Breaking down the task that scares you

There's a specific kind of ticket that makes my stomach drop. Not the hard ones, hard is fine. It's the ambiguous ones. "Migrate billing to the new provider." "Add multi-tenancy…

May 9, 2026Read more
Get the business logic out of your controllers

Get the business logic out of your controllers

I once opened a OrderController@store method that was 240 lines long. Validation, a discount calculation, three model writes, a Stripe charge, two emails, a Slack notification,…

April 25, 2026Read more
Form Requests are the most underrated thing in Laravel

Form Requests are the most underrated thing in Laravel

Most Laravel devs meet Form Requests once, in a tutorial, use them to hold a rules() array, and never look deeper. That's a shame, because a Form Request is the cleanest place i…

April 18, 2026Read more
Testing Laravel without mocking everything

Testing Laravel without mocking everything

I inherited a codebase once with 900 unit tests and no confidence. Every test mocked the repository, mocked the model, mocked the mailer, mocked the thing three layers down. The…

April 11, 2026Read more
Three Eloquent features that clean up your models

Three Eloquent features that clean up your models

The messiest Laravel model I ever wrote wasn't messy because of Eloquent. It was messy because I ignored the parts of Eloquent that exist specifically to keep it clean. The same…

April 4, 2026Read more
The migration that locked the table for eight minutes

The migration that locked the table for eight minutes

The deploy looked boring. One migration, adding a lastseenat column to the users table with a default of now(). I'd written a hundred like it. I ran it at 2pm on a Tuesday becau…

March 28, 2026Read more
Chasing a memory leak in a Laravel queue worker

Chasing a memory leak in a Laravel queue worker

The alert came in at 4am: one of our queue:work processes had been OOM-killed. The supervisor restarted it, it processed jobs for about forty minutes, and got killed again. It w…

March 21, 2026Read more