Professional Documents
Culture Documents
Be Specific Means That You Must Prepare Yourself For In-Depth
Be Specific Means That You Must Prepare Yourself For In-Depth
Be Specific Means That You Must Prepare Yourself For In-Depth
The goal of using the IMRaD format is to present facts objectively, demonstrating a genuine interest
and care in developing new understanding about a topic; when using this format, you don’t explicitly
state an argument or opinion, but rather, you rely on collected data and previously researched
information in order to make a claim.
While there are nuances and adjustments that would be made to the following document types, the
IMRaD format is the foundational structure many research-driven documents:
Grants
Proposals
Recommendation reports
Plans (such as an integrated marketing plan or project management plan)
1. Introduction: Address the problem at hand, identifying what the source in conflict is and
why there are multiple ways of looking at the issue;
2. Opposing View: Identify the overarching view of your component. If your opponent’s view
is complex (this will be determined by the topic at hand), you may wish to just give a brief
synopsis at this point, then clarify later. If your opponent’s view is easily explained in two
ore three paragraphs, go ahead and describe it in it’s entirety.
3. Validation of Opponent’s View: As a way to show respect an understanding, point out why
your opponent’s view is logical. State the view as you understand it and how you recognize
why someone could feel or think the way they do.
4. Your Position: After clarifying that you understand their perspective, shift politely to
suggest what your view is on the matter. Again, if your view is complex, simply state the
overarching point in 1 – 3 paragraphs.
5. Validation of Your Position: Elaborate now on why your position also makes sense.
Provide convincing evidence and sound reasoning as to why your argument should also be
considered. While you may be trying to persuade your reader that your idea is better than
theirs, don’t explicitly state that or you’ll often lose the respect and mutual understanding
you’re working towards.
6. Argument Back-and-Forth: If the problem/issue at hand is sufficiently complex that it
would help your reader to follow the argumentation by taking the argument in broken-down
segments, move back and forth between their sub-arguments and your sub-arguments, always
validating their point of view while showing convincing evidence as to why your point of
view is also very strong.
7. Benefits of Your Position: As you conclude, summarize your position, moving your reader
towards knowing why that position is beneficial in some way.
While you may or may not convince a person that you are right when arguing in the
Rogerian method, the goal is to at least show that you have compelling reasons why
someone should respect your opinion; but if you give enough convincing evidence, you
may just change their mind!
Rogerian theorist Douglas Brent has stated that it’s important to not be too prescriptive
when writing in the Rogerian method. There isn’t a precise step-by-step formula,
though it may help to look at the steps below to think about how you move from
problem to opposing position to your position to conclusion.
Example of the Rogerian Method
Imagine you are writing a paper about freedom of religion and you hold the view that
religion should be permitted to be openly practiced in public schools and government-
run organizations. You have opponents, however, that claim there should be a strict
separation of church and state and that, especially in schools, discussing or practicing
religions marginalizes groups and may make children and other groups susceptible to
being taught a belief structure in a place that should be religiously neutral.
In a case like this, your goal would be to recognize your opponent’s viewpoints, stating
an understanding of the issues they perceive with allowing religious perspectives to be
shared freely in schools. You would validate their opinion through anecdotes,
interviews, and other primary and secondary research. You would then position
yourself to state your opinion, giving evidence that may draw from similar types of
sources. While you are giving equal weight to each argument, you are making a
rhetorical move towards your opinion as you finish with your opinion and the ultimate
benefits of your position.
1. Buffer
2. Reasons
3. Bad News
4. Closing
The bad news is an emergency or the information is critically important (if people or
something else is in danger, get straight to the point);
The bad news is expected (like when a person is being told they didn’t get a job for which
there was a great deal of competition);
The situation is either very common or the seriousness of the situation is low (like when
cancelling a company picnic); or
The recipient would prefer to just hear the bad news quickly (like when you are admitting to
them that you made a mistake).
See the graphic below for a comparison of when to use the direct method vs. the
indirect method:
How Does the InDirect Method Work?
Following the four basic steps listed above (and inserting a fifth, apology if necessary),
use these guidelines for writing each section, in the following order:
Use a buffer. Put any good news or, at least, the best news possible right up front. Send
a positive message, when possible, to start. Also, consider doing the following:
give compliments when appropriate;
show appreciation for the person or group of people;
make statements that you think both you and they will agree upon;
provide facts (which will make your news seem more reasonable);
show understanding and empathy.
Apologize (if necessary). Apologize if a serious error has occurred, but only if the problem
is, truly, an error. Don’t apologize for things that are beyond the control of a single
person or department (like economic downturns or product failures). While apologies
for errors can significantly help repair a damaged relationship, apologies in advance of
bad news where no real blame is warranted can minimize the effectiveness of
introducing bad news—in fact, it can make the bad news seem worse.
Give reasons. People want to know why bad news happens. When there are budget cuts,
layoffs, product recalls, required overtime, etc., people want rational explanations as to
the reasoning behind it. Cite benefits first, if there are any, and then provide company
policies and new or developing laws. When giving reasons, use positive words, and be
sure to explain how you are being fair to all within the company or situation.
Cushion bad news. Position the bad news within paragraphs that are surrounded by
sentences with other positive comments or explanations. The goal isn’t to hide the
information, but to make it seem less of an emphasis. Consider using passive voice,
highlight the positive, imply refusals if possible, and suggest a compromise or
alternative solution for the person receiving the news.
Close pleasantly. Avoid leaving a bad news message on a sour note. Be polite, wish
people well, provide positive outlooks, and/or offer freebies or incentives when
possible.
1. Topic: State your topic and your purpose for writing the proposal.
2. Paradigm: Describe the current state or understanding as your audience knows it.
3. Gap: Identify the gap in knowledge of practice as the current paradigm sees it. Show what is
missing (this is essentially a problem statement).
4. Forecast:Forecast the organization of the proposal so that your reader knows exactly what to
expect. Then follow that order throughout the proposal.
5. Research: Provide detailed explanation of the research you will conduct to learn more about
the problem/gap and the solution.
6. Proposition: Propose something new, based on your research, that fills the gap or solves the
problem.
With those six basic components in mind, most proposals, especially ones that require
a great deal of formality, research, planning, and presentation, require much more
depth and the organizational structure can include up to 14 or more different
sections/components. If you’re looking for how to write a full, in-depth proposal,
include the following fourteen sections and follow the order provided below:
1. Transmittal Letter
2. Cover/Title Page
3. Executive Summary
4. Table of Contents
5. List of Figures
6. Introduction
7. Project/Deliverable Description
8. Methodologies
9. Timeline
10. Budget
11. Cost/Benefit Analysis
12. Qualifications
13. Conclusion
14. References
15. Appendices
Transmittal Letter
Transmittal letters are a courtesy and a formality. They are written in professional
business letter format and they are addressed to the person or review committee that you
are sending the proposal to. Your transmittal letter should include a brief introduction
that introduces yourself and the purpose for the proposal. The letter will usually
include a very brief (one or two paragraphs) description of the project you are
proposing. The transmittal letter should also include some kind of concluding
statement, usually providing you contact information and a statement about being able
to answer any further questions about the proposal or project.
Table of Contents
Properly designed proposals included a table of contents. Even for simple projects,
proposals end up being a minimum of 15 – 20 pages. It is important that your proposal
is organized and that readers can quickly find the information they are looking for. If
the accountants only need to see the proposed budget, for example, they should be
able to quickly find the page it is on.
Introduction
Introductions are best if they are kept short and to the point. If you need to introduce
yourself, you may, but make it brief. The primary purpose of the introduction, though,
is to state your project and its purpose. This is your first chance to really be persuasive,
so it is important that you really make it sound like the project you are proposing is
important. This means you need to
1) Introduce your topic
2) Provide a problem statement
3) Offer a quick solution to the problem
One of the greatest pitfalls in proposal writing is failing to clearly indicate that there is
an actual problem to begin with that is worth solving. Remember from above that
proposals are written to solve problems. So, for example, if you are a manager of a
branch of a nationwide company, and you want to propose to your superiors that you
need to relocate your store to another building, you’ll need to tell them 1) that you
propose the move the building, 2) that the building needs to be moved because its
location hinders growth (problem statement), and 3) that you have a location in mind
that will improve growth opportunities.
Regardless of what your proposal is about, however, you MUST have a problem
statement and solution in the introduction. If this isn’t clear and to the point, your
chances of someone reading the rest of the proposal become dim.
Methodologies
After describing the details of your project, you now how the chance to write how you
will be completing your project. Take your sections and descriptions from the
project/deliverables section and describe, in detail, how you will go about obtaining the
information, permissions, and other tools to complete the project. You may even need
to describe fundraising plans if more money is needed to complete the project.
One of the biggest pitfalls in the methods section is stating new components to your
project that were not described earlier, the project/deliverables description. Avoid
stating new information about the project here. Rather, focus entirely on how you will
research, plan, work through, and execute the project that was described earlier. If you
find yourself realizing that you didn’t explain something in the previous section of the
proposal, go back and include it there. Proposal reviewers hate nothing more than
getting new surprises along the way. If new pieces of the project keep popping up in
the proposal, they’ll start to wonder if you’ve thought this all the way through and if you
know how much is really entailed in the project.
With that in mind, it is important that you are very specific about your methods.
Describe, in detail, your research, if you will be interviewing people, who you will be
interviewing, how you will create or design something, who you will consult, and so
forth.
Timeline
The timeline, really, is an extension of your methods. But for clarity and organization’s
sake, the timeline usually gets a section of its own. Reviewers will need to know when
you will complete different benchmarks in the project and they will need to know if
you’ve planned ample time between segments. Mostly, they need something to follow
up with you on. A timeline is good for you, too, as it will help you keep on pace and
keep organized. Think creatively about how best to visually display your timeline. Is a
Gantt chart most appropriate? Or maybe a table? Or a linear timeline? Whatever you
choose, make sure that it is clear what will happen when and who will be involved at
various points.
Budget
To some extent, it is possible that some of your budget will show up in the methods
section, but only to the point where you describe how you will fundraise. In this section,
you need to outline every possible cost you can think of. You don’t need to
describe how you’ll get the money (usually the organizations you propose to offer the
money based on approval of the proposal and the budget proposed) unless your
proposal is, specifically, about raising money. But you need to be thoughtful of every
possible cost. Nothing is worse than getting a proposal approved then realizing that it
will cost you more than what you were approved to spend.
Cost/Benefit Analysis
Cost and benefit analyses aren’t a requirement for many proposals, particularly for
projects that don’t require a lot of money to complete. However, you may find yourself
proposing something that is controversial or that otherwise costs a lot of money.
Besides stating a very persuasive problem statement in your introduction, you may
need to elaborate on why this particular project is worth the money being spend. In
order to be persuasive, focus on all stakeholders; point to how many people,
organizations, or other entities will benefit from this. If there are risks, state them, but
frame them in a way that suggests the cost will likely outweigh the risks. Remember
that proposals, more than most documents, are persuasive documents and it is
important that you frame everything in a way that makes your project sound very, very
important. But, of course, don’t overdo it.
Qualifications
Many times you will be writing proposals to people you don’t know. But even if you do
know the person or persons in charge of reviewing your proposal, it is important that
you sound qualified. In the field of rhetoric, this is called ethos, which refers to your
credibility. Recognize that reviewers will be asking in their head as they read your
proposal, “but why this person? Are they capable?”
Provide as much information as you think is important to build your credibility. Avoid
anything that makes you sound less qualified. Some proposal reviewers will require
that you state your credentials, including college degrees, work experience, knowledge,
and even resumes and sample work. Make sure you know how much information
they’ll want and need.
Conclusion
Every document needs a beginning, a middle, and a conclusion. Unfortunately,
conclusions are often forgotten. In your conclusion, you need to restate the problem
statement, reminding the reviewers how important this project is. But you also will
need to provide a request for approval (so that it is clear you are hoping to obtain
such). Also, you’ll need need to let reviewers know how to contact you if they need
further information from you. Conclusions aren’t just busy work to polish off your
document; they are a courtesy, which makes your proposal more persuasive. Andy
they provide valuable information about getting a response and getting in contact with
you. Without a conclusion, you may leave some unwanted ambiguity in the proposals’
scope.
References
Be sure to cite all secondary research used for the development of your project and
proposal. While APA format is the most common citation format for proposals, you
may need to follow a different style depending on your organization, course
instructions, or other expectations. Regardless, it’s important that you cite sources
according to a recognized format and that you ethically give credit to all ideas and
direct quotes used.
Appendices
While not all proposals will need appendices, it is possible that yours might. Consider
what information your reviewers may want that doesn’t readily fit into other sections of
your proposal. You may need to include balance sheets, for example, that would take
up too much space in the budget section. Or, you may need to include drawings that
don’t really fit naturally into the project/deliverables description. If you do choose to
include appendices, however, make sure that you mention them earlier in the proposal.
You might state in the budget section, for example, something like this: “For further
financial information, please refer to the balance sheets in Appendix A.”