Form Follows Forces

← Back To TUG Talks

Summary: Dan Klyn and Abby Covert speak on working out problems of form, structure, and meaning in user experience, expressed as "form follows forces."


We live in a world where tens of millions of people are spending forty or more hours each month in places made of information. Some of those places are better than others. With the ones we like the most, there's often something about the interplay between "envelope" and "content" that's key to unlocking the genius of the thing.

Below is the full text of the first part of the joint keynote presentation that Abby Covert and I gave at World IA Day in Ann Arbor in February of 2014.

WIAD14.jpeg

Last year at World IA Day NYC, my co-presenter Abby Covert conducted an on-stage interview with Lou Rosenfeld about the history of information architecture, and Lou prefaced his comments with an observation that I’d like to re-iterate here in Ann Arbor today.

We’re living and working in extraordinary times, akin to those of the beginning of the Industrial Revolution.

We’re living in the midst of a change in human culture as monumental as that of the Industrial Revolution. When viewed from the timescale of history, we’re still in the first few hours of the first day of a new era.

And as was the case at the beginning of the Industrial Revolution, the ways of the “old” world and the ways of the “new” world are all smeared together. Horses and cars at the same time.

I made this observation to my friend Hassan Hodges a few weeks ago, and he told me to look up the “horsey horseless.”

horsey-horseless.jpeg

This is us now—fumbling for forms for the things we make that work in the actual world. In a world where the horses get scared by the cars.

It’s normal and natural and ok that most everything we’ve made in our infancy with these new media from the “new” world are goofy things that don’t really work.

But I don’t want to make goofy things forever. I want to get beyond horsey horseless. But how do you do that? How do you get to forms that work for the new world without re-creating the problems of the old one?

Denise Scott Brown has observed that “faced with the unmeasurable, people steer their way by magic.”

I don’t believe in magic. So one of the ways I’ve navigated all this is to look to and follow a figurehead—someone who’s seemed to master the unmeasurable, and who’s done and doing good work. What would they do?

What would Richard Saul Wurman do?

“It’s not enough in this moment in fast-moving history to make just a better version of what has happened before… its going to work for a while, so it’s going to fool people… but nothing goes on forever—they’re going to have to go backwards to find some new beginnings to branch out from.”

Just an improved version of what came before isn’t enough. Mr. Wurman recommends that we go backward to find new beginnings. Back to a place before the pre-conceptions about structure and meaning that are operative in web design and user experience today.

I had my graduate students doing this last fall in SI658, looking back at the ways people have thought about and practiced architecture in the built environment and digging into how it came to be that movements like beaux-arts provided a way for designers to know how form and structure and meaning ought to be worked out.

With modernism, the guidance for working out problems of form and structure and meaning is stated as a maxim: form follows function.

Glass-House.jpeg

This is the Glass House by Philip Johnson, and part of why the form of this structure is able to be so pleasing is because the functional requirements here have been simplified to the point of nonexistence.

Nobody lives in this house. Its not for living, it’s for photographing, and for the paying of homage to Mies van de Rohe, whose maxim was “less is more.”

Form follows function works best when function is hyper-simplified. Like Pinterest. Modernist approaches to structural form are appealing because everything is in its right place.

The reaction to modernism’s strict rules for selecting a structural form and working out its relation to function and meaning is called postmodernism—where form *flouts* function. In contrast with modernism’s “everything in its place” this is “whatever, all over the place.”

In between the strictness of “everything in its place” modernism and “everything all over the place” postmodernism is a weird micro-movement called mannerism. The mannerist maxim is “less is a bore.” Its approach to balancing form and meaning and function is through an embrace of human complexity and contradiction.

Screenshot-2014-02-25-10.13.22-300x162.png

This is the Sanisbury wing of the National Gallery in London, on Trafalgar Square—a triumph of mannerist architecture and place-making by the American architects Venturi and Scott Brown.

Venturi and Scott Brown’s mannerism isn’t an architecture of perfection like modernism, nor an architecture that denies the possibility of universal guiding principles, like postmodernism. The highest praise for or from a mannerist in the tradition of Venturi and Scott Brown would be to say that the work is “almost all right.”

Screenshot-2014-02-25-10.25.22-300x162.png

The Sainsbury wing is almost all right because it fits into its context on Trafalgar Square. In an almost seamless way. But it’s not seamless. It’s seamful. When you notice what the building is doing, that’s on purpose. There’s meaning in the breaks in the order, and also in the places where the order is not broken.

