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...
and Breaking Down the Design/Development Barrier The design department (the user interface and user experience kind) has always tried to influence the entire production lifecycle of a product out of an instinctive need to improve upon it from every angle possible. The same applies to modern day page & app design where the design department needs to have input from the very earliest concepts of the product all the way to construction and delivery. In this day and age and in the most forward thinking design departments, we are all designers. For this reason there is more and more overlap and connection between the various departments and indeed a complete breakdown of the siloes and walls when we form agile, multi-disciplined development teams. Here I want to talk about the overlap between design and front end development using component driven development. Component driven development is all about centralising, unifying and simplifying the design/development cycle. In the simp...
Comments
Post a Comment