Working More Slowly: Patching Leaky Motivation

This is a continuation, of sorts, of last week’s Working More Slowly: Preliminary Observations post. I had hoped to have a productive continuation of my early-rising work ritual (heretofore known as “The Morning Ritual”), as described in that post, but it collapsed. Why? I had no idea, so I collected my thoughts into this post. It turns out that I’d missed something important about the mission behind the Morning Ritual. Hint: it’s not really about having a productive day.

Last Week in Review

The week of Sept 30 through October 7 was intended to be a celebration of early-morning habits, but it was anything but! Here’s what I got done, in a nutshell:

  • MON: Up at 6:30. Writing emails. Started this blog post draft. Picked up sample ETP pads from printer. Asleep at midnight.
  • TUE: Up at 9:00. Stayed home. Client Focus on WordPress and related meeting. Schedule furnace replacement assessment. Asleep at midnight.
  • WED: Up at 11:00. Stayed home. Client Focus on Javascript Dev Environments and Best Practices. Meeting. Video shoot and dinner with friends. Worked on dev stuff. Asleep at 4:30AM.
  • THU: Up at 11:30. Stayed home. Client Focus on Javascript, Get proposal for new furnace ($3300). Schedule installation for Monday. Install Leap controller, compile test web app successfully. Asleep at 10PM.
  • FRI: Up at 9:30. Out to Starbucks. Tried to write. Went home and went back to sleep. Met with artist Kate for “art thinking time”. Played video games for rest of day.

You’ll see that I failed to maintain an early-morning habit pretty consistently. The weekend was even worse, spent sleeping and playing video games mindlessly when I could have been doing something more interesting. While I extol a certain amount of video gaming as healthy for my profession as an interactive designer, I was on a binge and didn’t like where it was going. This week was a real struggle.


So what was missing? It had been an OK week productivity-wise, but I felt I had lost control and satisfaction. This manifested as a loss of motivation, and I didn’t know where it was going.

So I wrote down a bunch of observations on Friday through Monday. Here they are, raw and roughly-grouped. The intent behind making this list is to find patterns in my feelings about the experiences of the week. From these patterns I hope to form a hypothesis about where my motivation is going.

Themed Days

Focusing on one main theme every day in the morning (business, client 1, client 2, domestic) seems to feel good. After getting that main chunk down, then filling in the rest of the day with smaller supporting tasks.


While I like the idea of “theme days”, in practice they don’t seem to improve productivity. It might be that I feel “I have all day” and then I don’t concentrate my effort. I think limiting the theme to just the first block of work is best. My impression arises from the late nights on certain days. Then again, I may be staying up late because I get sucked into a puzzle.

Feeling Productive

  • A good day is measured by what got resolved or finished.

  • To feel productive daily, I have to make progress on something that I can see and use in the future.

  • To feel productive over time, I need to see that my various threads of effort are making progress toward something I want. Goals, I suppose. Remembering the big picture is sometimes difficult, particularly for all-consuming projects.

Pacing and Goal Attainment

  • To stay focused and efficient, the Morning Ritual helps me with mindfulness, continuity, and balance. The writing that goes with it helps me maintain awareness of my day-to-day progress, which is an important contributor to feeling productive. Writing works for me since it comes to me easily.

  • I have a tendency to engage in “epic” challenges if I think I will get something finished. The urge to pull all-nighters when I’m in-the-zone is an example of this tendency, and it is what I did on Thursday. Which of course kills the Morning Ritual.

  • Personal continuity with regards to all the different activities I have is really important. I am worried that I’ll lose sight of something important if I don’t maintain that continuity (“what am I doing now, and why?”).

  • When there are multiple threads of effort active, I prefer that they converge toward one goal. The threads that don’t have an ending are less interesting in the long run.

Impulse Control

  • The more productive I am during the day, the less likely I will be successful at eating healthy and doing exercise. I tend to indulge myself because I am tired and can claim I deserve it. The easy rewards, however, tend to be bad things.

  • It may be that “good but unexciting” domestic tasks (going to the gym, cleaning the house) need to be done in the morning before work, even before the Morning Ritual. This might work because these tasks don’t require thinking, and I know I’m doing them because they’re good for me even though I don’t want to do them. The issue, though, is whether I will be physically tired-out by gym visits. Or perhaps I schedule theme as “theme days” in the morning.

  • Limiting the amount of time I spend on a project may be just as important to maintaining balance. Coding tends to pull me into a state where I am working very long hours, which disrupts my morning ritual because I go to sleep late. This means proactively monitoring myself during the day. I could also make sure I’m drinking enough water.

  • Social Media is a tempting distraction, because it is a source of new inputs and excitement, promising release from productive drudgery. It falls into the “reward” category.

