Design communication is like going to a Taiwanese seafood restaurant, there will definitely be “ordering the wrong dish”

Sharing is Caring

After working as a designer for a while, you will find it very interesting that you have to rely on some preconditions to achieve the job you receive, and when the job comes to you, you often don’t have sufficient preconditions. In some cases, these prerequisites are even hidden information, which requires you to be a detective yourself.

But the demand side is not intentional, and most people are not good at being the demand side.

It’s like you have eaten night market snacks all your life. The night market snack menu is clear, what to eat, and you have nothing to decide about the cooking process. At most, you will be asked if you want coriander and spicy.

But suddenly one day you go to a Taiwanese seafood restaurant and see a whole cabinet of seafood in front of the store, dumbfounded cat, why is there no menu? Every customer is pointing and pointing with the boss at the door of the store. When it is your turn, the boss’s tone is fast and anxious. You are in a panic. What kind of fish have you never seen before? How to order? What is the price? What is current price? Then how do I know how much the whole table dish will cost?

After eating, watching, listening to, imitating what others do, and listening to the boss’s advice, you can gradually figure out your own way of ordering, and then you will know the deeper level. It turns out that each restaurant is suitable for different ordering methods. If you want a specific way to eat, you have to find the right restaurant.

After ordering for a long time, you can choose the right restaurant, determine the appropriate budget, and be a handy demander based on the guests you want to entertain, the theme of the dinner, what to eat in this season, and other conditions.

Among these things, a large amount of learning costs are hidden, and when they appear in software projects, there are risks related to requirements.

When you are on a software project, there will almost certainly be a situation of “ordering the wrong dish”, even for experienced demanders. Because there are countless situations that interfere with demand, what you think is the demand side, there is a demand side behind it, and the layer-by-layer relationship is becoming more and more abstract, and it is even difficult to define a consensus.

But the human brain hates vague and incomprehensible things, and likes specific and clear things, so it wants you to do it first and then talk about it, so that you can know what you need. Look, isn’t this the process of learning?

Make observations, put forward hypotheses, test concepts, analyze results, and then proceed to the next round of actions. During this process, everyone extracts a consensus (or unique domain knowledge), and things gradually become clear, and the needs clearly know what they should do. What dish.

These things seem easy and comfortable when written in words, but in the real work schedule, they are full of stress, frequent short-term emotional interference, inconsistent interests, lack of consensus, vague feedback, and ambiguous communication terms. It is necessary to conduct three-legged cooperation with the demand side.

Therefore, sometimes your demand side also gives up struggling, because everything is really too vague and abstract, and it is not right to know what to do if you are the demand side.

And if we also give up struggling and simply follow orders, anyway, what the demand side tells us, we have to write in black and white before implementing it, and the risk is borne by others, then we will turn ourselves into a smart mouse and voice input method for workers.

Such a three-legged relationship between two people will become a hell for contemplating falling yin.

That’s why, when we start to become independent designers, we can’t just hide behind the design language and only deal with professional work. We need to take a few steps forward and find more ways to help the demand side reduce their cognitive burden and make more quality decision-making discussions.

A chef who values ​​quality and pursuit will definitely purchase ingredients by himself, or even start from the farm by himself.

Seven points depend on materials, and three points depend on craftsmanship.

Only by taking actions to help the demand side obtain reliable quality raw materials can we give full play to our strengths, and finally complete something more in line with the purpose, give back to the demand side, and realize the value in the market.

This power flywheel that forms a positive cycle needs someone to jump out of the original negative cycle to generate additional force. So we have to recognize that the demand side is often not intentional, his seat is not easy to sit, and more assistance is needed.

Sharing is Caring