Some of my most creative work has been done without a formal workflow design.
I have created workflows based on a telephone call, received designs in foreign languages, and I have even been given a workflow design drawn on a coffee napkin.
But even then I have insisted on being briefed on three main points: What is the business pain (and how to resolve it); the workflow diagram; the look and feel of the activity forms.
Now, although I enjoy a good challenge, I would always advise starting workflow development after a proper design.
These are the points that every good workflow design should have:
- Project description
- The business pain and business drivers
- Project critical success factors
- Project stakeholders
- Timeframe and phases
- Known risks
- Internal politics
- Workflow diagram
- Process initiation
- Process steps & activities
- Business rules
- Messages, notifications & recipients
- SLA reminders and escalations
- Look & feel
- KPIs & metrics
Infrastructure, Systems & Integration
- Solution, business & information architecture
- Development, testing and deployment
- Systems participating or interfacing