Before briefing a stakeholder, a product designer must:

The main goal:

• Understand people’s problems

• Develop a design that will improve people’s lives

• Bring profit to the product and stakeholders, and a salary to me

A stakeholder is a person (in the future it may be AI) who influences the product and is interested in its development.

Who can be a stakeholder?
Any team member can be a stakeholder. Also, each stakeholder has information that will be useful to us.

The first task of a product designer is to understand everything that exists now, and not to invent solutions and something new:

1. Key
   Is a stakeholder on whom a lot depends. He is the one who invests more time and money and depends on making a decision that will affect the entire product.
   
   

2. Technical
   Is the stakeholder responsible for the technical implementation of your designs. If his opinions are not taken into account, then it will likely be a big problem at the implementation stage of any idea.
   
   

3. Managerials
   They are stakeholders who are responsible for communications from the client’s side with us. That is, the CEO of the product does not always have time to be at your demo, and he just delegates these issues to his manager.
   
   

4. Users
   Are stakeholders who have access to valuable information from the users’ point of view. Most often — these are support workers. That is, they are always called and written to with complaints, and they hear a lot from users that no one hears. It is useful and necessary to communicate with them. If they are. If they are not there, then you need to look for users from the other side.
   
   

5. Legal
   Are the people responsible for the legality of your future designs. That is, all these ticks in the product about terms and conditions, or all these provisions about creating an account, it all depends on the lawyer.