workflow

How To Build Good Work Habits By Reducing Friction And Sparking Joy

 

Productivity writers often talk about reducing friction in workflows — essentially, how to be more efficient.

But what about having fun with work? Building elements of fun into your work not only makes work more enjoyable in the moment. It also supports good habits needed for long-term success.

Here’s how to do it.

Photo credit: AnastasiaDudka

Photo credit: AnastasiaDudka

Reducing friction

Let’s start with friction. An excellent way to support a positive habit is to reduce drag, release any “adhesions” — as a physical trainer might put it— and otherwise smooth out the system. 

For example, if you want to capture ideas more consistently, you need a quick and simple system, requiring the least amount of effort. Cal Newport recommends a simple text file on your computer — one that is always open — where you can type in ideas at once. There’s no fiddling around to find the right app, formatting text, tagging — or other forms of drag found in many capture systems.

To reduce friction when capturing tasks, I use OmniFocus. This app is admittedly more complicated to set up and manage. But my capture system is easy to use. For ideas and observations — anything I want to reflect on, potentially write about, or otherwise build on creatively — I use a combination of Drafts and Roam Research, a system I will elaborate on later.

My process feels frictionless. But more than that, it’s fun to use. And that, I realized, is what makes these systems work. So let’s look at the positive aspect of building workflows.

Sparking joy

Organizational guru Marie Kondo’s famously advises people to tidy spaces by pondering whether each possession “sparks joy.” If it doesn’t evoke positive feelings, people should gratefully discard the object — it no longer serves its purpose. And keeping the item dilutes the pleasure we experience from other possessions we value, by cluttering our closet, for example.

In designing our workflows, why not also ask, “does this process spark joy?” If not, maybe it’s time to redesign or replace it, or discard it altogether — like that sweater you haven’t worn in ten years.

Building positive habits

In Making Ideas Happen, Scott Belsky says, “the design of your productivity tools will affect how eager you are to use them. Attraction often breeds commitment.”

Thinking this way also supports good habits. In Atomic Habits, James Clear writes that good habits are characteristically painful in the short-term and pleasurable only in the long-term. (Think: exercise) The opposite is true for bad habits. (Think: eating Doritos while watching YouTube on the couch). 

Thus, cementing a good habit requires us to strengthen an association between the good behavior and the long-term reward. But in the short-term — to build the habit initially — we must find ways to experience pleasure and associate it with the new behavior.

Workflows for good habits

So for our work, build in a little pleasure into what might otherwise be a drab but important task needed for long-term success. Don’t think only about reducing friction. Find ways to make the task enjoyable, if ever so slightly.

One way to do this is with technology: using Siri, Shortcuts automations, scripts on a Mac — even formulas in Excel. When we see technology magically accomplish something tangible, it’s immediately rewarding — do I dare say, possibly even fun?

Sparks can shine outside the digital world too. Take pleasure in writing with a nice pen in a quality notebook. Find running shoes you like, ones you will enjoy lacing up as they launch you onto your feet. Maybe splurge on a hardcover edition to get you reading that challenging book.

So try to build in some fun — things that may take time to set up but will create happiness — and ultimately increase productivity by supporting a positive habit.

How have you incorporated elements of joy and fun into your work?



 

Why Process Improvement Should Matter To All Lawyers

One thing is now clear: for serial litigants, developing efficient processes for handling e-discovery is critical. Joan Goodchild at Computerworld sings a common refrain heard at the The Sedona Conference Institute e-discovery conference I attended last week:

NBC Universal is one of the largest media and entertainment companies in the world. Chief Information Security Officer Jonathan Chow and his team manage information security for several business lines within NBCU, including its broadcast and cable television to film production, online ventures and its two theme parks in Hollywood, California and Orlando, Florida. Among one of the biggest challenges in the last few years has been the incredible explosion in demand for e-discovery services, according to Chow.

Since different legal teams handle the needs of each line of business, the workflows associated with managing electronic discovery vary as well, adding another layer of complexity. And because of the growing number of cases, and increases in both the amount of electronically stored information and hours spent supporting the process, demand for e-discovery services has increased 30 to 50 percent annually. The costs were spiraling out of control and this sent Chow looking for a way to manage the process internally.

Chow . . . tackled the costly and time-consuming process and turned it into a cost-effective and more efficient system that has seen a 40-45 percent gain efficiency since its implementation.

I spoke with several in-house teams who've done a remarkable job developing standardized workflow for handling e-discovery. In doing this, they've discovered how wasteful the processes were when handled by outside counsel.

But the lesson isn't that in-house teams are necessarily more cost effective than outside lawyers. Outside counsel can do this too. The lesson is that process matters. Efficient processes allow in-house teams to save money for their companies. And outside counsel can give their clients the service they deserve.

Ninja Email Laws

Time Management Ninja offers “9 Laws for Work Email.” They're all worth checking out. My favorite is "Keep it Short," with the suggestion that all emails be less than five lines long. But I particularly like this insight:

Do not expect an immediate response – In our hyper connected world, email is the new snail mail. Once upon a time, email was considered fast. Wanted a quick response? Send an email. But it has since been demoted down the communication response priority list. If you need a more immediate response: call, text, or come see me. Many people check email only 2-3 times a day and are turning off their work email on breaks and weekends.

It's just impossible for busy people to reply quickly anymore. Handhelds aren't the solution, and by contributing to the volume of sent email, arguably they're part of the problem. And constant checking and responding to emails is poor workflow. If you need an immediate response, better choose a different medium.

If you find these rules useful, be sure to visit Merlin Mann's series of posts on email best practices.

D. Mark Jackson

Designing Software for the Workflow

There's an interesting article on Customer Relations Management (CRM) software in this month's California Lawyer.  It does a nice job describing what these applications do,  as well as some of their limitations.  And I was both surprised and pleased to read this section:

But in practice, most CRM systems do require a change in the way attorney workflow is handled on a day-to-day basis. Building a robust CRM system depends on a resource many firms are reluctant to surrender: attorney time.

"Your success or failure with CRM software is less a technology issue and more a process problem," says Andy Havens, a legal marketing consultant and founder of Sanestorm Marketing. "It has more to do with what you're going to require lawyers to do as part of their daily work than [with] the features of the software. You have to know what things your lawyers are willing to do that are trackable."

I find this dynamic to be true with any technology roll out, unless it's completely on the backend.  A great deal of management time goes into developing and then training on the new workflow.  If possible, our technology team works to customize the application to fit our workflow preferences, and facilitate any necessary changes to the workflow as gently as possible.

But isn't it amazing that many developers expect the users to model their processes around the application, rather than the other way around?  And it's not necessarily about customizability.  A lot of enterprise software, while including many powerful features, seems to have been developed with only minimal consideration of the workflow it is designed to facilitate.  Workflow should be a key element of  software design.

D. Mark Jackson

Bookmark and Share