What does AI enablement look like in practice?

From shadow AI and outdated documentation to a shared way of building.

Vinfen, a human-services organization of roughly two thousand employees, operating across several states in the northeast.

The situation

The HR team was working across a range of personal AI tools. That shadow usage produced inconsistent material and unclear sources of truth, and the approved AI environment could not become useful until somebody understood how people were actually working.

The work

An assessment of the team’s capability and of how people felt about using AI at work showed which HR subteams were best positioned to start.

Outdated SOPs were rewritten around the real process, including the knowledge that had only ever lived in experienced employees’ heads. Where it made sense they became Automated Operating Procedures, structured so AI could execute the work without that unwritten expertise.

Then the team learned to build with the discipline of a development process: context, testing, edge cases, troubleshooting, maintenance. The last piece reconsidered how the reclaimed hours got spent.

What changed

• Role redesign focused reclaimed capacity on more thoughtful and valuable work.
• The organization gained a shared view of current capability and AI usage.
• The strongest starting teams were identified deliberately rather than selected by volume or enthusiasm alone.
• Critical work was documented in a form useful to both people and AI.
• The team gained a repeatable approach for building workflows that address edge cases and can be maintained.