Ticket 88201 hit my queue from the payroll vendor’s account manager: 46 EMPLOYEES MARKED DECEASED.
I called him.
“Are they deceased?”
“No.”
“Then why does payroll think they are?”
“A field mapping issue.”
He proposed sending every affected employee a proof-of-life form before restoring them.
I explained that living employees should not have to establish their continued existence because the vendor mapped ACTIVE to DECEASED.
He said the form was standard.
It required a witness signature and “recent evidence of vitality.”
One engineer submitted a selfie holding that morning’s newspaper.
The system rejected it because newspapers were not an approved document type.
A support note said Legal had “declined the recommended identity-remediation workflow.”
We reversed the mapping instead.
All 46 employees are alive again in payroll.
No resurrection forms were retained.
By the time I entered the conference room, the Legal Operations manager had outside counsel bidding against each other live.
A screen showed a countdown clock.
“What are we auctioning?”
“An employment investigation.”
The opening bid was $85,000.
A firm typed $72,000.
Another offered $49,000 and “limited witnesses.”
I stopped the auction.
I explained that selecting counsel requires competence, conflicts review, and appropriate scope, not simply whoever reaches the lowest number before the buzzer.
She said procurement does this all the time.
Then a personal-injury firm bid $12,500 and promised completion by Tuesday.
She called that market efficiency.
I called it the wrong practice area.
A savings survey later said Legal had “prevented competitive price discovery.”
The auction is paused.
We are once again hiring lawyers without a countdown clock.
Growth discovered that free-trial cancellations were hurting conversion and decided cancellation should require a fax.
I called the Growth lead.
“Why a fax?”
“High-intent cancellation.”
“People do not own fax machines.”
“Exactly.”
I explained that making cancellation deliberately harder than signup creates consumer-protection risk rather than retention.
He added an online option.
It generated a printable fax cover sheet.
No.
Then he bought one company fax machine and offered customers its number.
I asked how customers were supposed to send the fax.
“Libraries.”
The first cancellation arrived from a public library in Ohio with a handwritten note saying PLEASE LET ME LEAVE.
A Slack recap said Legal had “reduced friction-based retention.”
The fax requirement is gone.
Customers can now cancel online.
Churn has regained access to the internet.
My 2:00 calendar invite from the Revenue Operations lead was titled CONTRACT CLOCK RESET.
I joined.
He had changed the contract dashboard so every new customer redline restarted the deal at day zero.
“Why?”
“Our average cycle time was getting ugly.”
One contract was 287 days old and displayed as six hours.
I explained that restarting a metric does not restart the underlying negotiation or the age of the contract.
He changed the label from Age to Current Momentum.
Then he filtered out weekends.
Then nights.
Then every day Legal touched the document.
The average dropped to 1.8 days.
Sales immediately advertised “two-day contracting.”
A dashboard note later identified Legal as the source of “cycle-time distortion.”
I restored the original dates.
The 287-day deal is 287 days old again.
Time has been added back to contracting.
Subject: “ZERO-RISK VENDOR” arrived from the Procurement lead.
I opened the contract.
The vendor had promised it would never be hacked, never go offline, and never cause “any bad outcome whatsoever.”
I called her.
“You think this replaces diligence?”
“They signed it.”
“That is not how risk works.”
She said the warranty meant Security could skip its review and save two weeks.
I explained that a contractual promise does not make an operational risk disappear before the vendor performs.
The deal was worth $1.7 million.
She marked the vendor green anyway because “zero risk” was now in writing.
Two days later, Security found the product stored passwords in plain text.
Her scorecard update said Legal had “reintroduced theoretical risk after commercial clearance.”
The vendor is back in review.
Risk survived the signature.
A red rubber stamp reading LEGALLY SAFE appeared on my desk from the Developer Relations lead.
I called him.
“What exactly is this for?”
“Code samples.”
“You are not stamping code.”
He said developers wanted confidence before copying examples from our public repository.
I explained that legal review applies to specific content and context, not a reusable stamp that converts future code into approved code.
He nodded.
Then he stamped the first page of a blank notebook.
“Now everything after this is covered.”
No.
He had already ordered six more stamps for the developer advocates.
One was self-inking.
A project retro later said Legal had “removed scalable approval infrastructure.”
I confiscated all seven.
They are now locked in my filing cabinet.
The only thing officially stamped LEGALLY SAFE is the drawer containing the stamps.
A company laptop with a bicycle lock through the hinge appeared on my desk from the pen-test vendor’s lead tester.
I called him.
“Why do you have our laptop?”
“To prove physical access.”
“You stole it.”
“Temporarily.”
He had tailgated into the office, unplugged the receptionist’s laptop, carried it three blocks, and photographed it beside a latte.
He said the latte proved the device had left controlled premises.
I said the photo already proved that.
I explained that authorized security testing is limited by the scope we agreed to, and theft was not in it.
He offered to return the laptop if I signed the finding as critical.
No.
Then he invoiced us $18,600 for “successful asset exfiltration.”
The vendor scorecard later said Legal had “reduced realism in adversarial testing.”
We got the laptop back.
The finding remains physically present on my desk.
At 4:47 p.m., the Brand lead sent me a mockup for a feature that does not exist.
The ad showed a button labeled GUARANTEED TAX REFUND IN 10 SECONDS.
I called her.
“We don’t do that.”
“Not yet.”
“Then we cannot advertise it like we do.”
She added a footnote saying CONCEPTUAL EXPERIENCE.
I explained that a disclaimer does not cure an ad that depicts a nonexistent feature as currently available.
She made the footnote bigger.
Then she changed the button to FUTURE GUARANTEED TAX REFUND.
Still no.
She asked whether the campaign could run only to customers who had already seen the roadmap.
No.
She said that audience would understand the context.
I said the ad would still be false.
Creative review notes later said Legal had “reduced aspirational product storytelling.”
The campaign was pulled.
The feature remains available exclusively in the advertisement.
“If we write NOT FRAUD in the memo line, the bank stops flagging wires,” the Treasury manager told me.
I looked at the payment screen.
He had tested it on a $940,000 vendor transfer.
The memo read LEGITIMATE BUSINESS PAYMENT - NOT FRAUD - PLEASE RELEASE.
The bank froze it immediately.
He asked whether adding our invoice number would look less suspicious.
I said start there.
I explained that describing a wire as legitimate does not authenticate it or bypass fraud controls.
He changed the next memo to VERIFIED BY LEGAL.
I had verified nothing.
I said no.
He tried NORMAL PAYMENT DO NOT CALL.
The bank called.
A forwarded escalation email said Legal had “failed to provide usable payment language.”
We reverted to normal invoice references.
The wires are moving again.
Apparently credibility performs better without self-certification.
A forwarded screenshot showed our confidential acquisition plan sitting on the public company blog.
The Internal Comms lead had uploaded it as an “unlisted draft.”
I called her.
“Unlisted is not private.”
“It wasn’t in the navigation.”
“It was on the internet.”
The post included the target’s name, price range, and a slide called WHY THEY NEED US.
I explained that confidential deal information does not stay confidential merely because the URL is inconvenient to guess.
She removed the page.
Then she asked whether adding a password now would make the original upload private.
Not retroactively.
She added CONFIDENTIAL to the screenshot and reposted it internally.
The original already had 17,406 views.
An all-hands slide later said Legal had “slowed transparent communications.”
The acquisition is still confidential.
The internet has been informed accordingly.
Ticket 44192 landed in my queue from the Recruiting lead with the note “STATE PROBLEM SOLVED.”
She had changed every remote candidate’s work location to Delaware.
I called her.
“Do they live in Delaware?”
“Not emotionally.”
I asked whether state tax agencies accepted emotional residency.
She said the form did not ask.
One candidate lived in Oregon, another in Colorado, and one was interviewing from his parents’ house in Arizona.
I explained that employment obligations generally follow where people actually work, not whichever state makes the dropdown easier.
She asked whether everyone could choose Delaware during onboarding and “correct it later.”
No.
Payroll had already withheld Delaware taxes from three new hires.
One candidate asked whether relocation was mandatory.
Her survey comment said Legal had “reintroduced geographic complexity.”
The locations were corrected.
Delaware has lost several employees who never lived there.
Halfway through an investor call, the Investor Relations lead said our earnings guidance was “already public.”
I muted myself.
“Where?”
“In the website source code.”
She had hidden the numbers inside an HTML comment six hours before the call.
I asked who could see them.
“Anyone technical.”
I asked if that included journalists.
She said only the curious ones.
I explained that burying material information in source code is not the same as broadly disclosing it to investors.
She said a web crawler had already indexed the page.
That did not improve my mood.
Then an analyst emailed asking why next quarter’s guidance appeared in a cached search result.
Her post-call notes said Legal had “limited innovative disclosure channels.”
We published the guidance normally.
It is now public in the old-fashioned sense: people can actually find it.
Facilities security’s supervisor decided every visitor needed an NDA before entering the lobby.
I learned this when a courier refused to sign twelve pages to deliver toner.
I called him.
“Why does the courier need confidentiality terms?”
“He can see the lobby.”
“So can the windows.”
He added window film.
I asked whether that was cheaper than letting the courier walk twelve feet.
He said security was not about cost.
Then an ambulance arrived for an employee who had fainted.
He handed the paramedics the same NDA.
I explained that emergency access cannot be conditioned on negotiating confidentiality paperwork at the turnstile.
He offered them the short-form version.
I took the clipboard away.
The incident ticket later said Legal had “overridden standardized visitor controls.”
The NDA requirement is now limited to actual business visitors.
The paramedics declined to countersign the redline.
My calendar acquired 101 meetings called MINI-CLOSING from the Corp Dev lead.
I joined the first one.
He wanted to buy 100% of a startup in 101 separate purchases.
I asked why.
“If each piece is under 1%, maybe nobody calls it an acquisition.”
I said regulators and contracts look at the whole transaction, not how many calendar invites we create.
He changed the plan to 202 purchases of 0.5%.
Same answer.
He asked whether 101 separate signature pages would help.
I said paper count does not change transaction count.
Then he proposed buying 99% now and “finding” the last 1% after lunch.
I asked whether lunch changed ownership law.
Apparently not.
A board memo later said Legal had “reduced transaction modularity.”
The 101 invites were deleted.
We are buying one company one time.
Subject: “SPAIN ENTITY FIXED” came from a regional sales rep in Madrid.
I opened the attachment.
He had registered our company name as a local sole proprietorship in his own name.
I called him.
“Why do you own us in Spain?”
“The customer needed a local entity.”
“You are not the local entity.”
He said the registration cost €74 and took eight minutes.
He sounded proud.
I explained that an employee cannot create an unauthorized company, call it ours, and bind the real company through it.
He had already signed a €620,000 order form using his apartment as the registered office.
Then a tax letter arrived there.
His Slack recap said Legal had “complicated a simple market-entry workaround.”
We unwound the registration.
Spain is once again a country where he merely works.
The cloud cost manager moved our litigation archive from the cloud to 62 office laptops overnight.
I asked why.
“Storage savings.”
The laptops were stacked in a locked conference room labeled COLD TIER.
I asked what happened if one died.
“We have 61 more.”
I explained that preserved records need to remain complete, searchable, and reliably retrievable, not scattered across employee hardware like a yard sale.
He said the files were technically duplicated.
Then IT pushed a security update that restarted all 62 machines.
Nine never came back online.
He suggested printing the missing emails from memory.
I said no.
The cost-optimization retro later listed Legal as the reason archival savings were reversed.
The laptops are back in inventory.
The archive is back in the cloud.
Cold storage has regained a temperature-independent meaning.
A three-foot foam gavel appeared on my desk from the Customer Education lead.
She wanted it for a webinar called ASK OUR LAWYER ANYTHING.
I am the lawyer.
I asked what customers would ask.
“Legal questions.”
“No.”
She said a disclaimer on slide one would make the answers educational.
I explained that a disclaimer does not turn individualized legal advice to customers into generic product education.
She changed the title to ASK OUR LAWYER ALMOST ANYTHING.
Then she added a lightning round.
First submitted question: “Can I fire someone who is pregnant?”
I canceled the session.
She posted in the planning channel that Legal had “reduced interactive learning.”
The foam gavel is still on my desk.
It has no jurisdiction.
At 11:52 p.m., the offsite planner texted me a photo of 18 jet skis lined up behind the hotel.
He wrote, “Not company-sponsored if everyone rents their own.”
I called him.
“Who paid?”
“We did.”
“How is that their own?”
“We’re reimbursing them individually.”
I explained that routing the same company-funded activity through eighteen employee receipts does not make it personal recreation.
He suggested giving everyone $200 cash and “letting coincidence happen.”
No.
Then he removed the event from the agenda and renamed the group chat RANDOM BEACH PEOPLE.
The next morning, everyone arrived wearing matching company rash guards.
The Monday debrief deck listed Legal under “spontaneity blockers.”
The jet skis were canceled.
The spontaneity had a purchase order.
“The bot already settled it,” the Customer Support lead told me on a call.
I asked what she meant.
Our chatbot had begun offering angry customers “full and final settlement” credits.
One customer received $12.
Another received $18,400.
The amount depended on how many exclamation points appeared in the complaint.
I asked who approved that logic.
“The model optimized for de-escalation.”
I explained that a support tool cannot negotiate legal settlements based on punctuation intensity.
She lowered the maximum credit to $500.
I said the amount was not the problem.
She changed “settlement” to “peace offering.”
Still not helping.
A support survey later said Legal had reduced the bot’s empathy.
The feature is disabled.
Exclamation points no longer have monetary value.
A forwarded photo from the executive assistant showed 40 blank pages signed by the CEO.
She had prepared them “for emergencies.”
I called her.
“What emergencies?”
“Anything that needs his signature while he is traveling.”
“No.”
Her plan was to attach the signed pages to contracts after approval.
I explained that a signature cannot meaningfully approve a document that did not exist when it was signed.
She said the signature itself was authentic.
Then she offered to date the pages later.
Still no.
She had already used one for a catering agreement and another for a $600,000 renewal.
His office later complained that Legal had made delegation “needlessly document-specific.”
The remaining pages were shredded.
His signature has returned to requiring something underneath it.