Share

Company Battlecards

On DeckKnow who to contact, what to say, and when to move

On Deck

Know who to contact, what to say, and when to move

SUBSCRIBE CONTACT US

Company Battlecards — Issue 2 | On Deck

Handoff Diagnostic

Three questions that separate AI-accountable companies from aspirational ones

Every company on your list says AI. You need to know which ones have operationalized accountability before you spend positioning energy. These three questions work in any first conversation.

"When something the AI does turns out to be wrong — where does that go?" Listen for an incident path. Companies that have operationalized AI name a team, a process, a change that happens before the next run. Vague answers about model improvement mean nobody owns failure.

"Walk me through a workflow where AI takes action — at what point can a human stop it before it's committed?" Listen for whether they distinguish reversible from irreversible actions. Human gates belong at the commitment threshold, not after.

"Who decided how AI gets used in core workflows — was design part of that decision, or did design come in after?" The mandate question. You're learning whether this role shapes the operating model or decorates one that Legal, Product, and Engineering already locked.

Ask all three. Concrete answers on all three mean they've thought about AI as something to govern. Abstract answers on all three mean they're hiring you to make AI features look trustworthy.

Handoff Diagnostic

Three questions that separate AI-accountable companies from aspirational ones

Every company on your list says AI. You need to know which ones have operationalized accountability before you spend positioning energy. These three questions work in any first conversation.

Ask all three. Concrete answers on all three mean they've thought about AI as something to govern. Abstract answers on all three mean they're hiring you to make AI features look trustworthy.

Reading the answers

Q1 — Failure routing

Strong: They name a role or process that owns AI errors. They distinguish model limitations from operating failures.
Weak: "The model is getting better." No named owner. Errors treated as training data, not incidents.

Q2 — Human gates

Strong: They know which actions are reversible vs. irreversible. Checkpoints exist at commitment thresholds, not confirmation modals.
Weak: "Users can always undo." No reversibility gradient. A confirmation step framed as UX choice, not operating requirement.

Q3 — Design authority

Strong: Design was in the room for operating-model decisions. They can name who owns AI design standards and who can block a launch.
Weak: "Design and product collaborate closely." Adjacent to governance, owns none of it.

Calibration: Ramp and Headway already post with accountability language in their listings. Use those calls to validate the pattern. Companies posting only tool-fluency language ("familiarity with LLMs, generative design tools") are telling you where they are.

PART ONE

Who Owns the Failure?

OPEN

Swept six design leadership postings for one signal: does the company name what happens when AI produces wrong output? Two have. Four haven't. That split changes which version of you to send where. More interesting: one posting uses your trust framework's language without knowing your framework exists. A buyer who independently arrived at the problem you've already published the answer to is the rarest signal in a job search. Action tiers for Tuesday, July 8 inside.

PART TWO

Two Buyer Archetypes Hiding Behind the Same AI Posting Language

OPEN

Every design leadership posting on your target list says "AI" now. But the buyer at Gusto asking "what happens when this breaks?" and the buyer at Ramp asking "what have you built recently?" are running opposite evaluations behind identical language. One tests whether you've designed for the failure mode. The other tests whether you'll import process that slows them down. This piece maps both archetypes — their tells in posting language and conversation, what wins and loses each, and exactly how to adjust your portfolio lead and outreach tone before Tuesday morning, when holiday-week inboxes are at their quietest.

Two Buyer Archetypes Hiding Behind the Same AI Posting Language

PART THREE

OpenAI's Design Leadership Gap and the Posting Pattern That Predicts What's Next

OPEN

OpenAI has no publicly identifiable design executive. I checked company pages, press coverage, design community directories, conference speaker archives, and personal portfolio sites. No VP Design, no Head of Design, no Director of Product Design surfaces anywhere. Two design-department postings appeared during the product reorg that followed Kevin Weil's CPO departure, and their sequence reveals something specific: infrastructure is being laid before leadership is hired. The design leadership role hasn't posted yet. This reconstruction identifies the triggers that predict when it will, what the posting will likely look like, and which of the four new product pillar leads to route outreach through the moment it appears.