Challenge Planned as a major upgrade from Citrix App Studio 1.0, App Orchestration (AO) 2.0 was expected to provide a simple, unified way for customers to manage Citrix application and desktop delivery technologies for multiple tenants, using multi
One key take-away for the team at this stage was that frequently making users context-switch away from using the product to look for assistance in a separate help system or external documentation was distracting to customers and often ended unsucces
For example, the Customer Experience team worked closely to integrate usage information into the design of the user interface, such as the introductory information shown here from an early iteration of App Orchestration 2.0:
On other screens, we designed the UI to provide customers with a clear context for understanding where they were and what they needed to do next.
Since App Orchestration integrated and built on many previously separate Citrix products, we quickly discovered instances of conflicting or confusing concepts and terminology. As a result, we devoted extensive efforts to crafting a unifying taxonomy
In the process, we identified some in-depth technical information that really needed to be written by senior-level architects and developers. Unfortunately, many of those individuals didn’t feel comfortable serving as Technical Writers. So we develo
Next, we developed a staged approach for usability testing, starting with early alpha versions of the product. Every 2 weeks, participating customers would receive the latest version of the product, along with the information needed to perform a sin
Results For App Orchestration 2.0, I co-facilitated 3 Design Thinking workshops (one for AO, and 2 for related cloud products). Based on the results of those workshops and other research, my team and I created the personas, workflows, paper prototy
AO 20 Installation Poster.png
prev / next