Sophie Morrison / AI Strategy & Adoption

AI policy should be useful
on a Tuesday afternoon.

Practical guidance for businesses adopting AI: where it can help, where judgment is essential and how to give teams clear rules they can actually follow.

01 / The business case

Adoption without direction creates its own problems.

Teams are already experimenting with AI tools. The challenge is turning that experimentation into sensible practices without overlooking data handling, quality control or accountability.

Good policy starts with the work people do. Which tasks are appropriate for AI assistance? What information should stay out of public tools? Who checks outputs before they reach customers? What needs human review?

The answer should be proportionate to the business and understandable to the people expected to follow it.

The objective

Give people enough clarity to use AI well—and enough guardrails to know when not to.

02 / Advisory areas

Clear guidance, built around actual workflows.

01

Internal AI-use policies

Draft policies covering approved uses, prohibited uses, data handling, human review and accountability.

02

Team guidelines & training

Translate policies into straightforward practices, examples and expectations for everyday work.

03

Opportunity assessment

Identify workflows where AI could save time or improve quality, with realistic limits and oversight.

04

Marketing AI practices

Establish sensible standards for AI-assisted research, content, analysis and customer-facing work.

05

Vendor & tool considerations

Support business-side evaluation of tools, permissions, information handling and operational fit.

06

Governance awareness

Account for relevant security and SOC-related control considerations while coordinating with qualified compliance and security professionals.

03 / Boundaries

Commercial and operational advisory—not a compliance audit.

Understanding how security and control frameworks affect business decisions is useful. It is not the same as certifying that an organization meets those standards.

What this work includes

Business-side policy development, use-case assessment, internal guidelines, stakeholder alignment and practical implementation support.

What it does not claim

SOC 2 certification, formal assurance, legal advice, penetration testing or independent security audits. Those require appropriately qualified specialists.

04 / In practice

A workable path from experimentation to policy.

01

Understand current use

Identify tools, common workflows, existing policies and the areas creating the most uncertainty.

02

Set practical standards

Define permitted uses, review requirements, information boundaries and ownership.

03

Make adoption usable

Develop clear guidance and examples that teams can apply without a compliance manual on every desk.

04

Revisit as tools change

Treat the policy as a living operational document, with review by relevant legal, privacy or security specialists where needed.

Start a conversation

A good place to start is a conversation.

For fractional CMO engagements, focused advisory projects, GEO consulting and speaking inquiries, share a little about the business and what needs to change.

Confirm the email address is active before publishing.