Before you reorg: pressure-test reporting lines, teams, and roles

Not business, HR, or legal advice. This page is not a substitute for your people partners, your counsel, your finance leads, or your judgment. It describes a product ritual for pressure-testing an org restructure packet (reporting lines, teams, roles) before you send the all-hands note that redraws who reports to whom. Nothing here is a retention guarantee, a layoff plan, or a promise that the new chart will stick.

Sunday night. A founder and an exec have a slide titled "New org" open next to a chatbot thread that already made the redraw feel clean: fewer layers, clearer owners, a date that sounds decisive. Managers want to know who they report to on Monday. ICs want to know whether their team still exists under a name they recognize. The chart has not left drafts. That is the moment this page is for.

People searching "how to reorg a startup" or "before you restructure your org" usually get span-of-control frameworks, RACI templates, and essays about flattening. Those can help. This page is narrower. It treats the reorg packet (which reporting lines move, which teams merge or split, which role titles change, and what you tell the people whose identity sits on the old chart) as a social object you are about to publish with your company name, and it is about pressure-testing the AI-shaped read of that packet before the all-hands or the org email.

This is not before you let someone go (ending one employment relationship). It is not before you hire (an offer letter going out). It is not before you pivot (renaming who you serve and how you go to market). It is not before you sunset or before you kill the feature (ending a product or a surface). It is not before you acquire (combining two organizations through a deal). It is not before you raise, and it is not the pressure cluster pages named validate, steelman, devil's advocate, pre-mortem, stress-test-your-deck, challenge-your-strategy, pressure-test-your-roadmap, or stress-test-your-okrs. It is the org redraw: changing reporting lines, teams, and roles inside a company that otherwise keeps shipping, in a way people will quote back for quarters.

Pingpong is a sequential review product for that ritual. Default chain: Grok, then Perplexity, then ChatGPT, then Gemini, then Claude. The first model drafts. Each later model sees your question, the prior answers, and a review frame that can agree, correct, restructure, or reject a weak premise. Brand: Pingpong at pingpongit.com. Not getpingpong.ai.

Definition: What is Pingpong. Mechanism: How it works. Exec role page: For executives. Founder role page: For founders. First run: How to run a Pingpong. Cluster hub: Before you commit.

Your first eligible web review is free. When you need more, web Plus is $19.99/month and web Pro is $124.99/month. On iOS the listing shows three free Pingpongs, then Plus at $24.99/month or Pro at $59.99/month. Start the free web review on pingpongit.com, then open Plans when you are ready for Plus or Pro. Full table: pricing.

Why an org redraw is a different kind of commit

A private org sketch in a notebook is cheap to erase. An all-hands that names new managers, new team names, and new role titles is not. Once people hear who they report to, that language becomes the official story of how work moves through the company. Softening a reporting line after announcement looks like confusion. Overclaiming "everyone already knew" trains the people who did not know to distrust the next note. A manager who learns their scope shrank from a Slack screenshot before the meeting starts rewriting their own exit story. An IC who finds their team dissolved into a new name without a named owner starts asking which roadmap still belongs to them.

Founders and execs often ask one model to "write a confident reorg note" or "make the new chart feel inevitable." The model returns calmer prose and a short risk list that preserves the original redraw. Socially pleasant. Thin when the next action is the all-hands, the manager 1:1s, or the room full of people whose title just changed. Related habit for irreversible moves in general: Catch AI mistakes before you commit.

What usually hides in the reorg packet

The dangerous parts are rarely typos. They are soft premises dressed as clarity. A reporting line that quietly demotes someone without naming the demotion. A team merge that erases a craft identity people still use in customer calls. A role title that sounds senior while stripping decision rights. A "span of control" claim that ignores the three people who actually unblock the work. A matrix that looks clean on a slide and double-books the same IC to two managers. An effective date that collides with a launch freeze, a comp cycle, or a leave you already approved. A "no headcount change" sentence that papers over a quiet backfill freeze. A promise that managers will cascade the why when the cascade deck does not exist yet.

One chatbot grading its own reorg memo rarely catches that pattern. It softens edges and keeps the structure. Later labs, reading a concrete reporting-teams-roles packet without being told to flatter the redraw, are a different social object. Framing: AI second opinion. Sycophancy angle: Debias AI and sycophancy research.

How the five-model handoff works on an org restructure

Paste one clear question, not a vibe. Example shape: "We plan to REORG on DATE. Here is the current chart, the proposed reporting lines, the teams that merge or split, the role title changes, who loses or gains scope, the cascade plan, and the objections managers already raised. Where is the redraw soft, the demotion unnamed, the dual-report fake, the effective date dishonest, or the cascade missing before we send the all-hands?" Attach the current and proposed charts, the draft all-hands note, the known manager objections, and the open people questions when you can. Do not paste secrets you should not put in a third-party tool.

Grok goes first. Perplexity reviews with that draft in view. ChatGPT, Gemini, and Claude follow in order. Each pass can keep, fix, or refuse. You get a final answer and can open earlier passes. The product bet is not that five models invent the right org design. It is that skipped edge cases and soft premises are harder to ship unnoticed when later labs have to look at them.

Architecture: Sequential vs parallel AI. Category map: Multi-model AI review. Fair single-model contrast: Pingpong vs ChatGPT.

What to listen for in the middle passes

Treat independent convergence as a stronger signal than polite agreement. If three later models keep challenging the same clause (a demotion dressed as a lateral move, a dual-report with no primary owner, a cascade with no named messenger, an effective date that hits a known freeze, a team name that erases craft without a home), that clause is your checklist, not a reason to force a synthetic consensus.

Treat unresolved split the same way. One model may want a narrower redraw; another may want manager conversations before any all-hands. You still decide. Pingpong does not replace your founder judgment, your exec team, your people partners, your counsel, or a real conversation with the managers and ICs who will live on the new chart. It pressure-tests the AI-shaped reorg story you were about to trust.

Decision reliability framing (not uptime SLAs): Extreme reliability. Clarification of the "insurance" metaphor: Decision insurance.

When to skip the chain

Skip it for exploratory "someday org" sketches, whiteboard brainstorms nobody will announce, and early span-of-control doodles. One strong model is enough when being wrong costs almost nothing. Save the free eligible review for the packet that is hours from an all-hands, a manager cascade, or an org email that redraws reporting lines. Role pages if the decision is not yours alone: executives, founders, teams.

Related commits

Plans

Your first eligible web review is free. Further web reviews need a subscription. Web Plus is $19.99/month. Web Pro is $124.99/month. iOS lists three free Pingpongs, Plus at $24.99/month, and Pro at $59.99/month (yearly options appear on the App Store). Confirm the live plan at checkout. Details: plans and pricing. Related: Is Pingpong worth it.

Run it before the all-hands

Take the current and proposed charts, the reporting-line changes, the team merges or splits, the role title moves, the cascade plan, and the reorg packet you already expect to defend. Restate them as one decision question. Run the default Pingpong order once. Keep what survives. Fix what later models break. Escalate what they cannot settle to a human who owns the people and the chart. Start with the free eligible web review on pingpongit.com. If the chain earns a place before your next org redraw, choose Plus or Pro under Plans (web Plus $19.99, web Pro $124.99; iOS Plus $24.99, Pro $59.99). Or start on the App Store.

Again: not business, HR, or legal advice. Not medical advice either. Hole-finding on your reorg packet is not a substitute for a founder, an exec, people ops, counsel, or a licensed advisor.