Taker
- What you do yourself
- Practice: how to request, verify and use the results.
- Where you put the effort
- Adoption, criteria of use and learning of the team.
- What you keep
- Agreed Uses, Licenses and Review of Responses.
Knowledge · The AI adoption model
Adopt a tool, adapt it to your context or build your own capacity. The model helps decide how much technology, knowledge, and dedication each process needs.
Karmina application system created by Ignasi Llorente.
It's not a race to Maker. It is a map to find the degree of adaptation that adds value to each case.
How to read the model
With Taker, the weight is in use. With Shaper, in the adaptation. With Maker, in the construction and operation of its own capacity. Change what the organization prepares, controls and must maintain.
The question is not “how can we get higher?” but “what do we need to make this process work better?” Volume, uniqueness of knowledge, risk and maintenance capacity guide the response.
Adopt
What can we solve with what already exists?
Taker is to adopt an available AI capability and incorporate it into a task. There is no need to develop your own solution: the person provides the context, asks for a result, reviews it and decides how to use it.
The important change is not to buy a license. It’s about moving from improvised use to a shared practice: knowing what to ask for, what information to input, and how to recognize an incorrect answer.
When the task is limited, a standard solution already gives a useful answer and manual intervention continues to be assumable.
If each result requires reconstructing the same context, copying data between tools or correcting the same deviations, the process may already need to be adapted.
Preparation time, quality after review and real utility for the team.
The same case, three approaches · Illustrative example
A person prepares a draft response to a consultation with an AI tool. It enters the authorized context, checks the information and sends the message itself.
An assisted task. The person drives every step.
Adapt
What do you need to know and respect the AI to be useful here?
Shaper is to adapt an existing technology to a specific way of working. Instead of explaining everything in each conversation, the solution has stable instructions, authoritative sources, formats, and review criteria.
This adaptation can include a documentary basis, templates, connections with tools or adjustments of the model when they are justified. Not everything requires training: often the difference is to consult the right knowledge and apply it well.
When the task is repeated and the result depends on the vocabulary, data, conditions or the organization’s own criteria.
A documentary base is not maintained alone. If the sources are contradictory or nobody assumes the update, the adaptation can reproduce errors with more consistency.
Accuracy with respect to sources, consistency, necessary corrections and updating of knowledge.
The same case, three approaches · Illustrative example
An assistant prepares the answer by consulting the catalog and the current conditions. Respect the agreed tone, indicate the sources and refer to a person the questions he can not solve.
A contextualized result. Knowledge is reusable.
Build Capacity
What capacity do we want to govern and evolve?
In the applied reading of Karmina, Maker means to build an operational capability of its own: a system that connects tasks, knowledge, tools and responsibilities. It can take advantage of existing models; self-development is on the whole.
It’s not enough for a demonstration to work. It is necessary to define what happens when data is missing, a tool fails or the result requires a human decision. Also who can stop the system, review the activity and approve a change.
When the process has strategic value, there is evidence that the solution works and there are resources to operate it beyond the pilot.
Build involves maintenance, dependencies and recurring costs. More integration does not have to mean more autonomy: every action needs its limits.
Quality of the complete process, incidences, cost of operation and ability to monitor, stop and recover.
The same case, three approaches · Illustrative example
A system receives the consultation, recovers the context, prepares the response and leaves it pending approval. After validation, you can execute the authorized shipment and record the result.
A connected process. Autonomy is explicit and delimited.
DUBTE BACK
There is no need to come up with a definite solution. In a free video call we can understand what concerns you, separate noise emergencies and order a possible first step.
The difference, at a glance.
It doesn’t just change the outcome. It also changes where you put the effort and what you need to take care of so that it continues to work.
Choosing with criteria
Before adopting, adapting or building, put four questions on the table. They do not give an automatic score: they help to make the decision explicit.
If the answer is yes, Taker may be enough. Check the result on the actual job, including the time you spend reviewing it.
If internal information, stable criteria, or specific formats need to be applied, explore Shaper. These sources must first be ordered and in force.
If the challenge combines various tasks and tools, it values a capability of its own. Define permissions, exceptions, and decisions that continue in people’s hands.
The project does not end with the first delivery. Without a manager, maintenance time and criteria to measure value, it is necessary to reduce the scope.
What does not change
In any approach it is necessary to know what data can be used, what is considered a good result and who responds when something fails.
Autonomy is not included in the name. A Maker system may require human approval in every relevant action, just as a Taker tool needs a risk-appropriate review.
To finish understanding him.
It is not a mandatory itinerary or a classification of better and worse. A standard tool can be a definitive solution. It makes sense to change focus when a specific need appears that the current one does not resolve well enough.
Yeah. The map is most useful when applied to use cases. A team can use a tool to summarize documents, an assistant adapted to consult procedures and a system of its own to coordinate a recurring flow. There is no need to put a single label on the entire organization.
Not necessarily. The response can be adapted with instructions, examples and source query, without modifying the model. The adjustment of a model is a technical option that must be justified by evidence, not a requirement to begin with.
In the technical formulation of reference, Maker describes the construction of foundational models of its own. Here we explain a reading applied to the organization: build and govern a system of its own, also on existing models. Developing an agent or an integration is not, in itself, equivalent to creating a foundational model.
No. An agent can be a standard product we adopt or a solution we adapt to our knowledge. In this applied reading, the step to Maker has to do with assuming the design, operation and evolution of a system of its own, not with putting the name of agent.
It is necessary to compare the result with the current way of working: quality, review time, errors, total cost and maintenance load. A useful pilot includes exceptions and stop conditions. If adaptation or development does not improve the balance, keeping the option simpler is a good decision.
Frame of reference: McKinsey · A CIO and CTO guide. Examples and operational capability-oriented reading are an explanatory adaptation of Karmina, not customer cases.
Let’s talk
Explain to us what you want to solve, what tools you use and where you find the limit. We will help you assess whether you need to adopt, adapt or build.
hello@karmina.ai