WEBVTT

1
00:00:02.600 --> 00:00:04.712
This is a fictional founder

2
00:00:04.712 --> 00:00:07.567
introduction created for demonstration.

3
00:00:08.317 --> 00:00:09.362
I am Maya,

4
00:00:09.362 --> 00:00:11.568
the founder in this example,

5
00:00:11.568 --> 00:00:13.426
and I am exploring Fieldnote

6
00:00:13.426 --> 00:00:14.819
for small teams that hand work

7
00:00:14.819 --> 00:00:16.162
from one shift to the next.

8
00:00:18.350 --> 00:00:20.794
My starting point is a familiar question:

9
00:00:20.794 --> 00:00:22.065
when a colleague leaves,

10
00:00:22.065 --> 00:00:23.238
can the next person see

11
00:00:23.238 --> 00:00:24.557
what still needs a decision?

12
00:00:25.100 --> 00:00:26.172
Fieldnote is a concept

13
00:00:26.172 --> 00:00:28.047
for recording three things together:

14
00:00:28.047 --> 00:00:29.029
the next owner,

15
00:00:29.029 --> 00:00:30.190
the open question,

16
00:00:30.190 --> 00:00:31.033
and the next action.

17
00:00:31.850 --> 00:00:33.050
Imagine a maintenance

18
00:00:33.050 --> 00:00:34.200
team finishing a visit.

19
00:00:38.600 --> 00:00:40.161
Instead of a long message

20
00:00:40.161 --> 00:00:41.834
with an unclear ending,

21
00:00:41.834 --> 00:00:44.175
the handover shows who follows up,

22
00:00:44.175 --> 00:00:45.625
what they need to check,

23
00:00:45.625 --> 00:00:47.359
and where the relevant note lives.

24
00:00:49.850 --> 00:00:51.525
This is an illustration,

25
00:00:51.525 --> 00:00:53.446
not evidence from a real customer.

26
00:00:56.600 --> 00:00:59.341
I am not claiming a qualification

27
00:00:59.341 --> 00:01:01.036
or a business result.

28
00:01:03.350 --> 00:01:05.655
If you lead a team with this problem,

29
00:01:05.655 --> 00:01:07.302
the next step is simple:

30
00:01:07.302 --> 00:01:09.608
walk me through one recent handover,

31
00:01:09.608 --> 00:01:11.753
and we can see whether the idea fits.