I almost never follow the schedule I set, but I manage to get everything done (deadlines are an advantage of being in school still, I think).
In a more freeform environment I impose a lot of structure on my schedule when I have a lot of executive function to spare (morning, coffee, 8+ hours of sleep, enough food). Then, the rest of the week (I plan in 1 week blocks) I stick to the schedule, and I don't really have to think about what I'm going to have to do.
There has to be some sense of flexibility, though. I forget to schedule things, and sometimes stuff pops up on short notice. Having items on my todo prioritized (1:=most important).
This is, of course, an idealized thing. I still strive to be consistent and effective in my routines.
It's a big motivator and important tool I've picked up.
The best part of the bullet journal method is the de-prioritizing of tasks. I don't give up on things to the point of detriment. With a bullet journal, I've learned to let go of stuff and move forward.
I have a kanban/whiteboard with small post-its and the "done" column is a reminder that things are being completed, even if not always at the pace I'd like. Not so much a hack as a reminder to not be down on yourself - we can't all be hyper-focused life hackers :-)
A trick I use is to start something "easy" towards the end of the day, but not finish it. That makes it easier to get the ball rolling the next morning.
Wikipedia has more details on MBTI, and there are online self-tests for your own MBTI classification.
Disclaimer: Note the "Criticism" part of the Wikipedia page. MBTI is AFAIK not a tool that professional psychologists would use. Nonetheless, I find it useful in order to find similar people on the internet. For example, if I want to learn a new skill, a search query like "[thing] tutorial for INTJ" gives me way better results than just "[thing] tutorial" because I get recommendations from people who think in similar ways.
Basically I am able to (mentally and physically) walk away from work and let go of it and go home and game or work out or whatever. Then, the next day when I sit down again, I get my bearings and see where I'm at and then proceed!
There are a few exceptions to this, of course, but it's always with hard problems I become absolutely OBSESSED about. For example I couldn't find an XML parser in Elixir a couple weeks ago that I liked, so I was faced with writing my own... which I did... and then released as open source https://github.com/pmarreck/mega_xml but I was literally up until 4:30AM one night figuring out how to turn an event-based XML parser callback mechanism into an Elixir Map datastructure (something I had never had to do before, but which I somehow knew I was barely capable of figuring out, lol). It was extra tricky (for me) due to the lack of mutability
My technical solution for this is using a personal Trello board. Each task is a Trello card, and for a new task I write a rough outline of what needs to be done. I keep these cards in separate stacks: To-do (not started), In-progress, On-hold (waiting for external activity), Done (for archival purposes). For longer running tasks I do update the cards with additional information and progress status. And I can put high-priority tasks to the top of the stack. Creating, updating, and moving cards is all low-friction in Trello, so I find it to be well suited for me.
| To Do | Doing | Done |
It happens that I can't really 'start' with work due to having too many things to choose from, or by not knowing how to really get started with it.
What always helps is writing down on a piece of paper a step by step guide of what I will do. this can be very general. But just having the steps written down helps me get started.
Kind of like a "todo list" except that I don't update it when I'm done.
This helps me when I need to make a choice for what to work on, but also to compartementalize the problems that I get stuck on.
For example, on my paper it says this at the moment:
It's just a rough outline for what I should be working on at the moment (instead of being on HN, probably).