Internal presentation how the Tradesy Design Team works together to solve complex problems, how you can improve your taste for design, and how to deliver effective feedback.
the team you actually have, not the team you wish you had. In most companies, you won't find one of the world's top 100 interaction designers waiting around to work on your project.
hence the use of the letter “T” to describe them. These characterisitcs represent the Breadth of Experience (x axis) and their Depth of Expertise (y axis). Depth Breadth The vertical stroke of the “T” is a depth of skill that allows them to contribute to the creative process. That can be from any number of different fields: an industrial designer, an architect, a social scientist, a business specialist or a mechanical engineer. The horizontal stroke of the “T” is the disposition for collaboration across disciplines. It is composed of two things. First, empathy. It’s important because it allows people to imagine the problem from another perspective- to stand in somebody else’s shoes. Second, they tend to get very enthusiastic about other people’s disciplines, to the point that they may actually start to practice them.
is that if you place your trust in a good process, then the end result will probably be pretty good. It’s that simple.” “I consider it a night-and-day difference between arriving at a solution on the first try and arriving at a solution having gone through rounds and rounds of iteration. The latter tends to produce better results, and even if it doesn’t (maybe because you just so happened to design a great solution right off the bat) the process matters.” https://medium.com/the-year-of-the-looking-glass/build-a-trustworthy-design-process-89e964d0a3a5#.473w43yg8
Research (or even worse, Sketch or Photoshop), it’s crucial that you sit down with your working team to define the design goals and constraints for your initiative. Doing so will allow you to anchor your efforts based on a mutual understanding of clear goals, business needs and scope. You are also able to question the logic and rationale of the initiative itself. This will make your life a lot easier. All it takes is a kickoff meeting. Meet with the working team For larger initiatives this will be the UX Designer, Product Designer and Product Owner. It’s important that all members are present for the kick off, so there is mutual agreement on stakeholders, design challenge and metrics of success. Fears, Uncertainty and Doubts Scheduling and Estimation Choosing Design Activities Problem Statement Business Goals Metrics of Success Timelines Scope Stakeholder Identified
in the Design process. Designers can create a beautiful solution to most problems, but this will not help your business or goals if you are not solving the right problem. Research allows us to anchor our designs with qualitative insights and quantitative data which we use to better understand the landscape surrrounding the problem. We are then able to take these facts and insights to create Design Principles and Feature Set Requirements. Dive in head first! Start with the Fears, Uncertainities and Doubts you identified earlier as a starting point, but there are many different ways to glean insights. Determing the right activities to learn more will ensure your design is comprehensive and most importantly, solving the right problem. Types of Activities Competitive Analysis Data Analysis User Interviews Stakeholder Interviews How Might We Design Principles Quantitative Insights Qualitative Facts Feature Set Requirements Final Definition of Problem Site Audit
done the research. It’s time to start creating your design! The key with ideation is to iterate on as many ideas as possible. Stay low-fidelity, as broad exploration is preferred over narrow focus. As you groom the ideas you like the most, it’s crucial to get feedback before investing a lot of time in any concept. The earlier and more often you share, the easier it is to change and adapt. Start with grounding yourself with the facts, insights and Design Principles you created in the earlier stages. From there, the workflow is your own, as long as you are getting feedback early and often. Types of Activities Collaborative Creation Design Reviews Stakeholder Feedback Sessions Design Concept Wireframes Core Flow Visual Design Prototypes Testing Plan
problem. You’ve done the research. It’s time to fully build out your solution, right? Not so fast. For a big initiative, it’s absolutely vital that you test your concept with real users. Data and insights get us so far, but there’s nothing like seeing real, live users interact with the core of your product. You will either reinforce your initial hypothesis or learn that you are wrong. Both outcomes are invaluable uses of your time. Somehow, some way get real, live people to use your concept. Usually this will come from a prototype you’ve made. There is no perfect way to test with users, but you have to do something. User Testing A/B Testing (in some scenarios) Insights from Users Decision (go or no go) Additional Features for future iterations
research, built a compelling concept and validated it with users and stakeholders. You’ve done great design work. Now build the thing. How you execute on your design will vary widely from project to project. Projects that require a lot of visual design will naturally be different than those that are more content focused. Ensure that there is solid planning and communication before jumping in. Types of Activities Project Plan Design Spec Edge Case Identification Visual Design Front End Development Design in in the wild.
have launched your design, but there’s a massive opportunity to learn and to optimize. We rarely get it right on the first try. Instead of launching our first solution and moving on, it is essential to reflect on what happened. Reflection is also invaluable because it gives you an opportuntity to kill features that are not adding value or even imposing negative value. Meet with your core team after a fair amount of time has passed since the release of your design. Revisit the Definition stage and ask if the Design achieved its goals in terms of metrics. Types of Activities Retrospective Data Results Qualitative Results Decision (Leave Alone, Optimize, Kill)
Rules for the Reviewers Presenter has the ability to present without interruptions or feedback (clarifying questions only!) Presenter sets the context: -Design Goals -Type of Feedback -Metrics/Research to Share -Next Milestone/Review in Design Process Phone and Laptops away No Interruptions Write down feedback to share later When sharing feedback, note both positive and negative attributes about the design.
ummerr
tooomo
recruitengineers
tsuyoshika
yasuhiroyokota
minamitary
chatwork_hr
euralisw
torije
webnaut
hirokazu_oda
yamatoiizuka
medley
sachag
nonsquared
smashingmag
cassininazir
lara
pauljervisheath
jlugia
chrisshort
philhawksworth
mojombo
bkeepers
