Resources
To decide with judgement, not with a pretty demo.
Three things that are useful even if you end up buying something else: the path of the first process, the questions that separate serious products, and the minimum glossary.
Rollout
The first process, step by step.
You don’t roll out a BPMS: you put one process into production, then another. This is the path we follow.
Pick the process that hurts
One with a clear owner, enough volume to notice and a measurable ending. Not the most complex one.
Draw it as it is today
In BPMN, with the real tasks and the real owners. This is where the steps nobody knew about show up.
Build the forms
Paper or spreadsheet formats become screens; AI writes the first draft and you correct it.
Set the deadlines
Business calendar, holidays and projected duration per task, with the alerts and who receives them.
Run it in testing
Test instances while the version is in design; publishing deletes them and leaves it clean.
Publish and measure
The published version serves people and the dashboard shows on-time, at-risk and overdue from day one.
Before you sign
Questions worth asking any BPMS.
Including the ones that make us uncomfortable. If a vendor says yes to everything, be suspicious.
Glossary
Twelve words that run through the whole conversation.
- BPMN 2.0
- The standard notation for drawing processes. Being standard, the diagram is understood outside the tool that drew it.
- Process and instance
- The process is the mould; the instance is one concrete case running, with its data and its history.
- Human task
- A step that waits for someone to act. It is the one that carries a form, an owner and a deadline.
- Gateway
- The point where the flow splits. A rule decides which path is taken, using the captured data.
- Multi-instance
- A task that repeats: one per row of a table, or one per case of the previous task.
- SLA
- The committed deadline for a task. It only means something when measured against the real working calendar.
- Business calendar
- The company’s schedule and holidays. It is what keeps a two-day deadline from falling due on a Sunday.
- Delegation
- Redirecting someone’s tasks for a period, without changing the process design.
- Version and publishing
- A new version doesn’t affect running instances; publishing is what puts it in front of people.
- Minor edit
- Fixing texts and lists on an already published form, with a justification, without creating a new version.
- Webhook
- An address where an external system drops a value. Here it is bound to one specific task, and it expires.
- Multi-company
- One installation serving several companies with separated data and different calendars.
Keep reading
The pages that answer the rest.
Would a conversation help more than a brochure?
Ask for the demo with a process of yours: in an hour you’ll know whether this fits.