From the square, the facade of the Sainsbury wing appears to be of a piece with the beaux-arts structure of the main museum. Blends right in.

But then in this stairwell, which is mostly occluded from view on the square, the beaux-arts gives way to high modernism.

Screenshot-2014-02-25-10.26.22-300x164.png


And even out on the square, where your first glance assessment is that these buildings are of a piece, and maybe even built at the same time, with a second, closer look you might notice these delightfully colored Egyptian-styled capitals atop the pillars that operate the iron gates that swing into place when the museum is closed. The collision of these three architectural styles and systems of meaning is skillfully balanced by the architects, but never perfectly resolved.

Abby and I quite like mannerism, and the best example in digital space of this almost all right—inconsistent at times and on purpose way of working out form and meaning is Medium, from the makers of blogger.

Medium is a new place on the Internet where people share ideas and stories that are longer than 140 characters and not just for friends. It’s designed for little stories that make your day better and manifestos that change the world.

Turns out, Medium doesn’t let you edit or write these little stories and manifestos on a mobile phone.

On a tablet or PC, fine. But not on mobile. Not because you can’t. Not because offering that functionality is hard or expensive or takes a long time. But because they think you ought not.

They’ve chosen forms for their product’s various expressions that are inconsistent at times and on purpose. Because of reasons. The breaks in the order mean something—teach you something about the service. These forms are almost all right. And they follow the operative forces.

Continued In Part 2

Form Follows Forces—Part 2

← Back To TUG Talks

Summary: Information architects Dan Klyn and Abby Covert give a talk at World IA Day 2014 titled "Form Follow Forces."


We live in a world where tens of millions of people are spending forty or more hours each month in places made of information. Some of those places are better than others. With the ones we like the most, there's often something about the interplay between "envelope" and "content" that's key to unlocking the genius of the thing.

WIAD14.jpeg


Below is the second part of the joint keynote presentation that Abby Covert and I gave at World IA Day in Ann Arbor in February of 2014. You can read the first part here.

Abby:

The world today is all about choices. Managing aspects and accidents. It seems that the quote used most often these days to describe the world of design is: Good, Fast, Cheap: Pick Two. I think that if we use this quote as a lens, we can start to break down the environment that designers are working in today. We can start to create a taxonomy of the forces that are at work in the world we work in. I have given countless talks now covering the context sensitive nature of design decisions and their outcomes, yet the single most common question I still get is something to the effect of: Should I make my website more like Facebook or Amazon or Something Else? I have endured countless circular conversations with other design-minded people about how hard it is to separate the opinions from the a**holes in a world where client services and lack of data collide.

But most importantly, I have spent the last few years not selling creative work, but instead helping creative people to prove out and communicate the value of their creative work. And in my experience, the spectrum of blanket uses for the concept of “Good” have risen up to meet this generation of designers. I want to unpack for you here the many varietals that we have created with the concept of good. Each stands as a little shelter for us to hang behind, shielding ourselves from diving into the complexity of deciding who we want to be when we grow up. Each stands in the way of consensus, collaboration and confidence in creative executions.

There has been a wind of change blowing through. A force that has many names, but is always centered on the same message: good enough is good enough. Students are taught that everything would have been better if you it released yesterday because you would have data today. We are holding ourselves less and less accountable to our intrinsic pride in our creative work and more and more to our deadlines and extrinsic motivations.

I have personally given and been given the following advice at an alarming rate in the last few years:
• Fake it till you make it
• Be Minimally Viable
• Live in Beta
• Fail Early and Often
These are all good pieces of advice for living in a world shaped by the force of Good Enough. But what does it mean for the next generation of designers? Should there even be another generation…

Remember when we could rely on a relatively small set of design standards to make a “website work”—well that time is not now. Today, things are changing literally while you are working. Because of this, the same rules do not necessarily always apply. What is appropriate is more contextual than ever before. And we have more people exploring the boundaries of the information medium than ever before. yet they are largely working without a net. And without a net, sites like Healthcare.gov get developed and then destroyed in a slew of articles that basically say: We don’t know what went wrong but it is all wrong.

In the mid-90s, anyone working on the web deeply will remember a term that they say was used for Information Architecture before IA was coined for the purpose. Well, “the pain with no name” is still alive and well, and its latest face is that of a lack of language, heuristics and poetics for the way we architect the information spaces we spend an increasing amount of time inhabiting.

