Problem:
The workflow designer tool allows consultants to visually design workflows. They can bring in many supporting resources, however it can be hard to access information about the version of the resources being used. This can cause confusion, introduce bugs and stall debugging efforts.
My role:
Product Owner and lead researcher on the project.
Background research:
- I picked up that consultants would often complain about problems caused by not knowing the version of the resources being used in workflows.
- This feature was designed as my own initiative.
Insights:
- I found that consultants had such a strong identification with their product that they found it difficult to reconcile low-fi prototypes with their existing product knowledge.
- High-fi prototypes were too often mistaken for built features.
- I developed the habit of embedding realistic product visuals into low-fi prototypes. This gave consultants a visual shorthand to identify what will change versus what is safe from change.
Ideation
- Went through 1-2 rounds of discussion with key users (our internal consultants) and the lead developer.
- Developed a wiki page to publish the design and invited feedback comments.
Prototypes:
- It is clear that some areas are “as is” or safe from change and some are open to suggestion.
Result
- After I designed this feature it was left on the product improvement backlog
- It was built after I left the team