IMG_2945 (1)

Wells Fargo App Diagnosis

This week for class we had the opportunity to really analyze the system of a banking app, by creating a concept map, which is a diagram that depicts suggested relationships between concepts.

I had the pleasure of analyzing the application of the large banking corporation, Wells Fargo. The application has many functions.

It is not the most user friendly application as many paths that the user can take lead to a page asking the user to call a number or visit one of their locations. It also has many paths that overlap others that already exist.

IMG_2945 (1)

To create this mapĀ I began by taking screenshots of the various pages of the app and printing each of them out. Once I did that, I was able to identify what the various functions and call to action on each page was.

From there, I started mapping these interactions and loosely found a way that each interacted with the other.

Quickly, my map became a mess. Four iterations later I created the one you see above (which still has many intersecting lines) but revealed many things about interactions within the app.

Generally, there are a lot of paths. And many of those paths lead to the same place as others. It can be difficult to know the one (ideally intuitive) place you should go to find a specific function.

To add, some prompts simply lead to a page asking you to call a number or visit a location, which feels like an unnecessary path.

IMG_2946 (1)

As such, as I considered my redesign, I wanted to make information on the app (which most all seems apt and important) more equitably distributed.

This was a very challenging exercise mostly taken up by creating a readable concept map design that showed the layout of information within a extremely robust and complex app.