The 1 Week Left Plan

this workflow-esque diagram explains how the solution will work in the real world, from kickoff to mass adoption


The scenario uses the personas that were developed and aims to answer these questions using scenes and screens: How will people find out about the website? How will they use the booklet? What will the system do for people and how will they interact with it? Where will it all live? What does the system do for store and community dynamics?

More website screens

Website Development

Here are some screenshots of the website aesthetics I've been working on the last few days:

Personas

Personas are representations of the end user, their wants, needs, desires and goals. I created two personas, Cheryl and Peter to represent the different demographic foci of my project.

Process Sketches

Site Map

First draft of the site map and I'm trying something new. Solid lines represent direct clicks, dotted lines represent where the website takes the user once the action on the previous page is complete.
The site map outlines the pages of the site and how the navigation levels interact. Starting on the home page, one click on the site will take the user to one of the five main content pages. Additional content on those pages live in the third navigation level, another click away. For example, if a registered user wants to post a new topic on the forum, he will click “forum” then “post new”. Once the post is written he is directed to the topic’s page, then can return to the Forum main page.

Design Phase: Ideation & Frustration

Identifying the solution of the bike theft problem is becoming a convoluted, painstaking, time-intensive challenge.
I've uploaded one of my design phase presentations for anyone to check out. It contains some of my sketches at the end, as well as the wireframes I'm working on for the website.

I think the best approach is to create a system that encompasses all aspects of education, awareness, community involvement and awesome hotness, but not everyone agrees with me. I presented the initial design work to the class and got some interesting responses, including, a) "Your approach is definitely one I wouldn't have taken," b) "Why do you think people are asking questions now? It's because they don't get it," and, c) "How how how is it going to be funded? What's the incentive? Who is going to be interested in this?"

I think the last questions (c) are the most valid ones and have led me to realize I still have some gaps to fill in, markets to pinpoint, and traditional cost analysis to do.

So just to clarify, comment a) was a reaction to my system approach of identifying touchpoints and tackling this large problem from a holistic perspective instead of through a direct, single-function product that "solves" bike theft. We're trying to educate and prevent bike theft here too you know. Question b) was probably out of pure frustration after my ideation presentation yesterday. People in my class have an infuriating tendency to question the most obscure, inane, irrelevant aspects of my work, leading me to believe they only pay attention when it benefits their personal agendas. Go figure, I know I do that some times, I just try to keep my mouth shut. But more importantly, is it an appropriate teaching tactic to corner a student and attack the work as if she's really the only one that cares about it? I understand it probably isn't as interesting to everybody as it is to me, but I appreciate some freaking guidance from my freaking professor. Constructive criticism and critique is what I prepare these presentations for, is it not? That's why I go to class, no? That's why we pay the $$$, and for what? ROR Moving on, c) is the real work I have to do to substantiate and validate what's being designed this week. Great.

First draft of the booklet, side one

First iteration of the wireframe

One of the first sketches of the wireframes for the website/forum/community/database

Design Opportunities

The sketch:


The presentation:
I identified 4 domains in which an appropriate solution can exist. The catch is that all the domains work interdependently with each other and any effective solution must incorporate all aspects of the domains. Basically that means a very big, very service design solution that includes everything I love times 1000.
Physical: an object or product that is made for specific users, lives in a specific location and is intended to be usable, accessible, useful and valuable to the user.
Digital: part of the solution incorporates an internet aspect in the form of a user-created-content forum, social network, database or all three. The digital aspect will work seamlessly with the other three domains to create a well-rounded tool and experience.
Education: awareness is created through accessible information. Giving users the tools and info needed to improve their lives is the best way to enable cultural or behavioral change. The education aspect will empower the community from the bottom-up.
Community: the support of neighborhoods, city government, local businesses and individuals will tie the domains together and create a successful solution that lives physically and digitally to promote the awareness of its people. The solutions exist within the community and for the community.

One idea/component for the solution is a physical booklet, a pocket-sized "manual" that gives the tools needed to promote strong biking practices in terms of registering a bike, how to lock up, what to do if it's stolen, et cetera.
The second page outline the contents of the manual and are a starting point for the final product. The manual will live in bike shops and community centers and serve as a physical aspect in the multiple-domain approach to solving bike theft in Savannah. Hell yes.

There's more on these sketches on my flickr. enjoy!

Research Presentation

I was the first to give my research presentation to my peers this week. I went over the time limit but people were interested and since I went first no one seemed concerned.  I presented my research through quotes and key findings in an effort to make it as contextual and real as possible.  Closing with my design opportunities, I discussed the directions I want to go for the solution.  Check out the whole presentation HERE.

Saturday Night, 12 midnight

