intent, outcome
do you care more about the intent of a project, or its outcome? should we think big, with the chance that it might blow up in our face, or do we rather think defensively and play it safe?
cruyff reminds me that he always preferred an attacking game: if you must lose, lose with grace, courage and honor. that’s still always better than the boring draw or the sneaky win.
Posted in thinking
April 22nd, 2006 at 6:49 am
it has to come from both, if the content sucks, the outcome will suck, in my opinion. know the capabilities of the project to avoid the blow up in the face.
April 23rd, 2006 at 8:46 am
i’ve been thinking about similar questions lately, as i start doing more projects of different types. some small, some big.
instead of focusing on intent or outcome per se, i am trying to remind myself that what counts are discernment, flexibility, and completion. evaluate on a regular basis the state of the project to see where i am and where i can go. change course as needed and desired (small/big, many/few, diff ideas to try, etc.). and no matter what, finish it in some way: maybe the idea was a dead end, but be sure to note the lessons and package what i have done so that it can be presented.
my work is with visuals and code, so your mileage may vary. plus often we don’t get to control the nature and process of our projects, of course.