Bridging the Gap: IA as an Essential Part of Domain Driven Design
Quietly, unbeknownst to us, developers have been teaching themselves to do information architecture. I say quietly, but they’re not being all that quiet about it. There are books, presentations, even entire conferences dedicated to it, and we had no idea, because they’re calling it something else: Domain Driven Design. This wildly popular software approach emphasizes matching technical design to the business and requires developers to create controlled vocabularies, model the flow of information through business units, and interview experts to uncover their mental models before they get down to coding. This is all the stuff that IA is great at, and there’s a whole new set of people out there desperate for our help.
If you’ve ever heard the phrase “ubiquitous language” or “business domain” from a developer, or you’re just frustrated with the constant discourse on design “getting a seat at the table,” come learn how to translate IA work into terms developers are already excited about and how techniques from Domain Driven Design can uplevel your IA practice.