Note, this is not a call for technical assesment — right now, the focus is figuring out what would be the optimal way to build a Workflows app, UX wise. Technical assesment comes, but it comes later :) !

Hi all,

A new UX prototype + video of Workflows is out — have a look here: http://ux.folio.org/prototype/en/workflows

UX questions to consider — feel free to comment on discuss with your ideas, advice, questions on https://discuss.folio.org/t/zap-workflows-ux-iteration-3-english/1041
1. How granular should steps be?
2. How meaning is it to have logic related steps like if/else and loop?
3. Which triggers would be meaningful for your work as an individual and for your particular group at your institution?
4. Which steps would be meaningful for your work as an individual and for your particular group at your institution?
5. How meaningful is the ability to add scripts you write yourself or get written by e.g. a more technical colleague?
6. How meaningful is the ability to publish workflows for others to download?
7. How meaningful is the ability to publish scripts you write for others to download?
8. What's missing from this prototype?
9. What works well in this prototype?

In theory I feel all the features I present are meaningful, but in practice I don't know — that's what these questions above are meant to clarify :)

Filip Jakobsen
UX & interaction designer, founder
+4531242526
filip@samhaeng.com

Samhæng ApS
Vesterbrogade 26
c/o Republikken
1620 Copenhagen
CVR DK38271547
www.samhaeng.com