The only way to discover your strengths is through feedback analysis. Whenever you make a key decision or take a key action, write down what you expect will happen. Nine or 12 months later, compare the actual results with your expectations.
"Kant described a mechanism as a functional unity, in which the parts exist for one another in the performance of a particular function.
An organism, on the other hand, is a functional and structural unity in which the parts exist for and by means of one another in the expression of a particular nature.
This means that the parts of an organism – leaves, roots, flowers, limbs, eyes, heart, brain – are not made independently and then assembled, as in a machine, but arise as a result of interactions within the developing organism."
— Brian Goodwin, How the Leopard Changed His Spots
I’m concerned with how I witness the work of user experience practitioners getting treated: like it’s just a set of motions toward a product’s all-important implementation, and one that we try to compress, due to its ostensible superfluity. Once the implementation is finished, the UX work appears to usually get discarded.
I submit that the materials that form the precursors to a product’s implementation have considerable value on their own.
My vision is that I will be able to ask a question as mundane as one about the wording of a single button, and trace the answer all the way back to the overarching business strategy to see that it makes sense.
It isn’t a site, or a service, or even an identifiable product at all, but rather a system for creating a skin around and connective tissue between things like:
Demographic studies
Contextual inquiries
Stakeholder and user interviews
Surveys
The business ecosystem
Personas
Scenarios
Sketches, storyboards, wireframes
Mockups, models and prototypes
Email and IM conversations
Meeting notes
Content inventories and audits
Concept schemes, taxonomies, thesauri
A UI style guide
A branding and visual identity guide
A voice and tone guide
A code style guide
...etc
The individual elements of such a corpus represent the work of half a dozen specialist sub-disciplines, and are useful for realizing a product’s implementation. But if you hook them all up together, they merge to become a strategic artifact that transcends products and operates as a critical control surface for the business. This is because what such an artifact represents is a coral reef of deeply-considered and hard-fought decisions, and a story of the process that yielded them.