WEBVTT

00:00:00.160 --> 00:00:01.420
The skill is there.

00:00:01.980 --> 00:00:03.380
The judgement is good.

00:00:03.940 --> 00:00:05.860
What needs strengthening is the support

00:00:05.860 --> 00:00:08.060
that allows us to play it effectively.

00:00:08.660 --> 00:00:11.460
Imagine a craftsman uncovering an unexpected

00:00:11.460 --> 00:00:12.880
layer beneath a coating.

00:00:13.180 --> 00:00:14.780
The picture shows the condition.

00:00:15.240 --> 00:00:17.020
A few words explain the piece,

00:00:17.540 --> 00:00:19.960
the stage of work and why it matters.

00:00:20.960 --> 00:00:23.380
Now the right expertise can respond.

00:00:23.480 --> 00:00:25.400
The specialist considers the history,

00:00:25.520 --> 00:00:27.820
identifies the next action and explains

00:00:27.820 --> 00:00:30.600
the reason. That explanation stays with

00:00:30.600 --> 00:00:33.940
the job. Additional preparation means time

00:00:33.940 --> 00:00:36.340
and materials. Connected to the agreed

00:00:36.340 --> 00:00:38.620
scope, those records let Duncan consider

00:00:38.620 --> 00:00:41.120
the commercial consequence and decide what

00:00:41.120 --> 00:00:42.660
needs agreeing with the client.

00:00:43.380 --> 00:00:45.240
Recording the resolution gives the next

00:00:45.240 --> 00:00:47.280
person somewhere useful to start.

00:00:47.540 --> 00:00:49.500
Watch what happens if the picture travels

00:00:49.500 --> 00:00:50.780
without its context.

00:00:51.460 --> 00:00:53.180
The specialist has to ask again.

00:00:53.760 --> 00:00:55.800
The hours arrive without a clear connection

00:00:55.800 --> 00:01:00.120
to the job. Someone reconstructs the story.

00:01:00.460 --> 00:01:02.080
Good judgement is still there,

00:01:02.340 --> 00:01:04.740
but its value has stalled between people.

00:01:05.580 --> 00:01:08.080
The same passage happens in our own work.

00:01:08.860 --> 00:01:11.720
I make the situation and my reasoning visible.

00:01:12.000 --> 00:01:14.040
Duncan’s response gives the work commercial

00:01:14.040 --> 00:01:18.140
direction. 04 Systems uses that context

00:01:18.140 --> 00:01:19.840
to build a dependable route.

00:01:20.440 --> 00:01:21.580
The team tries it,

00:01:22.220 --> 00:01:24.720
and what happens returns to the next decision.

00:01:25.000 --> 00:01:27.020
Each contribution needs a response from

00:01:27.020 --> 00:01:30.980
someone else. A technical fix is one contribution.

00:01:31.780 --> 00:01:33.520
Maintenance means different things from

00:01:33.520 --> 00:01:36.060
each position. We still need to know whether

00:01:36.060 --> 00:01:38.300
the person can complete the task again,

00:01:38.600 --> 00:01:40.340
using a process that works.

00:01:40.740 --> 00:01:42.940
The immediate work is to finish the remaining

00:01:42.940 --> 00:01:45.300
time and materials records and establish

00:01:45.300 --> 00:01:46.320
routine use.

00:01:46.540 --> 00:01:48.000
That is the foundation.

00:01:48.360 --> 00:01:50.560
Connected records can later help us examine

00:01:50.560 --> 00:01:52.480
ABC’s patterns with AI,

00:01:53.280 --> 00:01:55.040
with people checking what those patterns

00:01:55.040 --> 00:01:57.760
mean. The wider service could carry this

00:01:57.760 --> 00:02:00.080
same connection to captains and crews.

00:02:00.340 --> 00:02:03.920
Quality, pictures and useful insights give

00:02:03.920 --> 00:02:05.560
us something worth sharing.

00:02:05.860 --> 00:02:07.260
Someone must select it,

00:02:07.380 --> 00:02:09.919
place it in a relevant client conversation

00:02:10.139 --> 00:02:11.760
and follow up the response.

00:02:11.900 --> 00:02:14.140
We can reach a dependable finish and continue

00:02:14.140 --> 00:02:15.300
learning through use.

00:02:16.100 --> 00:02:17.920
Which of these connections would continue

00:02:17.920 --> 00:02:19.700
without my direct involvement,

00:02:20.400 --> 00:02:22.300
and what would need to carry the others?