The Short Version Nobody Gives You
The process approach has students brainstorm, draft, revise, peer-edit. The product approach gives them a model text and teaches them the features of that genre. Both work. Neither works well alone. I used to run 6-week writing units where the process side consumed everything, and students would turn in polished rough drafts that still didn't know how a proper introduction functioned. Then I switched gears and saw the opposite problem — students could replicate a five-paragraph essay flawlessly but couldn't think their way through anything unfamiliar. The balance isn't an even split. It's about knowing which half to stretch and which to compress depending on what your students actually lack. Start by diagnosing. Before you launch a unit, give your students a low-stakes writing sample — an opinion piece, a summary, whatever matches your curriculum — and look at what they can do without help. If their sentences are structurally sound but they don't know how to organize ideas, lean product. If they have content but their grammar and sentence structure are scattered, lean process. You'll be adjusting this calibration throughout the unit, not just at the start. Here's the practical workflow I use now instead of the one that burned me out for years. Week one is almost entirely process. Students generate ideas through freewriting and discussion, then I give them a model text — a published article or a strong student example — and we do a structured analysis of how that text works. Not a lecture. We look at the topic sentence placement, the evidence integration, the conclusion strategy. I've found that having students annotate a real piece before they write their own reduces the product-phase confusion significantly. By the end of week one, they have an idea and a blueprint.
Week two is drafting and revising. This is where the process side carries the weight. Students write a first draft. Then they swap. The peer review template I use forces them to comment on specific elements rather than vague impressions — "Where is the main claim?" "Is there evidence here?" "What part feels unclear?" — which saves about 20 minutes per class compared to unstructured peer review and actually catches problems instead of just confirming them. After peer feedback, they revise. Then they submit a second draft that I assess against the same rubric we used during the model analysis phase. The trap most teachers fall into is treating revision as optional polishing. It isn't. Revision is where the learning happens. When students rewrite based on feedback, they're internalizing genre conventions through practice, not memorization. That's the intersection of process and product right there. But it only works if the feedback is specific and the model text was clear enough to reference during revision. I had a particularly annoying edge case last year with a group of ESL students who were strong on surface-level grammar but completely lost when it came to academic argument structure. The standard process approach wasn't helping because they didn't have the genre vocabulary to discuss what was wrong with their paragraphs. What worked was introducing mini-lessons on sentence frames and transitional phrases specifically tailored to argument writing, then giving them a fill-in scaffold for their first draft before removing it for the second. It looked rigid. It was. And it produced writing that was actually usable for their level. After three weeks, I pulled the scaffolding away and they adapted without collapsing.
One counter-intuitive thing about this: students who struggle the most with the product side often benefit from MORE process time, not less. They need more opportunities to generate ideas and talk through structure before they can produce something coherent. The ones who coast on ideas but can't write well are the ones who need tighter product instruction — model texts, explicit teaching of conventions, direct feedback on form. Don't assume process time is the universal remedy. Another thing people miss is that the product approach doesn't require you to abandon student voice. A common misconception is that teaching genre conventions silences students. It doesn't. Students have plenty to say. They just often lack the structural tools to say it in a way that reads clearly. The product phase gives them those tools. The process phase ensures the tools are being used for something they actually want to communicate. Here's where the method breaks down. If your class has widely varying proficiency levels — and most of them do — a single model text won't serve everyone equally. I've found that providing tiered model texts, one at a slightly higher level and one at a slightly lower level for the same assignment, helps without singling anyone out. You just present both and let students choose which one they analyze first. The stronger writers will naturally gravitate toward the harder text anyway.
Get the Full Details
The rubric matters more than you'd think. A process-heavy rubric focuses on effort, revision cycles, and draft quality. A product-heavy rubric focuses on the final text against genre criteria. A balanced rubric weights both — maybe 40 percent on the revision process, 60 percent on the final product, with specific criteria for each. Adjust those numbers based on what your institution values and what your students need most. There's no universal correct ratio. Assessment timing is another detail people overlook. If you only grade the final draft, you're measuring product exclusively and ignoring the process gains. If you only grade the drafts, students lose motivation to polish. I grade the process through tracked revisions — students submit a brief reflection with each draft explaining what changed and why — and I grade the product through the final submission. The reflection itself becomes a learning tool because students have to articulate their own thinking about their writing changes. There's no download or template that fixes this. The framework is simple enough that most writing programs already have something close to it built in. What actually determines whether it works is your willingness to adjust the balance mid-unit based on what you observe, not your adherence to a preset schedule. I used to plan three weeks of process and three weeks of product and stick to it rigidly. Now I spend the first two days of any unit watching my students write and deciding where they actually are. It takes less planning overall and produces better results. The initial investment in diagnosis pays off because you stop wasting time on instruction your students don't need.
The biggest bottleneck in this approach is time. Multiple drafts, peer review, model analysis — it all requires class periods. If you're working with a tight schedule, you compress by combining the model analysis and the idea generation into the same session. Have students read the model while they brainstorm, and use the model's structure as the organizing principle for their notes. It saves a day and keeps both approaches active simultaneously rather than treating them as separate phases. Another honest limitation: this method assumes students have some baseline reading ability. If your students can't parse complex texts, the product side of the equation falls apart because they can't analyze the model. In those cases, you spend more time on reading comprehension before you even touch writing instruction. That's not a failure of the process-product balance. That's just the reality of what needs to happen first. No amount of balancing will fix a foundational literacy gap. What I've learned after years of doing this is that the balance is never static. Some units need more product focus. Some need more process. The diagnostic piece at the beginning tells you which direction to lean, and the mid-unit adjustments keep you from drifting too far in either direction. The method itself is straightforward. Execution is where most people struggle, usually because they apply it the same way every time regardless of what their current students need.
If you're trying this for the first time, start small. Pick one unit, not your entire curriculum. Run the diagnostic. Teach the model text. Let students draft and revise with specific feedback. Grade both process and product. Then evaluate what worked and what didn't before adjusting your balance for the next unit. The first iteration will feel clunky. The fifth one will feel routine. The key is actually doing the diagnostic instead of assuming you know where your students stand before you've seen them write.
