What is an artifact? The four forms

ProcessForge casts the same process knowledge into four ready-to-use forms: a BPMN model, an automation draft, an onboarding podcast and audit docs — one context, four results.

At Forge, “artifact” (in German: Ergebnis) isn’t a marketing word — it’s a distinction. An artifact is the ready-to-use result — not a draft that still needs six rounds of workshop, and not a document that’s only looked at. It’s what you actually work with afterwards.

How does an artifact differ from documentation?

Classic process documentation describes a workflow so people can read it. It’s an intermediate step: first read, then translate, then apply. An artifact skips the translation — it’s already built for the concrete use.

The lever behind it is always the same. Forge pulls the real as-is state from your existing sources — docs, tickets, system exports, conversations — and understands the process once, properly. From that understood context it then casts whatever form the occasion calls for. Same engine, same context — four different results:

1. BPMN

The formal process model from your real as-is — unambiguous enough to audit or automate. Not the workshop ideal, but the lived workflow, including the edge cases that appear in no target diagram. Usable without anyone having sat through a BPMN course first — more on that in BPMN without BPMN school.

2. Automation draft

Ready to plug into n8n, Zapier or Make. From the understood process straight to a runnable flow — instead of starting over from the diagram. The draft names triggers, steps and handovers concretely enough that the automation doesn’t start from zero. What the path from process to n8n flow looks like: From automation draft to n8n flow.

3. Onboarding podcast

Tribal knowledge as an audible format. It explains the why behind the process, not just the boxes and arrows — exactly the part that otherwise lives only in heads and walks out with the people. Why an audio format sometimes sticks better than any handbook: The onboarding podcast as an audio format.

4. Audit docs

Control mappings, risk registers and evidence — for DORA, NIS2 or the internal review. From the living context, not the 2022 docs, and referenced back to the source so it’s inspectable. How that becomes days instead of quarters: Audit docs in days, not quarters.

How to choose the form

You don’t have to decide at the start. The rule of thumb is simple: who should do what with the artifact? An auditor needs evidence, a developer a flow, a new colleague an entry point, a steering committee a model. The same context serves all of it — you build the form that’s due now, and the next when it’s due.

One engine, many forms

The point isn’t the list — it could be longer. The point is: one context, any number of artifacts. When the process changes, it isn’t a single document that’s refreshed, but every form you draw from it — from the state that holds then.

What stays with you isn’t the single artifact — it’s the ability to build the next one.

Which form is right for your concrete occasion shows fastest on a real source. To try it: bring an upcoming occasion into the demo call — we’ll build the first artifact from it live.