Listen, baba. You know the boy who came back from Singapore last Eid, the product wala, slimmer than his sister's wedding card and twice as serious? He sat at our table for an hour and told a story I have been chewing on all week. He shipped a feature, he said, from his desk in a shared workspace. Two quarters later somebody from compliance wrote a polite email and the feature was rolled back in week 23. The objection was reasonable, it just arrived very late. He had asked the customer, asked the sponsor, drawn a chart in four colours for the steering committee. He had not asked the eight people who actually decide whether a feature lives.
The customer and the sponsor are the two everyone counts, like the bride and the groom. seat 01· the customer told you what they wanted in a research call, you wrote it down, you misheard half of it, and at least the transcript exists. seat 02· the sponsor signs the budget and will defend the feature exactly as long as the quarterly numbers justify it, then quietly stop replying when their KPI changes shape in October. Fine, two people, half the room. The other six are the ones the boy missed, and the other six are the reason his feature is now a footnote in somebody's quarterly review.
Eight seats around your feature
Eight seats. One pot. Drag to spin, tap to sit.
Take Razia apa's nephew, who runs the steering committee at a bank in Motijheel. seat 03· the skeptic on his committee has been against the project since kickoff in February, was overruled in March, sat quietly through April, May, June, then resurfaced every single objection in July when the launch slipped by a fortnight. The man has the memory of an elephant on payroll, which is exactly what Razia apa says about her husband when he brings up the haleem from the 2019 Eid that she will never live down.
seat 04· the drive-by VP, the one I cannot stop laughing about. He walks into a sprint review at minute 38 of a demo that ran 45 minutes with one question that reframes the whole feature, and the boy from Singapore does not sleep that night. The toddler at the dawat does the same trick with one grain of rice and a packet of Pran chips, and somehow gets the whole room to rearrange around him for ten minutes.
seat 05· legal, please, do not get me started on legal. Legal replies in six weeks. The reply is two lines. The two lines change the data model, and the change cannot be negotiated. This is exactly Sharmin bhabi's vegetarian cousin from Mirpur, who is treated as a "logistical exception" at every dawat for fifteen years. Plan around her in week one. The whole evening becomes easier.
seat 06· the auditor does not exist yet, and this is the part that makes me clutch my dupatta. He will exist in fourteen months. He will be polite, and he will be devastating. He will ask why a particular field is collected, why it isn't deleted on a schedule, and whether the consent screen was tested in Bangla. Exactly like Khaleda khala's diabetic father, whose plate must be set aside before the guests arrive, because if you wait until the rush you will plate him chicken when you should have plated him fish.
The last two are about you. seat 07· past-you wrote the PRD with a different brain, and used the word "obviously" in two places that, on rereading in week eleven, are not obvious to anyone. This is the friend who showed up unannounced with a plus one at the dawat in 2022. She had told you, in passing, on the phone, while you were cooking, but you had not heard her. The plus one was real. The miscommunication was also real.
seat 08· future-you is the one nobody warns you about. She has to maintain the feature, currently does not know it exists, and in eighteen months she will open the codebase and read a comment that says // see PRD section 4.2. The Confluence has been migrated twice in the meantime, section 4.2 no longer exists, and she will weep into a cup of Square cha. Future you is the one who claims rights to the leftovers, calling dibs on the haleem before the lid is even off the pot. She does it eighteen months late, and the pot is empty.
Why does everyone underestimate the count this consistently? Partly because PM training emphasises the user, who is the easy stakeholder. Most of the people who will touch your feature are not loud. They show up late, in writing, with one specific concern that costs you a sprint.
The other reason is that "stakeholder management" sounds boring, so PMs delegate it to a RACI chart, four colours, a Confluence page, and consider the matter closed. Patrick Lencioni has been making the same point about meetings and accountability for twenty years now, and the line that lands with me is that the chart is the artifact you produce after you have actually had the conversation. Most teams ship the chart and never quite get around to having the conversation. The boy from Singapore did this in 2023, in front of a sponsor he had to email an apology to before lunch.
repeated for a week in the WhatsApp group
“The number of people who will quietly touch your feature is fixed long before the kickoff meeting, and the only variable is how many of them you have actually noticed by the time the launch ships.
”
— overheard, table four
What actually helps is unromantic, the way most useful things are unromantic. Three habits, which the boy and I argued about over the last cha of the night.
First, write everything down, even when nobody asked, especially the throwaway hallway comment from the VP who just drops by, at minute 38. The act of writing forces you to name the stakeholder, which is most of the battle. A markdown file in the repo is best, because future you actually reads those, while the Confluence page is read by no one except the auditor in fourteen months who will use it against you.
Second, share the document earlier than is comfortable. A messy doc circulated in week one beats a perfect doc circulated in week six, because the messy version surfaces the skeptic on the steering committee before they have privately decided you are a problem. You will feel exposed when you press send, and that feeling is the point of pressing send. Third, do not surprise anyone, ever, on anything that costs them work. Legal should hear about a particular data flow from you in a call of fifteen minutes in week two, not from a dashboard in month four when their inbox is fielding three other surprises. Fifteen minutes of warning ahead of time prevents about a quarter of the unscheduled rework, give or take, and the prevented quarter is the one that ate your November.
None of this is clever. It is the boring habit of remembering that other humans exist and have replies sitting in their inbox queue, which is the entire job of hosting a dawat for forty in May.
A daawat in Dhaka makes the same point in a different vocabulary. My mother-in-law decided, in April this year, to make biryani for forty for my husband's cousin's son's aqiqah, and there were eight stakeholders at that table too, exactly the same eight. The host who agreed to the date before checking the calendar. The mother-in-law with firm views on aloo (it should). The picky uncle who eats only one cut of mutton from the shoulder. The vegetarian cousin still treated as a logistical exception. The diabetic grandfather whose portion is plated before guests arrive. The toddler with his one grain of rice and his Pran chips. The friend with the surprise plus one. The one who claims rights to the leftovers, who called dibs on the haleem before the lid even came off.
The host who plans for the host and the mother-in-law and treats everyone else as an edge case runs out of mutton at 8pm and gets quietly written off in the WhatsApp group for a year. The host who has already plated the diabetic grandfather's portion, messaged the picky uncle on Imo about his piece, and texted the one who claims rights to the leftovers a polite no, runs an evening that gets remembered the right way, and she gets invited to plan the next one too. Your feature is the pot, the aunties are the steering committee, and the toddler with the Pran chips is the VP who just drops by. The dawat circuit has been operating on this metaphor for thirty years, and the biryani keeps being eaten.
A younger version of the boy would have made fun of that header on Slack, the way the rest of us made fun of seating charts right up until the year we had to host our own dawat for forty. It looks like bureaucracy. It is the opposite of bureaucracy, which is why it takes people a while: bureaucracy is a form you fill in because somebody requires it, and the header with eight bullets is a list you keep because you have personally run out of mutton at 8pm and do not intend to do it twice.
He will find one in somebody else's README.md next quarter, inherit eighteen months of a codebase along with it, and copy the format into his own PRD inside the week without mentioning where he got it. Then he will sit at our table on the Friday and describe it as something he had been meaning to try. Nobody in this family is going to say the words out loud, but his naani will pour him a second cup, which in this house is the same thing.