Feature creep is the ongoing addition of features and functionality which can eventually lead to over-complication and diminished efficiency. In the case of Axure, its ability to make all this documentation interactive, and to take static wireframes to the next level is a feature that can be, for some, irresistible. But just because you can, doesn’t necessarily mean you should.
If Axure is the primary tool in your UX workflow, use it judiciously. Getting caught up with all that you can do in Axure can put a heavy burden on deadlines and deliverables. The solution is to have clearly defined boundaries as to the scope of the deliverable in terms of interactivity at each project phase.
One way to accomplish this is to create two sets of “sitemaps”. One for the proposed information architecture, and the other for only the pages that will be framed out in the wires. As the project progresses, the page icons in the IA sitemap (which I prefer to call a “content map”) can easily be remapped to the wireframes, which will evolve into your prototype when the appropriate stage is reached.
Also, working form a library of standardized interface and content elements can be helpful. Resist the temptation to customize everything up front, and you can drag and drop your way to wireframes in no time, with time to left over to ideate for the long haul.
