Building your IDP’s information architecture

Poor information architecture is the #1 reason Internal Developer Portal programs fail. Unfortunately, it’s also an extremely complex challenge for engineering teams that affects all parts of your engineering stack. In this 2-part live event, Cortex Co-founder and CTO, Ganesh Datta, will draw from conversations with hundreds of engineering teams to share what he’s learned about the impact of establishing a resilient information architecture, why it serves rather than is served by a strong catalog, and how to define (or redefine) your own—without fear. After the event, we’ll invite attendees back for Part 2, where Ganesh will answer questions attendees may have as they begin the process of building their IA. We'll discuss: -How engineering teams should think about information architecture, and why a properly mapped IA is critical for success -Who’s responsible for an IA, and who contributes to definitions and dependencies -How the information in your IA can be used both programmatically and by individual developers in daily work -When you should consider retooling your IA, as well as what to do if you fear the rest of your data ecosystem is unreliable -Common pitfalls and gaps in deployment, plus how to unwind them if needed -What to do in the next 30, 60, and 90 days to create a resilient model that scales with your organization