Data is not ready
Sources lack owners, documentation is stale and knowledge remains dispersed.
Data readiness · solution selection · implementation · adoption
I help move from an idea to a solution with a clear objective, credible data and quality criteria. I can lead selection or represent the business during delivery by an internal team or technology supplier.
I do not start with the model. I compare built-in AI, enterprise assistants, API solutions, RAG and automation without AI.
Common starting point
The hardest problems rarely come from model access. They sit between data, process, responsibility, security and user capability.
Sources lack owners, documentation is stale and knowledge remains dispersed.
Models and demos are compared before the process, quality criteria and limits are agreed.
A few impressive answers replace representative cases, quality metrics and a go/no-go decision.
A supplier builds features while users cannot translate needs into data and acceptance scenarios.
Confidential data, retention, access, human oversight and logging are considered just before launch.
The team knows techniques but not when to trust, verify or escalate an answer.
Four delivery streams
Each stream has its own outcome and closure criteria. The scope can cover all four or fill a gap in an existing programme.
Inventory, quality, access, classification, metadata, knowledge and test cases.
Outcome: data preparation planOptions compared across quality, security, integration, cost, maintenance and flexibility.
Outcome: scorecard and recommendationRequirements, backlog, supplier communication, acceptance tests, go/no-go decisions and risk.
Outcome: solution accepted by the businessRoles, usage rules, scenarios, exercises, human oversight, champions and measurement.
Outcome: playbook and adoption planData readiness
Readiness is assessed against the use case. A knowledge assistant, a prediction and automated decision-making require different sources, controls and tests.
Required data, its source and the reference definition.
Gaps, inconsistencies, duplicates, stale knowledge and refusal cases.
Personal data, trade secrets, user roles, retention and supplier use.
Glossary, owners, document source, version, relationships and interpretation rules.
Representative questions, expected answers, difficult cases, prohibited data and expert criteria.
Solution selection
I compare the whole solution: user experience, process integration, data access, control, quality, implementation cost and maintenance.
| Option | When to consider | Primary condition | Typical trade-off |
|---|---|---|---|
| AI in an existing system | The process already runs in CRM, BI, helpdesk or an office suite. | The feature covers the use case and respects permissions. | Less flexibility, faster adoption and simpler maintenance. |
| Enterprise assistant | The team needs secure support for text, files and daily tasks. | Identity, data policy, tenant configuration and usage rules. | Broad use, limited process specialisation. |
| Knowledge assistant or RAG | Answers must use a controlled document and source base. | Content quality, metadata, index refresh, citations and retrieval tests. | More knowledge control, a pipeline to maintain. |
| API workflow or agent | AI performs process steps and uses company systems or tools. | Limited permissions, validation, logs, human approval and error handling. | Highest automation and operational responsibility. |
| Automation without AI | The task has fixed rules and no unstructured interpretation. | The process and exceptions can be specified clearly. | Less flexibility, predictable cost and outcome. |
Consultant during delivery
I can support delivery without replacing a software house, translating needs between sponsor, users, data, security and the technical team.
Objective, scope, users, data, risk, metrics, constraints and responsibilities.
Features, priorities, changes, integrations and consequences for users and data.
Golden set, expert tests, security, cost, latency, failure modes and go/no-go.
Feedback, incidents, quality, cost, adoption, model changes and controlled backlog.
Team readiness
Task formulation, context, result verification, sources, confidential data and escalation.
Task choice, human oversight, quality, responsibility, effect measurement and learning.
Approved tools, access, logging, retention, use register, incidents and change cycle.
Example library, office hours, feedback, feature testing and good-practice exchange.
Engagement process
Tasks, audiences, scale, business pain, frequency, risk and non-AI alternative.
Sources, quality, access, owners, policies, capabilities and technical dependencies.
Demo scenario, scorecard, options, total cost and supplier risk.
Prototype on representative data, golden set and quality, risk, cost and UX tests.
Backlog, integrations, security, monitoring, failure scenarios, documentation and tests.
Role training, playbook, champions, feedback, effect measurement and controlled development.
Tangible outcome
Document scope follows the stage. Not every project needs every item, but each decision needs an owner and evidence.
Data, process, capabilities, policies, risk and gaps.
Criteria, demo scenario, comparison results and recommendation.
Goal, scope, users, data, metrics, roles and exit conditions.
Golden set, rubric, results, errors and go/no-go.
Risks, controls, owners, monitoring and incident path.
Usage rules, roles, scenarios, verification and capability development.
Acceptance criteria
There is no universal quality threshold. Metrics and tolerances follow the use case, audience and consequence of error.
Honest limitations

Data, analytics and organisational change
I support organisations with data, reporting, automation and AI. That makes it possible to assess not only model capability but source quality, process integration, acceptance and team readiness.
Figures refer to the broader analytics, data and digital-transformation practice, not only production AI implementations.
Before we talk
Start with one process and a defined outcome, then assess data, users, risk, the current alternative and effect measurement before comparing solutions.
It covers systems of record, scope, quality, freshness, ownership, access and sensitivity. Knowledge assistants also need metadata, versioning, retrieval tests and an evaluation set.
I can compare models, but the recommendation covers the whole solution. Built-in AI, an enterprise assistant or automation without an LLM may be the better choice.
Yes. I can represent the business by refining requirements, leading the scorecard, reviewing backlog, preparing acceptance tests and supporting the go/no-go decision.
Training uses real tasks and roles. Users practise formulation and verification, managers design oversight and measures, and owners work on policy, access and incidents.
Yes. It covers opportunities, limitations, potential harm, responsible use, verification and accountability, matched to the users' knowledge and context.
First step
I will follow up on the business outcome, current alternative, data quality, risk, technology supplier and team readiness.
Prepare the decision