"I should lock it up you know ... but I don't have a lock, I'm homeless and looking for work you know, looking for food."

Utilizing RFID as a solution

Another few ideas came today after speaking with a bike mechanic and a guy who recovered his bike from the man that stole it by tricking him into "selling" it back to him. More details on flickr.


Because factory companies don't give components serial numbers, enabling cyclists to put unique IDs on their own components could help the recovery of stolen bike parts! In a user-created-content forum/database key data can be entered to catalogue a user's parts (and a batch of parts). A serial number will then be assigned to the component and the user can a) engrave the information on the part, or b) the system can send the user a set of serial ID stickers (with RFID implants?) to stick in discrete areas on the component.

A tracking system for bikes using RFID stickers is outlined in this sketch/scenario:

Research and Systems

I ran around town today and spoke to quite a few people about bike theft in Savannah. The police didn't have a lot of "readily available" information and made me run around a lot, calling people at various departments, none of which were there cause it was Friday...but plenty of leads to pursue come Monday... the "Property Room" and it's detectives and sergeants as well as the assigned bike investigators.

I contacted SCAD security and spoke to a few people that were good resources and also pointed me in strong directions. SCAD's procedure for stolen bikes goes like this:
I spent a good two hours at the new bike shop in town first gathering information, then because I got a flat tire right after I left and I had to go back and buy a patch kit.
The guys at the store relayed lots of opinions about the state of bicycle theft and what can be done about it. On registering bikes with the police or national registry one told me "It's all fruitless," because most bikes are chopped, resold, auctioned or shipped out of the area. Most agreed that in Savannah however, you can usually recover a bike because it was taken on a whim by an impoverished person and is probably being ridden around by them or someone similar.
"The worst thing you can do is lock up overnight." This is a common consensus among the shop workers who also agree that lack of proper locking and even more so, education on how to lock a bike, are the main causes of bike theft in Savannah.
Although the downtown shop takes in donated and refurbished bikes they claim to have not been offered a stolen bike since their opening a month ago. In the past they have called the police as soon as they sense the bike being offered was stolen, an event happened to everyone in the shop.

One of the results of all this was an idea for a system that may address some of these issues. I got pretty excited about it's potential but I realize it's only one idea and it's pretty complicated. RFIDs are not the answer, but this is a step in the direction of system design that could change (or positively affect) how people lock up and think about bikes.


More details on this idea at flicker.

Unfinished thought, part 1

The difference between industrial and interaction design has never been more simultaneously apparent and blurry than at the start of this project.
I came into this wanting to do “a strict industrial design project” – something that I really haven’t done since Studio I – just user research, ideation & sketching, creating a product, then making a model. I consider this different than an “interaction design project” in which there would be loads of contextual and quantitative research, a concentration on synthesis, and a system or idea created to address the opportunities found in the research.

A few things happened. Tom said I needed to back up from my proposal to do more research and let that be the driver the project. I said I wanted to come into the class with a solid direction so I could start developing a product right away in order to have as much time as possible to create a fully functional prototype.

So now I’m torn. I have backed up and I am doing more research, both secondary (blogs, forums, newspapers, crime statistics, video documentaries) and primary in which I’ll go speak to some area experts (police, security, bike shops, thieves and users). I love research. I would just do this for most of the quarter, which is what I’m afraid of. If I don’t get right into development there won’t be any time for prototyping.

But this research is revealing so many new opportunities I honestly don’t think another product is going to be the answer. Like most of the other projects I feel like the product is just another band-aid to slow the festering of a larger problem.

Serveral accounts state that bike theft is part of a vicious cycle that enables junkies and drug rings, and is therefore a crime of opportunity and necessity for a fix. In Portland,

“Bikes are one of the four commodities of the street — cash, drugs, sex, and bikes…You can virtually exchange one for another."

This leads one to believe that something more important than another bike lock must be created to solve this problem. To break a cycle that affects all major cities in the US and is too small to be addressed by police or government will require a systematic approach to service, community and culture.

I a way this is exactly what I was trying to avoid. It’s good, it’s familiar and it’s exciting. The think I consider myself weakest at is my ability to synthesize research into viable design opportunities that can be translated into tangible solutions. So now I’m one week in and I don’t know what I’ll be making but I know it will be good.

Remedy anyone?

First Step

Check out my design proposal presentation from the first day of class!

And I wrote a quick design brief that explains the project in greater detail. In the event too much effort is required to read the actual documents, here is the opportunity statement identified for the project:

Opportunity exists for the development of a contextual bicycle tool that prevents wheel theft and visually communicates security and status through its detailed design and application.
Exploring the need for bike components is a dynamic application of industrial and service design techniques through the modeling, testing, implementation and interaction of the product with it’s end users