Once upon a time, in the magical internet forest, Desi and Devy were walking along the banks of Web Creek. They had reached the widest and deepest part when they came upon Mr. User the turtle.
“Hi Mr. User!” exclaimed Desi and Devy. “What are you doing?” they asked.
“Hi Desi and Devy. Well, the creek is higher than usual, and I’m trying to figure out how to get to the other side.”
“We can help!” said Desi and Devy, and they started working out how to help Mr. User.
Desi, who always carried a notepad and pen, started sketching out a plan. She quickly finished and showed Mr. User a picture of a sail made out of leaves attached to his shell.
“That’s nice,” said Mr. User, “but…”
Just then Devy appeared from behind a tree with some sticks and branches wrapped together with twine.
“I made you a raft,” said Devy.
“Thanks Desi and Devy,” said Mr. User, “but my legs are powerful enough to propel me through the water, so I don’t need a sail. And my shell keeps me afloat, so I don’t need a raft. What I need is a rudder to help me navigate the fast-moving current. Can you work together to help me with that?”
“Yes!” said Desi and Devy, and they got to work.
“I’ll sketch a solution,” said Desi.
“And I’ll build it!” said Devy.
So Desi sat down to begin sketching, and Devy went off to find some materials that he might need.
When Devy came back, Desi handed him the final sketch and said, “I’m going to go talk to Mr. User about this while you build.”
As Devy was building, some of the parts of the sketch weren’t possible given the materials on hand, so Devy modified them a little.
Devy put the final touches on Mr. User’s rudder, and went back down to Web Creek where Desi and Mr. User were talking.
“That’s not what I sketched,” said Desi immediately.
“I know,” replied Devy, “but parts of your sketch weren’t possible with the materials I had.”
“Good work, both of you,” said Mr. User. “But I think if you really work together, you can come up with an even better solution for my rudder.”
So Desi and Devy sat down and discussed Mr. User’s needs, the materials they had, and the best way to create a rudder to help Mr. User cross the creek. Desi sketched and Devy built. And in the end, they created the perfect rudder for Mr. User.
“Thanks Desi and Devy!” shouted Mr. User and he set off across the creek.
“You’re welcome!” shouted Desi and Devy back.
All great stories have lessons we can learn from. While this isn’t the greatest story, there should be some obvious lessons we can learn about collaboration between design and development.
Before we can understand these lessons, we need to look at the design and development roles to see why working together is so important.
In its most basic form, the designers role is to create a visual representation of the client’s goals that a user or customer will then use to reach those goals. This includes colors, images, headlines, body copy, and user interface design.
Essentially, both design and development are creating the same thing, each with their own tools, based on the goals of the client. Which brings us to our first lesson.
1. Understand the User’s Needs
Both design and development need to be on the same page when it comes to understanding the client’s – and ultimately – the user’s needs.
During the discovery phase of the project, the client should be able to give information about their goals that should dictate the direction of the project. As the discovery phase progresses, there may be more information gathered, such as industry trends or user feedback in the form of study groups, that may also help solidify the client goals.
When everyone is on the same page about what the client and their users want, the outcome is a cohesive project that satisfies the requirements of the client and shows them that they were listened to and understood.
And to be on the same page means we need to understand lesson two.
2. Constant Communication
Design department and development department need to be in constant communication during all phases of the project, not just at the hand-off from design to development.
During the design phase, as the designer creates elements for user interactivity. Development should be present to talk through those pieces to help decide what will work and what won’t.
When design hands the project over to begin development, a style guide can help developers stay true to the designer’s vision, as well as stay on brand.
Understanding the user’s needs, working together, and constantly communicating are the keys to successful projects.