![]() What about snapshot workflows? You can document flows via Snapshots that change when the source page changes so you don’t have to keep updating documentation when you change a step in a flow - Just connect a bunch of snaphots together in a row. If you build to that level of detail, you can sit a user down and say “Accomplish Task A” - “What can I click on?” “Whatever you want.” You also don’t need to put user testing or demos on rails. ![]() If, tomorrow, we change text fields to a new style or our User Avatar Control mechanism changes, I do that in one place for ALL of my pages and documentation links. ![]() Changing something there and updating its style changes everything on the other side of every link ever sent out because the environment is a living system. Using masters and styles, I have a Style Guide page that contains every element in the platform. Heck, I’ve got functioning drag and drop re-ordering tables. Every piece of navigation, multi-select tables that present accurate “‘n’ selected” values, repeater tables w/ pagination and functioning column sorts/search filters - I’ve built Content Moderation features, Localization frameworks, Bulk Actions… all inside that “environment.” Each time, stake holders and engineers were able to USE the feature, (down to error handling) in the clearest form of communication between engineer and designer that’s possible. I have our entire enterprise admin platform in one Axure file. It’s about more than a list of features, it’s about building an environment rather than painting a sequence of screens that represent a desired flow of interaction. ![]() I had a QA guy once ask me how to get rid of a You have unsaved changes dialog. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |