Nicely put Carolyn, I particularly like “Prepare to be lost”. I am always blown away by the depth and complexity of an approach that a real power user of your tools can open up to you… even when you think you’ve heard it all!
Yes! That’s so nicely put Ian. I really agree that the easiest way for teams to understand ‘where we are’ is to try to frame it by ‘what deliverables we have’ and having two different artifacts that are both called mock/wire is very confusing.
I’ve noticed the same thing myself with the ‘product brief’. Often we’ll start off thinking we understand a…
I agree, in order to keep it descriptive you need to keep it high level, and then the story ends up very similar to what is used in a good design agency. I worked at agencies in the past and was thinking that they are probably clearer about how their process works, because when you have a client you need to be…
Exactly! maybe I should have said ‘read in most books or find on Google’.
(note that the ‘But’ in that paragraph is an error that got introduced somewhere in the editing process, it should really read:
“We came up with a best practice that wasn’t unlike what you read in most books or articles about design process. Our model…
Thanks Dorian, I agree that the concepts are not necessarily limited to the design process. I didn’t want to get too abstract in case things turned a bit Zen and the Art of Motorcycle Maintenance.
As to overcoming procrastination, I guess that’s a whole other essay which I will write as soon as I’ve finished shaving the yak.