AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |
Back to Blog
Pixel perfect design8/10/2023 A common pattern of doing a formal design phase is that designers often work in a silo, isolated from the developers who will build the solution. ![]() This is probably the most common way that design and development interact, based on what most designers and developers have described to me. When starting a new project or kicking off a new milestone, or starting a new sprint or build phase-or whatever jargon your team uses, how many of you have heard (or maybe even said) something like “we’ll start with a design phase, and then we’ll move into the development phase”? Traditional Design-Development Interactions So, let’s look at a traditional or common design/development interaction. Instead, let’s think about how design and development could better work together. Well, first: people are complicated, but that will never change. Why is that? We’ve been building software for decades now, and there are still problems at the seam of design and development, despite having had to work together for so long. You need an engaging and intuitive experience, so your users don’t find another solution-that’s the mandate for design.īut, traditionally, the intersection between design and development is messy. ![]() You also need an experience that users will come back to again and again. However, one thing that is consistent throughout all of my experiences is that both design and development are crucial components to the project’s success.Ī functional system that provides the functionality your users require is insufficient to attract, engage, and retain users. And in that ten years, I’ve seen and participated in many different software development processes and interacted with developers in many different ways. I’ve been designing and building software for almost ten years now.
0 Comments
Read More
Leave a Reply. |