Outside the day job
Desert Marigold School
I serve on the board of a public Waldorf charter school, where the work includes governance, financial oversight, and supporting the executive director. Much of our recent work has been turning established practices into policies the next board can understand and use. The people who follow us need access to that knowledge without depending on everyone who held it being available.
I use AI to organize the documents and support that work, with decisions remaining with the board and legal review with counsel. I remain responsible for reviewing and sending the material I prepare.
ArtsEd West
ArtsEd West connects educators and teaching artists across Arizona. My part covers business planning and budgets as well as membership, payments, and the technology supporting them. The other cofounders need to be able to develop the organization and change what it publishes without waiting for me to make every edit.
They submit website changes through Google Sheets and review what an agent prepares in a nonproduction environment. That keeps editorial decisions with the people who know the work, using tools they are already comfortable with. Our inaugural ALL AZ Summit took place on 11 September 2026.
A board or a small nonprofit needs the knowledge behind its decisions to remain available as people come and go. Writing down a policy or giving a colleague a way to update the website can make the work easier to share, provided the people responsible still understand what is being decided. Technology is useful here when it gives them more room to exercise that responsibility.
In board and nonprofit work, preparing information more efficiently can give people more time to exercise judgment. I weigh that benefit against whether the next person can understand the decision and carry the responsibility. A publishing process that colleagues can use themselves has value beyond saving my time, provided they can review what it will say and ask for changes before it becomes public.
If the people responsible for an organization's work have to come through me for routine changes, I have made myself part of their operating constraint. I make sure the teams I lead can make routine changes without me: tools they understand, a way to review consequences, and the knowledge they'll need when someone else takes over. That still leaves a role for technical support, without making every decision a technical request.



