Objection Dossier · Treatment: repair, not answer · Live source inspected and last validated August 1, 2026
This decays in days. Until it's fixed, strangers are evaluating a version of your work you did not approve and cannot see.
1. The Objection
"I read the piece on what you count. Is that material okay to be out there?"
AI-native and enterprise buyers, at screening and portfolio review, which is the stage you are not in the room for. That absence is why the objection usually arrives silently, and why the deliverable here is a repair order instead of a spoken answer.
2. What They're Actually Asking
The concern is not clarity. It's boundary discipline. Your entire pitch, across all three pillars, is that you design the moment a person decides to trust a machine's output, override it, or hand it more authority, and that the hard part of that work is deciding what gets exposed, to whom, under which conditions. A reviewer opens junochen.com. She reads your employer's pricing strategy, notices the lock didn't lock, and watches you fail your own thesis on the one artifact you control end to end. What she writes down has nothing to do with team-building. It's that you don't govern your own surfaces. She will not tell you, and you will not be shortlisted.
3. The Strongest Case Against You
- The gate runs in the browser and verifies against nothing. An unauthenticated request to /what-do-you-count returns the complete article. The password field is painted over content the server already sent. View Source is the whole exploit.
- What's sitting there is commercially specific. Competitor pricing from $5 to $2,400 per thousand requests, per-step pricing decisions, zero-credit failed runs, tier naming and pay-as-you-go mechanics. A claim that paying users underperformed free users on identical tasks. An enterprise buyer's fifty-concurrent-agent requirement. A
65%/32%left behind in a CSS comment. - You are never present when the link is opened. Gusto's Head of Design, Iru's Head of Product Design, and Instrument's Design Director all collect the portfolio password inside the application form. A VP or a design manager reads it alone, at speed, with no way to ask what a page was for.
- Your homepage does not retrieve as a single candidate. Two of three retrievals agree. The third lags, and it's the one a stranger may hit. Live source today, against a crawler cache still being served today:
| Live source (Aug 1) | Cache still being served | |
|---|---|---|
| Lab count | "Four live agents built solo" | "Five systems built alone with Claude Code" |
| Page title | Design Leadership for High-Stakes Systems | "Juno Chen — Product Designer" |
| TinyFish | Absent | "Case Study 05 TinyFish.ai" card, customer at 3,774 tasks, $743 infrastructure cost, $20 paid |
A search extraction from six days ago matches today's live source. So: one stale copy, not a site-wide drift, which is why step 4 is a recrawl request and not a rewrite. Three of the four labs open cleanly for a stranger. UAT Sentinel I could not confirm.
4. The Grain of Truth
Nothing here is a perception gap. Two of the three defects are verified properties of files you own. What no one can give you is a discovery rate, so the urgency argument rests entirely on asymmetry: one evening of work against downside that is silent and has no ceiling.
5. The Repair, In Order
Issue #5 flagged the client-side gate as an exposure risk and told you to fix it. This is the escalation. The material now public belongs to your employer, which makes this an employment-relationship problem before it is a positioning problem. Do it in this sequence.
Today
- 1. Pull the essay out of the response, not out of the navigation. Deleting the homepage link closes one discovery path and leaves the URL fully retrievable by everyone who has ever held it, which includes every recruiter you sent it to. Delete the page or put real server-side authentication in front of it. Then verify: clear the
pf_access_v1local-storage key, open in incognito, View Source, searchpricing,$2,400,per-step,65%. Request/what-do-you-countand/what-do-you-count.htmlseparately, because the second redirects to the first. Article body in the source means the page is public. (High confidence; directly inspected.) - 2. Delete the homepage excerpt as well. The Field Studies teaser names pricing decisions you made with your CEO and CPO. That is your employer's commercial content, on your front page, above the fold. Issue #5's rule stands: TinyFish lives in conversation, never in writing as design proof. This essay violates both halves at once.
This week
- 3. Choose one lab count and make it true in three places. The live page says four and names Carrier IQ, UAT Sentinel, Retail Velocity, Brand Pulse. Test each one the way a stranger will: cold link, no context, no you narrating. If UAT Sentinel survives that, four is right, and four appears identically on the site, on LinkedIn, and on the résumé. If it doesn't, say three and lose nothing. Nobody is grading the number. The disagreement between your three surfaces is what costs you.
- 4. Force the stale copy to refresh. Your live page has stopped saying Product Designer. At least one crawler hasn't. Fixing source does not fix what caches serve, so request recrawls, then re-scrape your link previews by hand so the old title and the TinyFish case card stop resurfacing in search snippets and chat unfurls. LinkedIn and Slack preview state I could not verify; log those as unknown, not clean. (High confidence that one cache is stale; low confidence on which other platforms are currently serving it.)
Unusually, this defect does not vary by tier, and that is exactly why the repair outranks every other open item on your board. The AI-native founder and the enterprise VP Design open the same page and reach the same conclusion about whether you hold a line.
After the repair, the page needs no positioning at all. Alibaba: Head of Design and Research for North America, $50B+ GMV, +20% transactions, +2.2pt NPS. Thermo Fisher mySupply: $20M+ margin recovered, six partners, 100% adoption. Red Cross: six systems consolidated to one, $847K disbursed, national. Add "Trust Is the New Interface" and the live labs, sitting under a homepage already titled Design Leadership for High-Stakes Systems. That inventory argues for a Director+ leader on its own. High confidence: the content is already leadership-grade. The defects are the only thing standing between it and a clean read.
6. What to Say
Post-repair only.
"There's a private tier I don't publish. Pricing and commercial strategy from my current role, and it isn't mine to hand out. If it's relevant to what you're evaluating, I'll walk you through the thinking live."
"Every lab on the site opens without me in the room. Start with Carrier IQ."
The first line is the one that converts, because it turns withholding into judgment, which is the precise trait the objection doubted.
7. What Not to Say
- "The site's a little out of date, I've been meaning to update it." You are selling oversight and governance. An ungoverned artifact does not read as a scheduling problem. Failure mode: a fixable defect becomes a character read.
- Any account of how the password works. Failure mode: you've handed a curious reviewer the coordinates.
- The pricing essay offered as proof of AI depth. Failure mode: your evidence becomes the moment they start wondering what you'd publish about them.
8. Early Signals
- The application form asks for a portfolio password. Confirmation that the review happens without you. Treat the artifact as your entire first round.
- Someone cites a detail that isn't on your current site. Five systems. Product Designer. A TinyFish case study. They are reading a cache. Correct it in one clause, send the canonical link, keep moving. Don't apologize, and don't tour them through the discrepancy.
Quick-Reference Card
Objection: "I read the piece on what you count. Is that material okay to be out there?"
Real fear: A trust-and-oversight leader who can't govern her own artifact.
Lead with: Alibaba. Head of Design and Research, North America, $50B+ GMV platform.
Say: "There's a private tier I don't publish. It's my employer's commercial material. Happy to walk you through the thinking live."
Avoid: "I've been meaning to update the site."
Do first, tonight: Confirm /what-do-you-count returns nothing to an unauthenticated request. Right now it returns everything.
- Where the password lands: Greenhouse holds application-question answers in the candidate profile alongside documents and hiring-team notes, and organizations can optionally mark a question private so only Site or Job Admins can view the answer — worth knowing that when you type a portfolio password into an application, you generally can't tell which of the two you're getting.
- Who actually reads it: A Figma recruiter's account of portfolio review says the person deciding whether to interview you is usually a design manager, creative director, Head of Design, or VP, working under severe time pressure, which is why she argues the portfolio has to communicate without you sitting beside the reviewer.
- The evidence nobody has: The two studies that come closest to your situation examined deliberate deception rather than accidental drift — public LinkedIn visibility changed what applicants lied about without changing how often — so treat the discovery rate for your defects as genuinely unknown and act on the asymmetry instead.
- The next artifact, once the site is clean: The gap in your public AI evidence isn't lab number five; it's one case that follows a failure through trace, diagnosis, design change, evaluation threshold, and release decision, which is the layer current AI design roles now name explicitly — Gusto's Head of Design posting assigns the design leader responsibility for deciding when AI output ships, when a human intervenes, and when output should not be sent at all.