Unfortunately many companies look at the call center, which should be the cornerstone of your customer-centric culture, as just a line item on the budget. How can you reduce costs? So call center solutions are geared towards cutting costs but in reality it should all focus on making a better customer experience for the caller.

Make sure you don’t do ALL your brainstorming and (digital) sketching in Axure. The use of many unoptimized images and widgets, even without heavy interactions, will weigh down your file. Unless you pay for an AxShare upgrade, you’re limited to rendering 10MB .RP files max.

Plan wisely!

I’d like to add a few points I found to be useful:

- Invest time once in a good Axure template: this way you don’t have to fiddle around with it in new projects, and you can focus on the prototype
- Building blocks: I’m building a library of patterns I use often (I call it building blocks), to save time when I need to prototype commonly used elements (and you can improve/iterate your functionalities at a central place). It saves me time
- Whenever I make big changes to a prototype, I create a copy and increase the version number. This way you have a reference in case there are any questions about removed/changed functionality, or when it’s rolled back you can simply paste & copy it back to your current document

Since you usually have to edit the functional spec, anything you can put in a master for reuse only needs to be touched once for document edit, not once per appearance in the site.

The same logic of reuse applies from document through prototype through site build: if it’s the same everywhere, document it once, add interactions once, build it once, by deciding early that you’ll reuse it.