Featured on @StorylineReddit: May 6, 2026
A Planner Nobody Reads
A Reddit assistant wedding vacation request sounds routine until the assistant books her ceremony on her manager’s approved time off, and then does it again a month later.
The planner was supposed to prevent exactly this. OOP, who manages a two-person Starbucks kiosk inside a Kroger, created it so she and her assistant Betty could coordinate time off without overlap. Betty’s engagement with the system has been to bypass it entirely, schedule her wedding on OOP’s pre-approved dates, lie to upper management about OOP agreeing to swap, and then, after that gambit detonated publicly on the sales floor, attempt the identical move with a different vacation weeks later.
Once might register as poor planning. Twice, on dates Betty knew were claimed, with a planner she knew existed, stops looking like coincidence and starts looking like a negotiation tactic that only works if the other person eventually gets tired enough to yield.
The Reddit Assistant Wedding Vacation Playbook
OOP manages a two-person kiosk where every absence lands directly on one person’s shift. Betty has built a recognizable rhythm around that constraint: bimonthly sick calls that conveniently extend her regular days off and a flat refusal to cover anyone else’s shifts. She clocks out the moment her hours end regardless of whether coverage exists. None of this has produced meaningful consequences. Management knows. District managers from both Kroger and Starbucks know. The documentation sits in emails and tracking logs, printed and filed in OOP’s locker. The file grows; the response does not.
Against that backdrop, the vacation collision reads less like bad luck and more like a stress test. Betty’s first attempt involved telling management that OOP had agreed to swap dates. When that claim collapsed publicly, Betty absorbed zero institutional fallout. Her second attempt dropped the fabrication but kept the core demand intact: schedule a wedding on OOP’s approved dates and pressure her to move.
The union factor
Betty invokes the union each time a decision lands against her, and management folds rather than engages. OOP has raised attendance concerns through official channels with no visible result. The system protects Betty’s employment while placing the operational burden of her absences squarely on OOP, who already works six days a week. A management structure has outsourced its conflict resolution to the person with the least authority to enforce it, and called that arrangement leadership.
Choosing the Same Dates Twice
Betty knew OOP’s January dates were approved. The planner existed. The system showed the approval. And Betty scheduled her wedding for those exact dates anyway, then told management OOP had volunteered to move.
That sequence does not describe someone who forgot to check a calendar. It describes someone testing whether emotional weight can override procedural order. A wedding outranks an anniversary trip in the hierarchy of social sympathy, and Betty appears to understand that calculus. The lie to management was not a clumsy improvisation; it was a bet that leadership would rather pressure OOP into compliance than navigate the discomfort of telling a bride-to-be no.
The bet nearly worked. Management approached OOP on the sales floor to thank her for her generosity before she had agreed to anything. Without OOP’s immediate correction, the swap would have been treated as settled. Betty’s strategy required exactly one thing: that nobody verify her claim before acting on it. In a two-person department where the other person was standing ten feet away, nobody did.
A System That Punishes the Person Who Uses It
OOP tracks every call-out for every employee, including herself. She has presented attendance data to both district managers. She keeps printed emails in her locker. She files vacation months in advance. She built the planner. None of this has produced a single documented consequence for Betty’s pattern of bimonthly sick calls, shift-end walkouts, or refusal to cover colleagues.
Betty, meanwhile, contacts the union each time a decision goes against her, and management reverses course. The institutional incentive structure is legible: compliance with the system yields nothing, while threatening the system yields results. OOP follows every available channel. Betty bypasses them. Both approaches produce exactly the outcome you would expect if the institution has decided that avoiding grievances matters more than enforcing standards.
The Reddit assistant wedding vacation conflict sits inside this larger vacuum. OOP’s January approval held only because she happened to be present when management congratulated her for a concession she never made. Her June approval held only because she preemptively told her boss before Betty could repeat the lie. Both victories required active defense of a process that should have defended itself.
You can read the for the full exchange, including OOP’s detailed breakdown of the union dynamics.
The File in the Locker
Here the picture gets less clean. OOP has spent a year building a paper trail that no one above her has acted on. She tracks Betty’s absences with the precision of an auditor, prints confirmation emails, and stores them in a personal file. She publicly corrected Betty in front of management on the sales floor. She threatened to go to corporate and the union and to quit, all in a single sentence, in front of her direct report.
OOP stopped managing Betty a long time ago. She is building a case. Those are different jobs. A manager who has shifted entirely into documentation mode has already concluded that the relationship is unsalvageable, and is now performing the role of aggrieved witness rather than supervisor. That does not make her wrong about Betty’s behavior. But it does explain why every interaction between them reads as adversarial rather than hierarchical. OOP does not give Betty instructions and expect compliance. She gives Betty instructions and expects defiance, then records it.
Betty will almost certainly call out during OOP’s Yellowstone trip. OOP already told management to expect it. The prediction will land in the file in the locker, alongside the attendance logs, the printed emails, and the planner entries nobody checked. Whether anyone opens that file remains, as it has for a year, someone else’s decision entirely.
What Reddit Said
The Audience Picks Sides, Then Switches Seats
The largest cluster treats Betty as the sole problem and OOP as a model of professional restraint. These readers fixate on the lie to management and the repeated date-targeting, reading both as evidence of a personality that has never absorbed the word “no.” Their emotional register runs hot, with visceral disgust at adult behavior they code as adolescent. The recurring argument is simple: Betty had a planner, ignored it, and fabricated a concession that never happened. For this group, the confrontation on the sales floor was not an overreaction but a correction that arrived late.
A second, smaller but vocal cluster redirects blame upward. These commenters identify the real failure as institutional: a management chain that receives documentation and does nothing, a staffing model that puts two people in charge of a kiosk and treats one person’s absence as a crisis. Several readers with direct Kroger experience note that store-level managers lose end-of-year compensation for terminations, creating an incentive structure where tolerating Betty costs less than removing her. Their register is analytical, and their frustration lands on the system rather than the individual.
A third cluster questions OOP’s reliability as a narrator. These readers catch specific tells: the dismissal of Betty’s Thursday-Friday agreement as illegitimate because no reason was given, the phrasing of Betty’s wedding as “a wedding she has been talking endlessly about” before revealing it was Betty’s own ceremony, and OOP’s insistence on calling Betty “my assistant” when the actual title is assistant manager. For this group, the narrative control feels too tight, and the details OOP chooses to emphasize reveal someone who has already decided Betty is the enemy and is constructing the story accordingly.
A fourth, quieter thread questions the entire premise. Several commenters point out that this is a coffee kiosk inside a grocery store, not an emergency room. The rule requiring one of two managers present at all times created the conflict, and nobody in the thread can explain why the kiosk cannot simply close for a few days or pull coverage from the broader store.
The comment section splits along a fault line that surfaces whenever a poster presents extensive documentation of a coworker’s failures. Readers who have managed difficult employees recognize the paper trail as a survival strategy. Readers who have been managed recognize it as something else: a supervisor who has stopped attempting to lead and started collecting evidence, which feels less like professionalism and more like preparation for a tribunal that never convenes.
This editorial is based on a story originally shared on Reddit’s r/BestofRedditorUpdates community.