Easy to create.
Take a quick photo or video, add the details, and move on. When the process changes, update the step without starting over.
For the people who make things.
Work instructions
that improve
with every job.
The approach
Useful instructions.
Less effort to keep them that way.
The goal is to make instructions easy to create, use, and keep current as part of everyday work.
Easy on the shop floor.
Open the job for current steps, photos, and files. At check-in, see what changed since your last visit. If something doesn’t work, send a quick note, photo, or video.
Easy to review and keep current.
Feedback comes with the job and step attached. Review the fix, publish the approved change, and keep a clear revision history.
Easy to get up and running.
Open a browser on your phone, tablet, or computer. Use the instructions you already have. No heavyweight install. The goal: get going in hours, not weeks, with less searching, explaining, and rework.
These are the design goals I’m testing with manufacturers before building Factryon.
Why the loop matters
Don’t solve the same
problem twice.
Instructions don’t always match the work. An operator adjusts something to keep production moving, but the fix goes unrecorded. Next time, someone solves it again, perhaps differently—or repeats an unchecked workaround.
Capture the adjustment, review the fix, and give the next person an approved approach.
Example: the part doesn’t fit the fixture
Following the instructions, an operator finds the part won’t fit in the fixture. They modify it to keep working. The part now fits; the change still needs review.
-
Capture the workaround
Proposed fix“Modified the fixture so the part fits.” A note and photo, attached to the step.
-
Review the fix
Check the fit and clamping. Approve the change—or send it back.
-
Update instructions
Approved stepUpdate the fixture photo and setup step. Keep the revision history.
-
The next job
At check-in, see the revised setup. Flag any new issues.
New issues go back through the same loop.
A note from Blake
Let’s start with
how your shop works.
Blake WileyMechanical engineer · Exploring Factryon
I’m a mechanical engineer working in manufacturing. I’ve seen how easily instructions fall behind the work.
Before building Factryon, I want to hear how your shop handles instructions and process changes—what works, what gets frustrating, and what you’ve tried.
Tell me about the last workaround.
Share a fix your team made and how it reached the next person. A 15-minute conversation or a few emails is enough to start.