Procedure Assistant

A Different Way to Capture a Procedure

The MinnSight Procedure Assistant takes a different approach. Instead of handing someone a blank page and asking them to write, it hands them a conversation.

The tool is an AI agent that interviews the subject matter expert about the procedure, the same way a curious, well-prepared student would. You don’t sit down and compose a document. You just talk through the process the way you’d explain it to someone new on the team: here’s what I do first, here’s why, here’s what can go wrong, here’s how you fix it if it does.

As you talk, the agent asks the probing questions that turn a rough explanation into a complete one. If you skip a step because it feels obvious to you, it asks about it. If you mention an exception in passing, it follows up and makes sure that exception gets captured properly instead of getting lost. If a step depends on a condition you haven’t spelled out yet, it asks what that condition is. It’s doing the work a good technical writer would do in an interview, except it’s available whenever the expert has the time to talk, and it never gets impatient asking the fifth follow-up question about the same step.

This is the real shift the tool makes possible: the expert’s job is simply to explain, not to write. Explaining a process out loud is something almost everyone can do well and without much friction. Writing a clear, structured, complete procedure document is a genuinely different skill, and it’s the part that usually causes the bottleneck. The Procedure Assistant lets each person do the part they’re actually good at.

From Conversation to Finished Document

Once the conversation is complete, the Procedure Assistant assembles everything into a properly formatted Word document. Steps are organized in order, exceptions and special cases are called out where they belong, and the structure reads like something written by a professional technical writer, not a first draft.

Because the output is a standard Word document, it fits right into however your organization already handles documentation. Someone can open it up, make edits, add a screenshot, adjust the tone, or route it through your normal review and approval process. The AI agent gets you a strong, complete draft; from there, refining it takes minutes instead of hours.

Why This Actually Matters

The value here isn’t just speed, though it is faster. It’s that the tool removes the drudgery that keeps good documentation from getting written in the first place.

Procedure documentation has a way of falling to the bottom of everyone’s priority list precisely because it feels tedious. It’s not that people don’t know their jobs. It’s that translating that knowledge into a formal write-up feels like a chore layered on top of already busy schedules. When that friction goes away, so does the excuse to put it off. Experts can knock out a procedure in the time it would have taken them to just think about how they’d start writing it.

There’s a quality benefit too. A guided conversation naturally surfaces details that a blank page never will. The probing questions catch the assumptions experts don’t realize they’re making, the edge cases they’d normally forget to mention, and the context a newcomer would actually need. The result tends to be more thorough than what most people produce when they’re staring at an empty document, trying to remember everything at once.

Getting Started

If your team has procedures living only in someone’s head, or documentation that’s years out of date because nobody had the bandwidth to update it, the Procedure Assistant is built for exactly that gap. Sit your subject matter expert down, have them explain the process like they’re training someone new, and let the agent do the work of turning that explanation into a document your organization can actually use, edit, and keep current.

Good documentation shouldn’t require your best people to become writers. It should just require them to explain what they already know.