The author is not trained, always accustomed to look at this type of work and myself from an outsider's perspective. In the past few years, contacted a variety of domestic and foreign companies, research Institute of the user Experience team. It is customary to see a variety of uxc/ued/uxd limitations, so with the idea of starting from scratch and covered with the bandits gas came to the company now.
2 years in the past, although still nothing, but in the jungle of doing things, eating a lot of pain and experience. Share one or two with everyone today. No matter the logic, the point is to stop.
Deliberately vague positioning: who cares what your name.
Whether or not they are willing to admit it, UX is more like a process job. If you are not satisfied, think about your greatest achievement of the past year, and then whether you have the courage to tell your boss to ask for a raise.
In the field of Cheng Wan, no one cares what you are capable of, but what kind of results you contribute. Whether it is a research or design, you put forward more possibilities, but did not make it a product result, or become the result but deviate from the original intention, or perfect online, but in the industry competition, the impact is very little, it is the process of work.
That's outrageous because no one has the patience to figure out what UX should do. People think: There is a project here, a person called UX went in, and after a while, this project will be a lot of NB. The rest is needless to say.
To this end, I tirelessly blurred the positioning with the research. Others vaguely feel that the company has a layer of such a team, can do some things related to users. That's enough.
The reason for this is that many things to contribute to the outcome, all aspects will eventually encounter two problems: ① misplaced the right to ② the power of approval.
Because fuzzy positioning, relative to solve the first problem. For aspiring young people to do things, leaders can also be demanding. The dislocation of the person although vaguely feel wrong, but do not know what you should do, there is nothing to say. The real problem still lies in the cultivation of the ability to think outside of the UX.
For each of us UX, in the end how to do, ask out the cooperative product team the most clear.
Adversity to survive: two abilities to support the team
No matter how brutal, it must be admitted that the UX team is still more marginalized. There are two abilities that I think are most important.
The first is "do not restore information in the field."
UX is peripheral and cannot get as much information as PM, even if it works well, most PM does not get all the high-level information. In this case, want to be responsible for the result, to restore a variety of background from a little bit of clues. For example, each of the company's top judgments, the root causes of differences between different decision-makers, the true attitude of everyone in the team, what information everyone gets/lacks, the strengths of each person in the project, where the short board is, and what role UX plays ... That has a fundamental effect on what I should do.
For example, I will use a product team to respond to the time difference/term in the discussion group to speculate on the degree of harmony, if the team is not familiar with each other, a single communication is a good way to intervene early.
The second is "to squeeze the value of every message."
For Uxer, the information/experience that has been summed up in the project is all your resources, to be reused. For what you want to do now, see what the other person's headache is, and then look for it from the previous experience.
For example, once in a company to intervene in a product, can not find the entry point. I think since this product is mature, leaders should start to pay attention to standardization. We have summed up the company's general planning problems from the previous project, causing the other leaders to resonate, with an innovative project as a standardized pilot, thus beginning to intervene.
A team culture that can't be learned: a true result orientation
The character of Fei (Hua) is that everyone thinks he understands. Sermon, as a child to write the text began to quote, and each end will sublimate once.
I used to think I knew "result-oriented," and then I found out that it was all fur. In an easy to understand way, although all speak of "result-oriented", but the proportion of the process and results is different. Most places 55 open, that is, as long as you have no fault in the process, and I also participated in a major decision, the final result is not good enough I do not blame you, and some places are 28 open, even if the nature of force majeure, even if the major decisions I do, but the final problem I still blame you ... The more exaggerated scenario is that you're all perfect but I feel like you're going to fail, and you don't realize I might think you're going to fail, and that's not enough. This is how crisis consciousness is nurtured.
Whether it's a result-oriented or a Cao Chong-like call. It's amazing how a person can really understand a way of doing things.
Leave a question for the UX: you are involved in a product that marketing is important, but you find that the company marketing department does not do enough, what do you do, to what extent?
The perception of self superiority and inferiority
As a process, you can fool others. But as a result, if you aim to save the Internet, be aware of yourself at any time.
Recently, I often ask myself, what is the value of the research? If I had been CEO one day, I would have been better than anyone else. For the time being, I think the help for me to be a CEO is to always be able to synchronize the cognition of ordinary people.
Software products, most still in the spell experience, is the product capabilities of the PK, it is obvious that the experience level gap is getting smaller. Another phenomenon is that the Internet product changes too fast, ordinary users of different products are biased. In this case, if I intervene in a new field, how to perceive the cognition of normal people, even to mistake use of this knowledge, than I come directly to the blue sea or the experience of details more important.
The advantage is no longer said (in fact, I also want to say research thinking itself). When it comes to disadvantage, the first is the value of a job, either you do something that no one else can do, or do something others don't want to do. and UX jobs, especially with research and interaction, in fact, in the PM work to dabble. If they learn your speed, more than you learn the speed of operation/business, do you still have to?
Only the waking self knows each day adjusts itself more quickly than the outside world changes, or complements itself.
Finally, the rule of the jungle is premised on what makes your girlfriend not run?
UX as a direct impact on product results, and PM The biggest difference is: PM KPI more and product binding, to entrepreneurial mentality in doing one thing (different company degree varies). If do not do well, at any time may be leather, product transfer master. With this sense of crisis, will think more, do more.
And as UX people, if not self-driven to do more, with what is to enjoy the process of stability and the results of credit, why not in the morning to see the company in the early hours of the former girlfriend to bask in happiness of micro-blog, the two lines of tears also write poetry to pretend to enjoy I also have a good ... Do not experience the law of the jungle, why do you want to blossom in the jungle. Only bear the same pressure, will develop the same mind and a keen sense of smell.
At the end of the last, the above is nonsense
My rule of thinking is that only the people who make it are right. I have not made a reliable result, so I think, are individual yy. Hope is not misleading, judge by yourself.
But for myself, as long as I believe that the moment, once done, will be more in line with what I need in the future, I will stick to it forever.
Share.