Advice: In-Plant Outcomes Program

In-plant print for teaching and research: the four build disciplines.

The full build detail behind the four Educator Capacity modules, written for the education in-plant. Each one is work you can start without waiting for anyone, and each one ends in a number you can post.

The Educator Capacity playbook names four modules and what each one proves. This is the build detail for all four: what the work actually involves once you decide to start.

Teachers, faculty, department leaders and researchers all send work to the shop, and each of them measures it on how little of their day it costs. These four modules are the shop-side work that makes it cost less. All four can involve a purchase, and every one of them starts with something you can do before any of that.

Module 01

Make the portal the default path for every submitter

Start with the recurring jobs that generate the most follow-up, because those are the ones where a template pays every cycle. A course pack, a class set, a lab manual, a syllabus run: build an intake template for each that captures everything the shop needs to run it without chasing anybody. File, quantity, due date, delivery method, service class, finishing, billing code.

Make service classification a required field at intake rather than a preference, and publish what each class actually promises. An instructor choosing Rush should be able to see what Rush means before choosing it, and the shop should be able to hold that promise because the class was chosen deliberately.

The point is not to make submitters follow a process. It is to make the supported path the easiest one available, so that following it stops being a decision. A portal that is harder than emailing a PDF will lose to emailing a PDF every single time, and it should.

Then add the visibility layer, because half the follow-up is not about submitting at all. Confirmation on receipt, status while it runs, a notification when it is ready. An instructor who can see where a class set is does not call to ask.

Proof points

Bad submission rate, status inquiry volume.

The test

Take the one recurring job that creates the most rework, build its template, and route it through the new path for a term. The number is how many submissions came back for missing pieces, before and after.

Module 02

Close the loop with smart-locker delivery

Walk the campus or the district for the places people already pass through. Faculty office buildings, library entrances, the main building lobby, residence hall mail rooms. Those are the locker sites, and the test of a site is whether someone reaches it without making a trip.

Deploy the network with notification and access control integration, so a "ready" status in the shop triggers placement and tells the recipient automatically. Delivery should happen without the submitter initiating anything, because the moment they have to ask, you have handed the day back to them in the worst possible form.

For a district rather than a campus, the same logic runs on the courier route instead of on foot: the locker sits where the run already stops, not where a new stop would have to be added.

Build chain of custody records on any locker holding student data, and keep that record automatic. A locker that logs who opened it and when is a governance asset. One that does not is a cupboard.

Proof points

Locker checkout cycle time, share of delivered volume routed through lockers.

The test

Route one building's finished work through a single locker bank. The number is the time from job finished to job collected, before and after.

Module 03

Absorb the mailings that go outside

Build the mailing capability the institution keeps buying elsewhere: presort processing, CASS-certified address verification, NCOA on every cycle, Intelligent Mail Barcode compliance, and variable data composition tied to the student information system and to HR data.

Handle the regulated cases properly, because they are most of the volume worth having. FERPA on anything carrying student records, and HIPAA-compliant handling wherever campus health data is involved. Getting that right is what makes an office willing to send you the file at all.

Then go after the recurring cycles that routinely go outside: open enrollment, bursar statements, financial aid notices, enrollment confirmations, family communications. Recurring is the word that matters, because a capability that pays once a year pays slowly, and one that pays every cycle compounds.

Start with a single cycle rather than the whole calendar. One mailing produced in house, with the postage and the undeliverable rate measured, is a proposal. A plan to absorb everything is a wish.

Proof points

Automated mailing volume against baseline, postage saved per cycle.

The test

Take one recurring mailing that currently goes outside and run a single cycle in house. The number is what the postage came to, against what that cycle cost before.

Module 04

Carry the specialty workflows the coalition demands

Audit the coalition before you buy anything, because the specialty list is different at every institution and it is knowable by asking. What do teaching, research and the professional schools each need that they currently get somewhere else.

The usual answers: wide format posters for research and conference work, perfect-bind dissertation and thesis workflows, grant proposal binding on a deadline nobody controls, case readers, residency handbooks, journal volumes, and bound course readers where licensing allows.

Document each one as a template in the portal so the submitter does not have to know the specification. A researcher should not need to know the bind method or the stock weight to order a dissertation. That is the shop's knowledge, and it belongs in the template rather than in a conversation.

This is the module that most directly answers why the work leaves. Often it leaves because nobody knew the shop could do it, which is a visibility problem the template quietly solves.

Proof points

First-time-right rate, specialty turnaround by workflow type.

The test

Pick the one specialty format that leaves most often, build it as a template, and run a term. The number is how much of that format came back right the first time.

Back to the playbook

Pick one module and work it to a posted number.

This is the build detail for the Educator Capacity playbook. The playbook itself carries the scorecard those proof points post to, and the step that turns a number into a conversation with the group that felt the friction. When you want another set of eyes on it, that is the In-Plant Outcomes Program.