# What BPM platforms do teams actually keep using and improving after the initial rollout rather than abandoning once the novelty wears off?

<p class="elv-tracking-normal elv-text-default elv-font-figtree elv-text-base elv-leading-base elv-font-normal" elv="true">I’m exploring what BPM platforms teams actually keep using and improving after the initial rollout, rather than abandoning them once the novelty wears off. Early implementation feedback is useful, but I’m more interested in what still works six to twelve months later.</p><p class="elv-tracking-normal elv-text-default elv-font-figtree elv-text-base elv-leading-base elv-font-normal" elv="true">From the<a class="a a--md" elv="true" href="https://www.g2.com/categories/business-process-management"> </a><a class="a a--md" elv="true" href="https://www.g2.com/categories/business-process-management">business process management </a><a class="a a--md" elv="true" href="https://www.g2.com/categories/business-process-management">tools </a>I’m reviewing, I’m seeing a few retention patterns:</p><ul>
<li>
<a class="a a--md" elv="true" href="https://www.g2.com/products/kissflow/reviews"><strong>Kissflow</strong></a> seems to stick when teams keep expanding workflows and running daily office routines inside it.</li>
<li>
<a class="a a--md" elv="true" href="https://www.g2.com/products/microsoft-power-automate/reviews"><strong>Microsoft Power Automate</strong></a> works for teams that keep adding automations as Microsoft 365 needs evolve.</li>
<li>
<a class="a a--md" elv="true" href="https://www.g2.com/products/laserfiche/reviews"><strong>Laserfiche</strong></a> appears useful when one platform can support many processes and document use cases.</li>
<li>
<a class="a a--md" elv="true" href="https://www.g2.com/products/nintex-nintex/reviews"><strong>Nintex</strong></a> fits organizations focused on visibility, documentation, and continuous optimization.</li>
<li>
<a class="a a--md" elv="true" href="https://www.g2.com/products/jotform-workflows/reviews"><strong>Jotform Workflows</strong></a> works for smaller teams that expand from one workflow into adjacent processes.</li>
</ul><p class="elv-tracking-normal elv-text-default elv-font-figtree elv-text-base elv-leading-base elv-font-normal" elv="true">What signals have you seen that a BPM tool will keep growing inside a team rather than fade after rollout?</p>

##### Post Metadata
- Posted at: 27 days ago
- Author title: Marketer
- Net upvotes: 1


## Comments
### Comment 1

Adoption death is real and it almost never comes from missing features. It comes from the tool being slightly more annoying than the spreadsheet it replaced. The ones that stick are where using the process is genuinely easier than going around it. So the question isn&#39;t which platform is most powerful, it&#39;s which one your least-enthusiastic teammate still opens in month six. Have you watched the skeptics use it, or only the champions?

##### Comment Metadata
- Posted at: 17 days ago





## Related discussions
- [How well does Trello scale into a larger team?](https://www.g2.com/discussions/1-how-well-does-trello-scale-into-a-larger-team)
  - Posted at: about 13 years ago
  - Comments: 6
- [Can we please add a new section](https://www.g2.com/discussions/2-can-we-please-add-a-new-section)
  - Posted at: about 13 years ago
  - Comments: 0
- [Quantifiable benefits from implementing your CRM](https://www.g2.com/discussions/quantifiable-benefits-from-implementing-your-crm)
  - Posted at: about 13 years ago
  - Comments: 4