The Consulting Background Concern That Reframes Can't Fix

Two concerns under one question

The consulting-background objection has a fork in it, and using the wrong response at the fork costs you more than the objection itself would.

Branch A is advisory-vs-build. The interviewer thinks BCG DV means slide decks. The standard reframe handles this: founding-team participation, shipped products, three ventures visibly operating years after your engagement ended. Covered in Issue #9. Brief treatment below, then we move on.

Branch B is multiyear ownership. The interviewer already understands you built real products. What they want to know is whether you've ever stayed with one through years of post-launch iteration: retention curves, accumulated technical debt, annual planning cycles, team turnover, competitive response. The standard reframe doesn't reach this concern. It addresses a version of the question they've already moved past.

The companion piece on reframe failures covers the general diagnostic for recognizing when your prepared response isn't landing. This dossier applies that diagnostic to the consulting case.

How to tell which concern you're facing

You can ask directly. Do it early.

If they respond with anything about "real products" or "not just strategy," you're on Branch A. Lead with BCG DV's venture-building structure, your role as Product Design Director at BCG Digital Ventures on the founding team, and the fact that Thermo Fisher mySupply, Equinox+, and Allē are still operating. That reframe is documented and effective; use it and move on.

If they say anything about "year two," "what happened after launch," or "long-term iteration," you're on Branch B. Stop reframing. Everything below is for Branch B.

What Branch B sounds like in the room

Interviewers probing for multiyear ownership rarely use those words. They ask questions that test whether you've lived through the phases that only happen after a product has been in market long enough to surprise you. Four recurring probes, drawn from practitioner and employer-published interview guidance:

"What happened to your success metrics after launch?" They want to know if you tracked outcomes past the deployment window. Did retention hold. Did the usage patterns you designed for actually emerge. This separates launch awareness from sustained outcome ownership.

"Which decision did you reverse after real usage data came in?" They're testing whether you stayed long enough for reality to contradict the launch plan, and whether you owned the response. Roadmap pivots, feature reversals, scope changes driven by post-launch learning.

"What did you rebuild rather than keep patching?" The technical-debt question. MVP compromises that became expensive. Design decisions that worked at launch scale but broke at growth scale. You only encounter this if you're still there when the debt comes due.

"What still worked after you were no longer making every decision?" Continuity through team changes. Whether your standards, systems, or operating mechanisms survived beyond the founding team. Adobe's design-leadership guidance flags this as a common gap: candidates end their story at ship without explaining what endured.

Some of these questions can surface in a Branch A conversation, particularly post-launch metrics. The difference is what happens after you answer. A Branch A interviewer asks about outcomes to verify the product was real — they're satisfied by the answer and move on. A Branch B interviewer asks about outcomes as the entry point into the next question: what you changed, what you rebuilt, what you learned only by staying. If the first outcome question leads to a follow-up about what happened next, you're on Branch B regardless of how the conversation started.

Two or more of these probes in the same conversation means the role likely requires multiyear internal ownership as a baseline expectation. The Exit Conditions Map classifies repeated year-two questioning as a signal that the mandate centers on optimizing an existing product through long lifecycle phases.

Classification

The section's framework distinguishes perception gap (they misunderstand what you did), evidence gap (you did it but can't prove it), and hybrid.

This one is hybrid, but the two components are unequal in size, and the larger one is not closable through positioning.

The evidence-gap component is narrow. If any of your BCG DV engagements involved post-launch design oversight — release reviews, KPI monitoring, advisory cycles — and you haven't documented it, that's closable. A project listing with engagement dates and any post-launch responsibilities would resolve it. If that documentation exists, build it out now. It shifts the boundary.

The larger component is not an evidence gap. Your documented maximum is twelve months for Thermo Fisher mySupply, six months for Red Cross, three months to MVP for Equinox+. No approved evidence establishes that you oversaw multiyear iteration, maintenance, retention optimization, or repeated annual planning cycles for any of the five ventures. As Issue #7 established: your portfolio supports shipped-and-adopted ownership through launch, not multiyear lifecycle ownership. You can choose which true story to tell. You can't create time on a product that wasn't there.

The qualification move

When the truthful answer is that you haven't done this, say so directly:

Then ground it immediately:

• Thermo Fisher mySupply, Product Design Director at BCG Digital Ventures. Twelve-month zero-to-live build across six pharmaceutical partners and nine sites. Exception-first triage design for a supply-chain platform that Thermo Fisher still operates and has expanded.
• American Red Cross, Product Design Director at BCG Digital Ventures. Six systems consolidated into one. Six months to national deployment. $847,000 disbursed and 1,689 cases opened in the first two weeks.
• Equinox+, Product Design Director at BCG Digital Ventures. Three months to MVP. Launch-sequencing decision that deferred two brands to protect quality for the first three. The product is still in active distribution six years later.

Allē and ZED Connect are excluded here because neither has the documented engagement duration or scope metrics that make the three projects above effective grounding. If you're asked about them, they're real ventures with the same Product Design Director role — but for this qualification move, lead with the evidence that carries concrete timelines and measurable outcomes.

The pattern across these three is build ownership at high velocity in high-stakes environments, with products that survived well beyond your engagement. That capability is different from multiyear stewardship, and you should say so before they have to point it out.

Why the boundary works better than the stretch

The instinct is to stretch. Find some angle that makes twelve months sound like multiyear ownership, or frame "the product is still live" as though it implies you owned its evolution. Interviewers at this level hear the stretch. It costs more credibility than the boundary itself would.

The qualification move concedes the narrow fact — engagement-structured ventures, not multiyear operating tenures — while your evidence contradicts the inference that usually follows. The Issue #9 principle applies directly: the fact is real, but the inference that consulting-built products don't endure or that the design leadership wasn't substantive is what your portfolio disproves.

A hiring committee that genuinely needs someone who has managed a product through three annual planning cycles, two platform migrations, and a team that turned over twice will not hire you for that. You shouldn't want them to. This is the exit signal the Exit Conditions Map describes: when the mandate centers on long-cycle optimization of an existing product, the role doesn't match your pattern, and continued pursuit costs search time better spent elsewhere.

A committee that needs someone who can build a complex product from nothing, ship it into a high-stakes operating environment, and leave it in a state where it thrives without you — your evidence for that is unusually strong. The question is which committee you're sitting in front of.

Pre-interview reference

Diagnostic question: "When you say ownership, are you asking about the build model or about operating the same product through multiple post-launch cycles?"

Branch A (advisory-vs-build): BCG DV venture-building structure. Three products visibly operating years later. You were Product Design Director at BCG Digital Ventures on the founding team.

Branch B (multiyear ownership): Stop reframing. State the boundary: "I wouldn't claim multiyear operating lifecycle ownership. My pattern is building from zero, raising the bar, and staying close to the work through launch and adoption."

Ground with: Thermo Fisher (12 months, six partners, nine sites, still operating). Red Cross (six months, six systems consolidated, national deployment). Equinox+ (three months to MVP, still in distribution).

Branch B probes to watch for: Post-launch metrics. Reversed decisions. Rebuilt-vs-patched. What survived after you left. If a post-launch question leads to a follow-up about what happened next, you're on Branch B.

Exit signal: Two or more year-two probes in the same conversation means the mandate likely requires multiyear internal ownership. Deliver the qualification move with confidence, and assess whether this role matches your pattern.

Classification: Hybrid. If you have undocumented post-launch involvement, build the project listing now. If you don't, the larger component is a genuine experience boundary. Say so with confidence.