What I frequently get back is half of the design. So I turn over mockups and workflows-in the form of stories or task diagrams-to the development team. Nor is there an opportunity for me to provide templates in HTML and CSS for every part of an application.
This means there is not a lot of time for creating detailed design specifications. That design gets vetted, iterated, and ultimately documented.īecause I mostly work with fast-paced Web companies, I frequently have to create my design documentation under aggressive timelines. I work with the product team to balance user goals, business requirements, and technical considerations to create a product design. We also frequently encounter the same issue: the need to consider what’s not there. We debate product strategy, information architecture, target audience, front-end technologies, and more. We discuss edge cases and clarify how specific interactions should work.
We work through what interactions and features are possible given our timeframe and resources. From big companies to small startups, the interactions between me-the product designer-and developers have been pretty consistent. During my years as an interface designer, I’ve worked with lots of different development teams.
0 kommentar(er)
