![]() In general, both partners really value and enjoy working with one another!ĭesigners appreciate when engineers engage in design activities and ideate, co-create, and brainstorm. ![]() Talking to our colleagues here at Spotify, many things work well in the dance between engineers and design. How do we succeed with this dance?How can we get our disciplines to dance well together without stepping on each other’s feet? What are the secrets? We call this the DNE of the tech team – Design and Engineering – shifting weights and collaborating throughout the lifespan of a product or feature. ![]() This dance is the DNA of any successful tech team. Design and engineering will engage in a dance where the expertise of the disciplines dictate who’s in charge. The Scale is not a one-time cycle either. When design is driving, engineering takes the front passenger seat and vice versa, but the collaboration should always continue. When the leading role shifts, this should not be seen as a handover instead, the weights of the roles shift. When the product team has agreed on a solution to test and design has mapped out the user experience, engineering leads the way into making the solution real. Product and engineering get involved to ensure that what’s being explored has business value and technical feasibility. This goes beyond design and engineering but in this post, we’ll focus on these disciplines.įor instance, design, together with insights, might lead the way in the “understand it” and “think it” phases by bringing in the users’ perspectives, facilitating ideation sessions, and exploring as many solutions as possible. In other words, different disciplines have different weights in the various stages of the product design process. We believe that, in an ideal world, all disciplines are involved in all phases of a project, but their engagement varies. We take the learnings from the shipped product and tweak the solution to continue producing better results ![]() Ship these solutions as lightweight as possible to quickly learn from our users what works and what doesn’tĥ. We build the product, tool or service and…Ĥ. We understand potential user needs, wants, and painsģ. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |