More design ideas keep coming for where The Goo should go. I've decided to extend it to non-programming artefacts as well - emails, directions, internet searches (i.e., trails), events, contacts etc. Ideally I want to scaffold a whole project by cascading artefact creation from pain -> problem -> project -> people.
I've also decided to reverse the cognitive polarity of my email inbox. Do you get 'buffeted' by your inbox? Incoming emails are a huge source of distraction and information overload. I find myself losing the plot under an avalanche of emails. But some of these emails are important for "projects" and involve the "people" working or helping on them. The Goo should maintain a "Care-o-Meter" where incoming emails are filtered depending on what you care about - what's giving you the most pain lately? Rather than your email blurring the focus of your work, your work should act as a lens on your email - filtering and focusing on the important stuff when you need it.
Sticking together the ideas behind "The Goo"
0 comments:
Post a Comment