The PhD is ultimately a writing project. The dissertation chapters, conference papers, journal articles, and grant proposals that constitute doctoral output are not reports of completed research — they are the research. The argument is not formed and then written; it is formed through writing. The evidence is not assembled and then presented; the work of assembling evidence for a written argument reveals what the evidence actually shows and what more is needed.
This has a practical consequence: the PhD candidate who waits to begin writing until the research is complete will not complete the research, because writing is how the research becomes complete. The productive orientation is to begin writing early, treat drafts as thinking tools rather than polished products, and iterate between writing and research throughout the doctoral process.
Four output types define the PhD candidate's scholarly production: dissertation chapters (the central scholarly contribution), conference papers (ideas tested publicly before formal publication), journal articles (the career-defining publication record), and grant proposals (the funding argument for future research).
Output 1: Dissertation Chapters
The dissertation chapter is the primary scholarly output of PhD education — the sustained argument, built on original research, that constitutes the independent scholarly contribution the degree requires.
The dissertation chapter writing process:
DISSERTATION CHAPTER WRITING PROCESS
Before writing:
CHAPTER ARGUMENT:
What this chapter argues: [The specific claim this chapter makes]
Why this matters for the dissertation: [How this chapter contributes to the whole]
How this advances the dissertation's primary argument: [Connection to overarching thesis]
RELATIONSHIP TO LITERATURE:
Key works this chapter builds on: [Literature it requires]
Key works this chapter challenges: [Literature it argues against or qualifies]
The gap this chapter addresses: [What wasn't known before this]
EVIDENCE REQUIRED:
What evidence is needed to establish the chapter's argument: [Specific list]
What I have: [Evidence assembled]
What I still need: [What remains to be gathered]
STRUCTURE PLAN:
Introduction: [What it establishes]
Section 1: [First major move — what it argues]
Section 2: [Second major move]
[Etc.]
Conclusion: [What it establishes and how it sets up the next chapter]
During writing:
ARGUMENT DISCIPLINE:
Every section has a specific claim it's making: [What is this section arguing?]
Evidence in this section supports that specific claim: [Is the evidence tight?]
"What would I cut if I had to?": [Forces identification of the non-essential]
WRITING BLOCKS:
Set specific daily writing targets: [Pages or words — specific, not "make progress"]
Writing happens before research reading on writing days: [Research reading expands; writing has a deadline]
ARGUMENT CHECK (end of each week):
Does the draft's argument match the plan?: [If not, is the deviation an improvement?]
Is the argument advancing or circling?: [Circling means the argument isn't clear yet]
Revision process:
AFTER ADVISOR FEEDBACK:
What the feedback says: [Advisor's main points — specific]
What I'm incorporating: [Changes I agree with and will make]
What I'm not incorporating: [With reasoning — scholarly judgment required]
What I need to clarify with my advisor: [Before revising — ambiguous feedback]
REVISION PRIORITY:
Argument-level concerns: [Changes to what the chapter claims — highest priority]
Structure-level concerns: [Changes to how the argument is organized — second]
Paragraph-level concerns: [Clarity and prose — last]
"Writing before research reading on writing days" is the discipline that protects writing time from the infinite expansion of reading. Research reading is open-ended; the literature never stops growing. If a writing day begins with reading, the writing often doesn't begin. The productive structure is: writing first, research reading second. When the writing day is allocated, writing occupies that time.
Output 2: Conference Papers
Conference papers serve a specific scholarly function distinct from dissertation chapters: they put developing ideas before a critical audience before those ideas are formally published. Conference presentation is how scholars test arguments in public, receive peer challenge, and identify weaknesses before the work goes to journal review.
The conference paper process:
CONFERENCE PAPER PROCESS
Before submitting:
WHAT I'M PRESENTING:
Core argument: [The specific claim this paper makes]
Where it fits in my dissertation: [How this connects to the larger project]
Why this conference is right for this paper: [What this audience brings]
WHAT I'M TESTING:
The part I'm most uncertain about: [What I want audience feedback on]
The objection I'm most concerned about: [Anticipated challenge]
What I'm hoping to learn: [What feedback would most help]
Abstract writing:
ABSTRACT STRUCTURE FOR CONFERENCE PAPERS:
1. The problem: [What gap in the literature this addresses]
2. My intervention: [What I argue or find]
3. The evidence or argument: [How I establish this — brief]
4. The contribution: [What this adds to the field]
Length standard: Match the conference's standard (usually 250-500 words)
Avoid: "This paper will explore" / "This paper examines"
Instead: "This paper argues" / "This paper demonstrates"
After the conference:
WHAT I LEARNED:
Feedback I received: [Specific comments from Q&A and hallway conversations]
Objections that landed: [Where the audience found genuine problems]
Objections that didn't: [Where I was prepared and the challenge was addressed]
Insights from other papers: [What other presentations taught me]
HOW THIS CHANGES MY WORK:
Changes I'm making to the argument: [In response to what I heard]
Changes I'm making to the evidence: [Additional evidence or reframing]
What I'm not changing: [Where I'm maintaining my position despite challenge]
NEXT STEP FOR THIS PAPER:
Target journal: [Where this goes next]
What needs to happen before submission: [Revisions, additional research]
Timeline: [When I'll be ready to submit]
"What objections landed" vs. "what objections didn't" distinguishes conference feedback by its scholarly significance. A conference audience will raise many objections; not all of them reveal genuine problems with the argument. The ones that land — where the presenter realizes the argument has a real weakness — require revision. The ones that didn't — where the challenge was addressed with existing evidence or argument — confirm the work's robustness. Distinguishing these honestly, rather than either incorporating all feedback (overcorrection) or defending all positions regardless of challenge (intellectual rigidity), is the scholarly judgment that conference feedback is supposed to develop.
Output 3: Journal Articles
Journal articles are the primary career credential in most academic fields. The process of writing for journals — selecting appropriate venues, understanding reviewer expectations, responding to peer review, revising and resubmitting — is a professional skill that develops throughout the PhD.
The journal article writing and submission process:
JOURNAL ARTICLE PROCESS
Selecting a target journal:
CANDIDATE JOURNALS:
[List of 3-5 journals where this paper might fit]
For each:
Scope: [What this journal publishes]
Reputation: [How the field regards this journal]
Typical article: [What published articles in this journal look like]
Turnaround time: [How long review takes]
VENUE DECISION:
Best fit for this paper: [Which journal and why]
What makes this paper right for this journal: [Specific reasons]
What the journal requires: [Specific formatting, length, scope]
Writing for the journal's audience:
WHAT THIS JOURNAL'S READERS EXPECT:
Theoretical orientation: [What theoretical tradition dominates this journal]
Methodological standards: [What rigor looks like in this venue]
Contribution type: [Empirical / Theoretical / Review / Other — what this journal values]
Literature engagement expected: [How deeply papers in this journal engage the literature]
HOW TO WRITE THE INTRODUCTION FOR THIS AUDIENCE:
What problem this journal's readers care about: [What motivates this audience]
How to frame my contribution: [For this journal's priorities]
What not to assume readers know: [What context needs to be established]
Responding to peer review:
REVIEWER FEEDBACK:
Editor's summary decision: [Accept / Major revision / Minor revision / Reject]
Reviewer 1 — Main concerns:
Concern 1: [What they said]
My response: [What I'll do]
If I disagree: [My reasoning — disagreement is appropriate if substantiated]
Reviewer 2 — Main concerns:
[Same structure]
REVISION PRINCIPLES:
Respond directly to every reviewer concern: [Even those I disagree with]
Write a response memo that explains every change: [So reviewers can verify]
When disagreeing with a reviewer: [Explain why politely and substantively]
What would change my position: [Stay open to the reviewer being right]
REVISION DOCUMENT:
Section-by-section: [What changed and where]
Corresponding to reviewer concerns: [Which change addresses which concern]
"How to frame my contribution for this journal's priorities" is the scholarly genre awareness that makes journal submission strategic rather than random. Different journals have different theoretical orientations, methodological standards, and contribution preferences. A paper that would be a strong contribution in an interpretive sociology journal requires different framing than the same paper submitted to a quantitative-methods sociology journal. Understanding the journal's priorities — from reading published papers, from editorial statements, from the scholarly community — shapes how the paper's contribution is framed without changing the underlying argument.
Output 4: Grant Proposals
Grant proposals are arguments for research funding — the claim that the proposed research is significant, original, and feasible, and that this investigator is capable of conducting it. Grant writing is a distinct genre with specific conventions and evaluation criteria.
The grant proposal writing process:
GRANT PROPOSAL WRITING PROCESS
Grant identification:
WHO FUNDS WORK LIKE MINE:
Federal agencies: [NSF / NIH / NEH / Other — with specific programs]
Private foundations: [With specific programs relevant to my work]
University fellowships: [Internal funding opportunities]
FOR EACH GRANT:
What it funds: [Research type and career stage]
Evaluation criteria: [What reviewers assess]
Recent award patterns: [What types of proposals have been funded]
Application requirements: [What's required]
Timeline: [Application deadline and award announcement]
Writing the core grant sections:
SIGNIFICANCE:
What problem does this research address?: [The scholarly or practical problem]
Why does it matter?: [Theoretical + empirical + practical importance]
What's the current state of knowledge?: [What we know and don't know]
Why now?: [Why this research is timely]
INNOVATION:
What does this research do that hasn't been done?: [Original contribution]
How is the approach new?: [Methodological or theoretical innovation]
What new knowledge will this produce?: [Specific new understanding]
APPROACH:
Research design: [Specific and feasible]
Why this method: [Why this is the right approach for this question]
Timeline: [Realistic — not optimistic]
Potential problems: [And how I'll address them — shows I've thought it through]
FEASIBILITY:
What makes me the right person to do this?: [Expertise, access, preparation]
What preliminary work do I have?: [Prior work that demonstrates capability]
What resources do I have access to?: [Data, facilities, collaborators]
After submission:
IF FUNDED:
What I committed to: [What the grant proposal promised]
How my research may evolve: [Contingency for the research going differently]
Reporting requirements: [What I owe the funder]
IF NOT FUNDED:
Review feedback received: [What reviewers said]
What I'll do with this for the resubmission: [Specific revisions]
Other venues for this proposal: [Where else this might go]
"Potential problems — and how I'll address them" is the feasibility field that reviewers specifically assess. Grant reviewers are not looking for a proposal that claims everything will go perfectly; they're looking for a researcher who has thought carefully about what might go wrong and has a plan for addressing it. "If my primary data source is unavailable, I will [alternative approach]" is more convincing than no acknowledgment of the possibility. Research proposals that don't acknowledge challenges appear naive rather than rigorous.
The PhD Candidate's Production Calendar
Academic output doesn't happen organically — it requires planning across long timescales:
The annual view: When is each dissertation chapter due? What conferences am I submitting to (and when are abstracts due)? What grants am I applying for? What journals am I targeting?
The monthly view: What writing is happening this month? What conference deadlines are coming? What review responses are due?
The weekly view: What are the specific writing targets for this week? What research activities support the writing?
The daily view: When is writing time today? What's the specific target?
Key Takeaways
-
Writing before reading on writing days. Research reading expands indefinitely; writing time must be protected.
-
Conference papers test ideas before formal publication. "What objections landed" vs. "what objections didn't" distinguishes feedback by scholarly significance.
-
Journal framing is audience-specific. The same argument requires different framing for different journals' readers and priorities.
-
Peer review response requires scholarly judgment. Responding to every concern doesn't mean incorporating every suggestion.
-
Grant proposals acknowledge potential problems. Reviewers look for researchers who have thought carefully about what might go wrong.
Conclusion
PhD candidate research-to-output across four formats: dissertation chapters (argument established before writing begins; "writing before reading on writing days" as the protected writing time discipline; revision with what I'm incorporating and what I'm not incorporating with reasoning; argument check weekly — circling means the argument isn't clear yet); conference papers (what I'm testing as the explicit feedback goal; "what objections landed vs. didn't" as the post-conference discrimination field; abstract structure: problem → intervention → evidence → contribution with "this paper argues" not "this paper explores"; next step for each paper after conference); journal articles (venue selection with scope, reputation, typical article, and turnaround; "how to frame my contribution for this journal's audience" as the genre awareness field; peer review response that responds to every concern including those I disagree with, with reasoning; revision document that maps changes to reviewer concerns); and grant proposals (significance-innovation-approach-feasibility structure; "potential problems and how I'll address them" as the feasibility field that reviewers assess; review feedback used for resubmission). The production calendar that makes writing happen: annual view of dissertation chapter deadlines and conference/grant timelines; monthly writing targets; specific daily writing time.
See also: Best Web Clipper Extensions.