General AI · 1.5 days · reviewed outline

Native

Work beyond the chat box. Choose a useful AI workflow, build one relevant work product and explain how its result was checked.

For
Employees and managers expanding beyond occasional prompting
Duration
1.5 days
Selected output
One useful work product, reusable instructions or workflow, a verification checklist and stated limitations
Commercial state
Quote required · dates unreleased

Inspect the work

The numbers stay owned by the source and the formula.

Change the region, period or metric. The chart, source rows and CSV update together; a zero denominator becomes undefined, not a misleading zero.

Example · sample dataLocal calculation

Sales by region

Fictional campaign rows · version 1

48 source rows. Revenue is grouped by region. North: 1,38,300; South: 98,800; East: 1,58,000; West: 1,49,600

Return on ad spend6.0×
Source totals5,44,700 revenue · 90,190 spend
Checked against source rows

From this example to the workshop

What this example does

A small synthetic dataset becomes a clear comparison, chart and source-checked result.

What you will use in the workshop

An approved assistant and spreadsheet confirmed before delivery, plus structured exercises and safe data.

What you will make and check

A working analysis, source rows, formula, chart and short explanation you can independently check.

Workshop scope

You build and check the analysis—not this website application.

Build a Native plan

What participants leave with

One useful work product, reusable instructions or workflow, a verification checklist and stated limitations. The selected work is accompanied by the instructions or workflow that produced it, a verification checklist and a clear explanation of its limitations.

Representative curriculum

  • Referenced briefing and presentation
  • Checked data analysis and management summary
  • Policy or knowledge assistant prototype
Workshop boundary. Four to six worked examples, one guided build and one selected application; no universal mastery or production deployment.

Standard 1.5-day agenda

WhenWhat happens
Before eventDevice, account, network, permissions and safe-data preflight
Day 1 · 09:30–12:30Orientation, working examples, workflow choices, safety and capstone selection; includes a short break
12:30–13:30Lunch
13:30–14:45Guided build
14:45–15:00Break
15:00–16:45Individual or team application with a fallback starter
16:45–17:30Verify, document limits and prepare the presentation
Day 2 · 09:00–12:30Showcase, feedback, recognition and next commitments

Tools and preparation

An approved core assistant and spreadsheet must be confirmed and tested before delivery. Participants need a laptop, working accounts, permitted browser/network access and safe data or the supplied synthetic fallback. Product names are not guessed before the buyer and faculty approve the toolchain.

Showcase and assessment

Each presenting unit receives ten minutes plus two minutes for feedback and changeover. The standard morning supports up to twelve individual units, or roughly 24–30 people in 10–12 teams with visible contributions. Larger individual formats require staffed parallel rooms or separate cohorts.

Assessment covers usefulness, correctness and evidence, repeatability, safe handling and explanation. A critical factual or data error requires rework.

Price and dates

No exact rate or delivery window has been approved. The current candidate therefore shows Quote required and Dates not released. A submitted preference is reviewed by staff against the complete external calendar; it never reserves a slot.