Anup Sivadas-Principal Solutions Architect at Amazon Web Services

Anup Sivadas, Principal Solutions Architect at Amazon Web Services (AWS), drawing from experience across retail technology, database engineering, Expedia Group, cloud migration, and enterprise solution architecture at AWS, this conversation explores how technical leaders connect business strategy with engineering decisions, develop industry expertise, and help organizations move beyond experimenting with AI toward creating meaningful business value. *In this episode, we cover:* 1. Why technical expertise alone is not enough to create enterprise value, and how Anup's experience across database engineering, cloud infrastructure, and solution architecture shaped his understanding of the relationship between customer needs, business outcomes, and technology decisions. 2. How customer obsession changes the way technical solutions are developed, including why engineers and architects need to understand the business objectives behind a request before determining which technologies, platforms, or architectural approaches should be used. 3. Why identifying the right problem starts with asking the right business questions, including understanding what customers are trying to achieve, whether a proposed initiative can generate measurable ROI, and whether the investment addresses a meaningful organizational priority. 4. How Amazon's Working Backwards approach and PR/FAQ documents help organizations clarify customer needs, challenge assumptions, and define the intended outcome before committing significant resources to complex technology initiatives. 5. Why industry knowledge is essential for effective enterprise solution architecture, and how researching customer priorities, understanding operational challenges, and collaborating with specialized industry partners helps technical leaders identify opportunities that may not be apparent from a purely technical perspective. 6. How data architecture has evolved from traditional relational databases toward increasingly specialized technologies, including NoSQL, graph, and in-memory databases, and why understanding the application's requirements and the quality of its underlying data is critical for building effective solutions, particularly with AI. 7. Why organizations should challenge whether AI is genuinely improving a business process or simply being added to an existing workflow, and how working backward from the desired outcome can reveal opportunities to redesign processes rather than automate inefficient ones. 8. Why enterprise AI strategy needs to move beyond productivity improvements and basic automation, including how technical leaders can help organizations think bigger about generating new revenue streams, creating business opportunities, and using AI to solve meaningful industry-specific challenges. #AWS #AmazonWebServices #PrincipalSolutionsArchitect #CloudComputing #EnterpriseAI #ArtificialIntelligence #AI #SolutionArchitecture #CustomerObsession #DigitalTransformation #BusinessStrategy #TechnicalLeadership #Podcast