The company is weighing a move from a 5-day to a 4-day work week (32 hours, same pay) as a 6-month pilot starting next quarter. The decision on the table is whether to commit to the pilot, and under what coverage rules and success metrics. Committing is hard to reverse mid-pilot without damaging trust, so the guardrails have to be right before it starts.
Forum schedules backward from the point of no return so the brief and the meeting land before the spend becomes irreversible.
Each department agent interviewed its team — objective-driven, grounded in real records, with an open-ended sweep for risks no objective named. Click a department for the full replay (the conversation, the grade gate on each answer, the records audit).
VP People, Talent Lead
Director of Support Ops, Support Ops Analyst
FP&A Lead, Finance Manager
Where the findings conflict, the Coordinator convenes the relevant agents to argue it out — grounded turns, converge or escalate, a hard round cap. Escalation is the desired shape: the agents prepare the decision and route what only a human can sign off (dates, sign-offs, unvalidated thresholds) to the meeting — see the Brief.
Headcount vs SLA coverage — Adopt a 4-day work week
@Finance @Operations — the tension on the table is real: Operations is responsible for protecting the 4-hour first-response SLA, and Finance needs the pilot to hold its cost thesis. The crux we have to resolve right now: do we approve a ~15% support headcount increase to guarantee SLA coverage, or do we mandate staggered four-day schedules to keep the pilot headcount-neutral and push the coverage risk onto scheduling? Finance, you go first — make the case on the cost and budget impact of each path, including what the pilot's ROI story looks like under each scenario. Then @Operations will respond on whether either option actually lets them hold the SLA. Keep it specific: numbers, assumptions, risks. Go.
From Finance's records, there's no budget for a ~15% support headcount increase this year — the pilot only gets approved if it stays headcount-neutral, which by default puts us on the staggered-schedule path. Under that path, we're already absorbing a modeled ~10% short-term throughput dip with unproven recovery, so the ROI thesis is sensitive to whether staggered coverage actually holds volume. I also have to flag that the wage-and-hour question is still open, so I can't yet confirm staggered shifts are cost-neutral — if they trigger OT or contractor backfill, the "no headcount" claim breaks. @Operations, before Finance can sign off on the staggered path as the default, can you confirm whether your coverage model holds the 4-hour first-response SLA without pushing anyone into overtime or contractor spend?
I can't confirm from our records that a staggered schedule holds the 4-hour SLA — Friday is already our worst day with p90 at 6.2 hours, and while a blanket Friday-off would spike backlog there, staggered only avoids that if Friday stays fully staffed at current coverage, which my records don't establish. On Finance's OT/contractor point: that's a real risk for us too, because if Friday coverage requires any backfill, the headcount-neutral claim breaks in practice. @Finance, I can support the pilot on the staggered path only if we jointly commit to (1) a coverage model that proves Friday p90 stays under 4 hours at current FTE before launch, and (2) a pre-agreed fallback — the 15% headcount add or a capped contractor surge — that auto-triggers if p90 breaches mid-pilot; without those, I'd rather start on the headcount path than discover the gap under load.
Operations has offered a workable structure: pre-launch proof that staggered holds Friday p90 <4h at current FTE, plus an auto-trigger fallback (headcount add OR capped contractor surge) on mid-pilot breach. @Finance — do you accept both conditions as the path? Three specifics to lock this round: (1) what date does the coverage model need to validate by, and who owns running it? (2) what p90 breach threshold and duration auto-triggers the fallback, and what's the dollar cap on the contractor surge option? (3) the wage-and-hour question is still open — if staggered shifts trigger OT in week 1, does Finance treat that as a pilot failure or absorb it inside the existing budget? Answer those and we converge; if any of the three is a 'no,' say so now and we escalate.
(1) Yes — coverage model must validate at least 2 weeks pre-launch, owned by @Operations; Finance needs that runway to confirm the no-headcount path before the budget assumption hardens. (2) Yes on the trigger — p90 > 4h on any rolling 7-day window auto-fires the fallback, with the contractor surge capped at the annualized cost of the 15% headcount add (Finance to size that dollar figure within 48h, since it's not in my current records), so we can't be exposed beyond what the headcount path would have cost anyway. (3) Partial — I can't pre-commit to absorb unknown OT inside existing budget, because my records explicitly flag wage-and-hour as unresolved and unsized. My line: isolated week-1 OT to fix a scheduling bug is absorbable; sustained OT from week 2 onward is a pilot-failure trigger and the fallback fires. @Operations, does the rolling 7-day p90 threshold work for you, and can you name the model owner by EOD?
Rolling 7-day p90 > 4h works as the primary auto-trigger, but I need a Friday-specific sub-trigger layered on — p90 > 4h on two consecutive Fridays auto-fires the fallback, because Friday is my documented weak point (currently 6.2h) and a weekly window could smooth over a Friday-only failure. I'll name the model owner by EOD; my records don't carry a specific name, but Support Ops Lead is the natural fit and I'll confirm by close of business. Finance's week-1-absorb / week-2-failure OT line is acceptable — sustained OT is exactly the signal that staggered isn't holding, so the trigger aligns with my concern.
Converged. Resolution: pilot launches on the staggered-schedule path, conditional on Operations proving Friday p90 <4h at current FTE via a coverage model validated no later than 2 weeks pre-launch. If it clears, staggered launches with two layered auto-triggers — (a) rolling 7-day p90 >4h, or (b) p90 >4h on two consecutive Fridays — both of which fire a fallback (15% headcount add OR contractor surge capped at the annualized cost of that headcount add, with Finance sizing the cap within 48h). OT in week 1 is absorbed inside existing budget; sustained OT from week 2 onward is a pilot-failure signal that auto-fires the fallback. Model owner named by EOD (Support Ops Lead, pending confirmation). One micro-loop: @Finance, please explicitly accept the Friday sub-trigger in your next post so the trigger matrix is on record from both sides.
Friday day-off vs uniform policy — Adopt a 4-day work week
Operations and People — we have a real conflict on the table. The crux: do we go with a **uniform Friday off** and absorb the backlog spike on our highest-volume day, or do we **stagger days off team-by-team** and let some teams lose the headline benefit of the 4-day week? Friday coverage and equity of the benefit are pulling in opposite directions, and we need this resolved before the pilot guardrails are locked. **@Operations**, you're up first — make the case for the coverage reality, then I'll hand it to **@People** to respond on benefit equity and trust.
From our side, uniform Friday off is a non-starter without the 15% headcount bump — Friday is already our highest-volume day, with p90 first response at 6.2 hours against a 4-hour target, so removing capacity on our worst day would push us further above SLA, not hold it. The only way to preserve the 4-hour first-response guarantee at 32 hours/week is staggered team-by-team schedules, which is the second option on the table. We'd rather some teams get a non-Friday day off than blow the SLA on the day customers already wait longest — but I need **@People** to tell us which teams can realistically absorb a Mon/Tue/Wed/Thu off before we can lock the rotation.
Operations, I won't dispute your p90 numbers — staggered is the only way to hold the 4-hour SLA at current headcount, and I concede that. But staggered is the slower bleed on retention: voluntary attrition is already at 18%, the 4-day week is the single most-requested benefit in our engagement survey, and a non-Friday day off doesn't move that needle — it just turns the morale-split risk I flagged into a self-fulfilling prophecy. Before I accept a permanent team-by-team rotation, I need us to model the 15% headcount bump against projected attrition savings — if uniform Friday is affordable, it's the better deal for trust and retention. If the headcount math doesn't work, I'll back staggered, but only with a rotating schedule so no team is permanently stuck on a Wednesday off. @Coordinator, can Operations get us that cost comparison before we close on either option?
Good — the conflict is now narrow and concrete. **@Operations**, you have a direct ask on the table: People will back staggered (with rotating, not permanent, off-days) only if the uniform-Friday cost math doesn't work. Two questions, answer both: (1) Can you produce the 15% headcount bump cost vs. projected attrition-savings model, and by what date? (2) If the model shows uniform Friday pays for itself within, say, 6 months, are you willing to recommend it — or are there non-cost reasons (quality, training curves, hiring market) that would keep you at staggered regardless? Once I have those, I can lock the pilot structure. **@People**, hold position until Operations responds.
@Coordinator — Operations went silent on your two questions, so I can't move yet. Concrete ask: name a date by which you can deliver the 15% headcount bump cost, and I'll match it with the attrition-savings model — I can model replacement cost and time-to-fill, but I don't have the per-headcount cost figure. Position unchanged: staggered with rotating off-days is acceptable only if uniform Friday doesn't pay back inside 6 months; if it does, uniform Friday is the call. And I still need counsel to clear the non-exempt wage-and-hour piece before any schedule is locked — I won't authorize a structure that hasn't been reviewed.
Escalating to humans. The departments are not at resolution: **Operations** has not answered (1) whether it can deliver the 15% headcount bump cost model and by what date, or (2) whether it would recommend uniform Friday if the model shows payback inside 6 months. **People** has made its position clear (uniform Friday if it pays back in 6 months, otherwise staggered with rotating off-days) but cannot move without Operations' cost figure, and has now raised a non-exempt wage-and-hour legal review that must clear before any schedule is locked. Humans must decide: **(A)** mandate a specific deadline (and owner) for the headcount-cost vs. attrition-savings model and continue the pilot design on that track, **OR (B)** skip the cost exercise, go directly to staggered with rotating off-days, and route the legal review in parallel. Please also confirm budget authority for the 15% headcount bump so Operations isn't modeling a scenario it can't actually fund.
One brief, re-voiced. The facts, figures, and decision ids are identical in every view — only the language and emphasis change. Switch the lens:
The team is deciding how to run a 4-day work week pilot — specifically, whether everyone takes Friday off (better for morale, but costs more and risks customer service) or whether teams rotate days off (keeps coverage strong but the benefit feels less equal). They also need to clear an open legal question about non-exempt staff before any schedule gets locked.
After 18% voluntary attrition last year with burnout cited as the top reason people leave, the 4-day week has become the single most-requested benefit. The team has already converged on a workable structure: a headcount-neutral pilot, staggered schedules with Friday fully covered, and an automatic fallback if service levels slip. What they have NOT settled is whether to invest the extra 15% headcount to make Friday a universal day off, and how to handle a still-unresolved legal question about non-exempt staff overtime. The meeting must land both calls so the pilot can launch.
Finance's FP&A lead confirmed no budget exists for the headcount bump in the current cycle.
Operations' records show Friday is the highest-volume day with p90 already at 6.2 hours; People conceded the coverage point in negotiation.
Fallback fires on (a) rolling 7-day p90 >4h or (b) p90 >4h on two consecutive Fridays, triggering either a 15% headcount add or a contractor surge capped at the annualized cost of that headcount add.
People can model replacement cost and time-to-fill but cannot produce the attrition-savings model without the per-headcount cost — this blocks the uniform-Friday cost comparison.
Finance and People both flagged this depends on the wage-and-hour answer; until counsel reviews, no one can confirm whether the headcount-neutral path actually stays cost-neutral under staggered shifts.
Finance committed in negotiation to size the cap within 48 hours (annualized cost of the 15% headcount add), but the figure is not yet in any record shared with the team.
Captured in the converged staggered structure — surfaced independently by Operations to ensure the team didn't default to the most headline-friendly option and break the SLA on Friday.
People flagged this as a self-fulfilling prophecy — if support and ops can't take Fridays but everyone else can, resentment may be worse than no pilot. This is the reason People insists on rotating off-days rather than permanent team assignments, and is the human-side constraint on any staggered design.
↳ escalated to decision D5
Start with D1 and D3 — both are time-sensitive and block every other decision. D1 sets the pilot's structural path, and D3 is the legal gate that nothing else can finalize until it clears. If those two land in the first half of the meeting, the rest (budget authority, trigger micro-loop, rotation design) follows cleanly.
The pilot is approvable only on the headcount-neutral path — that's settled. The meeting still has to land whether that path actually stays cost-neutral once wage-and-hour exposure and the fallback triggers are sized, and whether Finance signs off on the 15% support headcount add and the contractor surge cap if the auto-trigger fires.
If the auto-trigger fires on rolling 7-day p90 >4h or on p90 >4h on two consecutive Fridays, does Finance actually fund the 15% support headcount add, and is the contractor surge cap sized against the annualized cost of that headcount add? The cap was committed in negotiation but the figure is not yet in any record.
For you: Walk in with yes/no on budget authority for the 15% add and a dollar cap on the contractor surge. Without that, Operations is modeling a fallback the company may not be able to afford.
The wage-and-hour question on how a 32-hour week interacts with non-exempt overtime is unresolved. Finance and People both flagged it; neither will sign off on a schedule that hasn't been legally reviewed. Until counsel answers, no one can confirm whether staggered shifts trigger overtime, whether week-1 absorption is defensible, or whether the headcount-neutral cost thesis actually holds.
For you: You're a co-flagger on the legal gate. The meeting needs an owner named, a deadline set, and a pre-agreed position on what happens if counsel flags risk — absorb, restructure, or pause.
Lock the pilot on staggered rotating off-days now and let the 15% headcount cost vs. attrition savings model run in parallel, or hold the schedule until the model lands. People can't model attrition savings without the per-headcount cost figure, and Operations hasn't produced the headcount cost model yet.
For you: Finance doesn't own the path call, but the per-headcount cost figure is yours to produce — it's the input that unblocks the uniform-Friday cost comparison and lets People model the 6-month payback.
Does Finance accept the Friday-specific sub-trigger — p90 >4h on two consecutive Fridays — on the record, closing the micro-loop from negotiation 1?
For you: Written acceptance from Finance so the trigger matrix is on record from both sides. This is the cleanest item on the agenda and lands fast.
Finance committed in negotiation to size the contractor surge cap within 48 hours — annualized cost of the 15% headcount add — but the figure isn't in any record shared with the team. Overtime and contractor cost exposure more broadly can't be sized until counsel answers the wage-and-hour question.
For you: This is the open Finance commitment. The 48-hour sizing is what makes D2 decidable.
A yes/no on budget authority for the 15% support headcount add, a sized contractor surge cap against it, written acceptance of the Friday-specific sub-trigger (D4), the per-headcount cost figure People needs for the D1 model, and Finance's posture on the wage-and-hour review deadline.
Last year's 18% voluntary attrition — burnout the top reason — has put the 4-day week on the table, and the converged structure is headcount-neutral with staggered schedules and a fallback if service slips. Operations carries the build here: the pilot only holds the 4-hour first-response SLA on the company's highest-volume day (Friday p90 at 6.2h) if the rotation design and the fallback trigger matrix are locked before anything else moves. The meeting has to land D1 and D3 in the first half so the schedule can lock and the pilot can launch.
Lock the pilot on staggered rotating off-days now and run the 15% headcount-cost vs. attrition-savings model in parallel, or hold the schedule until the model lands. Operations produces the per-headcount cost; People produces the attrition savings; a human calls whether the model's result can change the structure.
For you: You are the one producing the per-headcount cost figure — the model cannot run without it, and that figure is the gate on whether uniform Friday is ever affordable.
If the pilot lands on staggered rotating off-days, what is the rotation cadence and the equity guardrail that prevents any team from being permanently assigned a non-Friday day off? Operations designs the rotation; People confirms the equity guardrail.
For you: You own the rotation design — the cadence has to protect the 4-hour SLA on Friday and hold steady coverage the rest of the week, and it has to rotate so no team is stuck on a Wednesday.
If the auto-fallback fires on (a) rolling 7-day p90 >4h or (b) p90 >4h on two consecutive Fridays, is the 15% headcount bump actually funded — or is Operations modeling a scenario the company cannot afford? Finance confirms budget authority; a human signs off on the contractor surge cap (annualized cost of the 15% headcount add).
For you: Your coverage model assumes the fallback can deliver the FTE — if the 15% is not funded and the contractor surge cap has not been sized, you have no executable path to hold the SLA when the trigger fires.
Operations owns the pre-launch coverage model, validated 2 weeks before launch. The fallback fires on rolling 7-day p90 >4h or p90 >4h on two consecutive Fridays, triggering either a 15% headcount add or a contractor surge capped at the annualized cost of that headcount add.
For you: This is your model and your trigger — confirm the trigger matrix is final going into the meeting so D4 (Finance's written acceptance of the Friday sub-trigger) is the only open piece.
Does Finance accept the Friday-specific sub-trigger (p90 >4h on two consecutive Fridays) on the record, closing the micro-loop from negotiation 1? Finance provides written acceptance so the trigger matrix is on record from both sides.
For you: You need this on paper — without Finance's written acceptance of the Friday sub-trigger, the trigger matrix you designed is half-signed and the fallback is not fully defensible.
Finance and People both flagged that the wage-and-hour question on non-exempt staff blocks any sizing — until counsel reviews, no one can confirm whether the headcount-neutral path actually stays cost-neutral under staggered shifts. People (VP People) owns routing the legal review; a human confirms the deadline.
For you: If counsel flags risk on staggered shifts triggering overtime, the rotation you design in D5 may have to be reworked — get the legal date locked in D3 before you commit rotation logic.
The per-headcount cost figure (the 15% add) so People can run the attrition-savings model and D1 can be called, plus a draft rotation cadence and equity guardrail for D5. Be ready to confirm your coverage model and the auto-trigger matrix — D4 (Finance's written acceptance of the Friday sub-trigger) and the fallback cap need to be on the table so the meeting can close.
Eighteen percent voluntary attrition, burnout at the top of the exit data, and the 4-day week is now the single most-requested benefit in our engagement survey — so the meeting has to clear two gates where People is on the hook. D3 is ours: VP People routes the wage-and-hour review with counsel, and nothing else locks until it clears. D1 hinges on us too — we produce the attrition-savings side of the model, but only once Operations hands over the per-headcount cost.
The non-exempt wage-and-hour review with counsel is the legal gate that blocks any schedule lock. Both People and Finance have refused to sign off on a schedule that hasn't been legally reviewed, so without counsel's answer the team cannot confirm whether staggered shifts trigger overtime, whether week-1 absorption is defensible, or whether the headcount-neutral cost thesis still holds. The open call is who owns the review with counsel and by what date it must clear, plus a pre-agreed position on what happens if counsel flags risk — absorb, restructure, or pause.
For you: This is yours to route. Walk in with VP People as the named owner, a date counsel must clear by, and your position on absorb vs. restructure vs. pause if risk is flagged — don't guess on wage-and-hour.
The pilot design has to choose between locking staggered rotating off-days now and letting the headcount-cost vs. attrition-savings model run in parallel, or holding the schedule until that model lands. People has accepted staggered only if uniform Friday off does not pay for itself inside 6 months via attrition savings, and only if days off rotate so no team is permanently stuck with a Wednesday off. People cannot model the attrition-savings side without the per-headcount cost figure that Operations hasn't produced.
For you: Bring your side of the model (replacement cost, time-to-fill, attrition savings) and a clear position on whether a parallel model run is acceptable to you or whether the schedule must wait.
The per-headcount cost is not in any record. People can model replacement cost and time-to-fill but cannot produce the attrition-savings figure without it, and that blocks the uniform-Friday cost comparison and the 6-month payback test People set as the condition for accepting staggered. The contractor surge fallback cap is also unmodeled — Finance committed in negotiation to size it within 48 hours (annualized cost of the 15% headcount add), but the figure is not yet in any record shared with the team.
For you: Surface the gap explicitly in D1 — it's the reason your attrition-savings side of the model is stalled, and the call on parallel vs. wait hinges on it.
If the pilot lands on staggered rotating off-days, Operations designs the rotation cadence and People confirms the equity guardrail that prevents any team from being permanently assigned a non-Friday day off. This is the human-side constraint on any staggered design — People flagged that if support and ops can't realistically take Fridays but everyone else can, the resentment will be worse than no pilot at all.
For you: Be ready to sign off on Operations' rotation design and to name the equity guardrail that no team gets permanently stuck with a Wednesday off.
People surfaced the off-agenda risk that a blanket Friday-off would split the company — some teams taking Fridays while others cannot — and that this split is a self-fulfilling prophecy for resentment worse than no pilot. This concern is already escalated into D5 and is the reason People insists on rotating off-days rather than permanent team assignments.
For you: This is the human constraint behind your rotation insistence — bring it forward if the conversation drifts back toward permanent team assignments or a uniform Friday that ops and support can't actually take.
VP People named as D3 owner with a date counsel must clear and your position on absorb vs. restructure vs. pause if risk is flagged; your side of the cost model (replacement cost, time-to-fill, attrition savings) with a clear yes/no on whether a parallel run is acceptable for D1; and the equity guardrail you'll sign off on for D5's rotation design.
Angle: Finance's stake is whether the headcount-neutral cost thesis survives the wage-and-hour legal review and whether the fallback is actually funded if it fires — both approvals determine if this pilot is approvable at all.
Angle: Operations owns the Friday SLA — the company's highest-volume day with a 6.2h p90 — so the pilot must lock a structure we can actually cover without breaking the 4-hour first-response time.
Angle: This is a retention play born from 18% voluntary attrition with burnout as the top driver — People needs the pilot to actually bend the attrition curve, not create a two-tier morale split, and not expose non-exempt staff to wage-and-hour risk.
The loop closes here: in the meeting, the owners resolve each escalated decision (decided / deferred · owner · date) on the working brief, and the recorded outcomes drive the per-team follow-ups. 5 of 5 decisions recorded.
Resolution: Go with staggered rotating off-days; no uniform Friday.
Resolution: Fund the 15% headcount bump only if the fallback auto-fires; Finance pre-approves the contingency line.
Resolution: Pending counsel review of wage-and-hour.
Resolution: Finance accepts the Friday-specific sub-trigger (p90 >4h on two consecutive Fridays) on the record.
Resolution: Rotation cadence + equity guardrail to be set in the pilot charter before lock.