As I write this there’s a group of about 15 developers and designers standing near my desk in a heated but constructive argument about how to check the design is right before the code heads off to QA.
For over seven months I’ve been working with the good folks at Alexander Interactive on some ambitious work for MetLife.
In one of the darker corners of my mind I imagine a future where there are a set of laws and industry standards that dictate the acceptable usability of digital products and services, much like medical or engineering standards.
To catch you up, Motrin posted the below ad and people, particularly baby-carrying mothers, were so offended that the makers of Motrin pulled the ad.
Keep status meetings to .5 hour, but do them every week Establish a natural way for the team to share what everyone is doing — eating together, or tasks we all do together — while protecting personal time to think and work individually Set up a team mailing list and liberally copy everyone on everything; make it easy to filter Have one place for everyone to go to see what is the next action Folders to set up – 1.
I tend to think and think and think and think and, at the last minute, throw together slides that represent what I want to say.
The common way that financial people will judge the potential value of a project, or a design concept representing a potential future concept, is by building a model, usually a discounted cash flow model like Net Present Value (NPV).
This morning Studio 360 broadcast a piece on Christopher Alexander, A Pattern Language, and the influence of patterns in software development.
In my research on concept design processes, I’ve come across two ideas that jumped out as vital behavior that differentiates expert designers from novices.
I’m back from Overlap 08 which is becoming my reliable annual inspiration for all things professional.
I think a lot about how organizations and their products evolve quickly rather than remain static, and Google Labs are a prime example of that.