Small Organizations Do Not Need an AI Department. They Need AI Leadership.
How a Small Nonprofit Built AI Leadership Without a Technology Department
When people hear the words “AI transformation,” they often imagine a large corporation with a dedicated technology department, data scientists, outside consultants, and a substantial budget. They rarely picture a small nonprofit association with a small staff, decades of industry knowledge to preserve, and a growing list of responsibilities.
That is the reality at the National Cleaners Association. We serve garment-care professionals who operate businesses in an industry affected by changing regulations, workforce challenges, technical problems, customer expectations, environmental requirements, and rapidly evolving technology. Our members do not need theoretical information. They need practical answers that help them make decisions, solve problems, protect their businesses, and serve their customers.
As the association’s Executive Director and Chief AI Officer, I understood that we could not continue serving our members effectively by relying entirely on traditional processes. The amount of work was growing, important industry knowledge was concentrated in the minds of a few experienced people, and too many responsibilities depended on individual availability. At the same time, we did not have the resources to create a large technology department or hire a team of AI specialists.
Instead of waiting for resources that might never come, I learned how to lead the transformation myself.
That work recently helped the National Cleaners Association become a finalist in the 2026 Stevie® Awards for Women in Business in the category of Organization of the Year, Government or Non-Profit, with ten or fewer employees. Our nomination, “Transforming Member Value Through AI and Operational Innovation,” recognizes the progress we have made by connecting technology to the association’s mission and the real needs of our members.
The recognition is meaningful, but the larger lesson reaches beyond our organization. Small organizations do not necessarily need an AI department before they can begin meaningful transformation. They need trained leadership, a clear understanding of how the organization operates, and someone who is accountable for turning technological possibilities into practical results.
Many organizations are already using AI in some form. Employees may use it to draft emails, summarize documents, create content, conduct research, or experiment with new tools. These activities can save time and introduce people to the technology, but using AI for individual tasks is not the same as providing AI leadership.
AI leadership begins when someone takes responsibility for determining where AI belongs, where it does not belong, what information it needs, what risks must be managed, and how its value will be measured. It requires more than familiarity with the latest tools. It requires the ability to connect technology to strategy, operations, people, organizational knowledge, and measurable outcomes.
A Chief AI Officer does not have to write every line of code or personally build every system. The role is broader than that. The CAIO must understand the organization well enough to identify the right problems, evaluate possible solutions, establish safeguards, involve the right people, and ensure that human judgment remains part of the process.
For a small organization, this responsibility may not begin as a separate department. It may begin with one well-trained leader who understands both the organization and the technology well enough to ask better questions. That leader must be able to determine which problems are worth solving, whose knowledge a process depends on, where the organization is losing time, what members or customers actually need, and which decisions should always remain in human hands.
Those questions have been more valuable to us than simply chasing the newest AI tool.
One of the greatest misconceptions about AI transformation is that it begins with selecting software. In reality, it begins with readiness. Before an organization can use AI effectively, it must understand how its work is actually performed. This includes documented procedures, but it also includes the exceptions, relationships, judgment calls, workarounds, and unwritten decisions that may exist only in someone’s memory.
I refer to the distance between having access to AI and being organizationally prepared to use it as the AI Readiness Gap. An organization may have access to powerful technology and still be unprepared to use it effectively. If the underlying process is unclear, AI may simply allow confusion to move faster. If the information is incomplete or unreliable, AI cannot automatically make it accurate. If no one owns the outcome, automation may create more problems than it solves.
Our first responsibility was not to automate everything. We needed to identify what we knew, what we did repeatedly, where work became stuck, which responsibilities depended too heavily on one person, and where our members needed faster or more consistent support. Once we understood those realities, we could begin turning individual expertise into repeatable organizational capability.
This is especially important in a long-established industry. Some of the most valuable knowledge in garment care has never been fully captured in a manual. It lives in experienced people who have spent years answering difficult questions, examining damaged garments, identifying fabric and dye problems, solving production issues, interpreting regulations, and helping business owners manage complicated customer claims.
That knowledge is enormously valuable, but it is also vulnerable. When knowledge remains dependent on one person’s memory or availability, an organization cannot access it consistently, preserve it properly, or pass it to the next generation.
AI has given us new ways to begin organizing that knowledge, making it easier to retrieve, and developing systems that support more consistent responses. However, the technology does not replace the expertise. The expertise is what gives the technology value. Our goal is not to remove experienced people from the process. Our goal is to ensure that their knowledge can continue working.
