Organizational Readiness Agent
A completed course project on its own GitHub branch. Not deployed.
A specialist assessing leadership, skills, workflow, data, resources, governance, culture and operating ownership for organizational technology adoption.
- Why
- I wanted to distinguish technical fit from the capacity to run a system sustainably.
How I built it
- I specified eight readiness dimensions.
- I separated pilot success from long-term staffing, funding and ownership.
- I tested an organization with uneven data and unclear operating responsibility.
- I retained gaps and evidence thresholds rather than forcing a yes or no.
- To copy it you need
- Start with one pilot and assess who owns performance monitoring, corrections, data quality and escalation.
Try it yourself
Copy this prompt and paste it into ChatGPT or Claude to try it yourself.
I want to build a small version of Jovan Diaz's Organizational Readiness Agent from his What Are We Building? profile. It is a course project, so treat it as a study exercise. It checks eight things: leadership, skills, workflow, data, resources, governance, culture and operating ownership. Instead of forcing a yes or no, it keeps gaps and evidence thresholds visible. His gotcha: a pilot can succeed because a temporary champion props it up, and the organization may not be able to keep that going. Start with one pilot and ask me who owns monitoring, corrections, data quality and escalation. Ask me for anything you need.
Tools I used for this project
ChatGPT: I used ChatGPT to draft, test, critique or work through the workflow.
Codex: I used Codex to help build or revise repository files and tests.
Python: I used Python scripts or validation tools to process and check structured outputs.
GitHub: GitHub holds all of my repositories: code, instructions, changes and review history.
