How to effectively communicate technical decisions to non-technical stakeholders

as a tech lead, i'm often struggling to effectively communicate complex architectural decisions to non-technical stakeholders like product managers and executives. for example, explaining why we need to re-architect a critical data pipeline to handle eventual consistency, or why a certain microservice boundary is important, often gets lost in translation. i can explain the technical details to engineers all day, but boiling it down to impact on risk, cost, time-to-market, or user experience for non-technical folks is tough. what strategies or communication frameworks have you found most effective in translating deep technical architecture concepts into terms that resonate with business stakeholders? are there specific analogies or ways of framing these discussions that have worked well for you?