On top of this lack of understanding what “Not Good” means, we are simultaneously faced with the fetishist design shower of shiny objects that rains down on the Internet daily. Products that are terribly architected, badly built or poorly designed are propped up by journalists. Never before have we had a community of criticism on the internet like what we see now. Yet these totems of awesome also lack language to describe them, data behind their magic or reasoning for what is “good” about them.

Very Good Examples stand on pedestals looming far over those looking for guidance and very good is aimed for. Meanwhile the contextual touch of good is missed entirely—design is prioritized over architecture, and imitation and un founded patterns thrive. We ask how can we be very good without asking what good actually means.

Anyone can tell you that we are moving fast. I think it is appropriate to look at two sides of the same coin when it comes to describing the force of fast on the design world.

People want information now, not in two clicks, not in “we will get back to you in 24 hours”—we live in a world where you can pirate any movie you want on or before opening night and the average article has a shelf life of less then 24 hours before it is forever buried in the stream.

Designers are constantly reminded that we live in an attention economy and their design is not likely to get much attention. So efforts are put into making things fast to sign up for, fast to learn, fast to use, fast to forget. The limited time that an average user will give an application or page to load is astounding considering we can almost still hear the screech of the dial up connection finally dying out, taking with it traditional media and advertising practices.

Today’s marketer needs to be a technologist. Today’s technologist needs to be a designer. Today’s designer needs to be a marketer and a technologist. The speed at which the internet is consumed has up ticked significantly and with it, the speed of production has had to increase all the way down the line.

Content Management Solutions sit squarely in the hot seat as some of the most powerful and money saving methods for bringing a business online, yet CMS is still a dirty word in most meetings and is the scope cut from many projects, where speed to release is prioritized over speed to refresh.

There are more cost saving and money centered talks afoot around information spaces than ever before. And the forces that have come out of the need for the commodification of design are undeniable.

A new breed of designer has emerged in the face of this wave of the cheap. The idea of a design unicorn is one person who can master any and all of the mediums involved in delivering creative services for a specific context. Finding that person who can design, build and maintain your website, mobile app, print materials and any other design-y nuggets your house might require to run.

The issue with this force is NOT that unicorns don’t scale. It is that unicorns do not exist. The classic “jack of many trades, master of none” statement comes in to bite the unicorn-wanna-bes that attempt to tackle larger projects, proving time and again that they are merely horses wearing horns. The best project for a jack of many trades is to kill what you yourself can eat. The complexities of today’s design world can not handle this kind of limit on collaboration and innovation.

While more and more unicorns are filling more and more design jobs in small and mid size companies, specialists seem to only be employed by consultancies and large brands boasting big projects. Small companies report not being able to afford things like research, strategy and content development because that kind of expertise is expensive, as it is always an external resource. There is a distinct sense that only really big companies can achieve architectural soundness, while anyone else is just making stuff.

The thought that architecture can be achieved without architects or that research can be achieved without researchers does not seem to penetrate the unicorn fortresses and instead due to lack of alternative tools or deep expertise in anything but, pictures of interfaces are used to solve all problems leaving business people frustrated and users underserved. Because when you are a hammer, everything looks like a nail.

Dan:

So! What’s it look like to do this stuff right? Not very good, or good enough … but good. How do we get beyond horsey horseless?

The standard I’d like to propose that we proceed from this morning in looking more closely at the things we make and assessing their relative goodness is one i’ve borrowed from William Hubbard at MIT. That makers and users alike find the forms to be appropriate, and that users’ reasons for preferring that the forms be the way they’ve been made lines up with the designers’ intentions. And just as a point of clarification—what do we mean by form? It’s more than what a thing looks like. And encompasses more than function. Form has to do with what the thing means because as Louis Kahn said, “Form holds the relation of its elements.”

Screenshot-2014-03-20-09.21.50-300x162.png

A popular contemporary form that holds the relation of the elements on web pages and in apps is the form of the hamburger. The form of the hamburger that slides open the basement. This form has or had meaning. Quite modernist as I see it—form following and indicating function. It used to mean ‘the navigation for our mobile experience is just a tap away.’

Screenshot-2014-03-20-09.23.07-300x162.png

