Analytics apps don't tell you much about usage behavior. You might be able to see how many users performed an event, or how many times they did it. But none of the analytics packages out there are good at showing you how often people do things. Are they using to-dos once a week? Every day? Only signing into the app once a month but happily paying for years?
Time matters. You can't understand usage without time.
Here I describe an approach for defining new information architectures for large organizational websites managed by many stakeholder groups.
Broadly speaking, there are four general phases to the approach:
Auditing. Begin by immersing yourself in existing content and encourage stakeholders to adopt a critical, audience-minded perspective of their content.
Diagramming. Work with stakeholders to develop new conceptual categories that better serve audiences and organizational direction.
Elaborating. Think through content in detail and test new categories against specific instances and edge cases.
Producing. Prepare content teams for production using a shared database of new sitemap pages and editorial considerations that you’ve developed incrementally.
The bottom line is certainly of concern, both to those seeking profit and to those seeking value, but neither of these can be measured solely by the amount of dollars spent on production or product. The nonquantitative word "quality" conveys countless ways in which a more expensive thing might be more profitable and yet a better buy as well. The advantages of thicker metal in an automobile body can clearly be argued from various points of view, including resistance to denting and even simple snob appeal. Whereas the manufacturer can use these as selling points and also as justification for a higher price tag, the buyer can easily justify spending more for a car that will keep its appearance longer and provide a status symbol.