Project Management

Citizen Development Insights

by , , , , , , , , , , , , , , ,
Citizen development is a disruptive approach to digital transformation and organizational innovation, where teams are empowered to turn ideas into applications using no-code/low-code technology. This blog provides insights, advice and practical knowledge from thought leaders and practitioners in Citizen Development.

About this Blog


View Posts By:

Cameron McGaughy
Ron Immink
Jody Temple White
Jason Mayall
Chandrasekaran Audivaragan
Jelili Odunayo Kazeem
Mario Trentim
Vivek Goel
Derya Sousa
Ryan Whitmore
Justin Sears
Raveesh Dewan
Dalibor Ninkovic
Ian Gosling
Kimberly Whitby
Tara Leparulo

Past Contributors:

Elizabeth Jordan
Arjun Jamnadass
Rogerio Sandim
Martin Kalliomaki
Richard Earley
Maelisa Woulfe
Octavio Arranz

Recent Posts

5 Top Citizen Development Myths Busted

Empowering Citizen Developers: Overcoming 5 Common Challenges Together

Citizen Development: The Path to Success Starts Small

Can No-Code/Low-Code ERP Replace Traditional ERP Platforms?

No Code, Big Bucks: How Citizen Developers Can Capitalize on the Future of Tech 


Agile, Best Practices, best practices, Career Development, CD Canvas, Change Management, Citizen Developer, Citizen Development, Citizen development, citizen development, Communication, Digital Transformation, digital transformation, Documentation, Innovation, IT Project Management, LCNC, Leadership, Lessons Learned, Low-Code, myths, No-Code, no-code, No-code and Gen Z, PM Think About It, PMI, PMI Global Congress 2013 - North America, PMO, Portfolio Management, Program Management, Programs (PMO), Project Delivery, Project Management, project management, Risk Management, ROI, software development, Stakeholder, Strategy, Talent Management, Tools


Engaging Stakeholders: A critical element to enterprise risk requirements

This post is the fourth in a series introducing you to elements on the PMI Citizen Development Canvas (see image below). These posts are designed to inspire you, share tips and insight, and further your knowledge and experience. I welcome your questions and encourage you to share your own stories.


In the last post, I introduced you to Business Analysis and Design. In this post, I will introduce you to Enterprise Risk Requirements. 

PMI CD Canvas - Enterprise Risk Requirements

Enterprise Risk Requirements is the component in the PMI Citizen Development Canvas that refers to functional and non-functional requirements within citizen development projects. It is also the area where the Citizen Developer identifies and manages other inherent project risks including stakeholder and communication risks. 


In this blog, I am going to focus on stakeholder risk and the importance of identifying, engaging, and communicating with them to improve the success rate of your project. 


Stakeholders - who are they and what role do they play?


A stakeholder is a person, group, or organization that has an interest in, or will be affected by, the application being developed. Stakeholders play a key role in the citizen development process. They help the Citizen Developer capture requirements and they provide valuable feedback. Stakeholders can be huge champions, or they can stop a project in its track.


Understanding who the stakeholders are, their influence, and how they perceive the project is critical, so one of the first steps in mitigating stakeholder risk is to create a stakeholder directory. 


Stakeholder Directories

Stakeholder directories come in all shapes and sizes, but in general, the directory lists the stakeholders, their roles, their influence, and their level of support for the project. This directory is used by the Citizen Developer and squad as a reference tool as they engage with the stakeholders throughout the project. 


Stakeholder Engagement Plan

In the course of creating the stakeholder directory, Citizen Developers will also be creating a stakeholder engagement plan. This will encompass how hands-on the stakeholders will be in the project, how and when they will receive status updates, and their expectations. Some stakeholders will be heavily involved in the build and by engaging them early on, it will encourage collaboration and feedback, create a stronger solution, and help reduce the potential for miscommunication. 


Capturing Requirements from Stakeholders.

Now that the stakeholders have been identified and an engagement plan has been created, stakeholder requirements can be gathered. Stakeholders help to identify app requirements and why they’re important. These requirements are typically functional requirements pertaining to the user experience or workflows. The requirement list provides direction and focus throughout the app development and it also acts as a checklist to make sure that the requirements have been met.


In my past blogs, I have shared situations where an app was created and the problem solved and they lived happily ever after, but the following situation is about a missed opportunity and a lesson learned.


What happens when a stakeholder stops it all.


Situation: A fast-growing urban non-profit was sinking in a swamp of details they couldn’t manage anymore. The organization was led by a small executive team and run by volunteers.  There were four lines of service, each led by a volunteer.


