Is it moral to propose work that's already partly done?
Academia involves a lot of proposals and approvals and it can save effort to combine them. A grant including work that's already been started is easier to satisfy. The applications I receive for independent study describe work that students have already started on. My grandfather used to tell me about submitting the same paper in several courses in his student days.
To generalize between these cases, failing to clarify the amount of work already done is a common tactic among researchers. What moral principles guide such actions? Are some specific techniques kosher and others off limits?
ethics working-time research-proposal
add a comment |
Academia involves a lot of proposals and approvals and it can save effort to combine them. A grant including work that's already been started is easier to satisfy. The applications I receive for independent study describe work that students have already started on. My grandfather used to tell me about submitting the same paper in several courses in his student days.
To generalize between these cases, failing to clarify the amount of work already done is a common tactic among researchers. What moral principles guide such actions? Are some specific techniques kosher and others off limits?
ethics working-time research-proposal
add a comment |
Academia involves a lot of proposals and approvals and it can save effort to combine them. A grant including work that's already been started is easier to satisfy. The applications I receive for independent study describe work that students have already started on. My grandfather used to tell me about submitting the same paper in several courses in his student days.
To generalize between these cases, failing to clarify the amount of work already done is a common tactic among researchers. What moral principles guide such actions? Are some specific techniques kosher and others off limits?
ethics working-time research-proposal
Academia involves a lot of proposals and approvals and it can save effort to combine them. A grant including work that's already been started is easier to satisfy. The applications I receive for independent study describe work that students have already started on. My grandfather used to tell me about submitting the same paper in several courses in his student days.
To generalize between these cases, failing to clarify the amount of work already done is a common tactic among researchers. What moral principles guide such actions? Are some specific techniques kosher and others off limits?
ethics working-time research-proposal
ethics working-time research-proposal
asked 5 hours ago
Aaron Brick
2,80411229
2,80411229
add a comment |
add a comment |
2 Answers
2
active
oldest
votes
Let me make two points. The first is that in order to write a research proposal you have to understand the area well enough to describe it. This implies that you have already explored it and have done some work to get it ready for submission. Even after you submit, you aren't likely to just forget about the problem until you get funding. The alternative would be just saying random things in research proposals. So, there is no alternative, in my view, to making proposals on partially done work.
The second point is at the other extreme. I've heard that some very successful researchers, though the stories may be apocryphal, work like this. Do research problem A. After you are nearly done, write a grant request for problem A and if it is funded, write the report but use the funds to do problem B, that wasn't mentioned in the grant request. If B is successful, write a grant for it (B) so that you have funding for problem C, etc.
You might question the ethics of this, but the realities are that the funders get what they funded, and the researchers get the funds they need to do research that the funders (and society) like. If you think about doing it any other way, what you wind up with is a lower success rate for funded research (hence less funds for students, etc) and lower reputations all around. That is because there is no guarantee that your initial thoughts on a research topic will bear fruit. So you try to solve more problems than you can reach conclusion on. Lower "success" doesn't serve anyone very well and turns research into a sort of jungle - eat or be eaten - situation.
But, I'll also note that if you apply for a grant for a piece of work and tell the funders that it is nearly done, you won't get funded. That should be pretty obvious, I think. On the other hand, if you ask for funding for a wild idea you just had, you won't get funded (unless you are already a superstar). So there is a tension here. So maybe there is a sort of "sweet spot" in which it all fits. But certainly the work is partly done before funding is contemplated by either the researchers or funders.
Even if the real situation isn't quite as extreme as this, a researcher funded for A and working on A would be foolish to completely ignore problem B if it occurred along the way. S/he would be wise to follow the threads for at least a while to see what potential there might be. People, including researchers, aren't machines that work on only one thing at a time to the (mental) exclusion of all else.
The reality is somewhere in between these extremes, though both extremes exist, I'm pretty sure.
add a comment |
The answer might depend on the field, but (at leat to me) one borderline is that you can not sell the same piece of work twice.
E.g. you can not apply for a grant whilst you have more or less the same work packages in an other grant application (or running grant). The same holds true for students work: You can d osubsequent work steps in one larger area, but you must clearly distinguish which part of the work has been done for which course / part of the exam.
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "415"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
noCode: true, onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2facademia.stackexchange.com%2fquestions%2f122339%2fis-it-moral-to-propose-work-thats-already-partly-done%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
Let me make two points. The first is that in order to write a research proposal you have to understand the area well enough to describe it. This implies that you have already explored it and have done some work to get it ready for submission. Even after you submit, you aren't likely to just forget about the problem until you get funding. The alternative would be just saying random things in research proposals. So, there is no alternative, in my view, to making proposals on partially done work.
The second point is at the other extreme. I've heard that some very successful researchers, though the stories may be apocryphal, work like this. Do research problem A. After you are nearly done, write a grant request for problem A and if it is funded, write the report but use the funds to do problem B, that wasn't mentioned in the grant request. If B is successful, write a grant for it (B) so that you have funding for problem C, etc.
You might question the ethics of this, but the realities are that the funders get what they funded, and the researchers get the funds they need to do research that the funders (and society) like. If you think about doing it any other way, what you wind up with is a lower success rate for funded research (hence less funds for students, etc) and lower reputations all around. That is because there is no guarantee that your initial thoughts on a research topic will bear fruit. So you try to solve more problems than you can reach conclusion on. Lower "success" doesn't serve anyone very well and turns research into a sort of jungle - eat or be eaten - situation.
But, I'll also note that if you apply for a grant for a piece of work and tell the funders that it is nearly done, you won't get funded. That should be pretty obvious, I think. On the other hand, if you ask for funding for a wild idea you just had, you won't get funded (unless you are already a superstar). So there is a tension here. So maybe there is a sort of "sweet spot" in which it all fits. But certainly the work is partly done before funding is contemplated by either the researchers or funders.
Even if the real situation isn't quite as extreme as this, a researcher funded for A and working on A would be foolish to completely ignore problem B if it occurred along the way. S/he would be wise to follow the threads for at least a while to see what potential there might be. People, including researchers, aren't machines that work on only one thing at a time to the (mental) exclusion of all else.
The reality is somewhere in between these extremes, though both extremes exist, I'm pretty sure.
add a comment |
Let me make two points. The first is that in order to write a research proposal you have to understand the area well enough to describe it. This implies that you have already explored it and have done some work to get it ready for submission. Even after you submit, you aren't likely to just forget about the problem until you get funding. The alternative would be just saying random things in research proposals. So, there is no alternative, in my view, to making proposals on partially done work.
The second point is at the other extreme. I've heard that some very successful researchers, though the stories may be apocryphal, work like this. Do research problem A. After you are nearly done, write a grant request for problem A and if it is funded, write the report but use the funds to do problem B, that wasn't mentioned in the grant request. If B is successful, write a grant for it (B) so that you have funding for problem C, etc.
You might question the ethics of this, but the realities are that the funders get what they funded, and the researchers get the funds they need to do research that the funders (and society) like. If you think about doing it any other way, what you wind up with is a lower success rate for funded research (hence less funds for students, etc) and lower reputations all around. That is because there is no guarantee that your initial thoughts on a research topic will bear fruit. So you try to solve more problems than you can reach conclusion on. Lower "success" doesn't serve anyone very well and turns research into a sort of jungle - eat or be eaten - situation.
But, I'll also note that if you apply for a grant for a piece of work and tell the funders that it is nearly done, you won't get funded. That should be pretty obvious, I think. On the other hand, if you ask for funding for a wild idea you just had, you won't get funded (unless you are already a superstar). So there is a tension here. So maybe there is a sort of "sweet spot" in which it all fits. But certainly the work is partly done before funding is contemplated by either the researchers or funders.
Even if the real situation isn't quite as extreme as this, a researcher funded for A and working on A would be foolish to completely ignore problem B if it occurred along the way. S/he would be wise to follow the threads for at least a while to see what potential there might be. People, including researchers, aren't machines that work on only one thing at a time to the (mental) exclusion of all else.
The reality is somewhere in between these extremes, though both extremes exist, I'm pretty sure.
add a comment |
Let me make two points. The first is that in order to write a research proposal you have to understand the area well enough to describe it. This implies that you have already explored it and have done some work to get it ready for submission. Even after you submit, you aren't likely to just forget about the problem until you get funding. The alternative would be just saying random things in research proposals. So, there is no alternative, in my view, to making proposals on partially done work.
The second point is at the other extreme. I've heard that some very successful researchers, though the stories may be apocryphal, work like this. Do research problem A. After you are nearly done, write a grant request for problem A and if it is funded, write the report but use the funds to do problem B, that wasn't mentioned in the grant request. If B is successful, write a grant for it (B) so that you have funding for problem C, etc.
You might question the ethics of this, but the realities are that the funders get what they funded, and the researchers get the funds they need to do research that the funders (and society) like. If you think about doing it any other way, what you wind up with is a lower success rate for funded research (hence less funds for students, etc) and lower reputations all around. That is because there is no guarantee that your initial thoughts on a research topic will bear fruit. So you try to solve more problems than you can reach conclusion on. Lower "success" doesn't serve anyone very well and turns research into a sort of jungle - eat or be eaten - situation.
But, I'll also note that if you apply for a grant for a piece of work and tell the funders that it is nearly done, you won't get funded. That should be pretty obvious, I think. On the other hand, if you ask for funding for a wild idea you just had, you won't get funded (unless you are already a superstar). So there is a tension here. So maybe there is a sort of "sweet spot" in which it all fits. But certainly the work is partly done before funding is contemplated by either the researchers or funders.
Even if the real situation isn't quite as extreme as this, a researcher funded for A and working on A would be foolish to completely ignore problem B if it occurred along the way. S/he would be wise to follow the threads for at least a while to see what potential there might be. People, including researchers, aren't machines that work on only one thing at a time to the (mental) exclusion of all else.
The reality is somewhere in between these extremes, though both extremes exist, I'm pretty sure.
Let me make two points. The first is that in order to write a research proposal you have to understand the area well enough to describe it. This implies that you have already explored it and have done some work to get it ready for submission. Even after you submit, you aren't likely to just forget about the problem until you get funding. The alternative would be just saying random things in research proposals. So, there is no alternative, in my view, to making proposals on partially done work.
The second point is at the other extreme. I've heard that some very successful researchers, though the stories may be apocryphal, work like this. Do research problem A. After you are nearly done, write a grant request for problem A and if it is funded, write the report but use the funds to do problem B, that wasn't mentioned in the grant request. If B is successful, write a grant for it (B) so that you have funding for problem C, etc.
You might question the ethics of this, but the realities are that the funders get what they funded, and the researchers get the funds they need to do research that the funders (and society) like. If you think about doing it any other way, what you wind up with is a lower success rate for funded research (hence less funds for students, etc) and lower reputations all around. That is because there is no guarantee that your initial thoughts on a research topic will bear fruit. So you try to solve more problems than you can reach conclusion on. Lower "success" doesn't serve anyone very well and turns research into a sort of jungle - eat or be eaten - situation.
But, I'll also note that if you apply for a grant for a piece of work and tell the funders that it is nearly done, you won't get funded. That should be pretty obvious, I think. On the other hand, if you ask for funding for a wild idea you just had, you won't get funded (unless you are already a superstar). So there is a tension here. So maybe there is a sort of "sweet spot" in which it all fits. But certainly the work is partly done before funding is contemplated by either the researchers or funders.
Even if the real situation isn't quite as extreme as this, a researcher funded for A and working on A would be foolish to completely ignore problem B if it occurred along the way. S/he would be wise to follow the threads for at least a while to see what potential there might be. People, including researchers, aren't machines that work on only one thing at a time to the (mental) exclusion of all else.
The reality is somewhere in between these extremes, though both extremes exist, I'm pretty sure.
edited 48 mins ago
answered 1 hour ago
Buffy
37.4k7120192
37.4k7120192
add a comment |
add a comment |
The answer might depend on the field, but (at leat to me) one borderline is that you can not sell the same piece of work twice.
E.g. you can not apply for a grant whilst you have more or less the same work packages in an other grant application (or running grant). The same holds true for students work: You can d osubsequent work steps in one larger area, but you must clearly distinguish which part of the work has been done for which course / part of the exam.
add a comment |
The answer might depend on the field, but (at leat to me) one borderline is that you can not sell the same piece of work twice.
E.g. you can not apply for a grant whilst you have more or less the same work packages in an other grant application (or running grant). The same holds true for students work: You can d osubsequent work steps in one larger area, but you must clearly distinguish which part of the work has been done for which course / part of the exam.
add a comment |
The answer might depend on the field, but (at leat to me) one borderline is that you can not sell the same piece of work twice.
E.g. you can not apply for a grant whilst you have more or less the same work packages in an other grant application (or running grant). The same holds true for students work: You can d osubsequent work steps in one larger area, but you must clearly distinguish which part of the work has been done for which course / part of the exam.
The answer might depend on the field, but (at leat to me) one borderline is that you can not sell the same piece of work twice.
E.g. you can not apply for a grant whilst you have more or less the same work packages in an other grant application (or running grant). The same holds true for students work: You can d osubsequent work steps in one larger area, but you must clearly distinguish which part of the work has been done for which course / part of the exam.
answered 1 hour ago
OBu
11.1k22549
11.1k22549
add a comment |
add a comment |
Thanks for contributing an answer to Academia Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2facademia.stackexchange.com%2fquestions%2f122339%2fis-it-moral-to-propose-work-thats-already-partly-done%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown