WEBVTT

1
00:00:03.500 --> 00:00:06.560
Changing a service can affect teams you never expected.

2
00:00:07.220 --> 00:00:09.660
NovusLens helps you see those connections and the

3
00:00:09.660 --> 00:00:10.420
evidence behind them.

4
00:00:10.880 --> 00:00:13.640
This guide follows one question: if we change this

5
00:00:13.640 --> 00:00:15.100
service, who else is affected?

6
00:00:20.644 --> 00:00:24.044
Imagine your organisation is replacing a customer service system.

7
00:00:24.584 --> 00:00:27.324
The organisation chart names the teams, but it does

8
00:00:27.324 --> 00:00:28.624
not show every handoff.

9
00:00:29.164 --> 00:00:30.884
Operations relies on a data team.

10
00:00:31.284 --> 00:00:32.804
That team depends on a supplier.

11
00:00:33.244 --> 00:00:35.604
An AI agent also uses the service.

12
00:00:36.124 --> 00:00:37.844
Their records sit in different places.

13
00:00:38.564 --> 00:00:41.664
Before changing anything, you need to understand those relationships

14
00:00:41.664 --> 00:00:43.144
and who answers for them.

15
00:00:47.933 --> 00:00:52.753
NovusLens brings teams, systems, suppliers and AI agents

16
00:00:52.753 --> 00:00:54.573
into one inspectable model.

17
00:00:55.013 --> 00:00:56.533
We call it an organisation twin.

18
00:00:56.913 --> 00:00:59.633
A connection shows that one part needs something from

19
00:00:59.633 --> 00:00:59.913
another.

20
00:01:00.693 --> 00:01:02.813
Select a team or service to see its recorded

21
00:01:02.813 --> 00:01:05.713
owners, dependencies and supporting evidence.

22
00:01:06.313 --> 00:01:08.793
The twin reflects the records supplied to it, so

23
00:01:08.793 --> 00:01:11.193
missing information remains a question to investigate.

24
00:01:16.539 --> 00:01:19.959
Start with an organisation chart to identify teams and

25
00:01:19.959 --> 00:01:20.739
reporting lines.

26
00:01:21.539 --> 00:01:24.859
Add policies and service documents to explain responsibilities.

27
00:01:25.599 --> 00:01:29.819
Supported infrastructure exports describe systems, while configured connections bring

28
00:01:29.819 --> 00:01:31.099
in operational records.

29
00:01:31.879 --> 00:01:33.179
People can contribute what they know.

30
00:01:33.719 --> 00:01:35.739
These inputs build different parts of the picture.

31
00:01:36.219 --> 00:01:39.639
An imported chart alone cannot establish how work actually

32
00:01:39.639 --> 00:01:40.759
moves between teams.

33
00:01:45.667 --> 00:01:49.707
Imports read company files, while configured connections bring in

34
00:01:49.707 --> 00:01:50.767
operational records.

35
00:01:51.447 --> 00:01:55.427
NovusLens turns structural records into teams, systems and

36
00:01:55.427 --> 00:01:56.707
relationships you can inspect.

37
00:01:57.287 --> 00:02:00.387
It keeps supporting evidence alongside that picture, so you

38
00:02:00.387 --> 00:02:01.487
can return to the source.

39
00:02:06.400 --> 00:02:08.600
Each claim carries an evidence label.

40
00:02:09.500 --> 00:02:10.940
Told means somebody stated it.

41
00:02:11.620 --> 00:02:13.260
Shown means a document supports it.

42
00:02:13.880 --> 00:02:16.040
Measured means a source recorded an observation.

43
00:02:16.720 --> 00:02:19.920
In our example, a team says recovery takes one

44
00:02:19.920 --> 00:02:20.060
hour.

45
00:02:20.500 --> 00:02:22.100
The plan states the same target.

46
00:02:22.600 --> 00:02:25.140
An incident record shows two hours on one occasion.

47
00:02:25.760 --> 00:02:28.160
Read each source, its date and what it covers.

48
00:02:28.600 --> 00:02:30.940
The label describes support, not certainty.

49
00:02:36.358 --> 00:02:38.038
Those different accounts are useful.