But not anymore. Increasingly, the desktop and tablet versions of sites are embracing the hamburger. Here on the recently- redesigned nbcnews.com the hamburger is presented as simpler navigation. And in mobile contexts, that’s what the hamburger delivers. Here less is indeed more.

Screenshot-2014-03-20-09.25.51-300x167.png

But now, when used on desktop and mobile …. what does this mean? Is the form working with or against what NBC intends and means? Is the reason why we as designers might recommend doing it this way the same one users would cite as the reason why they prefer this approach?

Screenshot-2014-03-20-09.26.34-300x170.png

Here, the hamburger does not actually deliver on its promise of simpler navigation. It delivers wall to wall navigation. And non-navigation also—these feature-tile things from the homepage are recursive here in the so-called simpler navigation. (“Yo dawg, I heard you like tiles so I brought some into the nav that I hid under the hamburger so you could concentrate on the tiles.”) Because we don’t know why we’re using this form, we break it as we build it.

The next structural form for consideration this morning: the stream. People—civilians, regular folks—spend three hours or more per day online. A week or more each month, in many countries and cultures. A lot of that is spent in places dominated by the structural form of the stream. The stream is the structural form for news and social media outlets who’ve given up on or have been overwhelmed when striving for “everything in its proper place.” MLive here in Michigan has replaced multiple uniquely-presented and organized local news presences with one approach to govern them all: a stream-based way of letting some loose business rules “curate” what shows up in the stream. The rule here seems to be crime and weather first, and then a blend of schools, politics and more crime to follow. Instances of what’s in the stream are localized, but the stream itself is both placeless and all over the place. What those who’ve embraced the structural form of the stream seem to have missed is that the nature of stream isn’t an even predictable flow.The nature of stream is lack or loss of control. The nature of stream is stuff floating by from upstream that we didn’t expect …. That we don’t actually like.

You can’t actually control a stream—its nature is to meander. To spill over what had once been edges. Which may be the unconscious motivation for designers and users alike in accepting and even embracing the stream—because “it means whatever it means ”—which I might read as a postmodern rejection of fixed meaning in the tradition of Peter Eisenman, or an embrace of “it’s only meaningful to me,” in the tradition of Frank Gehry. In both cases we take comfort in the non-controllability of the stream.

Screenshot-2014-03-20-09.41.18-300x186.png

Except when we don’t. Except when we get some on us—when what we thought was secure gets swept out into the flotsam. Twitter is an example of a stream-based digital place where the stream means whatever it means. It used to be strictly chronological. Now: not.so.much. Because the stream means whatever it means, design changes can be proposed and tested solely on the basis of hypothesis testing. “The people might like it, let’s see…”

For example, changes they’re introducing on the iOS platform are making it easier to post photos than text. And a stream that’s more full of pictures is a different place than the stream that’s more full of words. One that competes better (maybe) with Instagram and Pinterest. The penultimate structural type to consider in our contemporary context: the MVP and its evil twin, the pseudo MVP. If you’re truly a start up and truly need to have a product out there to discover market fit ASAP because you truly cannot afford research and planning and your dev team consists of a unicorn or two: fine. MVP is an almost an alright way to derive the form of your thing. Godspeed. In many ways a startup’s MVP is form-following-forces—what’s holding the relation of the elements together are the forces of time and function and money.

But big companies and consultancies with big teams are embracing the mvp as their form-giver … The big d-up-front-is-a-waste-so-figure-out-what-you’ll-make-by-making-it-in-quick-iterations crowd say this will be an evolutionary progression from minimally viable base robot forward into. Wherever the sticky-noted stories say we go. Hell, we started with a toaster. With the pseudo MVP, what’s holding the relation of the elements of a product or service together is fear. Fear of getting too far in front of what people can tell us they want. Fear of burning too much of the budget without proof the thing works. Fear of deciders changing their minds before we had a chance to realize the thing they said they wanted before they changed their minds.
The form we give these products and services is pre-figured to follow organizational dysfunction. What good means is that it shipped.

The camera on my phone can’t shoot panoramas without me activating that app. Nor can it trim video. Because theres an app for each of those discrete functions. Because we shipped the minimally viable 5 times instead of considering an integrated approach. Have you ever handed your iPhone to somebody for them to use an app without first activating that app on their behalf? No. Because it is unreasonable to expect anybody but you to be able to sort through your phone’s vast sea of app icons. And each new app you load pushes your other 876 apps a bit farther from your grasp.

