How your context turns into
real artifacts.
Guides, terms and fundamentals around ProcessForge — short and concrete. Growing every week.
Glossary
Terms, clearly explained- Artifact
- The ready-to-use result ProcessForge builds — BPMN, automation draft, podcast, audit docs. Not a draft that still needs six rounds of workshop.
- BPMN
- Business Process Model and Notation — the standard for formally modeling processes. With ProcessForge from your real as-is, not the idealized workshop version.
- BPM tool — and the difference
- A BPM tool models processes to look at. ProcessForge builds from context the artifact you actually use — and tomorrow the next one.
- Operating model
- The target picture of how an organization works. ProcessForge produces versions, comparisons and transition scenarios instead of a one-off document.
- DORA
- Digital Operational Resilience Act — EU regulation for ICT risk in the financial sector. Control mappings and evidence are a ProcessForge artifact.
- NIS2
- EU directive for cybersecurity of critical sectors. Like DORA: audit docs in days instead of quarters, from the living context.
- n8n
- Open-source automation platform. ProcessForge delivers the automation draft ready to plug in — n8n, Zapier or Make.
- Tribal knowledge
- Knowledge that lives only in people’s heads and is documented nowhere. Exactly the substrate ProcessForge makes tangible.
- Connector / source
- A system ProcessForge pulls context from: Notion, SharePoint, Jira, Salesforce, databases — via connector.
- Audit docs
- Control mappings, risk registers, evidence — from the living context, not yesterday’s docs.
Look up
What ProcessForge connectsMaterial
Blog, Learn & InspirationBuilding a process map — from the as-is, not the workshop
A process map built in a workshop shows how the organization believes it works. One pulled from the real as-is shows how it actually does.
Read →Writing SOPs — without the SOP graveyard
Most SOPs don’t die while being written, but afterwards: written once, never updated, eventually ignored. The problem isn’t the SOP — it’s its lifecycle.
Read →M&A & re-org: the operating model that survives the integration
Every merger produces a target operating model as a slide deck — and it’s outdated before day one is over. The way out isn’t a better deck, it’s a different format.
Read →The EU AI Act: your processes are the substrate of compliance
The EU AI Act asks not only which AI you use — but in which processes. If you don’t have the real as-is at hand, you can’t answer the question.
Read →Process documentation: the template was yesterday
A template produces an empty form someone has to fill — and that goes stale the moment it’s filled. The real lever is elsewhere.
Read →Living context: what it actually means
“Living context” sounds like a buzzword — but it’s a distinction from frozen docs. What “living” means in practice, explained through four properties.
Read →Preparing for the demo: which trigger do you bring?
A demo gets concrete when you bring a real trigger. The checklist for what makes a good example — so the call produces a first artifact, live.
Read →Trigger: when a process becomes something you listen to
Behind the scenes of one of the four artifact forms: how an understood process becomes a podcast that explains the why — in your language, not as a PDF blast.
Read →Trigger: making tribal knowledge measurable
A template for COOs, CHROs, and team leads: make key-person risk visible — which processes live only in heads — and turn it into an artifact before anyone resigns.
Read →Read enough?
Let’s forge one.
Show us your trigger — we’ll forge the first artifact from it live in a call.