Current Progress on the site! WOOOOOOOOOOOOOOhoo.
The direction that I wanted to pursue for my A3 project was to re-brand and promote a system for Multnomah Village. I wanted to be able to build logos that could fit a new and unified direction and help give Multnomah village a nice and friendly face lift. Overall I am fairly pleased with how my project turned out. Altogether I built 7 logos, (main logo and 6 businesses), a vertical banner idea, a sandwich board idea, and ideas on how to turn secondary elements into a tool one could use on any village business.
I think the strongest aspect of my project was the village mark itself. I had many ideas floating around, and the one I settled on was clean, simple and made sense. I had earlier designs that resonated with the 50’s, thinking that I would add an Americana flare. However, my goal was to bring the village into a newer, modern look, so the 50’s thing had to go.
I know Clifton was talking with me about materials and what would go well with the village mark. I think the only real section I did not hit on was creating a page on the actual village signage. Had I more time, that would have been an avenue to go into. We thought about the forestry signs, routing out the sign, or perhaps with the gray color, using slate as a background for the signage.
My original focus was to just make marks, but it turned out to be more than that. It turned out that I needed a system. I needed to have something to tie it all together. That’s where the secondary elements come into place. This is also where a fork in the roads starts.
1: Some people have no idea what I am doing. What? System? why? They seem to just think on the individuality of something, or something smaller scale. While that’s understandable, a system can be a hard sale for them.
2: Other people will think, ahh, I get it. A system. Following rules, patterns, a grid, or guidelines. Disneyland.(?). These people will then understand why some of the arbitrary features may be needed in order to get an understanding of what makes a system a system.
I think the worst parts of my project were a couple of the business logos. While I feel they are all better or different to a degree to their original counterparts, if I spent more time aligning them to a grid and really getting things positioned well, they could have been a bit stronger. Also I am not trying to do a full-on bottom-up re-brand, these logos are just on the surface. They would be a branching out point to the businesses and maybe they can be a conversation starter.
Another area I could have improved on was using the secondary elements in-situ. Meaning, finding a way to visually give the village a look that matches the look of the new business logos. Expanding what I got.
Lastly, I feel like my craft and my two books together just look, well. Sexy. I think this has been my hardest but most favorite project to date. Unlike the rest of my school projects, this one could really literally pay off down the road.
Hopefully over the summer I can continue the project, make more marks and perhaps talk with some of the owners. I wouldn’t ask or demand work or anything, but I could wet their appetite a bit and maybe someone will bite, you never know! :)
These three chapters were a great read, but to me, it was intended for those who have been in the business, who have a studio and want to find more work, For me what I liked about these chapters, is that he is thorough on the entirety of what a studio needs in order to be more successful. I liked how he stressed the importance of finding new work and trying to build a list of contacts that may want work in the future. It seems like building relationships is the best tool to use for securing future work from clients.
When he said designers are never happy with their portfolio, that couldn’t be more true. I am always unhappy with what I have and I always feel like my newer material easily replaces my older material. It also seems like if it’s purely invented design, it doesn’t seem to have the same level of authenticity that actual work would have.
Last week we talked about contracts and what should be considered in them. In CH 6, he mentioned if anything should be confidential. My Brother is in a senior capstone and is about to sign an NDA (non-disclosure agreement) in order to protect the code, secrets, and design of whatever he is doing. I think that these NDA’s are really smart as it helps establish secrecy, and keep the best interests of both parties so that nothing is made public. If the agreement is broken, then pending legal action could entail. (or you’d be sent to a dark room and never be seen again).
I think a nice clean website is a great thing to have for any studio or designer. Being able to have a website as a take-away in an email or if the interviewer could follow up on your work online could be a great push forward to securing a job. I think that it’s great that sophomores have sites up and running. Even if their projects aren’t the best as they could be down the road, it still gives them initiative, that they are driven and that they care about getting their foot in the door. In fact I wish that sophomores could almost have a 241 web class, just so they could build a portfolio site before the review. I think that could help with presentation, web skills, and be another realm to design in for the sophomore review.
#2: Pretty Much.
#5: Oh / awesome! (tie)
From chapter 2, she went into detail about the stuff designers consider that isn’t design. All the background and research and knowledge that goes into designing something for a client. One of the points Adrian writes is Time Management. I totally agree that setting up milestones for success is a great way to go rather than realizing one large goal on the horizon. With our 3rd project in this class, we are following schedules. These schedules are what we follow in order to stay on track and finish on time. Honestly, I don’t know why I’ve never done that in any other class I’ve taken. If I had a strict schedule to follow in 225, then my wine label project would have been much more flushed out and realized. It was good, but it could have been better—simply because if I had a schedule, then things would have gotten done quicker.
Another section she hit up on was writing skills. Editing and the delete key are your friends. I learned that revising and constantly changing your writing until it feels amazing should be stressed all the time. Finding better ways to write a sentence will help convey a smarter message.
Also, she discussed research and the importance of research. If you are following a logical approach to design, then you will come up with a dry, or sterile design that lacks imagination and creativity. However, it cannot be too visionary as that will lose structure when it comes to those who need that objectivity to ground in the design. Creating a balance between research and design is perhaps the biggest aspect of design we face.
For chapter 3, I liked how she talked about getting employed and trying to figure out what you want to do as a designer. I liked her approach and they way she talked about it. This was a more informal, personal chapter and because I am the target audience for that chapter, I thought it was very relevant to what I will be going through. I liked her pointers when she talked about getting an interview. Things to remember for when I take the Sr. Review or have any future interviews myself! The pros and cons to working in house vs. a studio was also an important read, as that may be something for me to consider here in a few months.
For this chapter, I thought it was a very important and crucial read and gave me much insight for when or if I consider going a freelance/personal studio route. I wasn’t fully aware of the trend of increasing freelance designers—meaning I didn’t know that years ago only pros did it. In this day and age with computers and technology and such, designers are able to do more, faster and better. I’ve talked to a few older designers who graduated in the 90’s never doing anything to the level students are doing today (students meaning myself :) ).
I found the information in this chapter doesn’t have to be applied to just a lone designer, but can be broadened to other realms, such as interactive website design teams, motion teams, photography studios, and independent game studios.
I want to take a little bit of time here in this last paragraph to talk about why I have been enjoying this book so much. Adrian writes this likes he’s done it before, that he’s failed before, that he’s succeeded. He isn’t writing it with a cold tone or disembodied, but as if he is down to earth and warm. I think what makes this book very appealing is that he’s been there and done that. He knows what it’s like to suck hard and to find moments of pure euphoria. That is what makes it such a great book to read.