WellGoverned.ai

A clear view of your AI position and what to do next.

A bounded engagement to understand where you stand, identify the risks and priorities that matter, and decide what — if anything — to do next.

For COOs, CIOs, IT directors, governance and innovation leaders, and others responsible for AI. Scope fits your organization’s needs and resources, whether you are introducing AI or taking stock of what is already in use.

An assessment is one way to begin. If the need is already clear, you can start with a focused assignment instead.

How it works

  1. Review what already exists. Policies, initiative lists, data-handling guidance, security procedures, and customer requirements — whatever is available.
  2. Hold discovery sessions. Working sessions with the people who own the business objectives, the systems, and the risk.
  3. Clarify the priority questions. Targeted follow-ups where the picture is unclear or contested.
  4. Synthesize findings. Strengths and gaps, positioned against the framework and against your own priorities.
  5. Present an executive readout. Findings, priorities, proposed next steps, and a decision.

Practicalities

Format
Commonly three half-day discovery workshops, tailored to scope and participants.
From you
An accountable sponsor, access to the right people, and whatever documentation exists.
Fees
Scope, schedule, and a fee cap are agreed before work begins. I do not publish rates, because the right scope varies too much for a headline number to be honest.

What you receive

  1. A high-level current-state profile

    Informed by the NIST AI Risk Management Framework, identifying material strengths, gaps, priorities — and the places where the available evidence was thin.

  2. A prioritized governance roadmap

    Typically covering 12 to 24 months, with sequencing, likely owners, dependencies, and relative effort.

  3. Proposed plans for selected follow-on work

    Each with its purpose, scope, audience, owner and reviewers, acceptance criteria, estimated effort, fee cap, and schedule — so you can decide on each one separately.

  4. An executive readout

    Structured to support a decision about what to pursue, what to defer, and what to stop.

Being clear about what this is not is part of why it can be done quickly. Where evidence is missing, that is recorded as a limitation rather than a reason to stop.

A recent assessment

Governance decisions and delivery planning

Situation. A business was expanding its use of AI across employee tools, a customer-facing product, and AI-assisted software development, and needed to establish who owns what before going further.

My contribution. I worked with the leadership team through evidence review and working sessions, then produced a current-state profile, a high-level framework profile, a prioritized roadmap, and proposed delivery plans for any follow-on work.

Result. The first phase is delivered. What follows is decided at the executive decision gate.

What happens at the end

There is no obligation to commission subsequent work. You can proceed with selected priorities, defer them, or finish with the assessment. Any further work, including technical validation or specialist work, is scoped and authorized separately.

Discuss an assessment