DesignOps and GeneXus

Official Content
This documentation is valid for:

This page and the related content discuss DesignOps, what it solves, what GeneXus solves, and how.

The Problem

What is the problem with traditional development methodologies, even modern ones?

Is it enough to have a DevOps process where there is true integration between developers and operations? Or with DevSecOps where computer security people sit at the table?

All those things are necessary, but in the era of UX, in the era of digital transformation, there is a great need to bring to the table people that are experts in interactions with users, experts in visual design, and experts in information architecture. The current problem is not only the increase in complexity in the development of systems but also the failure of many systems and projects because they do not have a mentality where users are truly put in the center of the scene.


To solve this problem and obtain better results in all touchpoints with users, the word DesignOps was born.

Paraphrasing DevOps, DesignOps was born, where the UX of solutions is given the greatest relevance and in a process that consequently implies a change of mentality, a change of culture, and of course implies changes in the tools we use.


According to Nielsen Norman Group, DesignOps is:

"DesignOps refers to the orchestration and optimization of people, processes, and craft in order to amplify design's value and impact at scale."

DesignOps like any process implies not only the change of tools but also the change of mentality.

In this change, it is essential to know what are the roles that are needed to start a path towards DesignOps.

Switching to DesignOps

Once we are willing to change our mentality and put design the right place, we have to move to start using the right tools and motivated people to do the change.
This process can start from a single person willing to acquire new skills or something that will surely emerge later is really diversifying the team with different people.

The choice of GeneXus as the development platform simplifies several DevOps steps, now in version 17 the first steps are being taken to simplify DesignOps processes.

In particular, in GeneXus 17 the GeneXus platform did the first step towards true integration with designers.

The first step

A first step that will simplify the interaction process between a visual / interaction designer and a GeneXus developer front-end is the choice of Sketch as an application design tool.

New tools will surely be incorporated in the future, but today Sketch is one of the most advanced tools in terms of its extensibility and openness, which makes Sketch today an ideal companion for DesignOps processes.

In this step, GeneXus create a plugin in Sketch in order to exporting your design and it creates an inspector in the GeneXus IDE in order to import sketch design. Sketch Import option


Please help us improve, we want your feedback! Be part of the conversation in the GeneXus Designers Google Group (you can subscribe at