On this week's episode of Inside Outside Innovation, we sit down with Jorge Arango. He's an information architect and author of the book, Living in Information. Jorge and Brian Ardinger talk about how Jorge's background and traditional architecture has affected his insights and approach to digital design. They talk about some of the trends in information architecture, and how digital environments are changing the way we work and live.

Inside Outside Innovation is the podcast that brings you the best and the brightest in the world of startups and innovation. I'm your host Brian Ardinger, founder of Insideoutside.io, a provider of research, events, and consulting services that help innovators and entrepreneurs build better products, launch new ideas, and compete in a world of change and disruption. Each week we'll give you a front row seat to the latest thinking, tools, tactics, and trends, in collaborative innovation. Let's get started.

Interview Transcript

Brian Ardinger: Welcome to another episode of Inside Outside Innovation. I'm your host, Brian Ardinger. And as always, we have another amazing guest. Today we have Jorge Arango. He is the strategic designer and information architect and author of the book called Living in Information: Responsible Design for Digital Places. Welcome to the show Jorge.

Jorge Arango: Thank you, Brian. It's a pleasure to be here.

Brian Ardinger: I'm excited to have you on the show to talk about your book, but more importantly, to talk about this whole world of information architecture. If my research is correct, you started your career in traditional architecture. And so I'd like to maybe start there and talk about how did you go from the world of physical architecture to the world of digital design?

Jorge Arango: Yeah, that's right. So, I studied architecture as in the design of buildings and it's been a while now. I'm part of a generation of folks who came into the workforce at a very interesting time in history when the worldwide web was coming into focus. It was becoming a thing. And when I saw the web, I essentially left my career in architecture to start a web design studio, because it seemed to me at the time that this was a new medium that would change the world. We didn't know yet, in what ways it would change the world, but it was pretty clear that it was going to be huge.

Brian Ardinger: To give the audience of understanding of what is information architecture and how does that differ then UX design or creative and that?

Jorge Arango: Yeah, there is some overlap there in that information, architects help create the experiences that people have when they interact with software. But it's in no ways constrained by the design of software. So, information architecture is focused on helping make information easier to find and understand. So, think of something like an online store where you maybe are offering your customers, a large catalog of goods.

There are going to be ways for you to structure that information so that your customers can find what they're looking for. And so that they can do things like compare products to other products or find related products and establishing those relationships, figuring out what distinctions to enable is a big part of what information architects do.

A lot of people who are involved with the design of software-based experiences, think of design as concerned with the way that things look and how they function. And that is certainly an important component of it. But information architects are concerned with the underlying structures that inform those things. That includes things like categories, navigation systems, the way that search engine search functionality, and such a system is structured and organized. Those are all within the area of concern for information architects.

Brian Ardinger: I can see now where traditional architecture can have a major influence in how you develop digital environments. How do you think you're learning in the physical world has influenced your digital design capabilities?

Jorge Arango: That's one of the reasons that I actually jumped on the web back in the mid-nineties. It was pretty clear to me that there was a direct relationship between the stuff that I'd been studying in architecture school and what was needed for this new medium.

The main things that I often talk about are a concern for structure. A building is not just a collection of forms and spaces. It is also a series of systems that are structural systems, right? Like, and you can think in traditional architecture terms or building architecture terms, you can think of the columns and beams and other physical structural elements that hold the building up and allow it to resist the forces like gravity.

It was pretty clear to me that there were structural aspects to the web experience even fairly early on. And the other one, which I've already touched on, was the fact that these are systems. They're never freestanding elements. And when you're designing the user interface to a software-based product or service, the stuff that you see on the screen, isn't all there is to it. Oftentimes these things form part of and relate to other component. That's very much within the area of concern for building architects as well. You have to be mindful of all of the systems that make up a building when you're designing such a thing.

Brian Ardinger: Well, I imagine as you're building out more and more digital products and more and more people are becoming used to that, it was different back when you're just developing a website and that was a place people went typically. But now digital is involved with virtually everything. Your phone's in your pocket and your hand. Smart technologies, IOT, things along those lines are giving you data and giving you access to things that changed the physical world, as well as the digital world. How do you go about approaching a new project to start mapping out how these systems and structures interact?

Jorge Arango: Again, there's a learning there from design of buildings. So, when you're designing a building, one of the first things that you want to do is understand what is called the program. Let's say that you've been hired to work on the design of something like a dance studio. When designing a building to serve the functions of a dance studio, there are going to be certain functions that that environment is going to have to be able to accommodate. And those functions call for different types of spaces. For example, in a dance studio, you're going to want rooms for people's bodies to be able to make a series of movements. And that dictates the form of those spaces.

You're also going to want. Other types of rooms that enable people to change in and out of their street clothes so that they can get into clothes that they're more comfortable performing dance moves with. And there's a whole host of other functions that such a building must accommodate. And architects oftentimes start by thinking about the program that a building must accommodate and what types of spaces are going to have to be a part of that and how those spaces relate to each other.

And the same is true for people who are designing software-based experiences. I find that one of the things most missing in our disciplines these days is taking a step back from how things will look and function and really thinki...

Psalm 118 | Psalms That Point To Christmas | 21 December 25 | Michaela Copsey l Holy Trinity Cambridge

Holy Trinity Church Cambridge

The Rejected Stone Becomes Cornerstone

The AI-powered Podcast Player