Situation Assessment
This objection is a compound. It sounds like one question but it's two fears firing simultaneously: she comes from enterprise clients and she comes from consulting. In the interviewer's head these merge into a single image: someone whose default mode is decks, stakeholder alignment, and twelve-week discovery phases. The image is vivid enough that it can override portfolio evidence if you don't address it before it calcifies.
Your job is to name it, reframe it, and redirect within the first ninety seconds. Everything below supports that sequence.
The Grain of Truth
Say it out loud before they think it. Enterprise and consulting backgrounds do sometimes produce slower operators. Someone who spent eight years inside a Fortune 100 design org, where a button-color change requires three stakeholder reviews and a brand-council sign-off, can import that cadence into a 40-person company and suffocate it. Someone whose consulting career was frameworks and presentations, never shipped code, can stall when the expectation is live product by Thursday.
That pattern is real. Acknowledge it plainly. If you skip the acknowledgment, every piece of evidence you present afterward sounds like denial.
Then pivot. The pattern is real, and it does not describe your portfolio.
The Core Reframe
There are two kinds of speed. The first is speed where error cost is low. Ship, measure, iterate, roll back if it breaks. The iteration loop absorbs mistakes. Most early-stage consumer products operate here, and the speed is genuine, but the difficulty is moderate because wrongness is cheap.
The second is speed where mistakes carry operational, regulatory, or human cost. Same compressed timeline. No rollback option. You ship fast AND you ship right, because the environment doesn't offer a second pass. You cannot iterate your way out of a federal disaster-relief disbursement that went to the wrong address. You cannot roll back a pharma supply-chain failure that delays drug delivery across three continents.
The second kind is harder. It is rarer. Your portfolio demonstrates it three times.
High confidence this reframe lands at growth-stage platforms in regulated or high-consequence domains (payments, insurance, clinical workflows). Moderate confidence in pure consumer contexts where the interviewer may genuinely value iteration speed over first-pass correctness.
Evidence Inventory
Red Cross Disaster Relief: 0→national deployment in 6 months. Replaced 6 disconnected legacy systems with one unified record. Built under federal audit pressure, for surge volunteers on slow networks, during active disaster declarations. 1,689 cases processed in the first two weeks live. $847K disbursed. Team: 1 designer, 1 researcher, 1 PM, 2 engineers, 2 BAs. That is a startup-sized team shipping at startup speed, except wrongness means a displaced family doesn't receive aid.
Equinox+: 0→MVP in 3 months. 600K+ premium members across 5 brands. Launched to a 4.8-star App Store rating. When engineering capacity allowed only 3 brand worlds with 6 weeks left, the scope call was made: SoulCycle, Equinox, Pure Yoga ship at launch; Precision Run and HeadStrong follow in the first post-MVP update. That is a speed decision with commercial consequence, made under pressure, documented publicly. For a premium brand where memberships run north of $300/month, a botched launch doesn't just lose downloads. It damages the relationship with a customer base that has high expectations and zero tolerance.
Thermo Fisher mySupply: 0→live in 12 months. 6 pharma partners across 9 manufacturing sites spanning EU, NA, and AU. Replaced spreadsheets and phone calls with real-time partner visibility. $20M+ margin recovered annually. Twelve months for multi-continent pharma supply chains, with 1 designer and 2 engineers, is not slow. It is fast for a domain where exceptions surface 2–4 days after commit dates and rescheduling costs 3–5x more than prevention.
When you present these, lead with the timeline and the constraint. "Six months, federal oversight, national deployment" lands before "American Red Cross" does. The timeline reframes the org name. Drop it, and "Red Cross" activates the interviewer's nonprofit-pace assumption before you can correct it.
Their Domains Prove the Point
The growth-stage companies most likely to raise the speed objection are the ones whose product domains demand exactly this capability. Once you see that, you stop defending your background and start describing their operating reality.
Headway's provider-facing workflows are high-consequence surfaces end to end. Credentialing, insurance verification, claims submission, session documentation. A credentialing error means a provider can't see patients. A claims submission error means they don't get paid. These are workflows where speed matters because providers are waiting, and correctness matters because the financial and clinical consequences of errors compound downstream. The Red Cross pattern (one unified record replacing disconnected systems, deployed under operational pressure) and the Thermo Fisher pattern (multi-party visibility across a complex transaction chain) map directly to what Headway's provider experience needs to become.
Maven Clinic's Claims & Payments role touches every clinical program Maven runs. Their posting says "errors have real consequences for members and providers." Claims adjudication, payer reconciliation, provider payments. A provider who doesn't get paid stops seeing patients. This is a ship-and-iterate domain only until someone's paycheck bounces.
Mercury's Disputes role frames disputes as "among the most important trust-building moments in banking." Missing money. Compromised cards. Investigator tooling where decision quality directly affects whether a customer trusts Mercury with their operating account. Their posting explicitly asks the designer to balance "customer needs, business requirements, and compliance obligations in a high-stakes environment."
Abridge builds real-time AI-generated clinical notes from patient-clinician conversations, with deep EMR integrations and what they call "auditable AI." The design work directly affects clinician cognitive load and patient care. Speed matters because documentation happens in real time. Correctness matters because it's a medical record.
When you're in the room with any of these companies, you are describing their operating reality back to them and using your portfolio as proof you've already worked in it. You are explaining why their problem is your problem, solved before.
The Consulting Sub-Objection
Do not say "BCG DV wasn't really consulting." That sounds defensive and invites a definitional argument you cannot win.
One sentence of context is enough if someone asks. BCG X describes itself as a tech build and design unit that builds, operates, scales, and transfers solutions. Its venture-building practice launches standalone products. Useful framing. But spend your time on the portfolio, not the org chart.
The portfolio carries this. Red Cross is production infrastructure handling active disaster cases. Thermo Fisher is a production system running across 9 manufacturing sites. These shipped into production with real users, real data, and real operational consequences. They did not live in a presentation and die in a drawer.
"Every case in my portfolio shipped into production with real users, real data, and real operational consequences."
Then stop talking about consulting and let them ask about the work.
The consulting concern and the speed concern are the same concern wearing different clothes. Both assume your default mode is analysis over action. The portfolio answers both simultaneously. The timelines prove speed, the production deployment proves build, and neither requires you to argue about what consulting is or isn't.
High confidence. "Shipped into production" is verifiable. The consulting frame evaporates once the interviewer is looking at deployment numbers instead of employer logos.
How the Reframe Tilts by Company Tier
Growth-stage platforms (Headway, Maven, Gusto, Ramp): This is where the speed objection hits hardest because "startup speed" is a cultural identity. The reframe tilts toward proving your default mode dissolves constraints into the product rather than layering process on top. Red Cross is your strongest lead: federal oversight requirements built into a system designed to work without workflow change under surge conditions. Compliance never became a separate review gate because the platform absorbed it. That pattern is what growth-stage companies need as they acquire regulatory surface area in insurance, payments, and clinical documentation. They need someone who treats constraints as design material.
AI-native startups (Abridge, frontier-stage): The speed objection is secondary to the craft-altitude question. They want to know if you understand AI as a material with properties. Lead with Thermo Fisher's multi-role architecture (one record, multiple role-appropriate views, permission-aware visibility) as a structural pattern that maps to AI-mediated workflows. Let the structural pattern lead; the timeline supports. Use with caution at frontier AI companies where the interviewer's mental model of speed is "ship a prototype by Friday, learn by Monday." Keep the consequence reframe lighter here. If the interviewer hasn't yet encountered regulatory or operational stakes in their own product, the frame may read as risk-aversion. Read the room through their questions: if they're asking about iteration cadence and experimentation velocity, lean on the Equinox+ timeline and scope-call story instead.
Enterprise platforms: The speed objection rarely surfaces here. If it does, it's a proxy for "will you be entrepreneurial enough inside our bureaucracy." Equinox+ is your lead: scope decision under pressure, multi-brand complexity, shipped MVP with a 4.8-star rating. The enterprise interviewer hears someone who can navigate organizational complexity and still ship.
Quick Reference for the Room
"How do you work in a fast-paced environment?" → "I've shipped 0→national deployment in 6 months under federal oversight, and 0→MVP in 3 months for a 600K-member consumer product. The difference in my background is that speed came with consequence. Mistakes in disaster relief or pharma supply chains don't get fixed in the next sprint."
"Your background is mostly enterprise clients. How does that translate?" → "The clients were large. The teams were tiny. Red Cross was 7 people. Thermo Fisher was 3. The pace was startup pace with enterprise stakes."
"You come from consulting. How do we know you can build?" → "Every case in my portfolio shipped into production with real users, real data, and real operational consequences. Red Cross processed 1,689 cases in its first two weeks live. Thermo Fisher runs across 9 manufacturing sites. Happy to walk through the build decisions in any of them."
"We need someone who can move fast without a lot of process." → "My default is to dissolve constraints into the product so they don't become process. At Red Cross, federal oversight requirements were built into the platform from day one. The system worked under federal audit pressure without adding process steps. Compliance lived inside the product as a design constraint. It never became a separate gate. That's how I think about speed: removing the things that slow teams down."
"What's the fastest you've shipped something from zero?" → "Three months, 0→MVP, Equinox+. Launched to a 4.8-star App Store rating across three brand experiences. The scope call that made that possible is documented in the case study."
H2 headcount typically unlocks mid-July. Outreach sent Tuesday or Wednesday of next week lands in quieter inboxes over the holiday. Be ready before the long weekend.
- Backdoor references are expanding: The Wall Street Journal reported in June 2026 that companies like Zapier now require hiring managers to have live reference conversations before extending offers, with some conducting as many as 10 calls for senior roles, which means every reframe in this dossier needs to survive repetition by someone who isn't you.
- Headway's two director postings: The Provider Experience posting foregrounds AI-native workflows and player-coach speed, while Core Insurance & Design Systems emphasizes predictability and systems craft, revealing that the same company can require entirely different speed profiles across roles.
- Structured hiring and hidden evaluation coexist: Greenhouse's structured scorecard workflows formalize what interviewers assess, but executive-search firms simultaneously run backchannel checks that no scorecard captures, so your counter-narrative has to work in both the formal panel and the informal call.
- AI governance as design credential: NIST's AI Risk Management Framework and the EU AI Act both define human oversight requirements that map directly to the "human-system operating contract" framing, giving the speed-under-consequence argument a regulatory tailwind as more growth-stage companies encounter compliance surface area for the first time.