Juno —
If you have live conversations this week, the BCG DV narrative will come up, and certain versions of it will get punctured by anyone who has built or run a product past year one. The claim-budget method from Issue #7 applies here with unusual precision because your BCG DV record has a specific shape: defined-timeline engagements that shipped real products into production, then handed them to the client. Every phrase below gets tested against that shape.
Everything below is grounded in your published project history and verifiable engagement structure, not assumptions about what interviewers will value.
Some of the expansive framing I'm about to flag appeared in my own first issue. "Venture-building," "founding-team product design director," products "still live in production today." I used those phrases because they felt accurate. They are accurate in a narrow sense. But they imply things the record doesn't support. This piece is the correction.
The background itself is strong. BCG Digital Ventures was not traditional consulting. You didn't produce strategy decks for someone else to implement. You designed and shipped production software with real engineering teams, real users, and measurable operational consequences. The problem is specific phrases that claim a duration and continuity of ownership the engagement model didn't provide.
"Venture builder"
An interviewer who has actually built a venture — raised money, hired through year two, survived the post-launch trough — will hear this phrase and mentally check whether you stayed. You didn't, because the engagement model didn't work that way. BCG Digital Ventures formed strategic venture teams to develop, launch, and grow products for corporate partners. Your role was Product Design Director. Engagements ran twelve months for Thermo Fisher, six for Red Cross, ninety days for Equinox+. You built the product and shipped it. Then you moved to the next one.
The phrase borrows founder connotation without the continuity that founders have.
Say instead: "I was a product design director at BCG Digital Ventures, where I led the design of new products built for major enterprise and institutional partners — zero to production, with real engineering constraints and real users at launch." True at every joint.
"Founding team"
Your homepage says "Founding design leader · Thermo Fisher, American Red Cross." Two of the four BCG DV projects. The case pages support this — both were built from zero, and your design decisions defined the product's structure. Equinox+ was also zero-to-one, but your homepage doesn't apply the founding label to it. Allē was a redesign of an existing loyalty system.
The gap: "founding team" in most people's ears means you were there before the product existed and stayed as it grew. The first half is true for Thermo Fisher, Red Cross, and Equinox+. The second half isn't. And the phrase doesn't apply to Allē at all.
"Founding design leader" — the phrase you already use on your homepage — is better than "founding team." "Founding team" implies ongoing membership in a group that continued building together. "Founding design leader" names a function you performed at a specific phase: you led the design work that created the product. Use it only for Thermo Fisher and Red Cross, where the zero-to-one build is documented. For Equinox+, say "zero-to-MVP design lead." For Allē, describe the scope directly: "I redesigned both surfaces of a loyalty system serving 30 million members."
"Four products still running"
Your homepage says "All shipped. All still running" about five systems — the four BCG DV products plus Alibaba, which is a separate role. The individual case pages are more careful. Allē's page says "Two surfaces. One loyalty system. Both live." The other three describe launch and deployment in past tense without claiming current status. My own Issue #1 said Equinox+ and Allē were verifiable in app stores and mySupply returned a live page, but Red Cross's current status was unverifiable, and I flagged that live status needed revalidation after July 15. I don't have confirmation that all four are still running in September 2026.
Two gaps. First, the factual claim may not hold for all four products today, and an interviewer who checks will notice. Second, even where the products are still running, you haven't been involved with them for years. Product survival after your departure is a legitimate signal — it means you built something durable. But claiming it as a headline metric invites the obvious follow-up: What happened to those products in the four or five years since you left? You don't know, because you weren't there.
Say instead: "I shipped four products into production at BCG Digital Ventures. The ones I've been able to verify are still live years later." The hedge is honest and strengthens credibility — it shows you're tracking outcomes without overstating involvement. If asked which ones you've verified, name Allē (your own case page says "both live") and note the others were live as of your last check. Don't lead with the number. Lead with one product's story and let the breadth emerge.
"Shipped under real constraints"
This phrase has the smallest gap between implication and evidence. Thermo Fisher: twelve months, one designer, two engineers, nine sites across three continents, $20M margin opportunity, 100% partner adoption. Red Cross: six months, national deployment, $847K disbursed, replacing six legacy systems, during an active disaster-response cycle. Equinox+: zero to MVP in ninety days, 600K premium members, 4.8-star App Store rating. Allē: 30M+ members, 40K+ provider practices, 3.2x redemption lift, CAC reduced from $92 to $42. These are production outcomes with measurable consequences.
The only risk is that "real constraints" sounds defensive — as if you're preemptively arguing against the consulting-background objection before anyone raises it. An interviewer who wasn't going to question whether the work shipped now wonders why you felt the need to assert it.
Drop the phrase. Describe the constraint directly: "I had one designer and two engineers to build a supply-chain platform across nine pharmaceutical sites." The constraint is in the specifics. Naming it as a category adds nothing.
The implicit claim: long-cycle product owner
This is the most dangerous phrase because you might never say it out loud. It lives in the accumulation of the other four. If you say "venture builder" and "founding team" and "four products still running," the listener assembles a picture of someone who built products and stayed with them through years of iteration, organizational scaling, and post-launch learning. That picture doesn't match the record. Your longest BCG DV engagement was twelve months.
As I wrote in Issue #9: product longevity does not remove a genuine requirement for sustained managers-of-managers experience or long-cycle internal stewardship. If the role needs someone who has guided a product through its second and third year — navigating organizational politics, managing a growing team, making the hard calls about what to kill — the BCG DV record doesn't answer that. TinyFish and Alibaba might. The BCG DV work answers a different question: can you take a complex problem in an unfamiliar domain, build a product from zero, ship it into production with a small team, and leave behind something that works without you?
That question is worth answering well.
The summary version
Title: Product Design Director at BCG Digital Ventures. Context: major enterprise and institutional partners — Thermo Fisher, Allergan, American Red Cross, Equinox — with production-grade constraints. Outcomes: four products shipped into production with documented metrics. Boundary: defined-timeline engagements — I built and shipped, then the client's team took over.
State the boundary before anyone asks. The interviewer who was going to probe for the gap finds you've already named it, and what's left is the work itself.
- Allē's case page dates: Your Allē page displays interface examples dated April and October 2023 and an analytics dashboard labeled Q4 2024, though the project header says "Shipped 2021" — worth reconciling before someone asks whether these are your deliverables or later iterations by the client's team.
- Thermo Fisher metric wording: The live page body says "$20M margin opportunity" but the open-graph metadata says "$20M visibility gap," which means a link preview and the actual page tell different stories about the same number.
- Red Cross live-status verification: Your homepage claims all five systems are still running, but the Red Cross case page describes launch in past tense and its interactive demos are explicitly labeled as recreations, not live product — confirm current operational status before repeating the "all still running" claim.
- BCG DV employer attribution gap: The individual case pages display your title but never name BCG Digital Ventures — only the homepage supplies that association, so a reviewer who lands on a case page directly won't see the engagement-model context that makes the work legible.