The British Council library used to sit on Fuller Road in Dhaka, on a quiet stretch between the Buet halls and a row of shops where books got bound. I spent late afternoons there in my twenties, on the side of the reading room where the returns trolley got parked at five. The desk staff did something every evening that took me ten years to recognise as the actual shape of the product job.
By five, the trolley would carry sixty books. Some came back without their slips. A few had a yellow post-it stuck to page seventeen with a complaint in pencil. One or two had a torn dust jacket the librarian would silently set aside for the binder. Two or three were on hold for a reader who had asked at the front desk that same morning. By six the cart would be empty, the shelves tidy, and the head librarian, a woman named Mrs Khan who had done that job for forty years, would be drinking the last of her milk tea. The junior who joined three weeks ago was still staring at the cart with the dazed expression of someone who has been handed a small jigsaw and a deadline.
That's the PM job, near as I can tell after a decade of doing it, and the output is not the roadmap itself but whatever lands on Monday, the residue of twenty separate inputs that arrived across the week, sorted by shelf and written up in a vocabulary the team and the leadership can both read without translation.
The inputs arrive whether you want them or not. Eight customer interview notes from research. A sales digest with the same complaint written four different ways by four different account executives. The engineering backlog, which has 187 items in it and will gain 14 more before Monday. A report on a spike in support tickets from the lead on call. The CEO's Monday email, mentioning two trends and an investor conversation by name. Three competitor roadmap leaks somebody screenshotted off LinkedIn at 11pm. A legal risk register with two new lines that GDPR put there. The platform team's deprecation notice. Some piece of internal politics that arrived as a calendar invite with no agenda.
If you read everything carefully, you spend the weekend on it and ship nothing. If you skim, you miss the one ticket that's actually a security incident dressed up as a feature request. The move Mrs Khan made at the cart was sorting on contact rather than reading on contact. A book hits her hand, she glances at spine and slip, and within two seconds it's in one of five places: back on the shelf, held for someone waiting, sent for repair, swapped out, or pulled for good. The reading happened the first time anyone catalogued the book; what she's doing now is moving it to where it can be useful tomorrow.
Marty Cagan, in Inspired, keeps coming back to the idea that the PM's first job is to discover what's worth building. Most PMs read it as "go talk to more customers." Read it twice and the work is closer to what Mrs Khan was doing at five. The books are already on the cart. Discovery is recognising, fast, that the same complaint has come back four times this week dressed as four different feature requests, and writing one line on the new roadmap that names the underlying thing instead of four lines that protect each escalation.
Julie Zhuo has written about this from the design management side, and her version of the move is calling it "the synthesis muscle." The muscle metaphor undersells it, in my view. Synthesis is a vocabulary you build over years, of the same shape of thing you've seen ten times before. The reason Mrs Khan could clear the cart by six was that she'd seen most of those books in most of those states already.
The junior couldn't, because every book on the trolley was a new species.
Lenny Rachitsky's interviews with senior PMs keep landing on the same pattern when he asks about roadmap structure. The good ones describe a weekly grooming ritual that has less to do with planning and more to do with editing. Inputs come in, they get sorted, the public artifact gets a single new line, and the rest of the work disappears into one of the other four bins. The bad ones describe a calendar full of meetings they call planning, and a roadmap that's still mostly what was there in January with seventeen extra bullets in the comments column nobody reads.
The editing frame matters because it makes the omissions legible. A roadmap that has every input on it isn't a plan; it's a memo from the desk to itself. Bret Victor's Inventing on Principle talk circles a related idea about the medium being the message. A roadmap that takes eight pages is, by virtue of being eight pages, telling the team they have not yet decided what matters. A roadmap that takes a page is doing the cart sort in public.
The habit worth stealing is to do the sort yourself every Friday between four and five, on paper, away from the laptop. Stickies on a wall, or index cards on a desk, but with the explicit job of touching every input once and assigning it a bin. The ones that resist sorting are the interesting ones, and they go in a small pile of their own, the working analogue of Mrs Khan's index card box. The sorted seventeen out of twenty that landed cleanly, with the duplicates already stripped out, are the raw material from which Monday's update, running to a single line, writes itself.
The grammar matters more than people who haven't done the job want to believe. A roadmap that says "investigate retention" is doing a different cognitive job from a roadmap that says "ship a flow that wins back users who've gone quiet for thirty days, before the GTM kickoff in July." The first is a sticky note that hasn't been sorted. The second is a shelved book, with a spine the team can find when they need it. The skill is in arriving at the second sentence after having read, sorted, and discarded the seventeen other framings that were sitting in the same cart.
The PM I most admired at one of my old jobs used to come back from Friday lunch around half past one. She'd close her door at the Mohakhali office until quarter to four, then emerge with a single A4 sheet that had eight lines on it. Eight lines. She'd read forty things that week and talked to twenty people, on top of six hours of meetings. What landed on the sheet was the residue. The team would read it on Monday, fold it once, and put it in their notebooks. The lines stayed roughly the same from quarter to quarter, which made the rare changes visible. None of the words people reach for, synthesis, grooming, editing, were what she called it; what she called it was "tidying the desk," the most accurate name I've ever heard for the job.
The juniors who watched Mrs Khan for two years started doing the same sort in half the time, on their own carts, on their own evenings. The ones who never figured it out either left the library for the bank across the road or stayed at the desk reading every book that came in and apologising at six for being behind. The job is sortable, and it can be learned, but the learning happens at the cart on Friday afternoons, with a small pile of index cards and the discipline of touching every input exactly once before going home.