I agree with Harry. The last thing I think of when I hear 'Quick' is a big 'thank you for buying my thing, and I hope you enjoy it' speech on the front.
A Quick Start Guide should just be the guide. On as few pages as possible. Everything should support the goal. The only reason for a cover I can think of is to make it easier to pick out of a line up later when your product breaks and needs to be configured again. But odds are good the user just tossed the guide out when they were done with it the first time. Now. If your guide isn't intended for basic users. DON'T call it a Quick Start Guide. Change the name of it and you've done all of the things your team wants with the intro page. Call it a: Training Enhancement Guide. Or something like that. You can do better. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Posted from the new ixda.org http://www.ixda.org/discuss?post=42044 ________________________________________________________________ Welcome to the Interaction Design Association (IxDA)! To post to this list ....... [email protected] Unsubscribe ................ http://www.ixda.org/unsubscribe List Guidelines ............ http://www.ixda.org/guidelines List Help .................. http://www.ixda.org/help
