Copy
View this email in your browser

INFORMA(C)TION No. 68:

Inflection Points

Making the most of opportunities for change. Plus Peter Morville on emancipating information architecture and other things worth your attention.
Jorge ArangoJorge Arango
November 1, 2020

Welcome to INFORMA(C)TION, a biweekly newsletter about systems thinking, responsible design, information architecture, and other topics relevant to humans who create digital things.

If you enjoy this email, please consider sharing it with others. And if you're not subscribed yet, you can sign up here. Thanks for reading!

Path junction at Colliers Wood (Photo by Trevor Rickard - BY-SA 2.0)

Inflection points are moments when the course of events branches off into one of several possible directions. After the inflection point, things change — one way or another. A life-altering car accident is an inflection point. So is the all-important presentation to the CEO.

Some inflection points are more consequential than others. Putting a new version of the app into production is an inflection point. But depending on the release’s features, it may only nudge the product’s trajectory slightly. On the other hand, a misfire when presenting to the CEO may kill the project altogether.

Expected inflection points are easier to deal with than random ones. If we’re aware of the upcoming presentation, we can prepare. We can put in extra effort to ensure we’ve addressed the main points, created the necessary materials to tell the story compellingly and directly, and practiced our timing and delivery.

But we don’t have to be victims of random inflection points either. For example, we can take precautions to avoid getting injured in a traffic accident. We can become more cautious drivers or configure our phones to stop showing notifications while we’re driving. We can also make large-scale structural changes that reduce the likelihood of injury. Some, like the obligatory use of seatbelts, initially meet resistance. Eventually, norms change as the cost of adhering to the status quo becomes evident.

Change requires that we agree on our desired trajectory. For example, we universally agree that we should reduce traffic injuries. As a team, we agree that we’d like ongoing executive support for our product decisions. To do this, we create mechanisms that allow us to align as close as possible to these desired trajectories over time.

While inflection points are critical, we mustn’t lose sight of these broader trajectories. Our near-term goal may be to deliver a kick-ass presentation, but the presentation is ultimately in service to keeping the project going. The project matters more than the presentation; the presentation is one of many inflection points that move the project along. By aligning our long-term objectives, we can work towards making inflection points nudge us towards the desired direction.

Over time, the sequence of major and minor inflection points defines our story. We can trace the course of events that got us to where we are. We can think about what we would’ve done differently at each inflection point and what we should do next. Wisdom entails looking backward to move forwards. By considering the big picture, we can ask ourselves: do we want to keep going in this direction? If not, upcoming inflection points offer opportunities for change.

Also worth your attention:

The Informed Life Episode 47: Peter Morville

Episode 47 of The Informed Life podcast features a conversation with Peter Morville. Peter is a pioneer in the discipline of information architecture. Among many other distinctions, he co-authored with Lou Rosenfeld Information Architecture for the World-Wide Web, the classic O’Reilly “polar bear” book on the subject.

This is Peter’s second appearance on the show. I asked him back because I wanted to learn more about his recent blog post calling for practitioners to emancipate information architecture. “Emancipate” is a strong term, and I wanted to know what he meant by it. This led to an enlightening (if too brief!) discussion about structural change. I hope you get as much value from our conversation as I did.

The Informed Life Episode 47: Peter Morville on Emancipating Information Architecture

Thanks for reading!

-- Jorge

P.S.: If you like this newsletter, please forward it to a friend. (If you're not subscribed yet, you can sign up here.)

SHARE THIS POST:
Share Share
Tweet Tweet
Forward Forward
Copyright © 2020 Boot Studio LLC, All rights reserved.

Jorge Arango
Boot Studio LLC
P.O. Box 29002
Oakland, CA 94604

Disclosure: This newsletter may include Amazon affiliate links.

Want to change how you receive these emails?
You can update your preferences or unsubscribe from this list.

Email Marketing Powered by Mailchimp