✶ TL;DR
Office gift coordination is the last unautomated workflow at most companies. The work is real — 3–6 hours per milestone, often spread across one to two weeks — and it concentrates on three roles: Executive Assistants, Chiefs of Staff, and Community Managers who do it on top of their actual jobs and rarely get credit for it. It's structurally invisible because the labor lives in the margins of paid time, the output is undocumented, and the work concentrates in roles whose seniority varies dramatically across organizations. The operational difficulty has gone up since 2020, not down: hybrid work broke physical proximity, payment apps fragmented, bank-level KYC cracked down on personal-account use, and generational gift-amount norms diverged. What good looks like isn't exotic — just every other modern operational workflow done well.
Three People Who Do This Work
The first thing worth saying clearly: the work is real. It isn't trivial. A typical office milestone — retirement gift, baby shower, sympathy collection, work anniversary — takes three to six hours of coordination spread across one to two weeks. Someone has to identify the moment, decide whether and how to mark it, draft the message to the team, set the contribution range, set up a collection, chase the slow contributors, decide what the gift should be, buy and assemble it, write or coordinate a card, and figure out how to present it.
In modern organizations, this work concentrates on three roles: the Executive Assistant who supports the senior person closest to the recipient and runs most office-level coordination as part of an already-full workload; the Chief of Staff in leaner orgs who inherits this kind of work because they inherit everything that doesn't fit anywhere else; and the Community Manager, the newest archetype, organizing the same work for distributed groups (alumni networks, fellowships, cohort programs, executive networks) that don't share an office at all.
If you're an executive reading this
Your reaction may be: but does anyone really care if we forget to do this? You'd be surprised how much people notice. The retirement that doesn't get marked properly is something people remember for years. The labor of remembering and coordinating is not optional infrastructure — it's part of how organizations actually treat their people, and people know which orgs do it well.
Why It's Structurally Invisible
Here is the strange part. None of this work shows up anywhere. It doesn't appear in any tool the company has bought. It's not on the EA's job description in a meaningful way. It produces no documented output beyond an envelope and a card. It's not measured, not reviewed, not budgeted, not staffed.
This isn't an accident — it's a structural feature with three causes: the labor lives in the margins of paid time so it never gets a calendar block or a budget line; the output is socially valuable but operationally undocumented (there's no project plan saying "deliverable: retirement card with all 47 signatures"); and the work concentrates in roles whose seniority varies (an EA earning $80K and a Chief of Staff earning $300K can end up doing the same task in different organizations).
Read the full briefing
The complete briefing covers the four reasons it's gotten harder since 2020 (hybrid work, payment app fragmentation, bank-level KYC, generational norm divergence), what good looks like, and how this connects to the broader pattern of unrecognized organizational labor.
No credit card. The full briefing opens right away.
Why It's Gotten Harder Since 2020, Not Easier
You'd think workplace technology improvements would have made this easier. They haven't. Four reasons: hybrid work broke physical proximity (the pre-2020 office gift workflow ran on physical adjacency)...
████████████████████████████████████████████████
What Good Looks Like
The version of this that works is not exotic. It looks like every other modern operational workflow does when it's done well — automated where possible, judgment-preserving where necessary, observable, and respectful of the people involved...
████████████████████████████████████████████████