Leaders who set direction
Interrogate use cases and vendor claims, establish decision rights, compare opportunity with exposure, and make clear proceed, revise, or stop decisions.
Portfolio criteria · leadership review agendaAI training for people who have real work to do.
Soxoa designs role-specific programs around the decisions, workflows, systems, and rules your teams actually carry. Leaders learn to govern choices. Operators rehearse approved use. Builders test and integrate. Oversight teams learn what evidence to ask for.
No prompt-trick roadshow. Every program starts with the work, the allowed data, the verification standard, and the handoff between roles.
- Executive
- Operator
- Builder
- Governance
A license creates access. It does not create capability.
Capability exists when a person can use an approved system inside a defined workflow, verify what it returns, recognize the edge of their authority, and route uncertainty to the right owner.
The unit of design is a role making a decision with evidence—not a prompt in isolation.An account is provisioned
The role knows which work is permitted and where the boundary sits
A demonstration is watched
Representative scenarios are practiced inside the actual workflow
A prompt is copied
Outputs are checked against sources, standards, and known failure modes
A successful example is shown
Exceptions are recognized, recorded, and routed to a named owner
One champion knows the tool
The organization owns the playbooks, facilitation notes, and review cadence
Every role learns its part—and the handoff.
One organization does not need one generic class. Each track carries a different responsibility, uses different evidence, and leaves behind a different working record.
People who run the work
Practice approved task patterns, inspect outputs, cite sources, protect data, handle uncertainty, and escalate the cases the system should not decide.
Role playbook · scenario practice recordTeams who configure and connect
Define evaluation sets, trace data boundaries, design human checkpoints, inspect system behavior, and document monitoring, change, rollback, and ownership.
Evaluation plan · technical runbookFunctions that oversee risk
Review inventories, translate policy into project questions, request usable evidence, examine controls, and make incident and escalation paths operational.
Oversight checklist · evidence registerBuilt from the work backward.
The curriculum is designed after the operating context is understood. That keeps training connected to the systems, controls, and human decisions people will inherit afterward.
- 01
Map the work
Identify the roles, decisions, tools, inputs, exceptions, and handoffs the program has to reflect.
- 02
Set the boundaries
Confirm approved systems, data rules, authority, verification standards, and escalation owners.
- 03
Build the scenarios
Turn representative work into exercises with expected evidence, failure modes, and review prompts.
- 04
Run the practice
Facilitate role-specific decisions, observe where ambiguity remains, and record questions that need an owner.
- 05
Transfer the program
Deliver the curriculum, playbooks, facilitator materials, and a practical review cadence to the organization.
Match the format to the decision in front of the team.
A focused leadership decision, hands-on workflow practice, and an internal facilitator handoff are different jobs. The program shape follows the job—not a fixed course catalog.
| Format | Use it when | Shape | Working record |
|---|---|---|---|
| Executive briefing | A leadership team needs a shared frame for opportunity, risk, ownership, and portfolio decisions. | Facilitated decision session | Leadership brief · review agenda |
| Role-based workshop | One or more teams need to rehearse approved use, verification, exceptions, and handoffs. | Scenario-led working session | Role guide · practice record |
| Working cohort | A cross-functional group needs repeated practice around a selected workflow or implementation. | Sequenced sessions with fieldwork | Program workbook · issue log |
| Train-the-trainer | Internal facilitators need an owned program they can deliver and maintain inside the organization. | Facilitator preparation and handoff | Facilitator kit · update guide |
The materials stay with the organization.
A session ends. The operating records should remain useful. Deliverables are tailored to the agreed roles, systems, policies, and exercises, then handed over in maintainable form.
Program architecture
Audience, role outcomes, sequence, dependencies, and accountable owners.
Tailored curriculum
Materials grounded in the organization's tools, policy, language, and work patterns.
Practice scenario set
Approved, redacted, or synthetic exercises with verification and escalation prompts.
Role playbooks
Permitted use, review steps, source expectations, exceptions, and handoffs by role.
Facilitator materials
Session plans, notes, timing, discussion prompts, and guidance for keeping content current.
Observation record
Questions, friction, unresolved decisions, and recommended follow-up without representing completion as certification.
Training stays inside clear boundaries.
The program can make responsibilities and questions explicit. It does not replace the authorities, controls, or operating work that an organization remains responsible for.
Useful foundations for the work
- A sponsor and named owners for the decisions in scope
- Approved tools, policy, or a path to confirm them
- Representative work or approved exercise material
- Access to the roles who perform and oversee the work
- An internal owner for materials and follow-up questions
What the program does not pretend to do
- Certify a person, system, policy, or organization
- Guarantee adoption, productivity, proficiency, or business results
- Replace legal, security, privacy, accessibility, labor, records, or procurement review
- Put sensitive live data into an exercise without explicit authorization and controls
- Substitute generic prompt tips for implementation, governance, or accountable ownership
Training is one part of the consulting practice.
Soxoa can connect workforce capability to the system being implemented, the governance environment around it, and the decision method that carries the work forward.
Questions teams ask before scoping training.
The useful answers depend on the work, roles, tools, and authority in scope. These are the boundaries Soxoa starts with.
Can we train people before choosing an AI platform?
Yes. Leadership and governance tracks can establish use-case criteria, decision rights, data boundaries, and review expectations before a platform is selected. Hands-on tool practice begins only when there is an approved system and environment to use.
Can the program use our real workflows and data?
The work should reflect real workflows. Exercise material is agreed during scoping and may use approved historical, redacted, or synthetic examples. Sensitive live data is not used simply because a tool can accept it; authorization, environment, access, retention, and facilitation controls come first.
Is this a prompt-engineering workshop?
No. Prompt patterns may appear where they support a defined task, but the program centers on decisions, data rules, verification, failure modes, human review, escalation, and the handoffs required to operate AI responsibly.
Which roles should attend?
That depends on the decision in scope. A program may involve executives, workflow owners, frontline operators, technical builders, security, privacy, legal, procurement, records, accessibility, learning, or other oversight functions. Not every person needs the same material.
Do participants receive a certification?
No. Soxoa does not represent attendance or exercise completion as certification, policy approval, professional qualification, or proof of proficiency. A program can leave an observation record and follow-up plan for the organization to use in its own governance process.
Can training be part of an implementation engagement?
Yes. Training can be designed alongside an evaluation, pilot, or production handoff so the curriculum reflects the actual system, approved workflow, review queue, and exception path. It can also be delivered as a separate leadership, role-based, or facilitator program.
Give every role a clear job in the AI operating model.
Bring the audience, the work, and the decisions that are creating uncertainty. A first conversation can identify the right track, exercise material, boundaries, and program shape.