The KIPP chapter in Outliers describes how an extended school schedule and a culture built around sustained effort produced measurable academic gains for students who had previously struggled in traditional school settings, tying directly back to the book's broader argument about the compounding value of accumulated practice time. For teachers designing writing rubrics, this chapter raises an interesting question: should a rubric assess only the quality of a final polished essay, or should it also credit the persistence and revision process that produced it? Schools and departments experimenting with grit-based or process-oriented rubrics often look to case studies like KIPP for a model of how sustained effort, not just innate ability, can be measured and rewarded within an academic system.

A purely product-based rubric, one that only evaluates the final essay submitted, risks rewarding students who arrive already skilled while providing little incentive or credit for students who make significant growth through revision but still fall short of top marks on a single final piece. This can inadvertently discourage the exact kind of sustained, effortful practice that both KIPP's approach and the book's broader argument suggest is central to skill development. A process-inclusive rubric, by contrast, explicitly credits evidence of revision, engagement with feedback, and improvement across drafts, which better aligns grading incentives with the kind of practice that actually builds long-term writing skill.

Designing this kind of rubric requires more structural planning than a simple final-product rubric, since it requires collecting and reviewing evidence across multiple drafts rather than assessing a single submission in isolation. Teachers need a system for tracking what changed between drafts and whether those changes reflect genuine engagement with prior feedback rather than superficial edits made to satisfy a requirement. This tracking overhead is a real cost of process-inclusive grading, and teachers considering this approach should weigh it honestly against the pedagogical benefits before committing to it across an entire course.

Building a Two-Part Rubric: Product and Process

One practical structure divides the total grade into two clearly weighted parts: a product score assessing the quality of the final essay against standard criteria, and a process score assessing evidence of meaningful revision across the drafting sequence. This structure preserves rigorous standards for the final product while still building in explicit credit for the effortful, iterative work that the KIPP chapter and the book's broader argument suggest matters just as much as raw final quality. A common weighting split gives seventy percent to the product score and thirty percent to the process score, though this ratio can be adjusted based on how much a particular course wants to emphasize growth versus final mastery.

• Define specific, observable evidence of revision rather than vague effort language
• Require students to briefly annotate what changed between drafts and why
• Weight the process score meaningfully but keep product quality the larger factor
• Avoid rewarding surface-level edits that do not reflect substantive revision
• Review process scores periodically to check they are not simply rewarding compliance

Avoiding the Pitfall of Rewarding Effort Without Substance

A common failure mode in process-based grading is rewarding effort signals that are easy to fake, such as simply requiring a certain number of drafts submitted regardless of whether meaningful revision actually occurred between them. Students quickly learn to game this kind of rubric by making superficial changes, a swapped word here, a reordered sentence there, without engaging substantively with the feedback that was meant to guide real revision. Avoiding this pitfall requires rubric language specific enough to distinguish genuine revision from cosmetic editing, such as requiring students to identify which specific piece of prior feedback they addressed and to explain briefly how their revision responds to it.

This kind of specific, evidence-based process rubric takes more upfront design work than a vague "did you revise" checkbox, but it produces a far more honest and useful signal about whether a student is actually engaging in the kind of deliberate, corrected practice that builds real skill over time. Teachers should expect some pushback from students accustomed to being rewarded for simple compliance, and clear communication about what genuine revision looks like, ideally with concrete before-and-after examples, helps set expectations appropriately from the start of a course using this kind of rubric.

Connecting Process Grading to Feedback Quality

Process-inclusive grading only works if the feedback students receive between drafts is specific enough to act on meaningfully, since a student cannot demonstrate substantive revision in response to feedback that was too vague to guide any particular change. This creates a direct link between feedback quality and the integrity of process-based grading: if feedback consists of generic comments like "needs more detail," it becomes nearly impossible to assess whether a subsequent revision genuinely responded to that feedback in any meaningful way. Teachers adopting process-based rubrics should audit their own feedback specificity alongside redesigning the rubric itself, since the two elements depend heavily on each other for the system to function as intended.

This dependency also means that process-based grading tends to work better in courses or programs already using structured, criteria-specific feedback rather than in settings where feedback has historically been brief or impressionistic. Departments considering a shift toward process-inclusive rubrics might reasonably start by first improving feedback specificity across the department, then layering in process-based grading once that foundation is solid. Attempting both changes simultaneously without adequate preparation risks confusing students and producing inconsistent results that undermine confidence in the new grading approach before it has a fair chance to prove its value.

Managing the Added Workload of Process-Based Grading

The most significant practical barrier to adopting process-inclusive rubrics is the additional grading workload involved in reviewing multiple drafts and tracking revision quality across an entire class roster, on top of the final product grading that still needs to happen. This workload increase is real and should not be understated when a department is weighing whether to adopt this kind of grading approach, particularly for teachers already managing large class sizes across multiple sections. Some schools address this by limiting process-based grading to a smaller number of key assignments each semester rather than applying it to every single piece of writing, preserving the pedagogical benefit while keeping the overall workload sustainable.

AI-assisted grading tools can meaningfully reduce this added workload by handling the more mechanical aspects of draft comparison, flagging which specific sentences or sections changed between submissions so a teacher can quickly assess whether those changes reflect substantive engagement with prior feedback rather than manually comparing full drafts side by side. This kind of support makes process-inclusive grading considerably more feasible at scale, turning what would otherwise be a prohibitively time-consuming grading approach into something a teacher managing multiple sections can realistically sustain across a full semester. For departments genuinely interested in rewarding the kind of sustained, corrected practice that both the KIPP chapter and Outliers more broadly describe as central to skill development, this kind of tooling can be the difference between a good idea on paper and a grading approach that actually survives contact with a real teaching workload.