"In contrast to traditional enterprise software, which imposes structure prior to use, this generation of software tends to encourage use prior to providing structure."Use prior to structure...
People always tell you this when you buy a house-- before putting in furniture, use it, walk around, figure out the traffic patterns, see which areas you and others naturally gravitate toward. Then, structure accordingly - make the furniture fit your lifestyle.
This is my precise philosophy on how to approach new research constructs (e.g. Influence, Engagement, Authenticity), and data analysis in general. Map it out. Use your data and then divine structure. Down with Field of Dreams, 'If they come, it will build (grow)' seems a bit more apt today.
Surely I'm naive. When is it good to impose structure prior to use? People tell me schedules and plans work well in life. Is there anything in the enterprise that clearly calls for structure prior to use or can everything evolve to a place where structure emerges organically?
