The base requirements were that Project Accelerator needed to be able to take the data from X project, auto populate X template with that data and allow the user to download the deliverable in X format, such as .docx, .ppt, .vsd and .xls. The requirements were really vague. This was often true with most of the requirements I received for feature requests for Project Accelerator. I had two options, I could try to pull them out of the product owner, or I could do some recon, brainstorm with a few of the brilliant people, and come up with a solution to present to the product owner. I chose the latter.
A LITTLE BREAKDOWN
IF YOU BUILD IT, HE WILL COME
He might come, but he won’t stay if it doesn’t meet his needs. I conducted user research to determine what the users expected this to be. The resounding answer was they wanted to be able to download these docs and easily edit them to suit their needs. They also wanted to be informed when a new document was available and when an existing one was updated.
TO FILTER, OR NOT TO FILTER?
Personally, I’m a big fan of being able to filter, but if the user won’t use it, it’s just clutter on the page. Dynamic deliverables are broken up into 4 sections, many file types and supported different products. Also, some would be dynamic, while others wouldn’t. The other important item here was to determine how much detail the user wanted regarding the document.
LEAVE NO STONE UNTURNED
There were 24 documents slated of the initial release of Plus+, Aside from filtering, pagination, dynamic docs vs. manual docs, It was extremely important to make sure the development team was able to understand all the working pieces of this moving part. To ensure this, and to sell the design to the owner, I created this redline documentation
DYNAMIC DELIVERABLES STORYBOARD
TELLING THE STORY THROUGH SKETCHES