Why the Way AI Feels Is as Important as How It Works - with Carsten Wierwille of HTEC

2026-05-29 · Source: The AI in Business Podcast · Field: Business & Management — Project & Product Management, Corporate Strategy & Leadership · Depth: Intermediate, extended

Summary

Carsten Wierwille, Chief Product & Design Officer at HTEC, argues that treating design as a late-stage step in enterprise AI initiatives is a strategic error, leading to technically functional but unused tools. With over 25 years in design, technology, and business, Wierwille highlights that companies often build AI because they can, not because they understand a specific problem. This approach shifts the bottleneck from ideation to review, overwhelming senior staff with concepts lacking clear evaluation criteria. He emphasizes that AI should amplify human judgment, citing the financial advisor model where AI handles routine tasks, allowing advisors to focus on client relationships. Wierwille also notes that the MVP framework often fails for novel AI experiences, advocating for "cognitive design" – thinking about user perception, decision-making, and trust before coding. HTEC is a global engineering firm with 20+ engineering centers.

Key takeaway

For AI Product Managers and Directors of AI/ML scoping new initiatives, prioritize design clarity from the outset. Your focus should shift from "what can AI do" to "what problem does AI solve for users." Integrating design and engineering early will prevent costly adoption failures and reduce the burden of reviewing ill-defined concepts. You must define evaluation criteria for AI output before development, embracing "cognitive design" to ensure user trust and effective human-AI collaboration, rather than just technical functionality.

Key insights

Late design in enterprise AI is a strategic mistake, leading to adoption failures despite technical functionality.

Principles

• AI should amplify human judgment, not replace it.
• MVP framework often fails for novel AI products.
• Design must define AI output evaluation criteria.

Method

Cognitive design involves thinking about user perception, decision, and trust before any code or model training.

In practice

• Use AI to automate routine tasks for financial advisors.
• Integrate design and engineering from an initiative's start.
• Define AI output rubrics with design and user research teams.

Topics

• Enterprise AI Design
• Cognitive Design
• AI Product Development
• Human-AI Collaboration
• MVP Framework
• Financial Services AI

Best for: Product Manager, AI Product Manager, Director of AI/ML, Consultant

Related on AIssential

• When AI started writing PRDs, I re-understood the value of PM. — AI automates output, elevating the value of human conscious thought, judgment, and contextual understanding in product management.
• Why Most AI Features Fail Before the Model Is Even Chosen — Successful AI features prioritize user friction and workflow design over model selection and abstract AI capabilities.
• What People Really Want From AI — Public perception of AI is complex, blending hope and fear, with practical concerns outweighing existential ones for most users.
• Guest Speakers Reveal Where AI Belongs In CX — And How Leaders Protect Trust — Intentional AI deployment in CX requires clear strategy, human oversight, and deliberate design to maintain trust and coherence.
• AI Is Smoothing the Human Out of Design — Current AI product design often fails by adding AI as a button rather than integrating it structurally.
• The design process is dead. Here’s what’s replacing it. | Jenny Wen (head of design at Claude) — AI-driven engineering velocity is forcing a fundamental shift in the design process, prioritizing execution support and shorter-term vision.

Open in AIssential →

Editorial summary, takeaway, and curation by AIssential. Original article published by The AI in Business Podcast.