Backing Into a System

Image credit: Back to the Future, 1985.

Today I went to a tech event here in Milwaukee. I attended a workshop, and listened to a presentation. They were from two different companies, on two different subjects, but they had one thing in common. They both were attempting to reframe a problem-solving approach by backing into it.

The first was a modeling workshop. This was run by a firm that specializes in information architecture, and much of their work centers around building models around what problem you are trying to solve, so that you can see where things are falling short, check whether everyone is in agreement, and find opportunities for solutions. The definition of a model is wide, and could include anything from a list to a flow chart to an architectural model. They had a series of 14 double-sided cards that were organized into 4 sections, intended to help you conceptualize and build your model.

While the use case for modeling was clear, actually sitting down to do one was wide open and difficult to approach. I couldn't help but think about how I'd build the instructions differently. A key challenge seemed to be consolidating their modeling expertise to a one-size-fits-all set of steps, approachable by a newbie. The presenters were deep into the concept of modeling, and I couldn't help but think about how I'd try to explain it to someone with no prior knowledge. Maybe I should model my ideas :).

The next presentation was from someone who had worked at Amazon. When new ideas are pitched at Amazon, they are presented as press releases. This forces the presenter to write in a particular style that is required to grab you with the purpose at the outset. It then follows a structure that hits certain points about the idea. It's fun because you can envision a time in the future when your idea has already been manifested. It's often followed with an FAQ section written as if users are asking questions about the existing product. The press release and FAQ allow you to start in the future, and then back into whatever the challenges might be with a particular product.

Both methods allow you to travel into a future of sorts, and give you tools to work backwards to a solution. Like looking at a painting upside down, this can alter how your brain approaches a problem. I'm looking forward to running these approaches through their paces, to see if starting at the end helps me create better solutions.