Why? Because realizing the minimally viable is (seemingly) less risky and easier to be rewarded for than attempting to realize the maximally valuable. Making a thing that’s pre-caveated as minimal and viable, where requirements are simple or simplified is less daunting than architecting a system. Form can simply follow function. You don’t need an architect, or research. Just a unicorn. To make a uni-thing. A monolith. There’s something absolutely beguiling about a monolith. Something awe inspiring about a perfect slab. Its discreetness. The totality of it. The simplicity of it. The way there’s no question about our relation to it or its rationale for being formed the way it is.

Screenshot-2014-03-20-09.44.56-300x167.png

Surely this is what’s behind the mass adoption of single-page parallax-scrolling “interactive storytelling.” Approaches like what Sony is doing here. Last year they might have realized this same set of objectives as a mini-site or a micro-site.. We like these better …. And we might even like them as designers for the same reason people like them as users.

Sometimes, monolith is good! Pulitzer-prize-winning good. Make the hairs on your arms stand up in awe, good.Relative to our standard, that makers and users alike find the form to be appropriate, and that users’ reasons for preferring that the form be the way it is lines up with the designers’ intentions. Boom! This story lends itself particularly well to verticality. And linearity. Because its content is all mountains and vertical drops and the lines traced in recollection and in the snow by the characters and their skis. The way its been realized and the way its meaning and effects are maintained across devices and modalities is marvelous. This may be the finest work of information architecture that’s visitable in your browser.

In the year that’s passed since snow fall, “to snowfall” has become a verb in the online news business. The nyt has done a number of other feature stories using the mono-slab-logic of the parallax scrolling page, some better than others. Not to be outdone (but sadly, they remain outdone), the Guardian adopted the structural form of the monolith for a story on Edward Snowden and the disclosing of once-secret NSA files. The contrasts here are vivid. And emblematic of the difference between form following forces, and form flouting them. Or worse: form following fashion.

The forces that are operative on a feature story like that of pro-skiers in an avalanche and the year-long investigation of how and why it happened…. Totally different than the forces operative on a “pizza box” story like Snowdon that’s transpiring in real time. Real time is horizontal, not vertical. And a breaking story like Snowdon is riddled with holes from what’s not yet been revealed—the act of reading is more like connecting the dots than tracing lines. I suspect that somebody important at the Guardian told the team to take this story and ‘hit it with the Snowfall stick.’ Form following the forces of fashion.

Abby:

Dan and I spent much of this talk talking about things that with your help can be the path we collectively don’t take. Before we get on with this fabulous day, we have a few takeaways in terms of the counter forces we could introduce to course-correct this world of ours.

“Users” need to be humanized in the mind of businesses, technologists and designers. “Businesses” need to be humanized in the minds of designers, technologists and users. We must apply a deeper level of ethical inquiry into what it means to add to this information overload we are collectively experiencing. We need to recognize the magnitude of the importance of differentiating architecture work and design work, as well as the recognition that our differences are less a land war, and more a miscommunication of intent.

Without working together, the integrity of our work will continue to suffer and our clients will continue to not understand. We can only change this from within our own walls, and through our own jobs. We need to learn from the lessons that have been forged in the creation of places over centuries by architects and planners that have made this world truly remarkable. The digital world we increasingly live in could use some slow reflection on where we have already been and the ground we have already started to cover. There is good stuff in there.

Let’s stop reinventing the wheel so we can start making hover cars! We need to work cross functionally to talk about and better define what “good” means when it comes to the structural integrity of meaning. Simple as that. If you are redesigning your whatever and using excuses like “it just seemed like time” or “because its not pretty enough” please take the time you need and come up with the right direction. You may be surprised how it affects your output, your strategic planning, even your org chart.

We have never had so much complexity to unravel. We have never had more battles of misunderstandings to battle. The global community of IA has never had so many reasons to shout proudly from the proverbial rooftops about the powerful effect our methods and tools can have on real people’s real problems in their real lives.

Gone are the days of us being a “forward thinking, up and coming industry”—the world has caught up to our hopes and dreams for the information we would have to architect. Now they just want to know what’s next and we think it is our job to help guide the form that this world takes next. We hope you are up for the challenge.

Maps, Territories, Language, & Place

← Back To TUG Talks

Summary: Andrew Hinton spoke at Midwest UX 2013 on how language is central to understanding place, and how we create embodied experiences in software and elsewhere.


