Mexican drug cartels communicate with bullets and knives. If you try to enter their territory, they will communicate very clearly and effectively this way.
As a UX product designer, the Project Brief is the first major document I need to have for building a product. If there is not one already, I create one or add to one. The following are the key questions that the brief needs to answer. I don’t always use every question, but I try to fill in as much as possible. It becomes the foundation of the project and becomes the source of truth. For this reason it must be updated should truths be changed or discovered. It is shared and open to all members of the project. Project Name Project title, code name and AKAs. Dates & Milestones Start date. Launch date. Major deadlines and targets if any. Other critical project dates. Description An overall description of the product. What problems are we solving and why? What is the goal? Key Team Members Stakeholders and project owners. Who signs off? Product Owner, Project Manager, BA, Designers, Developers, QA, others. Target Audience Who are th...
I have been managing staff now on and off for nearly twenty years. Although I still have a lot to learn, obviously, or at least I hope, I have learnt a thing or two and feel that perhaps it is time to share one of the most important lessons. That lesson is to respect your staff. Work is all about people. People are… well… people. They’re human. The point here being that they are not machines and do not react well to being treated like machines. They do however react well to being treated like people. Sounds like logic? You might not be surprised to hear that I have found this to be not commonly understood or practiced. I have no respect for the computer I am writing this on. None at all. I treat it like a machine. I abuse it, hammer it, and work it relentlessly. I do however have a deep and sincere respect for the people that built this wonderful machine. You see the difference? Respect your staff. Why did you hire them to begin with? Hopefully you hired them because they know th...
Understanding A fundamental function of the UX design department is to give the end user the best possible understanding of the application and its workings. The elegant solution is sought based on the designer’s intimate knowledge of the User Language. For this reason it is important that the designer understands Understanding as a concept. So what is understanding? You know the answer, but how does that help you? What you really need to know is what creates understanding. We know what it is but how do we create it? How do we increase it and manipulate it? To do this we need to break it down into the parts that make up understanding. In the world of design we hear a lot about communication, excitement, trends etc. Yet there is a lack of knowledge as to how all these tie together to improve the end user’s understanding. They all fit into the three parts that that make up understanding. These three parts are Affinity, Reality and Communication (ARC). Together they make understanding. Th...
Comments
Post a Comment