Full Stack Designers aboard!

Our Creative Team has been dynamically developing over the last three years. Within this course of time we have elaborated methods and models which have greatly contributed to our success and growth. Specially, we have found really important three attributes such as the right designer’s profile, designers’ working methods and a cooperation quality between designers and developers. What benefits could that bring to any company with an interdisciplinary team system? Read the blog post to obtain an answer.

Can you think of a dream designer’s profile?

To create a great consumer product interdisciplinary team has to skillfully use the power of its different fields of expertise. I mean combined work of backend and frontend developers, testers, project managers and, yes who else? To design a product, conceptual, analytical and visual parts have to be completed and supported with user input. In some companies this scope of work is performed by different individuals. That finds reflexion in a professional titles like: UX Designer, Information Architect, Interaction or Graphic Designer. In Polidea we have applied a different approach, most of work is conducted by Full Stack Designers. Let’s take a closer look into who they are.

Getting familiar with a model of Full Stack Designer

Full Stack Designers lead the whole design process — from an idea outline to the final product release. They possess a set of analytical and graphical skills. Their great sense of user experience derives from social science knowledge that is clearly demonstrated during workshops with clients and users. If they encounter something which is beyond their scope of skills they know whom to to ask for help and how to liaise to achieve the best results. The Full Stack Designer knows how to collaborate with the in-house team of developers and knows how to communicate with a client to acquire needed information. Being more than just a cog in the machine is what being full-stack is all about.

Why are we so hooked on Full Stack Designers?

Does this set of skills sound like to much for one person? Believe me, it’s not. We’ve empirically proved that Full Stack Designers are desired employees these days. Here is why:

They know the context

Context is a key. By being in a project from the beginning till the end designers are able to fully immerse in and control it. They understand the reasoning, motivations and limitations of particular operations. Having such broad perspective it gives them ability to stretch beyond constraints and improve project at any stage of the process.

They manage a sequence of events

The subsequent stages of design are often inseparable, e.g. the screen layout structure with graphic design. To let one person embrace all means to let oneself freely flow through the interweaved design steps. The work isn’t linear, it can be refined by iterations. Yet, the gradual outcome shouldn’t be hand over from one designer to another, it consumes too much time and you lose ability to create a consistent design.

They feel responsible and attached

A sense of ownership creates a sense of responsibility. As a full time project members designers feel more engaged and attached, both with the product and the team. They simply care and don’t give up on enhancing the design solutions.

They foster self growth

Full Stack Designers self progress is a constant process. They know how to diagnose, analyze and take an action to solve any problem. Their versatility don’t let them to be categorized and assigned to a particular field, e.g. graphic design. They learn all the time and rather avoid routine. Such approach boosts their creativity and foster their growth. They feel completely in their element when working in a company with a flat structure. Too many constraints can get them frustrated and diminish their abilities.

Full Stack Designers stand behind our final product quality

A Full Stack Designer is clearly a win-win model in our company. Our designers are the ones organizing research, creating wireframes, checking out UX patterns, organizing UI design, and generally making sure we aren’t ending up with stunningly beautiful apps that simply don’t have a purpose. My next blog post will be about full stack design process seen from different perspectives which are crucial in reaching understanding of a product development stage. So stay tuned it will be an interesting reading.


Originally written by Karolina Chmiel for www.polidea.com.

One clap, two clap, three clap, forty?

By clapping more or less, you can signal to us which stories really stand out.