How products evolve to accommodate AI systemsStructural redesign for LLM consumptionChunking as a design decisionMetadata and content normalizationVersioning strategies and lineage trackingData flow patterns built for LLMsVector storage as a first-class componentHybrid retrieval and rerankingReal-time indexing and refresh strategiesLocal versus cloud inference in the data pathProduction performance for AI productsLatency and throughput matter for product adoptionCore maturity metrics for LLM inferenceTime to first tokenTime per output tokenToken generation timeEnd-to-end latencyRequests per second and tokens per secondGoodputMedian performance versus tail performanceMonitoring product experience with P50, P95, and P99Designing product requirements around performance targetsExample 1 – chatbots for customer supportExample 2 – code assistantsExample 3 – document processing toolsPerformance enhancements in modern AI systemsSemantic caching for repeated or structured workloadsWhere semantic caching helps mostDesign challenges: staleness, personalization, and safetyToken prefill and KV cachingHow KV caching works in practiceToken prefill and shared prefixesReducing TTFT with LMCache – a dedicated cache orchestration layerWhat LMCache doesHow LMCache interacts with product architectureWhere LMCache fits in our performance toolboxInternal enterprise tools as AI-first systemsMigration from legacy dashboards to conversational toolsSafety, correctness, and trustModernizing enterprise searchMeasuring and improving relevanceDesigning approval flows for AI-generated workWorkflow checkpoints and risk tiersHuman review layers in regulated environmentsRollout planning across large organizationsStakeholder alignment and sponsorshipChange management and user adoptionCommon blockers and how to address themCustomer-facing products built around LLMsNew user experience patterns that emerged from AIStreaming text as a first-class featureConversational UI as the primary surfaceContext management and memorySafety, traceability, and user trustGrounding and citations as user experience elementsHallucination mitigation as product behaviorTransparent prompts and data useProduct tiering and pricing for AI servicesModel selection and feature setsContext windows, latency, and quotasAligning pricing with valueThe role of the product manager in AI-native developmentIdentifying opportunities with measurable valueScoping for capabilities, data readiness, and latency expectationsCapabilitiesData readinessLatency and reliabilityCross-functional ownershipMetrics and experiments for AI-enhanced journeysHow the build process itself adapts to AIAI-driven code generation and refactoringSpecification drafting with LLMsTest creation and automation with LLMsImpact on development velocity, staffing, and costQuality considerations in AI-assisted developmentRunning LLMs on smaller and edge devicesWhy on-device and edge LLMs?Compressing models for edge deploymentQuantization and low-bit inferenceSLMs and edge-oriented architecturesDistillation and specializationRuntimes and platforms for local LLMsGeneral-purpose local inference runtimesPlatform-specific ecosystemsHybrid edge-cloud patternsDesign trade-offs and implications for AI-native productsPractical architecture patternsWhen to use cloud inferenceWhen to use local inferenceWhen to combine bothRouting by complexity and confidenceRouting by privacy and policyRouting by resource and experienceExample blueprint for an AI-native productSummaryQuestionsReferencesJoin our Discord and Reddit space