Deadlines Spur Action
A hard lesson learned from the spice planet.
I was in the 8th grade the first time I ever tried to read "Dune." I had chosen the book for a book report and, despite having weeks to read all 900 pages of the tale of Muad'dib, I waited until the night before to start. But crafty-old-me had a plan. I was going to rent the movie (on VHS), then type up the report, and be ready to present to the class the next day. What could go wrong?
A few historical items of note:
This was the mid-1980s, and the internet was not that robust. Finding a helpful summary online was not an option.
When I said type up a report, it meant typing it up on a typewriter—a clickety-clackity typewriter.
The only "Dune" movie available was the 1984 version from David Lynch—yes, the one with Sting.
There was no ChatGPT. Unless you want to count the chat my dad was giving me about how I was going to bomb the assignment.
It might come as no surprise that the movie was of no help. Entertaining, yes, but not so useful. Also, fun fact, a teenager cannot consume the entirety of Frank Herbert’s masterpiece between the hours of 10 pm and 7 am.
I pleaded with my parents to keep me home, but I’d have had better luck against the Sardaukar.
So I went to school, stood awkwardly in front of the class for a few minutes, and mumbled something about how sandworms were cool, then sat down. I received a D, and it was the most merciful act a teacher has ever shown me or anyone.
So why the tale of woe from the planet Arrakis? Well, you can be sure I started the next book early. I was well ahead of schedule for each report and assignment for the rest of the year. My merciful teacher also let me do some extra credit to get my overall grade up. This whole experience taught me two very valuable lessons.
First, “Fear is the mind-killer. Fear is the little-death that brings obliteration.”
Second, deadlines spur action; consequences spur urgency.
I’ve seen this time and again in projects. If there are no deadlines or if projects don’t have clear milestones, they can languish for months. You need to put your team (or yourself) on a deadline to really get things done.
How do you achieve this?
Understand the scope of the whole project: At some point early on, you need to look at what you are trying to accomplish. All projects have some natural phases, but you should take a step back and take in the entirety of what you are attempting to do. If you are building a shed, know its size, type, and location. For a book, draft a high-level outline. Understanding the full scope helps in creating a schedule and setting milestones.
Break it down: Once you have your head wrapped around the task at hand, you need to divide the project into different phases. These represent a significant portion of work, forming the milestones.
Set specific goals for each milestone: Each milestone should have a specific goal or set of deliverables associated with it. I like to assign themes to these. For example, we have a project right now at work where we are on Public Beta 4 - “The Map Tool”. We’ve grouped all the bugs and feature requests of revamping the map tool into one release. Public Beta 5 is “The Grid”, this release is all about the crossword maker and how to make it better. Groupings like this help keep your goals measurable and clearly defined so that it's apparent when the milestone has been hit.
Set realistic timeframes: Estimate the time for each milestone, considering task complexity and resources. Sprints of 2-3 weeks are a good rule of thumb.
Assign responsibilities: Along with determining the time frames, you also need to work out who will be responsible for delivering on each part of the milestone. Everyone involved should be aware of the milestones, including what they entail, and their deadlines.
Adjust as needed: Monitor progress and be flexible to update plans as necessary. Remember the Iron Triangle of Project Management. If the delivery date isn’t flexible, your scope or resources need to be.
Celebrate you achievements: Take time after each milestone to take the win. This serves as a great motivational tool for the team (or yourself).
Setting up various checkpoints keeps your project on track, identifies potential issues early, and keeps the team motivated. And again remember that deadlines spur action. No one likes being late or behind, a little schedule can be very motivating. Oh and many years later I finally did read “Dune”. In fact, I have part of the litany against fear tattooed on my arm. I think my teacher would approve.
Ever forward.
— Derek (aka Chief Rabbit)
Enjoying Chief Rabbit?
This newsletter is free and always will be. But if you’d like to support this work, you can. You’ll get monthly Q&As, vote on topics, stickers, and help keep this ad-free.
You can also follow me on Threads where I sound off on all sorts of nonsense OR LinkedIn where I tend to be a touch more serious.
Also, thanks for being someone who reads to the bottom of the page, you’re a special human.
I can relate to the first bit way too well. There are countless times when I have gone to school without completing assignments, most of the time escaping because I had good grades in the subject. Homework always was a secondary thing to me, after reading the book I happened to read at that time.
Have you seen Tim Urban's TED talk on procrastination? It's a great one.
That aside, it was a helpful post :)