Structure arguments via CARS model (territory → niche → contribution)
Acknowledge limitations honestly, early
Responding to Reviews
Feedback
Response Strategy
"Missing related work"
Add citations, explain positioning
"Claims not supported"
Add evidence or soften claims
"Unclear methodology"
Expand description
"Limited evaluation"
Add studies or acknowledge
Response Letter Template
Dear Editors and Reviewers,
Thank you for your thoughtful feedback on our manuscript "[Title]".
We have carefully addressed all comments. Below we detail our responses.
Major changes include:
1. [Summary of major change 1]
2. [Summary of major change 2]
---
## Response to Reviewer 1
### R1.1: "[Direct quote of concern]"
We appreciate this observation. [How you addressed it].
Changes made:
- Section X, paragraph Y: [quoted new text or description]
---
## Response to Reviewer 2
[Same pattern]
Venue-Specific Templates
ACM CHI Paper Types
Type
Length
Purpose
Acceptance Rate
Full Paper
7,500 words
Complete research contribution
~25%
Late-Breaking Work
3,000 words
Preliminary findings
~40%
Workshop Paper
2,000-4,000 words
Community discussion
Varies
Case Study
7,500 words
In-depth design exploration
~25%
CHI Contribution Types
Type
Description
Evidence Needed
Empirical
New knowledge about people/technology
User study, data
Artifact
Novel system, tool, or interaction
Implementation, evaluation
Methodological
New way to study/design
Comparison to existing methods
Theoretical
New framework or model
Grounding, application
Dataset
New resource for community
Description, access, ethics
Survey
Comprehensive literature synthesis
Systematic review
CHI Writing Tips
Do
Don't
Use participant quotes (P1, P2...)
Generalize without evidence
State contribution type explicitly
Assume readers will infer
Include representative figures
Over-rely on text
Acknowledge limitations early
Hide weaknesses
Cite recent CHI papers
Ignore venue norms
HBR Article Types
Type
Length
Purpose
Feature Article
3,000-4,000 words
In-depth analysis
Spotlight
2,500-3,000 words
Focused insight
Big Idea
2,000-2,500 words
Provocative argument
Case Study
2,500-3,000 words
Company narrative
Web Article
800-1,200 words
Quick insight
HBR Writing Style Translation
Academic Style
HBR Style
"The study found that..."
"When we surveyed 300 executives..."
"Participants reported..."
"One CEO told us..."
"Hypothesis 1 was supported"
"The data confirms what many leaders suspect:"
"Implications include..."
"Here's what this means for your organization:"
Passive voice
Active, direct voice
HBR Submission Tips
Pitch first — HBR prefers pitches before full drafts
Lead with "What's new" — Why now? What's changed?
Name your framework — Memorable concepts spread
Include real companies — Real examples work better than anonymous
Write for the airport — Busy executive on a flight should get value
5-Phase Drafting Process
Phase 1: Preparation (1-2 weeks)
Step
Output
Literature immersion
Annotated bibliography
Gap identification
2-3 sentence gap statement
Contribution clarity
Explicit contribution list
Outline creation
Section-by-section plan
Figure sketches
Hand-drawn or rough diagrams
Phase 2: Rough Draft (1-2 weeks)
Don't edit while writing — Separate generation from editing
Start with what you know — Often Methods or Results, not Intro
Use placeholder brackets — [CITE Smith here], [need better transition]
Embrace imperfection — First drafts are meant to be messy