![]() ![]() ![]() This work item got accepted without key information that our designers learned through user interviews. An email is still a user interaction, and was totally within the right of the designers to weigh in. We were all “oh there isn’t any UI in this so we don’t need a designer,” thinking that because we weren’t putting a button on a page, designers wouldn’t be interested. I remember this one work item about changing the content of an email alert. Our designers weren’t being looped into the work in progress. Our developers were completely ignoring designers when they ask for a developer’s input on a design work item. We experienced a few problems with the way that we originally organized a team of developers and designers. My team is a group of 8, made up of 1 product owner, 2 designers, and 6 developers. It requires developers investing in discovery and design, and designers investing in development and delivery. The idea being that the entire team is responsible for and invests in the entire product development process. My team chose a third way, which you all probably know as Dual Track Development, where we came together as one team under product. And since the developers “were here first,” there’s an easy and terrible potential for us to think of “incorporating designers into the development” rather than “incorporating developers into the designing.” SEP started with developers, grew by hiring more developers, evolved by hiring designers. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |