March 02, 2004 | View Comments (20) | Category: Design
Summary: The hardest part is always getting started.
For me the hardest part of any project, be it programming or web design, is actually getting started. I always find myself in a duel between the blank screen and myself. Where do I start? Will it work? Am I doing the right thing? These are the kind of questions that initially hold me back. Sometimes it might take days before anything actually gets done. I can have all my sketches and my plans and my diagrams, but still I see the blank screen. Maybe I just need to surf the web for a while. Arghhh! It's 5pm already?! Didn't get anything done today. Surely tomorrow I will be well on my way.
Sometimes I think the screen will by itself produce some artistry that I may be able to call my work, but that never seems to happen. In my head I have the greatest ideas of what I want to do with the project, but in my head is the only place where they seem perfect. I wish I could run through projects like everyone else seems like they do on the web. You read one blog where someone is implementing a CSS designed site and the next day another. Then someone else is reinventing a new syndication format and it makes me wonder how do they even get started. I am getting better, but if you only knew how many ideas I have in my head, you would be surprised the percentage of things that actually get implemented.
When I do something I want it to be perfect. I like to plan things out so that I waste less time actually doing the work and messing up. That is what they taught me in school.
Design is the most important stage in the life cycle process.
I took their word for it. I design and design and design some more. I always think I am ready, but nothing ever happens. There is another part I might be missing or some concept I didn't sketch out well enough. Nothing is ever just right to get started.
Then I remember that sometimes you just gotta go. It doesn't matter how you start necessarily, but it's the fact that you just got started. It's okay if the beginning isn't what you had in mind. At least you have something to work with and you have momentum going. That is always key. Build your momentum. Also remember this:
You can't write perfect software
So just get started. Don't be afraid of what is going to happen. Whether you are coding or designing, the end will result will be completely different then what you started with (usually). For programmers, both the eXtreme Programming methodology and the Fusebox methodology (JC can tell you more about this stuff) provide ways to get started. If you are a designer start drawing because you can only surf for inspiration for so long.
Trackback URL: http://9rules.com/cgi-bin/mt/mt-tb.cgi/166
I'm reading this now because I should be throwing pixels onto a canvas.
[sigh]
pid (http://www.pidster.com)
that is so me...
I should be working in PS,alas..im surfing the web or sketching out ideas , but not getting anywhere.
I think it's important just to get started on your project, otherwise you'll be left pondering on thoughts and never get anyhing done.
Steven
It's true, you just have to start. In the first hour of real spadework ideas that won't work that took days thinking about get thrown out. And other ideas that never occured to you get happened upon by "accident" and work well. One idea leads to another when actually doing something. The conception grows and may end up nothing like your original idea. This to me is design. Those who make themselves sound more methodical from step one may be, or they may be making it sound that way after the fact.
On the other hand, there is such a thing as starting at the right time. We should not beat ourselves up so much for not starting and see it as an intuitive awareness that the moment is not yet right. Or, so I tell myself. But it is possible to develop a natural sense of rhythm that includes inactivity. All things move through openings and closings (the philosophy of the Daodejing).
When writing books, it's said to be 1% inspiration and 99% perspiration. I know what they mean, but also I can't fail to notice that 99% of books are rubbish. Which still leaves plenty to read of course.
Whatever your process is, you just have to go with it. I used to be very hard on myself for going through cycles of inactivity. Now I accept it as part of my process, having learnt that "something" always draws me back, that inactivity is not an end but a space in which things ferment.
Joel (http://biroco.com/)
"Design is the most important stage in the life cycle process."
In terms of the SDLC, a successful design only comes there is an identified plan and thorough needs analysis performed.
In terms of web / graphic design, I believe the same holds true. You (as the analyst / architect / programmer / designer) have to truly understand the purpose and the expectations before any design is going to be successful.
Relationships are also key. I have had numerous projects just "work" because the client and I had kind of a "kharma" with each other - our personalities just fit well together. With these type dream scenarios, the page rarely stays blank for long.
Other clients, well...you have to work past the personality clash and sometimes that takes a real, concerted effort.
It's just like any relationship. Sometimes both parties just see eye-to-eye from the start, and everything goes relatively easy. Others, come from two different places in life, and it's a struggle to come to the same conclusion.
Self-based projects are another thing all together.
Mark Fusco (http://www.lightpierce.com/ltshdw)
I run into this all the time. I also run into situations where I should be working on stuff for a job, and instead I find myself working on personal projects or trying to make some money on the side. Its very easy to get distracted and off the beaten path
jag5311
I know what you mean. The blank screen is so damn intimidating that some days it's hard to even consider starting anything. The sad part is that once I actually take that first step, I'm generally sucked in and can't *stop* designing for hours ... and I wonder why that first step is so hard.
Ste Grainer (http://www.wanderlost.org)
Sometimes I think I try to overplan and I just sit there sketching for hours thinking that I am saving myself some time in the long run, but I have found out that most of the time my finished product never looks like the sketches or at least heavily modified.
Scrivs (http://www.9rules.com/whitespace/)
I'm not sure I'm fully understanding the intent of this post (maybe it's early morning syndrome). You mention the difficultly to start work but I'm not sure if you are saying this because it's a personal thing (i.e. you just don't feel like starting yet) or because you feel as though you don't have enough information to get you going in a direction. I'm assuming it is the latter you are talking about. If so, then to me it is all about creating boundaries. Some people may find this funny because a lot of times they are trying to break out of them but in this case I think it actually helps. Why? Because if you have no boundaries or guides to work with then everything is open to you and it seems like there are a million directions to go. Hopefully, the more information you get from the client (of course you have to come up with the questions), the more information you will have in your creative brief, and the more boundaries you have to guide you. These boundaries then create a "frame" from which you can create your work within.
Nollind Whachell
Nollind, I think it's more on the eternal line of "an artist cannot begin with a blank canvas" -- several artists (of the school that didn't begin with countless sketches and studies, anyway) would do things like draw lines down the canvas or shake their brushes on it to break that intimidating blank expanse up enough that they could begin.
Writers sometims need a nudge, either starting with something they (or someone else) had previously written, or using some kind of technique like picking a dozen random words from a dictionary to start with.
For web jockeys, though, I haven't a clue how to break through. I've been debating building some sort of tool to help, similar to the improvisational poetry tools I built to help my writer friends, but it's significantly more complex for a website.
BTW, Paul, you linked to FLiP (Fusebox Lifecycle Process) which is what you wanted, but it's not the fusebox methodology. Fusebox methodology is charactarized by developing small reusable pieces (fuses) and building your application by plugging them into a central set of controlling files (the fusebox), or in larger applications, by setting the fuses into sub-application (a circuit) that can be reused or run on its own as a seperate fusebox application. It facilitates reusability, unit testing, and distributed development.
FLiP is a process that isn't fusebox dependent but can be used for any development where you have clients/customers/users. It can be used with eXtreme Programming -- once you get past the prototype stage and begin actually building fuses.
JC (http://thelionsweb.com/weblog)
Ahh, my apologies then JC. I was just taking the easy way out and using the Forever Geek link. Shows me.
Scrivs (http://www.9rules.com/whitespace/)
Ah, you had the right link, just the wrong name for it. :-)
it's a little vague if you're not familiar with it
JC (http://thelionsweb.com/weblog)
I find myself at the beginning of projects agonizing over the design (usually programmatic design). Usually there will be two or three different alternatives that I have fleshed out in my mind somewhat, but they each have tradeoffs and it's so hard to decide, because what if I choose the wrong one? What I really should do is prototype something small for all the alternatives, because you don't really get a good feel for something until you actually start doing it. But the important thing to remember is to throw the prototypes away and start from scratch for the real thing, otherwise you risk creating a very unscaleable monstrosity. Easier said than done, I know. And maybe that only applies to software design, not graphic design.
Anyway, I know what you mean. I think procrastination goes hand in hand with perfectionism.
Jennifer Grucza (http://jennifergrucza.com)
You've got to go through hell before you get to heaven.
I was just talking about this with Jay-Z the other day, and we both agree that sometimes you have to go through and try all the bullshit before you get to the real gold. That's the part of the creative "work" that most people do not understand.
Even if you don't use your sketches, or you spend hours in Photoshop with nothing to show, at least you have cleared the air by going through all the stuff you know you are *not* going to use.
Shit, if that fails...roll up another fatty, put on a new CD(preferably one by Jay-Z or myself, Steve Miller) and set it off. Pimpin ain't easy...but its a whole lotta fun.
Steve Miller (http://www.submunition.com)
You know, I think that I'm almost the opposite. When I start working on a project, I jump right in and start coding. I do my best to design the code and UI on a logical way, but I definitely make mistakes. When this happens, I just rework the UI or code and move on.
I think that I work this way because of the fact that my favorite part of the process is coding. Since I like to code, I'm more than willing to just jump right in and get to the coding. This probably isn't the best thing for me to do, but it's how I work.
milbertus (http://www.milbertus.com)
Aaron Swartz had a great piece on procrastination, referencing my old professor John Perry on structured procrastination. For him as well as I, doing "time-urgent" things like checking email seems more important than doing "important" things like studying or working. It's the opposite of Stephen Covey's "First Things First"
Bob (http://www.ryskamp.org/)
I'm sorry this is off-topic but... Steve, are you talking about Jay-Z (i.e. Crazy in Love and Black Album Jay-Z) or just some random Jay-Z?
I'm sorry, it just seems to strange to mention in a web design log! Heh.
Lea (http://xox.lealea.net/)
hmm...when starting off a project, I try and gather as much information about it as possible. The design, css, usability, SE optimization, content, target audience, features and the random suggestions my co-workers throw at me.
Then I open up a blank browser window. I think. And I take deep breaths.
This continues till the deadline is hours away and my creative juices start flowing. Somehow, I manage to complete it on time.
Of course, this dosn't apply to personal work. My own websites haven't moved beyond the default parking page for the last 3 years now :)
jinesh (http://www.jinesh.org/)
Haha, that John Perry article on procrastination is great - thanks Bob.
Jennifer Grucza (http://jennifergrucza.com)
The best method for handling visual design for me is to give myself 30 minutes, open photoshop, or whatever tool, go to town and then stop right at 30 minutes. Repeat however many times as necessary.
Then pick your favorites from the results, and start tweaking them. I also find it's good to take breaks between each of the 30 minute sessions or else you end up without much variety.
After forcing myself through this process, I'm usually in the mindset to work and I've got some great starting off points.
Garrett Dimon (http://www.brightcorner.com)
Keep track of comments to all entries with the Comments Feed
©2003-06 9rules, Inc. | Thoughts Feed | Notes Feed
Amazon Stores: Powertools | Jewelry | Books | Health | Landscaping | Kitchen | Movies
#1
At a certain point, surfing can become like watching TV, where you just shut off your brain completely and become a bit of a zombie. It's especially difficult to get started if you telecommute or if you are your own boss.
If you're feeling especially listless about starting on a certain project then you can always pick up a good motivational book or take a nice long walk with your laptop.
Jack (http://boxofjack.com/)