RSSUsing the design process
In engineering, programming, web design and most other creative work, many people consciously use The Design Process. The PBS show Design Squad provides some great examples of how people can work with this system. There are also plenty of resources for working with students and other learners on their site.
The Android G1 is pretty much ready for the public to use, but it is still not done. One of the reasons I wanted the G1 was to follow the process of developing a product from initial release. The phone and its systems work ok, well enough for product release. In a few years, months or weeks, it will be much better. The fact that the phone and its systems are being developed in an open manner is one of the most powerful aspects of it for me.
The innovation of the Android system and G1 phone is not limited to just employees, but explicitly involves the community of users and developers to make it a better system. If we decide that it should be better, we can change it without waiting around for some research group at corporate to get the resources to identify, solve and implement a solution.
Consider the the original ipod. If you put that collectors' item in the hands of a recent ipod touch user, they would experience little other than frustration. With a low res black and white screen that had no touchscreen interface, small mechanical hard drive, short battery life, heavy clunky form factor, drm locked music formats, lots of tactile buttons and a wide collection of other currently unacceptable design traits, it was enough to transform the music industry and modern culture. Apple had to start somewhere.
Steps
Often, the Design Process is presented as a series of steps that you go through in developing an idea or product. They (usually) include: Identify a problem, Gather information, Propose solutions, Choose the best idea, Test the idea, Evaluate and Communicate. There are many different versions, no set list covers all the ways people interpret the Design Process. As you get more familiar with the use of the process, you tend to skip around inside it as your project needs dictate.
Looping
In the image above, and in many other descriptions of the Design Process, it is shown as a loop. In considering a project to work on, you find a problem to solve, gather information, try out an idea, test it and evaluate. If you solve the problem, move on to another problem or aspect of the project that needs attention. If you don't solve the problem, you have some more information about what won't work. That information gets incorporated in your next go-round.
Making it right
As you cycle through the Design Process, your product should be getting better as you go. The more you identify problems, pose solutions, test them and implement them, the device, program, product or project gets better. New problems arise the more you work the process. If you nail the biggest ones first, eventually you have something that works pretty well and are fine tuning after a while. It is possible to over do this fine tuning part, causing the project to never see the light of day. It is also possible to short circuit this phase. Ebay, second hand stores and the dump are full of examples of products which did not get enough exposure to this phase.
Delivering
When your product is sufficiently complete, and you have resolved the most pressing problems determined in the process, it is time to deliver. This does not mean that the project is done forever, instead, it means that it is ready for more testing in a real world environment. As you (and your team, as may be the case) see the product in the world, you will hopefully be looking at it for examples of where it can be changed and improved. As you find aspects of the project that need refinement, you make a plan for revision and implement it. Hopefully these flaws you find at this point are not tragic enough to seriously stall or ruin the project.
How do you use the Design Process? Have you introduced it as a development technique when working with creative people? Have you taught it to kids? What are your experiences with developing ideas partially or fully by looping through these steps?
Post your ideas, experiences and observations into the comments!
Posted by Chris Connors |
Nov 18, 2008 07:00 AM
How it's made |
Permalink
| Comments (1)
| Email This |
| Digg this!
Recent Entries
- Welcome to Alternative CES -- "alt.CES" - BUGLab modules
- Contacts case for small parts
- Recycling for fun
- Crossword puzzle apartment building
- Spiffy face lift for an old toy...
- Benheck's PC Mod Pick of the Day - WMD PC
- Giant water tower cozy
- The Naked Scientists explain the science of snot
- Arduino shirt!
- Stealth project mixes sound creation with 3D lighting effects
Comments
Oldest comments listed first.
| Posted by: Rui on January 7, 2009 at 11:39 AM |
I think the most interesting aspect and the most interesting rule of thumb to get out of it is that the quality and overall time to do your project will be largely dictated by what parts of it you will tend to focus first.
The Design phase is the singular most important one, since its isolated and not on a loop, it will be much more viable as a workbench than the real thing.
The old saying that design costs nothing or at least little is damn true, and in my view, we should have this big loop INSIDE the Design phase since it, by itself IS a Design Phase too!
Design is King, it really is. What we must do is 1. Make Design a true process and 2. Conceptualize a way for a Design Process to blend in with the Implementation Process as seamless as it can...
We all know the madness of doing UML work and then just throwing it out the door, because its work is complete, and Design Docs getting out of sync with the implementation.
Food for thought.
Leave a comment
Subscribe to MAKE Magazine!
Subscribe today, save 42% and get web access to MAKE free. MAKE Digital Edition is available only to subscribers.
$34.95 / 1 year
(4 Quarterly Issues)
The online premiere of Make: television is January 3rd 2009, visit makezine.tv or iTunes to see the entire first episode! The broadcast premiere will follow shortly after depending on when your local Public Television station airs it.
Happy New Year from MAKE!
MAKE's 2009 New Year's message.What we're making in 2009.
MAKE's RSS feed is here.
Add MAKE to iGoogle - GoogleGoogle.
How to add MAKE to your RSS reader - Real simple.
Add MAKE on Twitter.
MAKE's fan page on Facebook.
Add MAKE on FriendFeed
Why advertise on MAKE?
Read what folks are saying about us!
Click here to advertise on MAKE!
Makezine authors!
Senior Editor
Tel: 707-827-7311
Twitter / AIM
Gareth Branwyn
Jonah Brucker-Cohen
Chris Connors
Collin Cunningham
Marc de Vinck
Mike Dixon
Peter Horvath(intern)
Kip Kay
Luke Iseman
John Park
Patti Schiendelman
Becky Stern
Jason Striegel
Current Podcast
Maker Profile - Bicycle Rodeo
Introducing Cyclecide, an inventive band of Bay Area performance artists who make creations out of materials from the junkyard. These Makers create everything from amusement park rides to outrageous bicycle contraptions to found-object sculpture. Plus, we take a historical...
More...
