Should I write the introduction first or last? I'm getting mixed advice.

[Kile]

Okay, this is the most confusing part of proposal writing. The UFV planner explicitly says: "Although this is the first section the reader comes to, you might want to write it last, since until then, you will not be absolutely sure what you are introducing" . It also says to write in the "future tense" since it's a proposal .

This makes so much sense! How can you introduce a project before you've figured out the methods or the literature review? But my advisor told me to start with the introduction to "set the stage." Who is right? The planner's logic is hard to argue with. You can't accurately introduce something you haven't fully designed yet. It also says the proposal can be changed and edited later once it becomes part of the final thesis . That's reassuring—it doesn't have to be perfect now, just a solid plan. For those who've written a successful proposal, did you write the intro first as a draft and then heavily revise it, or did you follow the "write it last" rule? I need a definitive strategy!

 

[Shawn]

Your advisor isn't wrong though. There's a psychological benefit to having an intro written early—it makes the project feel real and gives you something to anchor your thinking. But you have to go in knowing it's provisional.
I wrote my intro first, defended my proposal with it, then rewrote maybe 70% of it during final drafting. My methods changed. My lit review grew. My argument sharpened. The original intro was like a rough sketch that got painted over completely. If you're the kind of person who needs a draft to exist before you can improve it, write the intro early. If you prefer to know exactly what you're saying before you say it, write it last. Neither is wrong.