I was musing on this over the weekend while warping up my loom: good project planning manages to avoid most snitches, just like keeping warp threads tidy. So I'm pushing the analogy: here is a list of must-dos for each.

Keep the warp tidy on the warping board, keeping an eye out for any flaws in the yarn.

Create a top-level plan of each stage from beginning to end, chunking into manageable items.

Be diligent in placing the warp threads on alternate sides of the cross, or you'll have difficulty threading the leashes later.

Identify the critical points, what must happen for something else to go ahead later, or you'll come unstuck as the project unfolds.

Chain your warp when taking it off the warping board and to the loom: you want no tangles!

Document what you expect to happen at each stage before you go any further: you want no misunderstandings later!

Space the warp threads across the raddle and keep them in place by securing the raddle cover: you don't want bunched threads and uneven tension on the warp beam or the finished cloth will not be even.

Schedule each task so that each has sufficient time: you don't want any stage to be compromised due to lack of time.

Secure the warp well on the warp beam and wind tightly: same reason as previous stage!

Get your team into motion, briefing them well and giving them a tight ship to sail on (apologies for the extra metaphor): you don't want to suffer from a lack of people or skills

Thread each warp thread through the leashes, tying them onto the cloth beam regularly: now you are working to a rhythm!

Set the project in motion and keep an eye on its progress: now you are running your project!

Finally yet most importantly, did you check the tools for the job?

If you want to use a mohair warp thread, a rigid heddle will never work: the hairs tangle. Start again ...

Various analogies, such as: if you have a complex structure to your document, it won't fit into a simple schema/template: you'll be rearranging the proofs. Next time, plan creating the schema ...