Collaborate more, communicate more – this is the most important motto of modern product development life cycle – very different to what it was in the past. Days when roles of designer and developer was so clearly separated from one another are gone.
We need to put them next to the same table and let to work as one man. This opens a world of opportunity to improve and speed up submitting finished product to the store.
How close cooperation between designer and developer can shorten the development process?
#1 Instant problem solving
In Mood Up Labs we’ve noticed that pulling conversations out of text barriers and even digital calls increased our productivity a lot. Gathering feedback is quicker, solutions can be found in fast team brain storming and everyone gets on the same page immediately.
Email isn’t fun. It’s also slow, hard-to-follow way of talking. We know it so we start use applications like Slack and Skype. They add a big dash of fun but still… explaining something by tapping many, many keyboards keys can be painful. So what next? Recording audio message? Video conversations?
Maybe just a quick talk face to face?
#2 No more backtracking
We build app with the title powerful mix from scratch – working together prevents having to backtrack after something has already been approved by the client. In Mood Up Labs we know that joining forces can eliminate hiccups.
Designer is a keeper of client’s idea and he explore it everyday with developer who can make him evaluate the choices he might otherwise take for granted.
Pair programming is well known technique to boost yield, and simply being familiar with design before it hits developer plate can make building things so much easier for him, so we pair programming & designing to be sure that we can hit in client needs.
#3 Budget-friendly project
Both the developer and the designer have different tools and they use them in different ways. Developers are from technical standpoint and they can propose some new concept, more budget-friendly design, while designers being ingenious can meet it with original arrangement.
When two different minds collaborate to solve a problem, they create some type of harmony and we take advantage of it. There are situations when designer project something that looks like it will be superb, but once it gets built, it might not be so cool. Developer is the one who can foresee this might happen.
#4 Speed up the process
As we stated above, getting on the same page immediately is crucial to get things done easier and sooner but it’s not friendly to achive in industry passoniate by asynchronous electronic communication, that’s why we have both the designers and the developers on board in Mood Up Labs.
Documentation is irreplaceable as a reference but alone it often doesn’t matter – beyond that, there should be regular two-way solutions transmission in person. Marked-up screens aren’t the same as asking best friend sitting in front of you, especially in time when dynamic products require dynamic solutions.
When I joined Mood Up Labs, I’ve started to understand this. Communication is the key – found it incredibly useful to my designing to have developers in the same room. We start being collaborative team managing to accomplish significant amount of high-quality work in short timeframes.
We work in Agile and within our daily meetings, we discuss each other work, what and how have to be done further, find ways to improve and create well built product. It was new to me, but it turned out to be the best what we can do for clients.
We’d love to hear your opinion – what’s other ways that close cooperation between designer and developer benefit projects?