50
00:02:38.578 --> 00:02:41.518
A recovery target and an incident outcome describe different

51
00:02:41.518 --> 00:02:41.878
things.

52
00:02:42.558 --> 00:02:45.458
NovusLens preserves their sources so people can investigate

53
00:02:45.458 --> 00:02:46.118
the difference.

54
00:02:46.738 --> 00:02:49.838
It also surfaces gaps in recorded ownership and disagreements

55
00:02:49.838 --> 00:02:50.618
about structure.

56
00:02:51.238 --> 00:02:52.798
A finding is an item to review.

57
00:02:53.358 --> 00:02:55.978
It gives the people involved something specific to examine

58
00:02:55.978 --> 00:02:57.778
before deciding what needs to change.

59
00:03:02.633 --> 00:03:05.013
Relationships tell only part of the story.

60
00:03:05.633 --> 00:03:08.373
For this service change, the Knowledge library can retain

61
00:03:08.373 --> 00:03:11.253
the recovery procedure and explain the supplier's role.

62
00:03:11.873 --> 00:03:15.293
It holds procedures, definitions and written accounts linked to

63
00:03:15.293 --> 00:03:16.373
the teams they concern.

64
00:03:17.133 --> 00:03:19.893
Each entry keeps its author, date and audience.

65
00:03:20.453 --> 00:03:22.633
These records can support answers to questions.

66
00:03:23.193 --> 00:03:26.073
A written account remains its author's statement and can

67
00:03:26.073 --> 00:03:27.373
be challenged or withdrawn.

68
00:03:32.300 --> 00:03:35.460
When you ask a question, NovusLens retrieves records

69
00:03:35.460 --> 00:03:36.540
you are permitted to see.

70
00:03:37.080 --> 00:03:40.560
Its reasoning service uses configured AI models where interpretation

71
00:03:40.560 --> 00:03:41.080
is needed.

72
00:03:41.620 --> 00:03:43.700
The result links the answer to supporting sources.

73
00:03:44.360 --> 00:03:46.940
Your organisation can run this system on its own

74
00:03:46.940 --> 00:03:47.460
infrastructure.

75
00:03:52.500 --> 00:03:54.380
Return to our service change.

76
00:03:55.040 --> 00:03:58.060
Use the organisation view to inspect connected teams and

77
00:03:58.060 --> 00:03:58.980
their recorded owners.

78
00:03:59.600 --> 00:04:02.100
In Ask and find, ask who is accountable for

79
00:04:02.100 --> 00:04:02.680
the service.

80
00:04:03.400 --> 00:04:06.900
NovusLens retrieves relevant records and uses configured AI

81
00:04:06.900 --> 00:04:08.740
models where interpretation is needed.

82
00:04:09.820 --> 00:04:12.480
Answers link statements to sources and state their limits.

83
00:04:13.060 --> 00:04:15.240
You can bring the ownership record into the discussion,

84
00:04:15.240 --> 00:04:17.820
and show everyone what supports the answer.

85
00:04:22.667 --> 00:04:27.167
You can examine Complexity, Agility and Recoverability: the current

86
00:04:27.167 --> 00:04:30.867
structure, ability to change and ability to restore service.

87
00:04:31.427 --> 00:04:34.447
These scores depend on documented local rules and available

88
00:04:34.447 --> 00:04:34.947
evidence.

89
00:04:35.707 --> 00:04:39.827
Separately, Explore a change compares the dependency-chain index under

90
00:04:39.827 --> 00:04:41.887
one assumed change to a handoff.

91
00:04:42.367 --> 00:04:45.387
This index describes the weight of the longest dependency

92
00:04:45.387 --> 00:04:45.787
chain.

93
00:04:46.127 --> 00:04:48.327
The comparison helps people discuss trade-offs.

94
00:04:48.847 --> 00:04:51.087
It does not estimate time or money saved.

95
00:04:56.615 --> 00:04:59.615
When an AI agent takes on work, someone must

96
00:04:59.615 --> 00:05:00.675
answer for its outcome.

97
00:05:01.375 --> 00:05:03.895
NovusLens separates what it can do, what it

98
00:05:03.895 --> 00:05:05.575
may do and who is responsible.

