Process for a Purpose

There comes a time in the life of a project when it seems to call for processes and platforms.

To get the idea into the world requires an email account, a word processor, a project-management system, an instant-messaging service, and on and on.

Granted, there’s probably a better or faster way than the way any one of us uses. We learn to swim in the ways that work, and then we learn to use tech tools similarly.

My version of the crawl stroke sure isn’t the prettiest or most efficient, but it’s the one that works for me — it gets me from here to there faster and with less frustration or fuss than some other version of the stroke. Changing to an objectively more efficient technique would cost me time and energy, at least in the short run.

Processes help get better work get out the door quicker — if they’re implemented wisely. Those are worth fighting through the short-term learning curve.

On the other hand, some processes are just an excuse to send a message about the email about the comment about the task.

Every time you add a process, what’s the purpose?