# Four fours - Sentiers Media

How do you work? I think productivity gets somewhat of a bad rap, some people talk and write about it nonstop, for some it’s a way to optimize their workaholic tendencies, and sometimes it leads to too much focus on details, not enough on what you are actually trying to get done. On the other hand, I think it is useful to see how others work, and to try to have and evolve your own system, not simply diving in heads down in the morning and hoping for the best.

In the spirit of “this might be useful to someone else” but also, more so, with the goal of putting some low level peer-pressure on myself, I thought I’d share how I’m trying to structure 2021. Because I like alliterations and repeating things, but also simply because of our calendar, I call it the Four fours. Or 4x4x4x4.

- Four solid hours of knowledge work a day.
- Four work days a week.
- Four things delivered each week.
- Four projects a year.

## Four solid hours of knowledge work a day

This one is 100% lifted from Doug Belshaw. I’ve written about it before and it’s really Doug’s routine and his mention of it that got me to think this way.

> My time is precious. of solid knowledge work is what I aim for each day Four hours as research backs up my theory that this is optimal. I feel sorry for people who work in offices who have long commutes each way, have to spend time maintaining relationships with colleagues they don’t particularly like, and in meetings that are a waste of time.

There are a couple of links in the quote above, and I could find a few more through the research I was doing back in the day when I was writing a newsletter on lifelong learning. Four hours of focused work is roughly the most we can expect, and dozens of great creators had this type of schedule.

Like Doug, I don’t just work four hours; admin, emails, and meetings are not counted in there. But, especially in pandemic times with the kid at home more, if I manage four good hours of focused work, I consider it a good day. One hour, a quick break, another hour. Morning and afternoon, the rest falls around those hours. It’s a case of managing expectations. If only for morale reasons, it’s good to have a reasonable idea of what you can get done in a day and not expect too much of yourself in a tense time.

## Four work days a week

On this one I’m blatantly cheating. I do work five days a week but Friday is for writing Sentiers, which is not work per se. On that day I don’t book meetings or plan on anything else than catching up on readings, curating what goes in, and writing the insights/summaries. I’m doing all the same things as when I’m working but it’s for my own thing, written for readers but also for myself.

## Four things delivered each week

This is the new one and why I came up with this post. In his excellent thread on writing a newsletter, Lenny Rachitsky said this: “Just sending an email to a few friends regularly with your concrete goals about writing (and anything else) works wonders.” (Example below.)

Lenny’s example, lifted from his thread.

I thought about it a bit, but I couldn’t really think of enough friends who would be interested in getting this and pay attention to have a critical mass of some of them replying or inquiring. And thus, no pressure yet “bugging” people with it anyway. Also, I’m already achieving roughly that level of things, I wanted pressure for more smaller things and the flexibility of changing things up, as long as I complete them.

And so, I thought I’d start writing weeknotes. A well established practice a lot of people have been doing these for years. I plan on a simple version, a list of things delivered that week, potentially some more thoughts, and usually one “practice related” article read during the week.

By “things delivered” I’m just thinking of almost any kind of work completed. For example, this week:

1. Researched and wrote-up two posts for DA VINCI. (Yeah! Finally using project names!)
2. Wrote up two posts for the Sentiers website (this one and another scheduled to publish).
3. Wrapped up the archive conversion for ECO.
4. Completed and posted the report for CRICHTON.

I’m setting this up for two mental tricks on myself; the routine of writing these, and the (almost) entirely imagined peer-pressure of posting them in public.

## Four projects a year

This one I’ve already shared in On projects, newsletters, products, and formats. At this point, three projects of four months each might have been a better idea, but allowing for relatively blurry lines between each, I’m still hopeful to manage to ship four larger things a year. The first, ECO, was supposed to be over the last quarter of 2020 but is ongoing. I’m lining up a smaller project and might get both done before March 31st (😳). Although if the BABBAGE client project gets off the ground, maybe not.

## Two hundred fifty-six

Hopefully this can somehow be useful to others, and hopefully writing it and putting it out there, along with the weeknotes, helps me stick to the schedule and complete things with more regularity.