How this site was built.

The stack

Three tools, one workflow. Claude (Anthropic) was used for strategy, content drafting, framework design, and prompt engineering. Lovable was used to build and deploy the website itself. GitHub holds the canonical versions of all written content, framework documents, and process logs. The domain is registered with Namecheap and email is forwarded through their service.

What AI did

• Drafted bio, hero copy, and page content (later edited by me)
• Generated structured prompts for Lovable based on my design direction
• Researched current data on AI adoption challenges
• Helped design the AI Adoption Readiness framework structure
• Reviewed and critiqued its own outputs when asked
• Wrote skill files that can be reused for future Claude conversations

What I did

• Defined the point of view and the framework dimensions
• Made every decision about what to include, what to cut, and what to rephrase
• Provided the professional context and lived experience that grounds the content
• Reviewed and approved every line of public-facing copy
• Set the rules for tone, voice, and what "sounds like me" means

What this demonstrates

This site is itself an answer to a question I get asked a lot: how should operations leaders work with AI right now? My answer is that the human stays in the loop on judgment, voice, and strategy. AI accelerates the parts that don't require those things. The result is faster work that still feels like mine. This site took less than two days of my time. It would have taken weeks without AI. The judgment didn't get faster. The execution did.

What I'd do differently

I'd start the GitHub repo before the website, not in parallel. I'd write the point of view earlier, so it informs every prompt instead of being retrofitted. I'd build skills (reusable prompt templates) from day one. Most importantly, I'd remember that the friction of working with AI tools is itself useful information about how those tools will land in real organizations.

Try this yourself.

The system behind this site, GitHub for canonical content, Lovable for the public site, and AI as a strategic and writing partner, is reproducible. If you're an operations leader thinking about how to build a public body of work, this approach works. You don't need to be a developer. You need a point of view, willingness to commit to public work, and the patience to refine your own voice.