Constraints breed creativity, but not all constraints are made equal.
Finding the right constraint for your current situation is key to getting the most out of it.
So here's a small framework for choosing the right constraint.
Constraints breed creativity, but some constraints are better than others.
Which constraint you should create for yourself depends on what your problem is. If you have trouble starting, set tight format constraints. If you have trouble finishing, set tight time constraints.
Format constraints for the procrastinator, time constraints for the perfectionist.
Format Constraints
Probably the biggest source of procrastination is not knowing what exactly the first step is. With an infinite canvas of what the work could look like, finding the first step is super hard – even with a deadline looming.
In fact, a time constraint can make this even worse, because you fear you won't be able to course-correct if you make a wrong choice.
So to fight procrastination, set tight format constraints for yourself. Format constraints make the first step easier, because you know where you're going.
Time Constraints
You can polish and tweak forever, no matter what you're working on. And if that is the reason why you're not shipping your work, format constraints won't help.
In fact, they'll likely push you to polish more so you get closer to the "ideal" set by the format constraint.
So to fight perfectionism, set tight time constraints for yourself. Ship when the alarm rings, no matter what.
• • •
Missing some Tweet in this thread? You can try to
force a refresh
But after just writing three hours on my dissertation, I can tell you: sometimes you actually need to context switch to keep going.
Read on below 👇
I'm just coming off a three hour writing session on my dissertation.
There's still so much work today, but I know that I can't do any of that work right now. I can't see the structure of my writing in my head anymore, I've exhausted my ability to think clearly about this topic.
Don't make the same mistake I did last year and take too little notes on what you're working on.
Better notes on what you're working on has three key long-term benefits you don't want to miss out on.
I am LIVID at how bad my interstitial journaling practice was last year.
Recently I had to revisit a paper I was writing for my dissertation, and the last time I had closely looked at it was a year ago. Going over my notes from then I found...nothing. Nothing actionable at least.
So let me tell you why I wish I had done interstitial properly last year.
Which means selecting the right tools and learning to use the tools right is time well spent.
Your brain doesn't know when you're using a tool.
A sword, like in the movies. A violin or guitar. Your keyboard. The app you're using. Your brain doesn't know. If you know how to use the tool, your brain just...acts and does what needs doing.
Ergo: selecting the right tools and learning to use the tools right is time well spent.
What you actually want to get good at is KnowledgeOps.
Let me explain.
I dislike the term Personal Knowledge Management.
I find it to be limiting and too static. It conjures up images of shuffling around books on a shelf, sorting them for easier access. Important, but not enough.
Instead, I think we should think about the whole process.
In software development the term DevOps describes
"a set of practices intended to reduce the time between committing a change to a system and the change being placed into normal production, while ensuring high quality" (Bass et al. 2015)