Developers often find themselves at the end of the production chain that already seems to be messed up even before their work has begun. Facing unrealistic deadlines, small budgets or missing specifications can cause frustration and helplessness. Here are a few thoughts that can help to improve your production workflow and meet the expectations of developers

1. Involve Developers early in the process

2. Clear requirements

Writing a good briefing is important. How can a developer start on a project without understanding how it should work? Handing over undercooked project project specs will cause frustration and slows down the development process. If you follow my suggestions of point 1 it should be a pretty easy task to sit down together and define the final project specification before heading into production.

3. Missing Project Leads

Developers often find themselves in the role of the master mind of a project. Probably because they tend to dive deeper into things than anybody else before. Define somebody in the team who owns the product, who will keep the overview and is willing to answer and think of any questions raising.

4. Changing requirements

Constantly changing specs during production is probably one of the biggest game breakers for developers. Even an agile workflow needs a stable scope of work for every sprint. So don’t throw tasks into the production cycle that are not thought through or feel imperfect.

5. Context switching

Context switching can cause huge problems regarding efficiency.
Asking a developer to switch from Task A to Task B is pretty tough since the time that it takes to get into a new scope is pretty high.

7. Take responsive design serious

The majority of website designs are delivered desktop only. Responsive states are discussed in passing which is totaly fine for most of the cases. But as soon as components become more complex, have a lot of interactions and different states, just talking about the responsive version won’t work anymore. Try to find a way to communicate your visions and help you to think through responsive states. Team up with developers and think about it together and you probably don’t have to deliver final designs, sometimes wireframes do the job perfectly fine.

9. Missing breakdowns and style guides

Browsing through a huge PSD or Sketch file in order to collect used fonts and font sizes, colors and icons is simply a pain in the ass. Provide breakdown sheets that provide basic information about your design work. Furthermore it can serve as the template for a frontend styleguide to onboard upcoming team members quickly.

10. Regular meetings with the whole project team

Just do it. Meet up with all project memebers on a regular basis. It will keep the process transparent for everyone involved. Talk about the projects scope of work, the current timeline and about outstanding tasks for the next day or two. Discuss incoming requirements and different opinions anytime. But try to keep this as efficient as possible. 10–15 min standup meetings every day should be enough.

I was inspired to write about this after reading that excellent article

I’m a Frontend Software Engineer currently leading Design Systems and Design Tooling at ResearchGate. Follow me: @weaintplastic

I’m a Frontend Software Engineer currently leading Design Systems and Design Tooling at ResearchGate. Follow me: @weaintplastic