Before: The quality of service and communication was showing signs of stress. Volunteers were working extra hours to keep up with inefficient methods.


Process: A Citizen Developer who was familiar with the organization saw the situation and believed an app could solve the chaos and help scale the organization efficiently. He presented the idea of a low-code/no-code (LCNC) app to the executive team (Enterprise Stakeholders). They liked the idea of an app and introduced the Citizen Developer to the volunteer leaders of the four lines of service. He met with each one to demonstrate a prototype and to discuss how the app could save them time and improve their service.


Three of the four volunteer leaders saw the app as a solution, but the fourth felt the expense was unnecessary. She was happy to work the extra hours to save money. She would not budge from her position and even though the executive team felt the expense was worth the saving, they bent to her wishes.


After: The Citizen Developer dropped the project. The organization and its volunteers continued to struggle and count on volunteer overtime to succeed.


Missed opportunity and lesson learned:

While the non-profit was still in its infancy and developing its structure, it had an opportunity to quickly and cost-effectively solve an operational issue that was only going to get worse. The organizational structure had no real leader which made it difficult when the solution was presented. They missed a huge opportunity. 


The Citizen Developer learned a valuable lesson. He skipped a few steps and dove right into solving the problem before fully understanding the stakeholders, their roles, and their influence. Had he spent a little more time engaging the stakeholders and listening to their concerns and pain points, he may have been able to alleviate the cost concerns with the resistant stakeholder. This was a valuable lesson to learn.


Some tips from my experience:

  1. Identify the stakeholders quickly and engage them as soon as you can.
  2. Communicate with stakeholders. Find out what their expectations and requirements are.
  3. Listen and ask questions. Find out the stakeholder's pain points, needs, and perspective, not just about the solution, but the project in general. 


Stakeholders are crucial to the build and the ongoing success of the project. If the stakeholders aren’t supportive, you’re in for a steep climb that may not be worth the risk.


What did this post spark in you? Are you new to no-code/low-code app creation? Have you used a suitability assessment in your company? Please post your questions, comments, and stories below.

Want to learn more? Grab your copy of the newly released book Citizen Development: The Handbook for Creators and Change Makers.

Posted by Jody Temple White on: April 16, 2021 01:33 PM | Permalink | Comments (7)

How Will Citizen Development Impact Leadership, Decision-Making and How Projects are Run? Part 3

Welcome to part 3 of my 3-part series on how citizen development is impacting projects and project management. Through the lens of citizen development, I am looking at the areas of

  1. Leadership – How citizen development related to the leadership face
  2. Project Manager – How citizen development relates to the PM face  
  3. Decision making – How citizen development can impact decision making


If you missed parts 1 and 2 you can read them here and here.


How Citizen Development Can Impact Decision Making


At the core of Citizen Development lies decision-making about projects and programs that must align with organizational strategic objectives, the readiness of the decision-makers, the underlying factor of Return on Investment (ROI), and the uncertainties of citizen development, but one factor that keeps citizen development ahead is the speed of delivery of products or services in less time.


Lots of programs have failed even though time and a huge amount of funds were spent to deliver the benefits. Sometimes, products become obsolete at roll-out. The recent Covid-19 saga has shown the world that one has to respond faster to contain it. Real-time development and deployment of products or services is key to citizen development.


In my training as a Software Tester, one must not wait to find all the defects for a product to go live, some defects will pop up when the product goes live in different environments. Feedbacks will eventually help in fine-tuning the flexibilities required when the product is live and in use.



It is great to know citizen development is already launched on an existing low-code/no-code (LCNC) platform. The usage of LCNC is on the increase and the platform will get better as it progresses. The world is changing, the need for building applications will grow higher and the world will not find a better way to deliver products or services than to leverage on a low-code/no-code platform to deliver applications cheaper and in less time.


Applications will be launched faster with a higher Return on investment (ROI). This will not be negotiable for CEOs who always go for profit maximization. The low-code/no-code market will be huge in the nearest years.


This boom will reshape organizational development in my opinion. This is because it will create more opportunities for both the organization and the employees. Ideas can be brought to life in no time, and organizational growth will be rapid.


The strength of every organization is the people (employee), the fear of investing lots of resources on the employee ideas will be gone with a low code/no-code platform and ideas can be brought to life faster and cheaper.


The growth will be unstoppable with a low code/no-code platform.



Posted by Jelili Odunayo Kazeem on: January 27, 2021 02:54 PM | Permalink | Comments (10)

"Doubt is not a pleasant condition, but certainty is absurd."

- Voltaire