What is a citizen developer, and can anyone become one?
Citizen developers are analytical thinkers with domain knowledge.
Read more
Anyone delving into the world of low-code quickly comes across the term “citizen developer”, as a counterpart to the professional software developer. What exactly does this mean? Can anyone become one? And what qualities make a good citizen developer?
A citizen developer is someone who develops applications using low-code (or no code), with no formal background or training as a software developer. Because building with low code is primarily visual in nature and uses existing components, a citizen developer does not need to have extensive programming knowledge.
Citizen developers are usually analytical thinkers with a lot of domain knowledge: they work within the organization and have a lot of knowledge and experience with the business processes. They are almost always professional knowledge workers who can abstract information, model and are good with logic. Citizen developers don't have to be in IT; these individuals can be found throughout your organization. In fact, in low-code environments, an skilled citizen developer can develop as fast as a traditional developer.
What is the difference between a citizen developer and a traditional developer?
The difference between a citizen developer and a traditional developer is in the way they develop software.
• A citizen developer creates software with low code or no code, mainly based on a visual interface and using existing components or building blocks.
• A traditional developer uses code to develop software.
Typically, a traditional developer has formal IT education and extensive expertise in the field. However, that is not always the case as software development is a field in which you can go far with self-study, or on the job training. Ultimately, the difference between a citizen developer and a traditional developer lies primarily in the way they work, and secondarily in their knowledge and background.
Low-code is not only suitable for citizen developers!
Software developers with considerable IT knowledge can also work very well with low code. A technical background and solidly trained analytical thinking skills definitely help to be fluent in low code. In addition, programming knowledge is not necessary, but it can certainly come in handy.
Low-code also has benefits for traditional software developers:
• Low-code allows you to develop much faster than building from scratch. This is true for any high code software developer, including experienced programmers.
• For less experienced developers, low-code is a great way to learn quickly and get results.
• Additionally, low-code is an efficient method for creating meters and prioritizing tasks , knowing minor details are taken care of. The Grexx environment takes a lot of work off your hands, without you having to start from scratch, especially when it comes to aspects like security and compliance.
Within Grexx Platform, you can have the ability to choose to build part of your application with code. This can be helpful when low-code options does not offer the desired outcomes, or when you just can't resist writing a piece of code.
Can anyone become a citizen developer?
The answer is both yes and no. In principle, anyone can get started with low code. But it is not equally suitable for everyone. Low-code is especially suitable for IT and professional knowledge workers with strong analytical skills as well as people with a lot of domain knowledge. We distinguish two groups:
Citizen developers and analytical thinking skills
Having strong analytical skills can greatly assist with developing applications with low-code. In practical terms, we're talking about abstracting processes or tasks into models such as the classic "if this, then that" approach but on a larger scale.
An analytical thinker can easily identify what is needed to get from point A to B. For example, if a support request comes in, then process X, Y and Z need to be set in motion (with a if or but here and there, for which other processes apply). If you can visualize these types of workflows, then your analytical skills are solid. Logical reasoning (logic), problem solving abilities and efficient information processing will also help.
A colleague with these types of qualities would make an ideal citizen developer, able to create low-code applications quickly and successfully with relatively little training. A citizen developer with these skills can get ahead in low-code just as well as a traditional developer without requiring extensive knowledge of IT or programming.
Citizen developers and domain knowledge
The second group consists of citizen developers who have extensive domain knowledge. These people know a field like the inside of his or her pocket, for example the processes that mortgage lenders must deal with in the financial sector. A domain expert knows exactly how those processes work, what the laws are, what unwritten rules apply, what exceptions are encountered. Becoming a domain expert takes time and experience.
To note: Domain knowledge can refer to a (part of a) field, but the term can also be used for the specific course of action within an organization such as, for example, a credit acceptor who knows exactly how the application process works, and a support person knows how to tell you everything you need to know about the various support issues the company faces. From that point of view, it can make a lot of sense to use a credit acceptor or support employee also as a citizen developer.
However, this second group of citizen developers may not have the necessary skills to independently develop low-code applications as analytical thinking is essential. Nonetheless, they do have the necessary knowledge and experience to test, maintain and extend existing low-code applications.
What makes a good citizen developer?
Besides analytical thinking skills and domain expertise, there are plenty of skills and traits that can come in handy as a citizen developer including:
• You want to be or become a citizen developer
Perhaps an open door, but still: that credit acceptor or support person we talked about earlier will only become a good citizen developer if he or she is interested in it. If the interest or attention is not there, then it will be nothing.
• Solution-oriented work
A good citizen developer is curious, likes to puzzle and works solution-oriented. Developing applications with low code is largely about solving problems: you identify and diagnose the current situation, you come up with a solution, and you implement it.
• Critical thinking
In addition to coming up with solutions, you must also be able to really take a critical look at your own solutions. Is what you came up with really the right choice? When does this solution not work? Are there exceptions, and how do you deal with them? What else do you have to take into account? If you can identify and eliminate the obstacles on the way, the quality of your work will improve.
• Creativity
Those who dare to think outside the box will get further. Since low code consists largely of building with existing elements, it helps when you can look at it in different ways.
• Empathize with the user
Good chance that the applications you build will eventually be used by other people. For example, by customers, colleagues or suppliers. If you want them to use the application properly, you will have to empathize. What do they expect? How do you make the application foolproof?
• Working systematically with an eye for protocols
Those who develop models will have to be systematic. If you always build applications in a similar way, you make managing them a lot easier. This also includes paying attention to the protocols that apply within your organization. Think about governance, privacy, security and best practices used.
• Flexible attitude
Anyone who starts working with technology will soon notice that developments follow each other in rapid succession. Without an IT background you might not be aware of this, but technology changes rapidly and as a citizen developer you will have to be able to deal with this. Learning fast, embracing new tools, dealing with feedback and continuing to develop yourself are great qualities for a citizen developer.
There are many other qualities and skills that a good citizen developer can benefit from. Think for example of having an eye for design, being able to fathom data quickly or good communication and cooperation. The list is basically endless - the above seven points at least give you a good start!
Citizen developer support, training & certification
At Grexx, we think it's important that citizen developers actually get to build themselves. We do everything we can to support you in this. We offer an extensive learning environment in which we teach you or your team how to work with Grexx low-code, and it is also possible to record your skills in a certification.
In addition, we offer a number of other forms of coaching & consulting, including the weekly Q&A session where you can get to know the Grexx community and ask questions live. Apart from that, we have a solid support team that will gladly look with you, should you get stuck on something. Together we will make sure you can get back on track.
You now have an idea of what a citizen developer is and what traits are useful in that role. Want to spar about what that's like for you or your team? Feel free to schedule a discovery call ! Our team is happy to think with you.
Curious about all the options?