Doctoral Research Proposal Development

Here’s the PhD #research #proposal that got me into the #PhD program at the #LSE (Dept. of Methodology) back in 2018. It also landed me a full #scholarship (tuition + stipend—pretty standard for the UK). My 2 cents on what to do with this (and what not to do): Do: - Get a sense of structure and the elements of a standard research proposal - A cracking literature review. That is fully within your control and is a good way for you to show your research chops! This should end with a 'gap' that you propose to address. Will you eventually address that gap? Who knows. But you've shown the panel that you've found a gap based on a robust review of existing literature - Get your citation/referencing game on point. Use Zotero so you don't make silly citation errors (I did my citations manually and they were a disaster). And work on citing 'key' papers (well cited, classic stuff) in your field. - Provide evidence that you are able to single-handedly execute this piece of work. Discuss the networks you will use for primary data collection, potential field sites you can easily access, secondary datasets you can access. You need to show the evaluators that you can finish the PhD in the 4 years as that is what they care about - Related to the previous point, throw in a Gantt chart. Mine was rubbish, but having one in there demonstrated that I fully intend to devise a concrete plan for the PhD years Don't - Plagiarise my work. I have no way to know if you do, and I frankly do not care if you do. But it is in your best interest to avoid lifting things from here. Citations/references obviously ok! - Treat this as the *exact* way/format to write a proposal. The structure is pretty standard, so use that as a point of departure - Overpromise. Evaluators will also look for feasibility. If you've said that you're going to collect data from 10 fieldsites in a 4 year period, that is cause for worry. Be realistic and discuss contingencies. Other things to keep in mind: - This is a far cry from a 'perfect' proposal. In fact, I will go as far as saying that there is nothing like a perfect proposal. I look back at the writing and laugh to myself because I realise how little I knew back then. I cringe at the writing, the claims I made, basically at everything. But that's the point. You aren't expected to know everything about research. That's what a PhD will train you for. Even after that, you won't know everything, but that is a different story. Point is: you need to do/show enough to convince the evaluators that you have the skills and the know-how to execute this project. And that you will refine/revise things along the way! - Your final PhD thesis WILL DEVIATE MASSIVELY from the proposal, so don't be too precious about it. Why? Because you only truly understand how to frame and execute a piece of research during the course of a PhD (and through good supervision) Good luck!

After securing over $2M in research funding and reviewing 100+ proposals, I've identified the exact elements that make reviewers stop, pay attention, and champion your work. How to write a research proposal that gets funded: (7 moves that make yours stand out) 1. Frame the Problem • Show real-world impact • State one clear issue • Use simple language 2. Command the Literature • Challenge old assumptions • Connect past to present • Map key research gaps 3. Clear Methods • Match tools to questions • Detail data collection • Plan for problems 4. Require Resources Right • List exact tools + people needed • Budget precisely • Show feasibility 5. Map the Timeline • Set clear milestones • Break into phases • Add buffer weeks 6. Style the Writing • Make it scannable • Lead with impact • Cut jargon 7. Follow the Format • Follow guidelines exactly • Check every citation • Submit early Want to know the secret? Good proposals tell stories. Great proposals solve problems. Get my FREE guide from: https://lnkd.in/eev8U5K5 What's your biggest proposal writing challenge? Share it below ⬇️ #phd #research #proposals

The job of a PhD student is solving a set of difficult problems over several years. But here’s the part we often skip—validating the problem itself. In academia, we tend to validate our solutions, not our problems. Many projects start with: “Here’s what the literature says.” But real impact begins with a different question: “Is this a real problem worth spending years on?” There’s a quote often attributed to Einstein that captures the idea: “If I had an hour to solve a problem, I’d spend 55 minutes understanding the problem and 5 minutes on the solution.” To ensure that a research problem is real, relevant, valuable, and future-aligned before investing time in designing solutions, I ask PhD students to use a Problem Validation Framework comprised of the following stages: 1.      Reality Check – Is this a real problem? 2.      Worthiness Check – Is it worth investigating? 3.      Solvability Gate – Is this problem solvable? 4.      Startup Scan – Are innovators trying to solve it? 5.      Future Alignment – Does this address a future-oriented need? If any Fail, then we must refine, narrow, or redefine the problem before proceeding. Then I encourage the student to combine Stages 1–5 into a one-page Research Value Proposition (Why I should be spending several years working on this problem?). If PhD students validate the problem first, everything that follows—methods, data, solutions—becomes sharper, more relevant, and more impactful. What do you think? How does this framework align with the way you approach research problems?