Product Builders

The episode identifies a real problem - accountability gaps in AI-assisted product decisions - and offers some useful framings (governance debt, decision logs, single-point ownership), but largely circles around the core issue without providing concrete, actionable solutions. The conversation acknowledges the problem repeatedly ('who is responsible', 'system issue', 'accountability debt') but offers limited new specifics beyond 'assign one person' and 'ask five questions at C-level.' Most substance arrives in the final 5 minutes; the middle section re-hashes the same concerns.

“who is responsible for that AI feature? One specific person. Because thanks to that, the impact on that feature is trackable.”

“it's more a problem of a system uh actually because the way we use A.I. uh that process, that system doesn't acknowledge that there is somebody responsible”

The core insight - that AI-assisted decisions lack clear ownership and accountability - is sound but not novel; the framing of 'governance debt' and 'accountability debt' are borrowed terms presented as fresh. The suggested remedies (assign one person, log decisions, ask C-level questions) are sensible but not counterintuitive or first-principles. No contrarian arguments or unconventional approaches are offered; the entire conversation sits firmly in conventional product governance thinking.

“I've heard such story that if you need to, if the answer for your question is like it depends it means that you have a governance depth”

“Who is responsible for that AI feature? One specific person.”

Kamil Marczak is a designer working inside development teams at Boldare (a software house), giving him relevant hands-on experience with the problem. However, he is not a widely-recognized practitioner or operator at scale; he is a practitioner speaking from one company's perspective. The host is unnamed and plays a facilitator role. Neither guest has obvious senior authority (C-suite, founder, VP Product at major company), limiting caliber relative to the seniority-and-relevance standard.

“Kamil Marczak, a designer at Boulder. And Kamil doesn't work next to the development team. He works inside it, which is exactly what, um, and why he sees the design to code CMAP to close.”

“I'm Anna, uh, your host today.”

The episode lacks named examples, concrete metrics, or data. Kamil references 'stories' and generic scenarios ('issues led to trial in court', 'financial products', 'social services') but provides no actual case studies, timelines, or measurable outcomes. The one personal anecdote (using AI to prototype a design and losing ownership feeling) is vague and unquantified. No numbers, named companies, or specific incidents are cited; the discussion remains abstract and illustrative rather than evidential.

“I've even heard stories, uh, where, uh, issues led to trial, uh, in course in court.”

“I wanted to uh experiment with AI as much possible and for a meeting with a product manager I've designed uh a prototype.”

The host asks reasonable setup questions and maintains structure, but rarely challenges, pushes back, or dig deeper when Kamil offers vague answers. When Kamil says 'it's more a system issue' or 'it's hard to find one specific person,' the host accepts this without pressing for concrete examples or testing the claim. Follow-ups are often restatements rather than probes ('So taking it in the summary, do you have any idea'). The host does redirect to practical application near the end, which is constructive, but overall the conversation lacks sharpness and productive friction.

“And from the practical perspective, um, what does a decision log even look like right now in a team”

“I would say that it's always about the same thing. Who is responsible at the end”