I really do.
I've been reading until my eyes can't 'track' anymore. That takes a lot for me. And I read quickly - this is a lot of reading. I'm digging the reading Bill posted the most (the Robinson book was (is) entertaining, fascinating, etc. and I'd *honestly* consider reading it AGAIN)....but I'm enjoying the more factual and historical side of AR in the reading assigned by Margaret.
I'll go over a few notes I made from my Tim Brown book (Paul's assigned reading).
I could tell Brown was gonna be a good read when I popped open the cover and saw his "table of contents" format - the flow chart (or mind map as he calls it) design...of course, he was sure to add the more traditional ToC for his anul retentive, OCD, linear thinking readers (and that *might* be me....). I liked matching the two ToC's, comparing them. How much can one person blog on just the ToC to a book?
Our team needs to come up with a "BRIEF" (p22 ff) - I will post that opinion on my team's forum strand in Sakai. I think we have a pretty good general concept of what we'd like our design to accomplish....and I suppose that is essentially the content of a 'brief' : framework, benchmarks to be met, set objectives --- and we need to leave it *open* enough to allow for much change, creativity, PROCESS, etc.
We need to define our concept's desirability, viability and feasibility. And we need to keep in mind that we are NOT designers ... we are design thinkers. Maybe the title of the project, overall, should be changed from DESIGN to DESIGN THINKING (sorta like VirtCamp was changed to Cadre Camp...it simply better defines the challenge).
I'm trying to keep in mind the steps - I know we were told at camp to NOT take notes...but I'm assuming that taking notes at home is appropriate and NECESSARY (especially since we are working on so many things at once).
Process phases: inspiration, ideation, implementation.
I seem to keep coming back to one particular quote by Brown. On page 17 - I even wrote it in the front of my book to use as a sort of mantra while design thinking: "A nimble team of design thinkers will have been prototyping from day one and self-correcting along the way. [...] 'Fail early to succeed sooner.'"
Now, that being noted....I don't think our team was jumping the gun by getting the head start that we did. I think we are (were, still are?) right on target. I'm glad to be with a group who believes we can have a GREAT working and desirable design earlier than the expected date for the class.
I'm certain that anyone who knows me, can understand when I express how disagreeable I become when my free movement is impeded in some way. (I say this in jest - please, no one get offended) I'm thankful we have instructors guiding us (thanks Paul) and explaining that we're doing okay, but that we just need to back up and "stew" a little more on certain issues. It's good.
There's more - this book is packed with good stuff and I've made so many notes in the margins. This blog is long enough for now and I suppose I've made a few good points.
`a bientot ;-) ...
I've been reading until my eyes can't 'track' anymore. That takes a lot for me. And I read quickly - this is a lot of reading. I'm digging the reading Bill posted the most (the Robinson book was (is) entertaining, fascinating, etc. and I'd *honestly* consider reading it AGAIN)....but I'm enjoying the more factual and historical side of AR in the reading assigned by Margaret.
I'll go over a few notes I made from my Tim Brown book (Paul's assigned reading).
I could tell Brown was gonna be a good read when I popped open the cover and saw his "table of contents" format - the flow chart (or mind map as he calls it) design...of course, he was sure to add the more traditional ToC for his anul retentive, OCD, linear thinking readers (and that *might* be me....). I liked matching the two ToC's, comparing them. How much can one person blog on just the ToC to a book?
Our team needs to come up with a "BRIEF" (p22 ff) - I will post that opinion on my team's forum strand in Sakai. I think we have a pretty good general concept of what we'd like our design to accomplish....and I suppose that is essentially the content of a 'brief' : framework, benchmarks to be met, set objectives --- and we need to leave it *open* enough to allow for much change, creativity, PROCESS, etc.
We need to define our concept's desirability, viability and feasibility. And we need to keep in mind that we are NOT designers ... we are design thinkers. Maybe the title of the project, overall, should be changed from DESIGN to DESIGN THINKING (sorta like VirtCamp was changed to Cadre Camp...it simply better defines the challenge).
I'm trying to keep in mind the steps - I know we were told at camp to NOT take notes...but I'm assuming that taking notes at home is appropriate and NECESSARY (especially since we are working on so many things at once).
Process phases: inspiration, ideation, implementation.
I seem to keep coming back to one particular quote by Brown. On page 17 - I even wrote it in the front of my book to use as a sort of mantra while design thinking: "A nimble team of design thinkers will have been prototyping from day one and self-correcting along the way. [...] 'Fail early to succeed sooner.'"
Now, that being noted....I don't think our team was jumping the gun by getting the head start that we did. I think we are (were, still are?) right on target. I'm glad to be with a group who believes we can have a GREAT working and desirable design earlier than the expected date for the class.
I'm certain that anyone who knows me, can understand when I express how disagreeable I become when my free movement is impeded in some way. (I say this in jest - please, no one get offended) I'm thankful we have instructors guiding us (thanks Paul) and explaining that we're doing okay, but that we just need to back up and "stew" a little more on certain issues. It's good.
There's more - this book is packed with good stuff and I've made so many notes in the margins. This blog is long enough for now and I suppose I've made a few good points.
`a bientot ;-) ...
No comments:
Post a Comment