We use Promapp for both business as usual process management i.e. maps due for review, approval, reference, improvements, and also as a project resource. BAU and Projects have disparate needs which can't be accommodated in the configuration requirements.
An example is the review approval workflow. If this was to be switched on for BAU it would cause nightmares for projects as Business Analysts and Project Managers would be constantly getting update reminders. They would also reflect as overdue in the dashboard (which also can't be restricted to BAU making it unusable).
For us it is not as simple as 1) project creates a process, b) published and c) handed over to BAU. We may create multiple versions with different purposes e.g. once is very detailed reflecting integrations for testing but is not required to be maintained post project so won't ever have a BAU owner. Another is a BAU higher level process.
Has anyone else come up against this, and if so what did you do?
Best answer by MarkduToit
View original
