Now that my General Assembly class is over, I’m looking for ways to continue learning how to create great user experiences. Being able to articulate strengths and weaknesses from a UX perspective is something I’m working on, so I decided to try a new thing and see how it goes. Each week, I’ll do a short post about a great (or not so great) experience I had as a user and talk about what made it that way.
In my opinion, intuitiveness is what makes Treehouse a really good experience. (By the way, nobody’s giving me any incentive to say any of this.) I never had to read a manual on how to use Treehouse, or consult any FAQ section. The visual cues on the site were enough to show me around the first time I visited the site. Here are four other navigation elements that make the platform enjoyable to use:
Yesterday, I wrapped up my UX design class with General Assembly. It was only six weeks long, but I feel like I’ve come a long way since the beginning of August! When I started, I had a vague idea of what the design process looked like, but now I’ve actually been through every step of it.
Here are six things I learned:
1. You can learn something from every project, even if you create a product you don’t love.
These last couple weeks in the course have been somewhat of an exercise in persistence. I’ve gained a ton of knowledge and experience, but overall, I feel like I’m creating something that adds work for people. Which is probably the opposite of what I should be doing as a UX designer.
Let me back up a bit. I’d written previously about how, according to my user research, people were having problems with yoga classes not being quite what they expected, and they wanted to know more information before stepping into the studio. So my mission was to figure out a way to give them more information. If you want to know where it all went wrong and what I’m learning from it, keep reading.
Whoa, this class is moving along quick! This time last week, I was listening back to the user interviews I did about the process of finding new yoga classes. Now there are colorful sticky notes all over two walls of my office, and I’m starting to see the shape that my final project will take.
When I say “starting to see,” I mean that. I’ve concluded that users are saying that finding yoga classes is easy, but finding classes they’ll like is not, but I’m still trying to figure out how to solve that problem in a practical way.
In this post, I was going to go through all the work I’ve done and all the steps I’ve taken to get to the short list of features for my final project. But then I realized that that would be boring for you, the user. And I’m no expert yet, but I know that boring the user is probably bad UX. So I’ll just tell you about my favorite part, creating a user persona, if you want to keep reading.
Right after my front end web development class ended, I decided to dive right into another class. This one is an intensive online workshop in UX design through General Assembly. The idea is to take students through the entire UX design process, from research to final product, in six weeks.
This first week was all about user research. The challenge was to pick an area to research, find some people who are interested in the topic to interview, and use what I learned during interviews to identify a problem. Then during the rest of the course, I’ll be creating a solution to that problem.
The topic I picked was the process of finding and choosing yoga classes, and to keep a long story short, I found that everyone I interviewed wished that process were different in some way. The most common thing people said was that they’d like more information about teaching styles or what poses a class will consist of before getting to the studio and stepping on their mat.
I ended up really getting into the process of doing user research and interviews. If you want to know more about what went well and what I’d like to improve, keep reading.
Exactly a year ago, I was taking an intro to HTML and CSS workshop through an organization called Girl Develop It. I signed up for it because I’d just celebrated a big milestone in my personal life and I wanted to try something new and adventurous.
I know most people wouldn’t exactly consider making websites adventurous, but for most of my life until that point, I’d actually been somewhat afraid of technology.
Growing up, I associated technology — answering machines for the family business, 90s-era PCs that were a pain to set up, printers that never seemed to work right when a school paper was due — with stress. And nobody likes stress, so I learned to tell myself, “Well, I’m just not a computer person.”
I didn’t realize until I was 31 years old that “computer people” were just people. (I guess I’d always thought that people who were good with technology had some kind of innate superpowers that I just didn’t get somehow.) I was working around a lot of developers and engineers and I slowly started to realize I had things in common with them. As we humans tend to do, you know. Then I heard a great quote while listening to a story on The Moth podcast: “I don’t think that smart people are smarter than me, I think they read a book I didn’t read.”
Things are winding down for my front end web development course in the Code Louisville program. I finished all the required classes on Treehouse, I attended my last class meetup, and earlier this week, I turned in my project. It has to go through final review before I officially pass the course, but I’m pretty optimistic.
At this point, I thought it would be cool to do a look back at the project and how far it’s come over the past few months. If you just want to see the final version, it’s here. But if you want to see the project’s evolution, including screenshots of its (very) humble beginning, keep reading.