99
00:05:06.475 --> 00:05:08.755
Compare reported activity with recorded permissions.

100
00:05:09.395 --> 00:05:12.215
If ownership is missing or the accounts differ, you

101
00:05:12.215 --> 00:05:14.255
have a specific question to put to the people

102
00:05:14.255 --> 00:05:16.255
responsible before assigning more work.

103
00:05:21.494 --> 00:05:23.274
Return to the service change.

104
00:05:24.094 --> 00:05:27.334
The affected teams, supplier and agent owner are now

105
00:05:27.334 --> 00:05:27.574
visible.

106
00:05:28.154 --> 00:05:30.214
Bring them together around a management brief with the

107
00:05:30.214 --> 00:05:31.014
supporting records.

108
00:05:31.634 --> 00:05:34.294
In our example, the recovery plan says one hour;

109
00:05:34.634 --> 00:05:36.034
the incident record says two.

110
00:05:36.734 --> 00:05:38.754
Ask the service owner to review that difference with

111
00:05:38.754 --> 00:05:40.174
Operations and the supplier.

112
00:05:41.034 --> 00:05:42.574
Record the review and the decision.

113
00:05:43.214 --> 00:05:45.734
Everyone can examine the same basis for proceeding.

114
00:05:50.667 --> 00:05:53.347
The next change need not start from scattered records

115
00:05:53.347 --> 00:05:53.727
again.

116
00:05:54.247 --> 00:05:57.107
Keep the decision, its sources and the explanation behind

117
00:05:57.107 --> 00:05:57.467
it.

118
00:05:58.047 --> 00:05:59.767
Suppose a new supplier record arrives.

119
00:06:00.507 --> 00:06:02.987
Revisit the affected relationships and the recovery question.

120
00:06:03.587 --> 00:06:06.407
Your team can inspect the new account alongside the

121
00:06:06.407 --> 00:06:07.067
earlier review.

122
00:06:07.587 --> 00:06:10.527
The organisation retains the context for its next decision.

123
00:06:15.467 --> 00:06:18.407
A service change reaches beyond the team leading it.

124
00:06:18.947 --> 00:06:21.987
NovusLens makes the recorded dependencies visible: the data

125
00:06:21.987 --> 00:06:24.707
team, the supplier and the agent using the service.

126
00:06:25.427 --> 00:06:27.487
Follow those connections to find who needs to be

127
00:06:27.487 --> 00:06:27.767
involved.

128
00:06:28.427 --> 00:06:30.387
You can take the proposal into review with its

129
00:06:30.387 --> 00:06:31.787
wider implications in view.

130
00:06:36.667 --> 00:06:39.707
The organisation chart places a team in Operations.

131
00:06:40.247 --> 00:06:42.407
A team account names a different reporting line.

132
00:06:42.847 --> 00:06:44.467
A division record gives another view.

133
00:06:45.167 --> 00:06:46.787
Which account applies to this decision?

134
00:06:47.547 --> 00:06:50.727
NovusLens keeps the sources distinguishable and supports review

135
00:06:50.727 --> 00:06:51.527
of contradictions.

136
00:06:52.267 --> 00:06:55.767
Novus-i2 advisers help you examine the evidence, its dates

137
00:06:55.767 --> 00:06:57.847
and scope, and work through the disagreement.

138
00:06:58.467 --> 00:07:00.907
You gain a question to resolve before relying on

139
00:07:00.907 --> 00:07:01.327
the picture.

140
00:07:06.200 --> 00:07:07.920
Know what your change affects.

141
00:07:08.540 --> 00:07:10.680
Give the right people a shared basis for deciding.

142
00:07:11.340 --> 00:07:13.680
Keep the evidence and understanding for the next change.

143
00:07:14.200 --> 00:07:17.560
That is the value of NovusLens alongside Novus-i2

144
00:07:17.560 --> 00:07:18.600
advisory support.

145
00:07:19.280 --> 00:07:21.060
Start with one transformation decision.

146
00:07:22.000 --> 00:07:24.700
Build towards an organisational twin your team can run,

147
00:07:25.360 --> 00:07:26.020
use and retain.