Complex Installation Process

Problem:

  • Release 99.9.9 vastly increased complexity of the product capabilities
  • There was a concern that the installation process would become too complicated, even for customers not using the new features
  • Old installer technology placed constraints on the install process
  • Enabler components need to be installed at key points in the process

My role:

  • Product owner / Agile Business Analyst

Background research:

  • Current functionality
  • Develop a cases matrix showing how new options would impact the installer
  • Understand the options for supplying information to the installer e.g. command line, config file

Insights:

  • A number of questions can be skipped if not using new components
  • A significant amount of data can be supplied via config files, minimising user error during install

Ideation

  • Workshops with key developers
    • What do we need to ask?
    • What can we skip over or ask in a config file?
    • What order does the installation happen in?
    • Do we all agree this is the best we can do?

Prototype

  • Mapped the process including data sources
  • Colour-coding made it easy to link related components together

Once we agreed that the right data was being collected, in the right order, and that this was the best flow possible then this epic was broken into story tickets for each team to commence the build.

Great UX in a Text-based Installer?

Great UX is possible even in a text-based installer. In fact, it is vital. Some features of great text UX include:

  • Consistent phrases
  • Template answers and string-matching verification
  • Default answers (indicated in CAPITALS)

I created centralised resources to drive uniformity in the installer questions across teams. This is to avoid the user encountering a jarring change in tone during the install process.

e.g.

This is poor UX:

How many gateways do you want to add?
What is the URL for Gateway 1?
Where is Gateway 2 located (please type the URL)?
Gateway 3 URL including port ……………..

This is better UX:

What is the URL for Gateway 1? (http://sub.domain.com)
Do you wish to add another? (YES/no)
What is the URL for Gateway 2? (http://sub.domain.com)
Do you wish to add another? (YES/no)
What is the URL for Gateway 3? (http://sub.domain.com)
Do you wish to add another? (YES/no)

Leave a comment

Your email address will not be published. Required fields are marked *