Briefly state your position, state why the problem you are working on is important, and indicate the important questions that need to be answered; this is your "Introduction." Push quickly through this draft--don't worry about spelling, don't search for exactly the right word, don't hassle yourself with grammar, don't worry overmuch about sequence--that's why this is called a "rough draft." Deal with these during your revisions. The point of a rough draft is to get your ideas on paper. Once they are there, you can deal with the superficial (though very important) problems.
The calculus of quitting also changes what it means to have a good division of labour at work. If your goal is to get a job somewhere else, not all work projects are equally valuable. Workers must jockey for the tasks and projects that might lead to a job elsewhere. They must try to avoid tasks that, either due to intellectual property issues or for other reasons, are too company-specific. Linus Huang, a sociologist at Berkeley, saw this happening in the Silicon Valley startup where he was working when Java was first becoming a popular programming language. There was quite a bit of work in his company involving the general-purpose programming language, C++ , and for many of the company’s needs, it was sufficient. Employees wanted to have practice with Java, however, because Java would make them more marketable in the future. Workers began to evaluate projects in terms of whether they would improve their Java skills. The managers began to struggle to find people who would do the day-to-day programming work, mostly in C++, upon which the company depended. They had no trouble, on the other hand, finding people to work on the few Java projects. When you work a job that presumes you will quit before too long, the tasks that are good for the company might not be good for you.