Skip to content
← Back to the KDK method

A PUBLIC SAMPLE OF OUR METHOD

A plan you can put to work.

Being AI-first means making thoughtful use of AI in everyday work. This illustrative plan connects processes, knowledge, training and follow-up.

We agree the areas, groups, sessions and applications to address in 90 days. The examples explain the method; they are not client results.

KDK / TRANSFORMATION MAP90 days · 6 stages

Select a stage

Weekly follow-up throughout the programme.

Weeks 1–2 · STAGE 01

Understand how your business works

We walk through the work with the people doing it. We identify time lost, missing knowledge and how your existing AI is actually used.

What we do

  • Interviews with leaders and team owners.
  • Map tasks, documents, handovers and blockers.
  • Inventory tools, licences and actual usage.

Your team takes part

  • Show tasks and approved examples of your work.
  • Explain what you check, repeat and find difficult.

THIS STAGE’S OUTCOME

A clear picture of the business

  • Processes and owners
  • Current tools and usage
  • Time and quality baseline

We validate the map with your team and find improvements worth testing early.

Weeks 3–4 · STAGE 02

Turn the diagnosis into a plan

We rank opportunities and choose what to address first. Each initiative connects a business problem with an owner, a solution and a way to measure it.

What we do

  • Prioritise by value, feasibility and effort.
  • Select tools and review overlapping licences.
  • Plan training and implementation by team.

Your team takes part

  • Validate priorities and assign owners.
  • Confirm availability, data and required access.

THIS STAGE’S OUTCOME

A shared transformation plan

  • Initiatives, scope and owners
  • Work and training schedule
  • Delivery and measurement criteria

Every priority has a next step. Purchases and development need a clear justification.

Weeks 5–6 · STAGE 03

Prepare AI for your work

We prepare the agreed tools and applications: business context, instructions, templates, knowledge and automation where it adds value.

What we do

  • Configure the selected tools.
  • Organise sources and task instructions.
  • Test approved examples and review errors.

Your team takes part

  • Validate documents, access and quality criteria.
  • Try the first applications and identify exceptions.

THIS STAGE’S OUTCOME

Applications ready for practice

  • Configured tools
  • Reusable instructions and templates
  • Test records and adjustments

We check results against real work before extending usage.

Weeks 7–8 · STAGE 04

Learn through the work of each role

Teams practise on their tasks: proposals, document review, information analysis and questions. Training follows each role and starting level.

What we do

  • Team workshops using their applications.
  • Guidance on context and response review.
  • Improve guides and configuration through practice.

Your team takes part

  • Apply the learning between sessions.
  • Share questions, errors and opportunities.

THIS STAGE’S OUTCOME

A shared way of working

  • Guides by role and task
  • Practice on your own work
  • Owners and review criteria

People can repeat a task and explain how they check the result.

Weeks 9–10 · STAGE 05

Make sure AI is actually used

We review what has become routine and what remains unused. We resolve blockers, repeat practice where needed and compare progress with the baseline.

What we do

  • Weekly reviews of usage and blockers.
  • Compare task time, quality and corrections.
  • Adjust applications and reinforce training.

Your team takes part

  • Bring completed work and user feedback.
  • Check results against business criteria.

THIS STAGE’S OUTCOME

Adoption and improvement record

  • Observed task usage
  • Results against the baseline
  • Blockers and corrective actions

An active licence is not enough: we check AI is used in real tasks.

Weeks 11–13 · STAGE 06

Leave the team ready to continue

We consolidate what works and prepare your team to maintain it. The handover explains what changed, what remains and how to continue.

What we do

  • Document configuration and decisions.
  • Practise maintenance with internal owners.
  • Review progress and the next roadmap.

Your team takes part

  • Demonstrate use and maintenance of agreed work.
  • Choose priorities and owners for what comes next.

THIS STAGE’S OUTCOME

Handover and continuity plan

  • Your company’s resources and accounts
  • Owners able to maintain them
  • Progress, remaining work and priorities

We close the agreed scope. Any ongoing collaboration is defined separately.

1 / 6

Illustrative timeline. Stages overlap and early tests can begin during diagnosis. We agree areas, participants and deliverables before starting.

EXAMPLES / FROM PLAN TO A TASK

Every application, with a purpose.

EXAMPLE 01

Sales proposals

Input
Meeting notes, approved catalogue and proposal template.
Output
A structured draft for the sales owner to review.

What counts as delivered

  • Keeps the needs captured in the meeting.
  • Does not invent prices, terms or delivery dates.
  • A person reviews and approves before sending.

What we measurePreparation time, corrections and weekly usage.

EXAMPLE 02

Internal knowledge

Input
Current procedures and team-approved documents.
Output
Answers with references to find and verify the information.

What counts as delivered

  • Uses only permitted documents.
  • Shows sources and acknowledges missing information.
  • Respects agreed user permissions.

What we measureSearch time, errors and questions resolved.

ADOPTION / VERIFYING THE CHANGE

An active licence. A team using it.

We review actual usage throughout the programme. Each week, we check progress, resolve blockers and agree the next practice. The aim is for the team to know how to do the work and make it part of its routine.

  1. 01 / PEOPLE

    Training by role.

    We define groups, starting skills and tasks for each area. We practise with business context, instructions and review. A person from each group demonstrates they can repeat the task without our help.

  2. 02 / WORK

    Usage, time and quality.

    We agree a baseline using comparable tasks. We review frequency of use, time spent and corrections required. We record observed results and blockers without assuming savings.

  3. 03 / TOOLS

    More value from what you have.

    We review which licences are used, where they overlap and what the current setup can handle. Every new purchase or development must address a specific need.

RESPONSIBILITIES / THE KNOWLEDGE STAYS WITH YOU

Who does what.

KDK

Leads the audit, prepares the plan, delivers training, configures agreed applications and follows adoption weekly. Documents decisions and deliveries.

Your business

Assigns an owner, provides approved access, practises between sessions and validates deliveries against business criteria.

At handover

You receive documentation of usage, configuration and decisions. Accounts are created for your company, with access and completed work handed over as agreed.

The proposal details scope, groups, session count, time commitments on both sides, deliverables and total price. Licences, complex integrations and additional development are scoped separately. Ongoing support after the programme is agreed if needed.

LET’S TALK / KDK INTELLIGENCE

Let’s talk aboutyour business.

Tell us what you want to improve. We suggest how to get started, with a clear scope, timeline and budget.

You can also email ushola@kdkintelligence.com

Tell us the essentials.

Fields marked * are required.

Add context (optional)

Your request goes directly to the KDK team.

WHAT HAPPENS AFTER YOU CONTACT US

  1. 01

    Discuss your business

    We understand your objective and answer your questions.

  2. 02

    Receive a proposal

    Scope, timeline and pricing in writing.

  3. 03

    You decide

    Review the proposal before you commit.