Participant Experience App

The Problem

The orig­i­nal sales doc­u­ment was an elab­o­rate Pow­er­Point pre­sen­ta­tion that could­n’t eas­ily be taken off-site in one self-con­tained unit. Our busi­ness part­ners were insist­ing on another structure.

Analysis

To ascer­tain a base­line before mak­ing deci­sions on the new plat­form, we audited the exist­ing sales expe­ri­ence, took a con­tent inven­tory and had account man­agers walk us though a sales presentation.

After that, we sat in a room with stacks of post-it notes and did card sort­ing exercises.

Structural Decisions

Microsite or App?

To address the pain points of the sales team, we weighed out the pros and cons of each option. Cre­at­ing a hybrid app in Adobe’s Dig­i­tal Pub­lish­ing Suite would make the struc­tural build much more dif­fi­cult. How­ever, since an inter­net con­nec­tion was­n’t always an option, a microsite would­n’t be practical.

Internal Structure?

HTML in a shell, ePub, or a com­bi­na­tion of the two? We sketched out sev­eral options on our white­board explor­ing sev­eral struc­tures within the dig­i­tal pub­lish­ing suite. In the end, my propo­si­tion of all DPS with a spe­cial HTML tem­plated library of sales sam­ples won out. Logis­ti­cally, it was the eas­i­est to update while also low­er­ing the risk of error input dur­ing each quar­ter-end update.

Wireframing & More

To ascer­tain a base­line before mak­ing deci­sions on the new plat­form, we audited the exist­ing sales expe­ri­ence, took a con­tent inven­tory and had account man­agers walk us though a sales presentation.

After that, we sat in a room with stacks of post-it notes and did card sort­ing exer­cises. Any­thing we weren’t sure how to cat­e­go­rize, went on a list of ques­tions for the sales folks.

Once that was done, we began wire­fram­ing nav­i­ga­tion and spe­cific func­tion­al­ity options. Because we were push­ing the lim­its of Adobe DPS (at the time), we had an Adobe devel­oper to con­sult peri­od­i­cally dur­ing this process.

Approval, Testing, and Design

Dur­ing the sev­eral iter­a­tions of test­ing nav­i­ga­tional pro­to­types, my col­league, Rob, began work­ing on the design.

Once the nav­i­ga­tion was approved and a cou­ple of design options were set­tled upon, we had a minor setback…

Monkey Wrenches

What would a major cor­po­rate ini­tia­tive be with­out a few sur­prises here and there? We were mak­ing a pretty good pace with the project when the cor­po­rate brand was refreshed and our project was going to be used as a new brand stress-test. Luck­ily, our mas­ter designer eas­ily incor­po­rated changes into his designs.

The needs of the stress-test kept chang­ing as we were build­ing out the nav­i­ga­tion, design­ing pages and work­ing toward our first Beta test.

Betas and More

At last we com­pleted most of the build. HTML sam­ple client libraries were built out dur­ing the beta test­ing since there were more than 200 sam­ples to be created.

The beta prod­uct was tested by selected sales agents who had to be trained on the new struc­ture and func­tion­al­ity. Final release was successful.

My Role: brain­storm­ing, struc­tural deter­mi­na­tion, func­tion­al­ity test­ing within DPS, page build-out, testing

Skills

Posted on

November 16, 2013

Submit a Comment

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