This works well for writing. Writing, though, comes at a later stage after you've done at least some of the actual work (code, experiments, whatever). It's the work that people have most trouble with. The ideal trajectory is something like MVP -> write -> iterate. People usually get stuck in the MVP phase.
I don't have a good solution to this, except that at least from personal experience, prolonged procrastination is an indication that you don't like the work. And this can be difficult to acknowledge because maybe you liked it earlier, or thought that you did. And then ego becomes involved. Knowing what you like and don't like can also be quite tricky. Sometimes, the only real solution is to quit and do something else.
Yeah. I'm not a particular vomit draft or mindmap or whatever proponent for writing. But the original post seems to be more about actually doing the lab work for the thesis that's a prerequisite to writing something.
That was where I was with my undergrad thesis. There were dependencies on other work in the lab which wasn't progressing quickly and I just had a lot of trouble getting to the point where I had something to write about. The writing wasn't the big deal.
I don't have a good solution to this, except that at least from personal experience, prolonged procrastination is an indication that you don't like the work. And this can be difficult to acknowledge because maybe you liked it earlier, or thought that you did. And then ego becomes involved. Knowing what you like and don't like can also be quite tricky. Sometimes, the only real solution is to quit and do something else.