Why Peer Programming With A Designer Is A Powerful Methodology
In a world where old and never-ending processes are replaced with fresh and quicker models, spending efforts at the right place and at the right time is becoming more crucial than ever. And it is all about communication efficiency.
Peer programming is an agile practice that includes at least two programmers learning from each other in one unified setting.
Developers tend to lose focus when they are alone. They get stuck on irrelevant aspects of a feature development. The benefit of peer programming is that you avoid this natural pattern. When paired with someone, it gets easier to stay focus and head toward goals faster. With a co-worker beside, you keep away from getting lost in the vast galaxy of possibilities.
Designer are no different. This is why adding a designer to peer programming works really well. By reducing the amount of contributors, communication is improved for more efficient work.
Improve Communication
Cover the basic first with an evolving design system
In order to improve the fluency of discussions between a designer and the developers, have a design system that covers generic guidelines. This will give them more room to deal with deeper problems. This is where efficiency starts.
If you want to know the basics about how to create a design system, please read my previous article about it.
Aim for simplicity by getting rid of useless contributors
Documentation management is a tricky beast, but essential. While having the generic information covered in a complete design system, user stories will cover the complex information about specific features. These two information holders will cover 80% of the feature’s specifications, which is quite enough.
The last 20% is all about crucial details that are hard to think of at first. It gets more complex as you approach the last part of development. Specially when there is to many people involved through too many documents and channels. This Hellish 20% is where surprises appear. This is where communication f*cks everything up. This is where people start getting nervous. Focus disappears and all hell breaks loose.
Simplify the chain of communication for better management. Empower you designers and developers with knowledge, decision power and trust.
Designers & developers together
Designers are not developers. It is really challenging for them to think about everything that would make sense in a developer’s point of view. Moreover, a developer will also have a hard time to think about everything. Even when they sit together to determine the scope, they rarely determine exactly how to do something before they really do it. Discovery is present throughout the process of development.
Don’t think too much. Don’t try to avoid mistakes because this is where problems are defined properly. With the problem defined, you are left with solution solving. Embrace chaos, let mistakes happen and let the designers and the developer peer program.
Final Thoughts
You may think that having a designer sit beside a developer is a waste of time because the designer “does not design”. In fact, it is quite the opposite. It is the most efficient way to design when you can see what you get. The faster you get these two working on problems together, the faster you will be releasing your features. Because this will reduce the number of blockers to a minimum. Empower those who develop and you will produce more.
Everything is about doing mistakes and rectify through proper communication.
Communication is complex, but important. Old processes suggest that you add as many people as possible in order to improve communication. Well, rather than improving communication, it reduces the accountability in order to avoid taking the blame. More people are speaking to each other, but less work is done because the process is way too long. Mistakes are crucial because they point toward what does not work. The faster you know what does not work, the faster you get sh*t done. So stop talking altogether, give power to your people, make mistakes and let the peer programming find the solutions quickly.
Related articles
I have written an article about the importance of learning to fail in order to grow bigger and faster. Don’t add people to avoid mistakes. Provoke failure and learn from it.
We live in an era where it is way easier to create consistency, save time and improve productivity. Read the basics of creating a design system to improve the efficiency of your company.
The last version of Sketch now handles UI Libraries perfectly. Benefit from this efficient software to create strong and consistent user experience and user interface.
I also write about a lot of methodologies and philosophies that are applicable on many portions of your work.
Please feel free to follow me if you consider my content relevant and useful. Don’t hesitate to share your thoughts! :)
Cheers!
T.
