The Standing Row
A four week AI practice for working instructors. One task. One colleague. About a hundred minutes total, and you can run every phase of it on a free chatbot.
Why this kit exists
Seventy seven percent of faculty now use AI in their teaching. Seventeen percent describe themselves as advanced or expert. Those two numbers came out of the same survey, of the same eighteen thousand instructors, in the same month.
Sixty points of daylight between holding the tool and being good with it. That gap is not an access problem, because everyone has access. It is a practice problem, and practice is the one thing a ninety minute August workshop cannot deliver.
The evidence, in two lines.
Digital Education Council, AI in Higher Education Survey 2026 (July 2026, 45,398 respondents across 35 countries, 18,114 of them faculty): faculty AI use 77 percent, student AI use 88 percent, both up 16 points year over year. Advanced or expert faculty users: 17 percent. Students who believe their instructor is equipped to guide AI use: 29 percent globally, 17 percent in the US and Canada.
Darling Hammond, Hyler and Gardner (2017), Learning Policy Institute, on the seven elements of effective professional development: strong programs engage teachers “over weeks, months, or even academic years, rather than in short, one off workshops.” Sustained duration, coaching, and collaboration are three of the seven. The August in service day has none of them.
A farmer who tries to fix the whole field in one season fixes nothing. He picks one row, works it until it produces, then starts the row next to it. Same idea here. Four weeks, one task, one witness.
How to use this kit. Work one phase per week. Type directly into the fields, they save nothing and send nothing, so use Copy Everything at the bottom when you are done and paste it wherever you keep your notes.
Pick the row
Most faculty pick wrong here. They pick the ambitious project, the whole course redesign, and it dies in week two because there was never a second rep. Pick the boring thing that comes back every seven days whether you are ready or not. Repetition is what turns use into practice.
Pass or redo. If your row cannot happen again next week without you scheduling it, it is a project, not a row. Go back to question one.
Run it twice on real work
Not a demo. Not a sandbox. Real student material, this week, that you actually have to deal with. Twice matters: the first run teaches you the tool, the second teaches you your own judgment, because by then you know what it gets wrong and you start steering. Fluency does not live in the prompt. It lives in the correction.
The honest rule. If the draft was not good enough to use, say so in field 6 and keep the row anyway. A rep that failed is still a rep. A rep you skipped is not.
Route the hour before you have it
This is the phase everyone skips, and skipping it is the reason AI time savings feel imaginary. You saved two hours. Where did they go? If you did not decide in advance, they went to email. They always go to email. Reclaimed time without a destination evaporates, and then you tell people AI never really saved you anything, which is not true. You just never caught it.
Three destinations that reliably move outcomes. Feedback returned the same week, while the assignment is still alive in a student’s head. Twenty unhurried minutes for the one who is slipping. The unit you have meant to rebuild for three years.
Hand it to a colleague
Show one person your rep. Walk them through what you did, what the tool got wrong, and how you caught it. Then let them push back, and write their objection down. Teaching it is how you find out whether you understand it, and you will discover the parts you have been faking inside ninety seconds. It is also the collaboration element from the research, and it is the difference between a habit that survives October and one that quietly does not.
You have finished the row when you can name what the tool gets wrong, you have a routing sentence with a date on it, and one colleague can repeat your process back to you. Not when you feel confident. Confidence is not the measure.
What happens in week five
The Standing Row fixes one row. That is the right way to start, and it is also the arithmetic problem you hit the moment it works and you want it on everything else.
Grading is one row. Rubrics are another. The discussion board, the announcement, the email you read four times, the new prep with its syllabus and outline and assessments. Doing each of those honestly is another month, and another, and another, and every one of them starts from a blank chat window that has never met your course.
That is the question the Faculty Toolkit was built to answer: thirteen purpose built tools, one Course Record you fill out once, and your own voice on every draft. Run the Standing Row first. If it works, you will know exactly which row you want next.
Pick your row today.
Just the one. The task that comes back every week whether you want it to or not. Four weeks from now you will have a practice instead of a subscription to somebody else’s opinion about AI.
Built by Professor Dean at Harvest Kernel. More free faculty kits at harvestkernel.com/resources. Want it built around your courses? Explore SeedStacking or book a free call.
Plant Ideas. Cultivate Skills. Harvest Results.