Archive for the 'Uncategorized' Category
Paul Stamatiou’s Logo Design Project Tuesday, June 5th, 2007 by Mike
I’ve just completed a logo design project with tech guru, and fellow 9rules blogger, Paul Stamatiou.
Paul writes commentary and reviews on varied topics with a focus on technology, and has very high visibility on the web. So as you can imagine, I found it a fun challenge to work with Paul.
Below are links to the set of mockups and final art at Paul’s Flickr account:
Paul Stamatiou Logo Design Set
Paul Stamatiou Final Logo Design Spec Sheet
It was fun, and different working with Paul, since he put all of the sketches, black and white and color mockups I did for him on Flickr — as they were delivered — and opened them up for public comments. I’ve not had that kind of in-progress, public critique done with my work before. Paul and the commenters liked the work and through the normal process, Paul selected a final winner.
One advantage to having your client post in-progress to final work posted on Flickr is, prospective clients can see the process, how it works and looks — which hopefully sends them to me and MakaluMedia for their identity design.
All in all, it was a blast working with Paul. I think we’ve found a clean, crisp and memorable mark for Paul to use as personal branding, on the blog and for other things, which makes me very happy.
Thanks for choosing to work with me Paul! :-)
DEVONthink Usage Tips Saturday, November 5th, 2005 by Matt
I was recently asked by someone on a mailing list to document some usage tips related to the DEVONthink information manager. I’ve been looking for time to write a complete article, and haven’t found any, so what I’ve decided to do is to publish bit by bit, starting with this post.
The Problem
My company, MakaluMedia GmbH, is a software engineering and services company, and at any point in time we’ve got several commercial and internal projects active. During the course of any given day, I will receive a multitude of emails, meetings and phone calls (some of which are important and some of which are not).
The Solution
To help manage this information, I have created the following structure in DEVONthink:
DailyNotes/
MakaluMedia/
Projects/
Project A/
History/
Project B/
History/
Of particular importance are the root-level DailyNotes/ folder and the project-level History/ folder.At all times, I keep a separate window of the DailyNotes/ open, and set to the "Outline" view. This splits the window into two vertically stacked sections: 1) the top section listing the contents of the folder (DailyNotes), and 2) the bottom section listing the contents of any selected item in the above list.
Whenever anything noteworthy happens during the day, I create a new text or RTF document in DailyNotes, and give the document a name that completely describes the event. I also use a Spell Catcher shortcut to enter the date and time in the file title, in the format YYYY-MM-DD-HH-MM:
DailyNotes/ 2003-11-06-15-07 MLK Requested New FTP Account to be Established
Sometimes the document title alone serves as a sufficient representation of the event. In case more information is needed, I record that information in the document content. In the above example, I could copy/paste the contents of the requesting email.
Replicates
Once this is done, I use DEVON’s “replicate” function to create a replicate of the entry. A replicate is like a duplicate, except that the replicate is the same as the original — so if you edit the original, the replicate is also changed.
Once the replicate is created, I control-click on it, and move it in the menu hierarchy to the MLK project’s History folder:
Projects/
MLK/
History/
2003-11-06-15-07 MLK Requested New FTP Account to be Established
In this way, my DailyNotes folder has a running history of everything that happens, while my Project History folders have a running history of the project-related happenings.
Record Everything
I use the DailyNotes area for everything, not just project-related information. I also record software purchases there, modifications to my computer, etc.
DailyNotes/ 2003-11-07-09-36 Installed Apple Security Update on TiBook 2003-11-06-15-13 Purchased Freeway Pro for the Mac 2003-11-06-15-07 MLK Requested New FTP Account to be Established
Actions/ToDos
Taking this all one step further, if an event requires that I take some action, then I will embed the word ACTION in the document title:
DailyNotes/ 2003-11-07-09-36 ARTS Request to Clarify Specifications [ACTION]
At the end of the day, or whenever convenient, I will scan the recorded events in DailyNotes, and will create ToDos in (one of) my other critical productivity applications, Life Balance.
Clean-Up
I normally keep about a month’s worth of entries in DailyNotes/. At the end of the month, I’ll create a new folder within DailyNotes/, e.g. “2003-06″, and drag all of that month’s entries into that folder, thereby shortening the DailyNotes visible list, while retaining the entries.
Conclusion
I’ve found that consistently documenting events in this manner helps in many ways. I quickly review the past week, getting an idea of how “under-control” things are. If a particular project has a lot of entries, and needs some intervention, it becomes apparent. When a customer calls, I’ll switch to the history of their project, and immediately have a complete project overview at my fingertips, with all details available. The information is all available for easy drag-and-drop into an email (using Mailsmith, of course. :-) or other programs.
And having all this data available to DEVONthink’s amazing internal search engine is icing on the cake.
Ok, that’s all for now. More tips on the way in future posts. Hope this was helpful.
Getting Things Done Wednesday, September 22nd, 2004 by Matt
The recent posts of Merlin Mann have re-kindled a long-time interest I have in the area of personal productivity. According to Peter Drucker, one of the defining aspects of our generation is the fact that, as a society of information workers, many of us are responsible for defining both what we do, and how we get it done. Complicating matters, many of us work in environments (i.e. in front of internet-connected desktop computers) that provide us with a continual barrage of inputs (email, chats, browsing, RSS feeds, phone calls, etc.). Defining what we should do, how it should be done, and then getting (the right) things done are some of the biggest challenges we face.
In this article, I hope to describe the system I’ve put in place for myself. I’m quite satisfied with it, although it remains under continual review. The system is based on a guiding philosophy and supported with an implemented process.
Philosophy
I agree with Steven Covey’s view that all the things we do can be mapped on four quadrants in two dimensions, with a vertical axis of Importance, and a horizontal axis of Urgency. Most of us seem to spend too much time in the “Urgent/Not-Important” quadrant and far too little time in the “Important/Not-Urgent” area. Urgent/Not-Important activities might include responding to a request to chat with somebody, or attending to emails, while Important/Not-Urgent activities might include exercise or review of a company’s quality system.
So, when working, I try to focus on avoiding losing too much time in Urgent/Not-Important things, and to spend more time with the Important/Not-Urgent ones.
Process
I follow a process that is based on Getting Things Done (GTD). In a nutshell, the idea is to:
- Write down everything that enters your life or mind that may require some action, or later reference. Getting things out of one’s head reduces anxiety, and the possibility of things being forgotten.
- Process this list regularly, filing reference information where it can be easily located, and creating action items or projects for things you have to do.
- Maintain a list of action items and projects (todos), and let those guide your work.
- Review ongoing projects and todos regularly with the objective of possibly adjusting priorities (i.e. keeping on track with our philosophy)
My driving principle in the definition of the process itself, is that it should be as simple as possible, so we don’t fall into the trap of spending a disproportionate amount of time managing the process, planning and organizing, and as a result, actually accomplish very little.
My process is implemented primarily with desktop computer tools, for the Mac OS X platform:
I use Hog Bay Notebook as my information entry point and repository. (It’s where I’m writing this article.) HBNB is basically an outliner, with exceptional search capabilities, and has user interface features that supports efficient data entry (e.g. pasting things from the Dock menu, an OS X Service menu item, contextual “Move to…” and “Copy to…” commands on entries, etc.)
I use Life Balance, as a todo list and project management system. Life Balance allows tasks to be decomposed into sub-tasks (steps), and allows for any given task the assignment of “importance”, possibly scheduling information (i.e. a due date) and an associated “place”. At any moment, LB will show a list of todos based on an advanced algorithm that takes into account due date, importance and place (context). More details about LB are discussed later in this article, but let me emphasize that while Life Balance has a learning curve, it is truly one of the most powerful and valuable applications I’ve ever come across. As LB also syncs with a version running on the Palm, I also use it as my portable “Inbox” when away from the desk.
I use Apple Mail, as email is a primary source of inputs these days.
ImOnTime. This is a background program that does one thing—reminders. I can’t imagine a better implementation of the perfect reminder program. It’s very easy to create new reminders, there are reminder “templates”, useful snooze features, etc.
Here’s how I have each of these setup:
Hog Bay Notebook.
I have defined the following outline nodes in HBNB (all mapped to quick-access “Bookmarks”):
Inbox. This is where I record everything notable that happens. If, for example, I see a reference to a new book I’d like to read, I create an entry here. If I get a phone call, I’ll jot down a summary here. Etc.
Projects. This is where I store reference information (clippings, notes, etc.) about projects I’m currently working on.
Someday/maybe. This is where I record ideas for things I hope to do at some point in the future, but for which I don’t want to create any actions now.
Goals. This is where I document goals I have related to my professional context, and related to various time spans.
- Areas of responsibility
- 1 to 2 years
- 3 to 5 years
- Life
Resources. Any information I may wish to refer to at some point in the future goes here. I may copy and paste in a nice website article about some technology I’m interested it, or I may document how I solved a problem with my computer, or the contents of a phone conversation. HBNB makes it very easy to later locate the information through its search facilities.
Life Balance
I have defined the following “Places” in Life Balance:
- Work (+)
- Work (-)
- Personal (+)
- Personal (-)
- @Waiting For…
- @+
The (+) places are more important contexts, and the (-) places are less important (recall the philosophy of important and non-important things.) The @+ place aggregates all the important places together. In the LB todo listing, if I switch to the “Work (+)” place, I am shown all the todos related to work, that I consider important. The order of the listing will be arranged according to the “importance” slider setting I’ve specified for each tasks. If I switch to the Personal (+) place, my todo lists updates to show only personal-context items, that I consider “more important”.
I have defined the following top-level todo outline in Life Balance:
Inbox. Same concept as my inbox in HBNB.
MakaluMedia
- More Important. Things I’m working on, or need to do, that I consider more important, are found here, and assigned the place “Work (+)”.
- Less Important. Things I’m working on, or need to do, that I consider less important, are found here, and assigned the place “Work (-)”.
- Routine. Things I regularly need to do, are found here (e.g. create a monthly off-site data files backup.). They may be assigned to either “Work (+)” or “Work (-)” place.
Personal
- GTD Process. I have defined “routine” (recurring) todos here (and assigned to the Personal (+) place), that guide my daily and weekly GTD process, e.g.:
- Daily
- GTD-D: Clean out Email Inbox.
- GTD-D: Review Email Waiting For…
- GTD-D: Clean out Hog Bay Inbox..
- GTD-D: Clean out Life Balance Inbox…
- GTD-D: Review Life Balance Waiting for…
- GTD-D: Check iCal calendar.
- GTD-D: Review Life Balance todo list, and get to work.
- Weekly
- Review HBNB Projects
- Review HBNB Someday/maybe
- Daily
- More Important
- Less Important
- Routine
- GTD Process. I have defined “routine” (recurring) todos here (and assigned to the Personal (+) place), that guide my daily and weekly GTD process, e.g.:
In my email program, I have (in addition to others) the following folders:
- @Inbox. It’s important to keep an empty in-box in one’s email program. Any incoming email during the day that I can’t address immediately, gets filed here for processing, at latest, one day later.
- @Waiting for… For any emails I send to people requesting something, I copy myself, and file the copy here as a reminder that I’m waiting on somebody for something.
How does this all work?
Following is a (simplified) example of a typical day:
First thing in the morning, I sit down at the computer, switch into Life Balance, and switch to the “Personal (+)” place. I’m shown my daily list of GTD related “todos”. The first one is “Clean out Email Inbox”, I check this off as done (it will appear again tomorrow), and I switch into my Email program.
I switch into my @Inbox folder, and process every mail here. Each mail may generate a response, may generate a todo or a project in Life Balance, or may get filed. When I’m done, there are no messages left in this box.
Life Balance tells me I now need to process my “@Waiting For…” email box. I run through the messages pertaining to things I’m waiting on, and will maybe send a reminder if a particular thing is getting urgent.
Life Balance tells me I now need to process my Hog Bay Inbox. This will usually contain, on average, 10 new items created since the previous day. Each item is processed, such that this “basket” is empty when I finish. Items in the Inbox generally get filed into “Resources”, or result in the creation of projects or todos in Life Balance. Say one item is, “Customer X requested an offer to do Y.” I’ll process this entry by switching into Life Balance, and creating a new todo in my “Work (+)” place. I’ll then break down this entry into small steps, each defined as a sub-task. (The parent task I’ll refer to in the future as a “Project”, since it’s a todo with sub-tasks.)
Life Balance now tells me to review my iCal calender. I switch to iCal and have a look at the day and the week, in case I may have some appointments.
Life Balance tells me I’m done with my daily GTD processing, and it’s time to get to work. I switch to the “Work (+)” place, and have a look at my todo list. For any todo (project) that has sub-tasks (or any sub-task that has sub-tasks), LB will allow me to specify “complete sub-tasks in order”. This implements the “Next Action” concept from GTD, such that I’m only shown the very next thing that needs to be done. So, I review my todo list of things I’ve noted as important (i.e. things assigned to the Work (+) place), possibly modify priorities for a task here and there by adjusting the “importance” slider for a given task, and then I start to work.
The whole morning GTD processing takes about 45 minutes on average. Then I get to work on my todos.
Say I get a phone call, I’ll switch into Hog Bay (via a hot-key I’ve assigned with MaxMenus), into my “Inbox” (by clicking on its sidebar “bookmark”), and create a new entry titled, “Phone call with Carol.” I’ll document the phone call there, and maybe create some immediate actions if necessary. If I don’t want to think about it right now, I’ll leave it, because I know that it’ll get processed tomorrow morning.
Say I decide to read some RSS news feeds, and come across an interesting URL. I’ll use Hog Bay’s Dock icon to paste the URL into the Hog Bay inbox, without leaving my browser. Tomorrow, when reviewing my Inbox, that entry will get filed under “Resources” for future reference.
Say I get a phone call from Carol, asking me to call her back at 3:00. I’ll create a quick reminder in ImOnTime, to popup a reminder 10 minutes before 3:00.
At noon, an ImOnTime reminder pops up reminding me to check email. I switch into my email program, and process every new incoming email. Most go into the @Inbox, for processing in tomorrow morning’s GTD activities. (Note, I’ve disabled Mail’s notification, and use ImOnTime to schedule the checking of mail only twice per day.)
And that’s how the day basically goes.
Conclusion
Well, that in a nutshell is how I work. This process has been under refinement for a number of years, and works quite well for me. The one thing it doesn’t address, which is a problem I’m still trying to solve, is planning according to estimated load. Assume I have 10 ongoing “Projects”, and that Project 1 requires 40 hours to complete, and must be completed by next week. I wish that some aspect of my process could inform me that I should only work on that activity, because if I work on anything else, I won’t meet my deadline. (That’s simplified, of course. The value of a planning mechanism comes when you’re trying to juggle several projects with different load estimates and deadlines.)
I hope to write more later. Let me know if you found this useful.