~/aakash
Writing ← Portfolio
Project Mgmt December 23, 2026

A Week in the Life of a PM in 2026

None of the individual days look dramatic. Put together, the shape of the job has changed more than any single one of them shows.

01

Monday: the update writes itself

The status update writes itself before I have finished my coffee, pulled together from the tickets and the commits. It is well formatted and mostly accurate. I spend the time it saved me doing the thing it cannot: working out whether "mostly accurate" is hiding the one thing that will matter this week. It is. A developer went a bit quiet on Friday, and quiet usually means stuck.

Five years ago that update was an hour of my Monday. Now it is done before I sit down, and the hour goes into the conversation the update could not have known to start. On balance that is a better Monday. It just does not feel like less work, only different work.

That swap is the whole story of the job in miniature. The visible, produce-a-thing work got handed to the machine, and what came back in its place is quieter and harder to point at: noticing, deciding, following up on a hunch about a developer who went quiet. It does not photograph well. It is most of what actually matters this week.

02

Tuesday and Wednesday: saying not yet

Tuesday. Three features could start today. The team clearly has room. I say not yet to two of them, which feels wrong every time, because starting is nearly free now and saying no leaves nothing to show for itself. But an easy start is not an easy finish, and a fast team aimed at a half-formed idea only arrives at the mess quicker.

Wednesday. A client watches a rough version come together in an afternoon and asks why the rest takes weeks. I explain, again, that the afternoon was the cheap part and the weeks are the decisions, the edge cases and the being-sure. It lands, because it is true. I schedule an article to go out today, which is either fitting or a bit too on the nose.

Both days are really the same lesson wearing different clothes. Tuesday it is holding the line at the front of the pipeline. Wednesday it is explaining that the cheap-looking part was never the expensive part. Both are me standing between how fast things now look and how fast they actually are, which is a fair description of the whole role lately.

03

Thursday: the thing I almost did not read

I catch myself about to forward something an agent generated without really reading it, because it looked done. I stop and read it. There is a small assumption buried in it that none of us actually made. Ten minutes now, an awkward conversation avoided later. This is most of the job now, quietly, and none of it shows up on a board.

Half of what I do in a week is decide which of the machine's confident answers to actually believe.

04

Friday: reviewing what nobody quite understands

I review code the team shipped this week and spend most of the time not on whether it works, it works, but on whether anyone actually understands it, or whether we have accumulated a small pile of things that pass their tests and nobody could fix at two in the morning. Some of both. I make a note to slow down next week, knowing I probably will not.

That note-to-self, made every Friday and rarely kept, is at least honest. The pace does not really let up, and the tools that made it fast are not going to make it slow again. So the discipline has to come from me, in small deliberate acts of slowing down: on a Thursday that looked done, on a Friday review nobody asked me to dwell on. That is the job now, and mostly it is invisible.

If you had shown me this week five years ago, I am not sure I would have recognised it as project management. Less making things happen, more deciding what to believe. But it is the same job underneath, aimed at the same thing: getting a good outcome, safely, with someone answerable for it. The tools just moved where the hard part lives, and the hard part, as ever, is the part worth being here for.

None of the individual days look dramatic. Put together, though, the shape of the job has changed more than any single day shows. Less of it is making the work happen, the work happens fine now, sometimes too easily. More of it is judgment, reading, and deciding what to trust. The parts that used to feel like the job, the tidy board, the clean report, mostly run themselves. What is left is the part that was always the actual job and never looked like much from the outside.

So I am curious what your week actually looks like now, under the tools: has the shape of your job changed more than any single day of it lets on?