Editor’s note: interactive designers have been in the industry for many years. Where are the ceilings? Once the article is released, many designers feel empathy. I believe you will have a good harvest after reading it.
1. To reject a demand is the greatest pride.
Remember the first day of work, not yet finished the trainer sister has given me the assignment, to the workstation immediately began docking with the product manager needs.
At that time, my job as an interaction designer was to draw pictures: whether the buttons were on the left or right, whether to jump to a new page or use a floating layer, and how the network didn’t display well… Listen to the product manager’s request, draw it as an interface, and then call the development students to interact with the review, until the final requirements on-line, and everyone together to double-check the data effect.
The first surprise was that I successfully rejected the needs of a product manager. When he finished describing what he wanted to do, I wrote three reasons on the paper to prove that the requirement was unreasonable, and finally the product manager agreed. Look, I’m not just a designer who was legendarily forced to revise by the product manager, I have my own judgment.
When I was in demand, I was very tired physically, but mentally well. After all, I am proud of choosing the latter from the two offer of product and interaction.
What is arrogant? Pride is the ability of drawing others. I don’t work like a product, but I have real skills and real abilities.
I would dislike the product manager’s wireframe and often tell them not to waste time drawing, think logically, and give me the interface.
In communications and reviews, I struggle to argue against suggestions about the “experience” of products and technologies, which is, after all, the domain of our interaction designers, and your views are personal exceptions.
For this reason, even at the end of the workflow, even as a purely executive, I pride myself on my expertise.
In the days of pride, the painting interface is all the interaction designer. What I see most every day is design professional websites, reading design specifications for different mobile platforms, learning prototyping tools, and a passion for dynamic effects and airplane drafts. The meeting time is only about 30%. Once you have finished a demand, you will go to the next one.
2. after the N draft, return the first draft? Nonexistent
Inferiority must start from being hit.
At that time, I was not allowed to write with an innovation project, from 0-1, confidentiality and weekly reports. The first batch was painted like a visual draft, which lasted several nights a week before the project was reported. Do not want to, after the report is not passed, business logic loopholes.
Since then, it has been the second round of reporting and the third round of reporting. N round report. It is not like the story, let us use the first draft, but really come to a different point.
After two months of reporting and bumping, I learned two things.
First, in the midst of frequent business changes, I’ve found that drawing skills are common to many people, but product managers don’t want to waste time thinking about every detail, so they give it to downstream interaction designers. And because “experience” is a very subjective judgment, there are a lot of hard-to-refute opinions about your solution, whether it’s product, R&D, testing or application research. These opinions come from their own judgments, or from the ideas of “friends” around them, as well as the reference of competitors.
Second, business patterns can change in many areas, such as knowledge sharing, social networking, e-commerce, and O2 O, but there is little difference in interaction design, which is front-end typesetting. The vast majority of “experience” good designs cater to user habits and expectations, in other words, are well-documented solutions (specifications, industry benchmarking, etc.). Therefore, in a project, design really will not be the core competitiveness, nor will it be the main factor that determines the survival of the project.
With the increase of psychological anxiety, the body will not be relaxed.
The promotion of projects often starts with technical backwards. On the 20 line, testing for 5 days, developing 12 days, PRD 2 days, then there is only one day left for the design. The difficulty of downstream technology implementation is irrefutable, the time spent is difficult to compress, the upstream logic and business output dominate, and the time of intermediate design is often reduced. It’s also common to ask for demand half an hour before work, talk about it until midnight in the evening, and have meetings on Friday and Monday.
So I always feel that the interaction designer is just doing something dispensable.
3. Do designers want to learn code?
In recent months, I have done a lot of things that should not be done by designers. I’ve learned to write a crawler that collects lots of competitive data for my current business, I go to the business plan to find out what’s wrong with it, I do the overall product design, and I do project management for offline activities.
So many friends who read my articles often ask in the background: “are you a product manager? ”
In fact, it is not.
From a few years ago in fashion so-called full stack designers, or product designers, they ask for their own drawings, their own development and operation, similar to the slash youth attracted the envy of many industry interaction designers.
The question of whether a designer should learn code or not has been around for years, and the corresponding tools and design products are emerging in endlessly.
But I want to say that interaction designers need to be self-conscious when encouraging them to stand forward, fill in, and cross borders.
First, the gap of professional competence. Don’t give the front-end engineer a thumbs-up call just because you’ve learned some front-end tools to write demo, don’t assume you’ve found a data analyst’s loophole just because you’ve done some perspective on the data, and don’t assume that the product manager will just fool around and take over. Sometimes you think that a second-rate designer who makes third-rate products, fourth-rate operations, and five-point data is a 10-point person, and probably ends up with zero.
Second, our posts lack natural information input. Many business judgments and data analysis rely on industry information, and the same data in your hands and in the hands of professional data analysts come to different conclusions, not because of differences in data processing capabilities, but probably because of differences in background information brought about by different positions. If a product doesn’t sell well, you might think it doesn’t perform well enough, but more likely it’s going to be phased out.
Third, our posts lack the right to speak. Doing cross-border things requires not only the ability, but also the right to speak. When everyone does his or her job, you jump out and say that the other person is not doing enough, unreliable and gives a replacement plan. Most of the acceptance happens in the workplace fiction, and more often than not you get a response that allows you to do your own thing.
Obviously, it has its irreplaceable value. Why do we have to learn something different?
So do designers want to learn code? I think at least you have to make sure you’re professional in one of your abilities, for example, you’re already a design expert, and it’s okay to spend a little more time improving your skills. But if both sides are done, neither side will be fine.
4. the ceiling may be higher than we thought.
Today I happened to see a veteran experience designer recalling what his former colleagues were doing. Some of the five cases are still interactive design experts, others are transforming into product directors, and of course some are starting businesses.
When an interaction designer finds a way to see his pride, inferiority and self-consciousness, he can really explore the future of the industry. Perhaps the ceiling is higher than we thought.