I thoroughly enjoyed speaking at this year’s Midwest UX, in glorious Grand Rapids, Michigan (home of one of TUG‘s studios).

As a number of our blog posts about the event will surely mention, the curated theme for this year’s conference was “Place.” What does Place mean to design? How do we create or affect the experience of place?

To that end, I prepared a talk on how language—something we don’t normally think of as especially environmental or physical—is actually central to how we understand place, as well as how we make coherently embodied experiences in software and elsewhere.

Slides below! For easier reading of the notes, use full-screen, or download PDF.

My presentation at Midwest UX 2013 in Grand Rapids, MI. The theme was all about "Place." This talk explores how language is a crucial foundation for how we create and understand places, whether virtual or real.

This talk is somewhat related to my earlier post on “Language is Infrastructure,” and gets most of its material from the book I’m slowly completing for O’Reilly Media on designing context.

I’m looking forward to working on this topic even more for events that are coming up in the next year.

Practical Conceptual Modeling

Summary: Information architects Kaarin Hoff and Andrew Hinton share how to use conceptual models to aid understanding when planning for a digital environment.


Andrew and Kaarin spoke at a Detroit UX Meetup about conceptual modeling in 2015, and this content is still very relevant. Please enjoy a blog-friendly version of their notes.


Many Kinds Of Models

1. Hi! We’re here to talk about how practical modeling helps make sense of design by making invisible things visible. It’s part of a workshop we’re developing with our fellow information architect and TUG colleague Joe Elmendorf.

Slide 2—Many types of models

2. There are many sorts of modeling, including things like physical scale models of buildings, mathematical and statistical models. These overlap in many ways. But we’re talking about conceptual modeling.

3. Conceptual models help us do some important things really well, like
– Make concepts into visual objects we can manipulate
– Allow us to explore their relationships
– Let us work with parts and aspects of complex systems

 

Slide 4—Comparing models and interfaces

4. We see Models on a sort of continuum with Interfaces. For digital design work, the ultimate goal is usually to create some kind of interface. But models can do things that the specifics of interfaces can’t. Models are a way to work through questions about relationships and ideas, without being tangled in the specifics of interaction.

 

5. Both of them help us determine what we are making, but they’re better at different challenges. Some questions are better answered at one end of the spectrum than the other.

6. We emphasize this is ‘practical modeling’ because there’s a misconception that conceptual work isn’t practical. But, in fact, all these approaches are practical, when used for the right purposes.

 

Slide 7—What we think shapes what we make

7. Ultimately, the way we conceive of concepts and their relationships creates structures we use for making the final product—whether we realize it or not. So why not make them visible and work with them on purpose?

 

Slide 8—Models facilitate collaboration

8. When we rush ahead it often causes more work in the end. Thoughtfully producing a model to guide a conversation at the beginning of a project can help avoid a lot of this pain. It helps us gain a shared understanding, and get everyone going in a similar direction. Modeling priorities allows us to arrange them and focus on the right parts in the right order. It helps us discover assumptions that could trip us up later, and it especially helps map systemic scale and complexity.

 
A project timeline that represents models at the beginning, middle, and end

Slide 9—Models are tools of communication for the entire journey

9. Another misconception is that modeling is only useful at the beginning of a project. But we’ve found that models used at the beginning continue to be used and updated throughout the work, and even after something has been launched.

 

Examples Of Conceptual Modeling

10. Let’s look at some examples of what we mean—these are various sorts of models we (Kaarin or Andrew) have worked with in our own projects.

Slide 11—Grouping and relating the elements of the system

11. This is an information model that exposes all the pieces, parts, actors, and shows how they interconnect. This can be used as a discovery tool and a discussion tool. We have often created these models collaboratively with clients. One client recently told us they still refer to the info model on their wall daily (we haven’t worked with that client for 1.5 years)!

 

Slide 12—A model for stakeholder IA strategy

12. A major non-profit was enhancing its site’s purpose by creating a huge resource library and home management applications. This simple diagram helped get alignment among stakeholders about the equal weight of each of those purposes, and how they would be integrated.

 

Slide 13—Focusing on user needs with a workflow model

13. This student flow was created for a higher ed client. It helped us discuss the need to break the department-based structure of the website to focus on the audience member’s main needs throughout their university experience.

 

