As pointed out in part 1, current versions of Minneapolis skyway maps are mostly cluttered and confusing – but I can’t really blame the map creators. It’s a confusing system! A literal skyway map is a mess any which way you try to attempt it. Just think of the layers of the skyway, you have streets, buildings, and the actual skyways, that zig and zag through a building.
“Straight and orderly the skyway is not”
Therefore, I’m suggesting we deconstruct the skyway system and I feel best way to do this is to follow the transit (aka subway) map model with a few variations.
As an example of deconstruction, we only need to look at the experience of riding a train – only three things really matter. The stop, the route, and the destination. A train can go around a curve or two but what’s that to you? The train is taking you where you need to go and it only stops at marked stations.
The legendary Massimo Vignelli brilliantly took advantage of this in designing New York’s subway map. You’ll notice he completely ignored streets, distances and curves, instead he used horizontal and vertical straight lines and the occasional 45 degree angle. He also used colors to signify routes, and stations were simple equally spaced dots on the map.
Today we couldn’t imagine any subway system without it this type of map.
Now it is time to apply the principles of Vignelli’s map to the skyway and its jagged edges. And we to need to start by identifying what matters to the skyway user.
1. Buildings: Essentially these are equivalent to a train stop.
2. Skyways: These connect buildings to one another.
3. Destinations: The skyway user doesn’t necessarily need to know North from South or East from West – especially considering that Downtown Minneapolis sits on a NW – SE street grid. Therefore, a skyway users needs to know they are headed in the correct direction and getting closer to their intended location.
However, we do have a few extra use cases to consider that are unique to skyway users:
4. Distance: Skyway users are for the most part, walking. This means we can’t completely ignore the concept of distance. While not needing to provide exact distances we don’t need to be exact either.
5. Streets: The skyway is in many ways an extension of the street and is connected to the street. Therefore, we can’t completely ignore streets. They would also form a good barometer of distance – as measured in blocks.
Taking these five concepts into consideration, I created the following map:
That’s so pleasant. Here are some things worth highlighting in the map:
- The street grid was changed to be completely vertical and horizontal, even though IRL it is not. This is in response to pedestrians not needing to know which way is true north.
- Skyways are made straight through buildings — UNLESS there is an important jagged edge worth noting to users or multiple paths through a building.
- I’m introducing routes to the skyway. This would help us to let users know they are moving in the correct direction.
- I have been unable to walk all 11 miles of the skyway to confirm its accurate enough. I created this version off of old maps. If you have any suggestions for improving the routes please let me know!
Feel free to use the map as you see fit. Admittedly, signage is still a big piece to this project as it may be difficult to use this map without. I address signage in part 3. Onwards!