Design standards for a process guide
It should be written in Plain language, it should allow a user to check tasks off, set reminders for others, save her progress, share her info & have it saved into the navigator, complete her forms and tasks on the platform, and generally be her all-in-one guide to getting this task done.
It should be like an expert paralegal, or court navigator, plus personal assistant to help a person complete all the steps of a legal procedure without missing paperwork, deadlines, or crucial small details. It should also help the person form an accurate timeline & workload expectation from the outset of a legal process, so she has a more transparent view of what’s coming & what she should be doing.
What are different styles of process guides?
- The wizard: taking the user through an entire task one step at a time, showing her which steps there are and how many she has completed. The wizard offers a series of screens/dialog boxes that has the user do one step at a time, and lets her jump to a previous or next step, til she reaches the conclusion. They are meant to be fast and easy, breaking a complex task into manageable bites.
- The timeline: laying out steps along a sequence track
- The checklist: listing out steps one after the other, letting a person go through one by one and marking off the completed ones
- The map: showing the paths open to the user, and then letting her zoom into each one-by-one
What makes for a good process guide?
- All details, forms, and action items are presented along with the steps — at the right time, right there integrated into the guide
- It is clearly up to date & reliable (or marked clearly if it might be ‘expired’)