Slide 14—A high-level representation of the user’s journey from shopping to purchasing

14. This model helped establish an understanding of the behavior patterns shoppers have in just about any retail situation, and the essential functions a site needs to accommodate each category of behavior. It’s not a site map, it’s not a wireframe, and not exactly a user journey — but it establishes structure that guides many design decisions.

 

Slide 15—A picture IS worth 1000 words. This model created clarity for software developers in the middle of a meeting

15. Sometimes you don’t have the model at the beginning, but you can still use one to make sense of the work. This model was thrown together in a meeting when we already had pixel-perfect comps, annotated detail wireframes, but we still lacked alignment on what was happening behind the scenes. This model cleared up the confusion quicker than any conversation could had, plus it was able to be referred to later, unlike conversation.

 

16. Last, we want to share one way in which models can go from very abstract to much more concrete.

Four circles imply possibility; four squares implying structure

Slide 17—Circles keep ideas and conversation flowing

17. You’ll notice that we have a lot of circle-shaped blobs in some of these. When we start trying to figure out new things, we often start with circles.
Circles don’t have sides, so they don’t imply any particular direction or order. They let us move them around more easily than squares. As things get more figured out, they become more square.

 

Slide 18—Bubble diagrams help architects plan physical spaces

18. It turns out, even built-environment architects often start by scribbling bubbles and blobs on paper to work out the relationships between all the elements they need to compose into a coherent system — before deciding where walls or doors should go.

 

Slide 19—Bubble diagrams and floor plans are abstractions in designing a home

19. But even a floor plan is still an abstract model. While it’s more literal than the blobs, if you look closely, it’s still mainly just doing the work of establishing the definitions and relationships between the main functional areas of a structure.

 

Slide 20—Clustering to visualize affinities

20. We often start with bubbles and blobs in a similar way, even if what we’re designing is digital. It gets all the elements on the table as objects we can move around, and show relationships between. They allow us to find emergent patterns and dynamics.

 
A bubble diagram of the stakeholder priorities

Slide 21—Stakeholder priorities emerging as the affinities coalesce

21. Often, the blobs coalesce—sort of like mercury merging into bigger globules—that help us identify the primary purposes of a new product, service, or environment. These become a way to represent the big priorities and decisions that stakeholders or even team members are aligned on. And it does this without debates about what should go in the global navigation or what color the menus should be.

 

Slide 22—The site structure emerged from the functional model

22. More often than not, we find this sort of approach helps us discover the ultimate structure something can have—such as the navigation structure of a website or search application. The example on the right is a site structure diagram, but it’s more like a floor plan than a flow chart—it establishes places and their relationships, much like in building architecture.

Because a lot of the bigger questions have already been settled, the conceptual architecture isn’t a big surprise—in fact, it often just feels inevitable, rather than unsettled and up for debate. After this, we can better focus on the finer points of detailed structure and interaction design, without disruptive surprise

Modeling Is A Kind Of Making

23. To conclude, here are a few thoughts to leave behind: Modeling is a kind of making; rather than the craft of an object or interface, it’s the craft of understanding. It can work at many levels of fidelity—from abstract blobs to specific structures. Even if you aren’t included in the beginning strategy or architecture work of a project, modeling is still a powerful tool for helping figure out big or complex systems and find shared understanding.

24. Thanks!


Want to Learn More About Making Models?

If you’re interested in learning more, please see our current workshops!


Complete Slide Deck

Practical Conceptual Modeling at UX Detroit Feb 2015 from Andrew Hinton

Andrew Hinton's UX Lisbon Interview

← Back To TUG Talks

Summary: Andrew Hinton recaps his presentation at UX Lisbon, and his and Abby Covert's podcast with UX Podcast on improving environments by getting language right.


It was my great pleasure last week to attend UX Lisbon, in beautiful Portugal, where I led a workshop based on my book, Understanding Context. The delightful attendees brought great energy to the gathering, as we learned about essential models and principles for how people perceive and figure out their contexts.

After an overview of the models and principles, we went out on foot to explore the surrounding area.

The group worked in teams, following “missions”: locate a pharmacy, and explore the information about the city’s rail systems. This meant we had the pleasure of walking around Lisbon’s beautiful Gare do Oriente train station, which contains many contextually rich wonders involving wayfinding, digital systems, and service design.

