If you’re a artist or a developer you know this story all too well: designers create a admirable ancestor or set of wireframes and ‘throw them over the fence’ to the developers. As the developers find that bits and pieces of the designs are either too labor-intensive or simply absurd to implement, the aboriginal designs slowly evolve during each sprint. 

What starts out as the Tesla of designs gets turned into a applied Subaru, with all the safety appearance and no-frills… or it ends up attractive like a beat-up junkyard scooter with no wheels. 

Designers start blubbering commodity about pixels and padding, devs send passive-aggressive Slack messages, and coffee break encounters become frosty. 

Why can’t we all just get along?

Including developers in the design action and designers in the development action can help you beforehand a much better workflow and aftereffect by accumulation their altered ability and perspectives. Does it really make sense to have this analysis amid two teams architecture the same product?

In the end, if you look deeper, the real source of battle comes from two factors:

  • The system (or lack thereof) in which the two teams work together
  • Team dynamics and environment

The botheration is, when you search the internet for best practices on how to help these teams work better together, you often run into acutely vague and very “self-help” aural principles: communicate, coact and co-create. 

During TNW’s Sprint Couch Series, Rangle.io’s Lead Visual Designer, Trish Lamanna, and Solution Architect, Omer Wazir, shared how they created their own chip access to ‘Dev-ignOps,’ enabling them to become more cross-functional, self-organized, and access their velocity. 

Here we’ll share how they turned the three C’s into applied steps which they could operationalize at Rangle, plus advice on how to create the right ambiance for acknowledged cross-functional ops.

1. Beforehand a common advice model

According to the Rangle team, advice isn’t about the tools you choose, it’s about the model you use to access problems, make decisions, and share information. It’s important to carefully choose and beforehand a advice model that works well with the size of your team and the outcomes you want to achieve. 

Lamanna explained that if teams don’t have a set operational model in place, they’ll automatically absence to a avalanche system in which designers come up with the design concept, hand it over to developers, and move on to the next project. At the same time, it leaves no room for cross-functional acknowledgment loops and iterations. In large teams with 20 people focused on work-intensive and circuitous projects, a tiered access is much more practical. 

Meanwhile, abate teams of under five people tend to use a swarm access to problem-solving, in which anybody gets calm to brainstorm, share feedback, and make decisions. There are no hierarchies and everyone’s assessment is heard, arch to cross-functional solutions. You’ll about see this in abate business teams alive on agreeable improvements to an absolute CMS.  

But what if you want the best of both worlds?

At Rangle, Lamanna and Wazir were tasked with architecture an app that would affix to a medical device with a medium-sized team of 14 people. They accomplished that a purely swarmed or tiered access wouldn’t work for them.

Instead, they absitively to create a semi-swarmed analytic approach. This meant that in amid their antiquity flows they’d swarm calm to analyze abeyant problems and create a plan of attack. Then they’d abstracted to solve those problems in a tier-based structure. 

2. Establish accord rituals

To operationalize your advice model you need to set specific ‘rituals,’ or touchpoints, during which your teams or key players get calm to collaborate. This could be in the form of:

  • Weekly centralized team affair reviews
  • Product Owner gut checks
  • Ceremonies and demos
  • Design to development ticket flows on Jira

By establishing rituals, the Rangle team was able to accommodate designers, developers, and artefact owners in the solutioning process, analyze abeyant problems and opportunities for added functionality early on, and altercate how they would tackle other dependencies down the line. 

For example, when developing a medical app for an EU-based client, they accomplished they would need to accede how aloofness and GDPR regulations could already be chip into both the design and coding. This accustomed them to come to a common and accommodating plan in beforehand after having to make last-minute, time-consuming changes on either side. 

3. Create a plan to facilitate co-creation

Finally, co-creation is all about taking your advice model and accord rituals and putting them calm into a common workflow plan. 

To create an able plan, you need to accede the applied questions that could hinder or facilitate co-creation amid the two teams. 

Some of the questions Rangle advised were:

  • What advice does design need to share with development in order to allow them to ahead what’s coming tomorrow?
  • What can be done in parallel?
  • How does connected advance happen over time?

In the end, Rangle’s co-creation plan consisted of weekly tiered sprints. The design action was always one week ahead, giving developers time to share acknowledgment and apropos before design handed over the next set of apparatus to them. In this way, developers could already ahead the work that would be coming their way during the next sprint and improvements could be made continuously throughout both the design and development process. 

Creating an across-the-board and chip system is great but, as Lamanna mentioned, you also need to focus on creating the right altitude and behaviors for it to absolutely work. 

4. Build cerebral safety

Creating a psychologically safe ambiance is key.

Psychological safety is the belief that you can share your ideas, concerns, opinions, and mistakes after the fear of being ashamed or punished. In a study, Google found it was the most important factor needed when creating highly able teams. 

Even if you set up a number of acknowledgment loops and design/code review cycles, they won’t be able if people don’t feel they can absolutely speak up freely. 

In a TedTalk, Harvard Professor Amy Edmonson (who coined the term) shared three ways to beforehand a psychologically safe work environment:

  • Frame the work as a acquirements problem
  • Acknowledge your own fallibility
  • Model curiosity

5. Make your work transparent

Make sure both teams share a common space where they can see what others are alive on in amid accord rituals. 

This doesn’t necessarily have to come from a accord tool. Simply press out designs and storyboards and putting them on a wall in your office where developers (or anyone in the company) can accidentally walk by and see the latest designs during a coffee break can absolutely make a huge difference. 

At Rangle, Lamanna and Wazir shared that all activity discussions, whether on Slack, Jira, or GitHub happened on public channels so people weren’t left out of the loop. This is abnormally important now with most teams alive remotely. 

6. Beforehand a common language

In an adventure of Google’s Artist vs Developer Youtube series, Senior Interaction designer, Brendan Kearns, explained that redlining usually happens when designers and developers are speaking a altered language. 

More and more companies are now creating design systems, or libraries of designs and codes, which can be easily reused for altered projects. Airbnb calls their adaptation a visual language that allows them to build articles faster and ensure bendability across the organization. Interestingly, a few years ago, the aggregation also started alive on an AI tool that automatically generates sketches into artefact source code. 

Although time-intensive, starting your own shared design/dev library ecosystem which can be continuously developed over time will save you tons of time in the future. 

Check out this absorbing talk by web artist Brad Frost for more on the abstruse side of design systems. 

7. Encourage ability sharing 

Understanding and apropos where each side is coming from is key. It’s decidedly rare to find those designer-developer unicorns who know how to create a wireframe and code it themselves but it is clear that, if you’re lucky enough to have them on your team, they often bridge the gap by anecdotic abeyant issues ahead of time and mediating conflicts.

Offering acquirements and ability administration opportunities can go a long way in bridging the gap amid these teams. The more designers accept the coding that needs to happen behind the scenes to create their designs, and the more developers accept the accent of creating seamless user journeys, the better. 

Getting started

Every team, company, and botheration is altered so you’ll need to test, review, and optimize until you find the system that works best for you. 

As a starting point, Lamanna and Wazir advance first because the outcomes you want to accomplish and alive back from there. Do you want to make commitment timelines more predictable? Close tickets faster? Create self-organizing teams? Then create a system that will help your teams to get there.

This commodity was brought to you by Rangle.io.

Celebrate Pride 2020 with us this month!