Staying Focused


p>My memory definitely fades if I don’t do the daily journaling, which means that I lose personal continuity, and that’s important to me. On days that I don’t do the Morning Ritual, I fall into a reaction/distraction pattern that is loosely organized around “I need to do X”. This is not structured, and I tend to lose sight of the big picture. While the day can still be productive, at some point I have to then put on my Manager Hat and figure out if I got anything done. That is what I am doing right now, in writing this post.

I have to remember that there are two main areas of focus, too: my own projects and client projects. I maintain separate project journals for each client. It’s my projects that I tend to lose sight of; the Morning Ritual, I should remember, is for managing my time most effectively so I can make progress on my own goals.

Energy Management

If I get less than 8 hours of sleep a night, then it comes out later. Energy drinks currently seem to help, but I would prefer not to rely on them.

Visual design tasks, doing WordPress theme feature coding, and researching unfamiliar technologies that I need to master are high-drain tasks. Converting the unknown into the known takes a lot out of me.

Tweaking, adjustment, documenting tasks are medium-drain tasks, which I can do indefinitely. That is because the hard part of understanding the system and putting the pieces into place are done, and the adjustment/tweaking is more a form of play.

Writing down what I am thinking or think of something is a low-drain task. If I have the knowledge in my head already, it’s very easy for me to think-through.

A Model of Daily Activities

As I considered what was high-drain, medium-drain, and low-drain, it occurred to me that I could put together a model that described the way I approached my work. It could be helpful in determining how I schedule my days.

Dreaming Stage – No Commitment = Low Drain

  • Collecting Inspiration
  • Identifying interesting directions
  • Learning interesting skills
  • Encountering an opportunity
  • Seeing a possibility
  • Desire to make something…anything!

Getting Started on the Journey – Scoping Uncertainty into Best Guesses and Supporting Metrics = Medium Drain

  • Establishing Expectations, Actions, Metrics
  • Defining Tangible Targets
  • Setting Goals (tangible + timeframe + desired state)

The Hard Drain – Commitment to Uncertainty = High Drain synthesis and contingency planning + critical research + iterative wandering

  • Creating Certainty (hypothesis, mapping, design, research)
  • Creating Methodology and Process
  • Building Prototypes and Testing

The Tweaking Stage – Certainty Attained, can now screw around and have some fun = Low Drain

  • Tweaking, Testing, Refining, Remixing
  • Trying new arrangements of built modules
  • Getting Feedback

The Moment of Truth – Does it work in the field? Do we have to start all over? High Drain Tension!

  • Looking Back
  • Worth Going

Having Guts and Conviction Stage – Now, the tedious work of finishing. High drain, because this part feels like the end but it’s actually a whole separate project.

  • Polishing and Packaging into Finished Product…?
  • Marketing and Finishing
  • Profit…?


While the high-drain, medium-drain, and low-drain task model is interesting, I think I know what is missing: I am not making progress on my personal goals, because I feel they are being squeezed out by other projects. And that doesn’t have to be the case.

I know from trying the 15-minute hack that one can get a lot done, but for it to be successful I need to have the right attitude:

  • I haven’t picked a single personal project to push on, because I am seeing a million of them.
  • I have subconsciously prioritized client projects as more important than my own projects, when they should actually be equally important.

The Morning Ritual is not about developing good waking habits so you can have a productive day. That’s just a side-effect. The whole point of having this ritual is to commit to myself and make progress on what matters deeply to me. That is what has to come first, otherwise everything crumbles.

Such progress has to happen at least once every three days, I reckon, given my current project load. So let’s reboot and make some choices:

  • Picking one thing to work on this week for me: Organize the Digital Products in the Calendar Category.
  • Making this the “theme of the week”, to be addressed every day for 15 minutes minimum.
  • Maintaining progress on the Javascript stuff, which I’ll have to write about later because it’s cool.