We returned to the workshop venue to do some contextual modeling and discuss among the groups. The workshop participants were really sharp folks who picked right up on how to use the models, discovering how various modes of information helped or hindered an individual “agent” attempting to understand the environment.

Later in the week, TUG alum Abby Covert and I stopped in to record an interview with the folks at UX Podcast, where we chatted about the importance of getting the language right as the “spine” of any organization, and how it enables coherent, understandable environments for customers and employees. Gee, that makes it sound awfully dry, but it was actually very informal and fun.

Thanks to Bruno Figueiredo and everyone who produced this excellent conference, now known the world over as one of the premiere learning and networking experiences among digital design folk. Highly recommended, if you ever get the chance to attend.

A Beginner’s Guide To Taxonomy

← Back To TUG Talks

Summary: With case studies and personal process anecdotes, Jessica DuVerneay explains how taxonomy is a valuable tool that should be in every IA's toolkit.


Screen-Shot-2015-05-27-at-2.39.22-PM-300x226.png

Last year, I was asked to act as Global Producer for the first ever World Information Architecture Day 2012. While it was a great challenge, it was one of the best things I’ve been able to do to support the global IA community. This year, I was honored to be asked to contribute to the local community through speaking at WIAD 2013 in Ann Arbor.

Nervous, as this was my first conference presentation, I was able to wrangle my friend and colleague Marti Gukeisen (from Enlighten) to tag team a presentation entitled “A Beginners Guide to Taxonomy”. Fresh off of our first “real” taxonomy projects, we were able to take a subject commonly perceived as dry and make it engaging and entertaining.

Using case studies and personal process anecdotes, the practitioner focused message was simple: Taxonomy is an incredibly valuable tool that can be approached in a simultaneously methodical and user centered way, and should be in every IA’s toolkit. In our talk we outline an quick and dirty approach to taxonomy, explain it’s benefits and challenges, and encourage practitioners to jump in and give it a try themselves.

If you missed the event in Ann Arbor, or want to chime in on the awesomeness of taxonomy, please check out this video of the Taxonomy talk and let us know what you think!

The Rise And Fall And Rise Again Of Information Architecture

← Back To TUG Talks

Summary: TUG co-founder Bob Royce shares a pdf of the talk he gave at EuroIA titled, "The Rise and Fall and Rise Again of Information Architecture."


Last week I was honored to be able to present a talk at the Euro IA conference in Prague titled “The Rise and Fall and Rise Again of Information Architecture” which presents my perspectives on the field having witnessed it’s birth but only recently having engaged directly in it. The conference was wonderful, with good talks and even better conversations among the international attendees.

The Rise and Fall and Rise Again of Information Architecture (PDF)

2017 IA Summit Closing Keynote

← Back To TUG Talks

Summary: To cap off IAS17, Dan considers the larger context of IA and our community and asks: is it dishonest to call ourselves information architects?


To cap off IAS17, Dan Klyn gives the closing plenary address. He questions whether — in our quest to make better online experiences — we’ve lost sight of what’s true. He also reflects on his research over the 8 years, seeing that progress in the field of information architecture requires a shift in emphasis.

Dan wonders: Is it dishonest to call ourselves information architects?

IAS17 Closing Plenary Address

Delivered on March 26, 2017 in Vancouver, BC, Canada. Dan is currently serving as the president of the IA Institute’s Board of Directors.

Allow me to begin with some thank-yous.

Thank you Susan Mercer, Dave Cooksey and Marianne Sweeney for the countless hours of hard work you put in so that the rest of us could enjoy this event together. I consider it an honor for you to have entrusted me with the task of closing it down for you.

Thank you to Peter Morville, for taking me on as a mentee 17 years ago, and for providing a model of what it looks like to be a professional information architect that I could learn from and follow. I got an email from him this morning wishing me luck with this speech, and he suggested that if all else fails, to consider taking my pants off.

Thanks and praise are also due to ASIS&T for its steadfast support of this community through eighteen IA Summits, and especially for having had the wisdom to select Vancouver as the host city for 2017. As a Michigander, I’ve been a visitor in Canada probably a hundred times, and this was the first out of 199 border crossings that caused me to feel ashamed of where I’m from.

So it’s good to have had some time away from all of that, and to have been welcomed so warmly in this breathtakingly beautiful place.”

Read the rest on Medium:

medium.com/@danklyn/2017-information-architecture-summit-closing-plenary-address-efb0e0e21d2c