WEBVTT

00:00:00.000 --> 00:00:03.700
Hey everybody, and welcome back to the
Operational ITAM Podcast.

00:00:04.360 --> 00:00:07.660
I'm Bill Van Nort, and today we're going
to fix a meeting.

00:00:08.220 --> 00:00:10.660
You know the one. Procurement has a better
price.

00:00:11.400 --> 00:00:14.940
Finance wants the saving. The application
owner says the replacement won't be

00:00:14.940 --> 00:00:18.840
ready. Asset management has found a
licensing condition nobody put in the

00:00:18.840 --> 00:00:23.160
business case. And somebody has written,
"All stakeholders aligned," at the

00:00:23.160 --> 00:00:25.340
bottom of the slide. That's optimistic.

00:00:25.900 --> 00:00:27.380
They've all received the slide.

00:00:27.920 --> 00:00:31.980
Here's the question. When those people
disagree, who actually has the

00:00:31.980 --> 00:00:34.060
authority to decide what happens next?

00:00:34.440 --> 00:00:38.180
Because a renewal can move through every
department, collect every comment,

00:00:38.400 --> 00:00:41.620
and still reach its deadline without
anyone owning the decision.

00:00:42.100 --> 00:00:44.340
The contract renews. The meeting recurs.

00:00:44.860 --> 00:00:47.680
Apparently, only one of those things
required a signature.

00:00:48.200 --> 00:00:50.220
Today begins The Decision Table.

00:00:50.540 --> 00:00:52.240
Who Owns the Renewal Decision?

00:00:57.740 --> 00:01:00.880
Good morning, good afternoon, or good
evening, wherever you're listening

00:01:00.880 --> 00:01:04.920
from. This is the show where we take the
unglamorous machinery of enterprise

00:01:04.920 --> 00:01:07.040
technology and make it make sense.

00:01:07.500 --> 00:01:11.440
Grab your coffee. In episode fourteen, we
challenged the bill before

00:01:11.440 --> 00:01:15.680
negotiating the discount. We separated
price, quantity, and terms.

00:01:16.060 --> 00:01:19.480
Now we're leaving the Grid and doing the
operating-model work I promised.

00:01:19.860 --> 00:01:23.680
Who uses that evidence, who can commit the
business, and who checks whether

00:01:23.680 --> 00:01:25.180
the result actually happened?

00:01:25.700 --> 00:01:29.900
ITAM, or IT asset management, connects the
technology estate to its

00:01:29.900 --> 00:01:33.680
ownership, rights, obligations, costs, and
lifecycle.

00:01:34.200 --> 00:01:38.120
FinOps connects technology consumption and
cost to business value through

00:01:38.120 --> 00:01:41.920
collaboration. That's consistent with the
FinOps Foundation's current

00:01:41.920 --> 00:01:46.460
framework. They overlap. Neither becomes
the other just because both have a

00:01:46.460 --> 00:01:50.520
spreadsheet open. The Foundation's twenty
twenty-six framework update puts

00:01:50.520 --> 00:01:54.860
explicit attention on executive strategy
and decisions across technology

00:01:54.860 --> 00:01:59.140
categories. Its Intersecting Disciplines
guidance describes coordination

00:01:59.140 --> 00:02:03.860
between FinOps and functions such as asset
management, procurement, finance,

00:02:04.200 --> 00:02:08.320
security, and architecture. It allows
different organizational arrangements.

00:02:08.780 --> 00:02:10.900
You don't have to merge departments to
begin.

00:02:11.520 --> 00:02:16.180
My opinion, clearly labeled: start with a
decision that matters, and make the

00:02:16.180 --> 00:02:18.140
working arrangement prove itself there.

00:02:18.520 --> 00:02:20.500
You can discuss reporting lines afterward.

00:02:20.840 --> 00:02:24.360
Preferably after somebody has demonstrated
that the arrangement can produce

00:02:24.360 --> 00:02:27.000
an answer. The counterargument is fair.

00:02:27.500 --> 00:02:31.140
Some organizations need structural change
because authority is genuinely

00:02:31.140 --> 00:02:34.680
fragmented. A meeting won't repair
conflicting mandates.

00:02:35.160 --> 00:02:39.460
But working through one decision exposes
exactly which authority is missing.

00:02:39.780 --> 00:02:43.400
That's a better basis for escalation than
a general complaint that nobody

00:02:43.400 --> 00:02:45.800
collaborates. Let's work a case.

00:02:46.260 --> 00:02:50.200
This is a fictional company, with invented
prices and explicit assumptions.

00:02:50.700 --> 00:02:53.260
It isn't a client story or an industry
benchmark.

00:02:53.260 --> 00:02:55.480
All amounts are U.S. dollars.

00:02:56.140 --> 00:02:59.920
The company runs customer support on a
software service with a renewal quote

00:02:59.920 --> 00:03:01.880
of six hundred thousand dollars a year.

00:03:02.140 --> 00:03:05.940
A competing service offers the required
subscription scope for four hundred

00:03:05.940 --> 00:03:10.004
eighty thousand a year. The first slide
says, "Save a hundred twenty thousand

00:03:10.004 --> 00:03:13.420
dollars annually." Then the delivery
estimate arrives.

00:03:13.900 --> 00:03:16.860
A hundred twenty thousand dollars to
change platforms.

00:03:17.320 --> 00:03:21.220
That estimate includes data conversion,
implementation, overlapping

00:03:21.220 --> 00:03:25.180
subscriptions, training, and the internal
effort assigned to the project.

00:03:25.580 --> 00:03:29.280
For now, assume the estimate is complete
and the migration finishes on

00:03:29.280 --> 00:03:31.840
schedule. We'll test that assumption
shortly.

00:03:32.200 --> 00:03:35.980
In the first year, the alternative's
subscription and transition total six

00:03:35.980 --> 00:03:39.140
hundred thousand dollars. The recurring
price is lower.

00:03:39.500 --> 00:03:41.720
The modeled first-year total is the same.

00:03:42.420 --> 00:03:45.940
Finance also needs to distinguish cash
payments from internal capacity.

00:03:46.360 --> 00:03:50.260
A salaried employee's project time can be
a real economic cost without

00:03:50.260 --> 00:03:52.220
becoming an additional payroll payment.

00:03:52.560 --> 00:03:55.300
Record it once, and say what kind of cost
it is.

00:03:55.580 --> 00:03:57.500
That's the position when our meeting
starts.

00:03:58.000 --> 00:03:59.680
There may be a good reason to move.

00:03:59.880 --> 00:04:03.220
But the original slide has skipped the
work required to get there.

00:04:03.480 --> 00:04:07.040
Before inviting anyone, write the decision
in plain language.

00:04:07.420 --> 00:04:11.920
For this case: should we renew the
incumbent, migrate to the alternative, or

00:04:11.920 --> 00:04:15.580
pursue a shorter bridge arrangement while
we resolve a specific uncertainty?

00:04:15.940 --> 00:04:18.460
Then write the deadline that preserves
those choices.

00:04:18.460 --> 00:04:20.800
The renewal date may be too late.

00:04:21.060 --> 00:04:25.040
The notice clause, procurement lead time,
migration schedule, and any

00:04:25.040 --> 00:04:26.780
required approval come first.

00:04:27.120 --> 00:04:31.680
This is episode nine's renewal clock, now
attached to a decision somebody has

00:04:31.680 --> 00:04:35.560
to make. I would ask the service owner to
explain the business requirement.

00:04:35.960 --> 00:04:38.280
Which customer interactions must keep
working?

00:04:38.600 --> 00:04:40.640
What would acceptable performance look
like?

00:04:40.880 --> 00:04:43.720
Which integrations and historical records
are essential?

00:04:44.260 --> 00:04:47.820
The requirement needs to be clear enough
to test against either supplier.

00:04:48.460 --> 00:04:52.300
Asset management brings the entitlement
position and lifecycle evidence.

00:04:52.900 --> 00:04:55.900
An entitlement is the documented right to
use something.

00:04:56.480 --> 00:04:58.580
What have we bought? Which terms apply?

00:04:59.080 --> 00:05:02.720
What is assigned or deployed, and what
would change under each option?

00:05:03.180 --> 00:05:07.560
If we retain part of the old service,
identify that obligation explicitly.

00:05:08.340 --> 00:05:11.240
FinOps brings the consumption pattern and
its cost drivers.

00:05:11.760 --> 00:05:13.520
What is the service actually doing?

00:05:13.520 --> 00:05:18.780
What changes if demand grows, falls, or
shifts into a more expensive feature?

00:05:19.260 --> 00:05:22.920
A forecast should describe the business
behavior that produces the bill.

00:05:23.460 --> 00:05:26.280
Procurement brings the executable
commercial options.

00:05:26.920 --> 00:05:31.160
Quote validity, notice requirements,
minimum commitments, renewal provisions,

00:05:31.420 --> 00:05:33.160
and the route to a signed change.

00:05:33.980 --> 00:05:37.700
Legal reviews the interpretations and
obligations that need legal judgment.

00:05:38.460 --> 00:05:41.820
Security and privacy review the relevant
controls and data handling.

00:05:41.820 --> 00:05:45.840
They can prepare their findings before the
meeting; everyone doesn't need to

00:05:45.840 --> 00:05:47.160
sit through every discussion.

00:05:47.760 --> 00:05:51.520
Engineering or architecture validates
whether the alternative can work in our

00:05:51.520 --> 00:05:55.640
environment. The delivery lead establishes
whether the migration can happen

00:05:55.640 --> 00:05:57.420
with the people and time available.

00:05:57.960 --> 00:06:01.600
The service owner accepts the operational
outcome within their authority.

00:06:02.100 --> 00:06:03.320
Those may be different people.

00:06:03.940 --> 00:06:07.720
Finance agrees how the options will be
compared and how any benefit will be

00:06:07.720 --> 00:06:11.380
recognized. It should be possible to
follow the numbers back to the

00:06:11.380 --> 00:06:13.160
organization's financial records.

00:06:13.680 --> 00:06:17.180
Finally, identify the person with
delegated authority to approve this

00:06:17.180 --> 00:06:21.220
decision. Their authority must cover the
spend and the tradeoffs being

00:06:21.220 --> 00:06:23.720
accepted, or the decision needs
escalation.

00:06:24.220 --> 00:06:28.680
A budget holder cannot simply waive a
legal obligation or override a security

00:06:28.680 --> 00:06:30.700
requirement outside their authority.

00:06:30.980 --> 00:06:33.460
That person needs a recommendation they
can act on.

00:06:33.460 --> 00:06:37.680
"Everyone should review" is an assignment
that can survive indefinitely

00:06:37.680 --> 00:06:39.460
without ever being completed.

00:06:40.200 --> 00:06:41.600
Now we put the evidence together.

00:06:42.140 --> 00:06:45.820
Same service. Same scope. Same comparison
period.

00:06:46.240 --> 00:06:50.440
Dates on the source records. Someone
responsible for resolving each material

00:06:50.440 --> 00:06:54.780
gap. Suppose the usage report shows fewer
active people than the license

00:06:54.780 --> 00:06:57.140
register. Don't average the counts.

00:06:57.540 --> 00:06:58.960
Find out what each one measures.

00:06:58.960 --> 00:07:03.520
A monthly active-user report and a count
of assigned licenses are answering

00:07:03.520 --> 00:07:08.300
different questions. Seasonal use, service
accounts, people on leave, and

00:07:08.300 --> 00:07:11.000
retention requirements can explain part of
the difference.

00:07:11.420 --> 00:07:13.660
So can genuinely unused assignments.

00:07:14.240 --> 00:07:18.980
Episode thirteen gave us FOCUS, the FinOps
Open Cost and Usage Specification,

00:07:18.980 --> 00:07:21.560
as a way to make billing data more
comparable.

00:07:21.800 --> 00:07:25.400
That helps this meeting. It doesn't turn a
billing record into proof of

00:07:25.400 --> 00:07:29.420
entitlement or tell us whether a customer-
support workflow can move safely.

00:07:29.840 --> 00:07:32.880
Keep those evidence types linked, with
their limits visible.

00:07:33.300 --> 00:07:36.160
If a report excludes a subsidiary, say so.

00:07:36.440 --> 00:07:40.360
If the contract interpretation is
unresolved, give it an owner and an answer

00:07:40.360 --> 00:07:44.020
date. A green cell shouldn't conceal an
unanswered question.

00:07:44.400 --> 00:07:46.300
You also need a route for disagreement.

00:07:46.740 --> 00:07:50.740
If the service owner says migration takes
six months and the proposal assumes

00:07:50.740 --> 00:07:52.860
three, that's a decision input.

00:07:52.860 --> 00:07:55.920
Ask what would make the shorter schedule
credible.

00:07:56.700 --> 00:07:58.500
Additional people? Reduced scope?

00:07:58.940 --> 00:08:02.840
A different cutover? Price those options
and test the consequences.

00:08:03.500 --> 00:08:06.700
If nothing supports the shorter schedule,
change the model.

00:08:07.100 --> 00:08:10.400
The spreadsheet doesn't get a vote on how
long the integration takes.

00:08:11.060 --> 00:08:13.340
What if nobody will accept the decision
authority?

00:08:13.960 --> 00:08:18.140
Then your next action is escalation, with
the consequence made explicit.

00:08:18.640 --> 00:08:20.820
This option expires on this date.

00:08:20.820 --> 00:08:23.780
This notice must be sent by that date.

00:08:24.200 --> 00:08:26.360
Here is what happens if nobody acts.

00:08:26.900 --> 00:08:30.460
Ask the executive who owns the relevant
budget and service to name the

00:08:30.460 --> 00:08:34.340
authorized decision maker, following the
organization's delegation rules.

00:08:34.780 --> 00:08:38.500
Don't quietly assign yourself authority
because everyone else is busy.

00:08:38.840 --> 00:08:41.040
And don't interpret silence as approval.

00:08:41.580 --> 00:08:45.360
Your contribution is to make the
unresolved choice visible while there is

00:08:45.360 --> 00:08:49.000
still time to resolve it. There is also a
difference between someone

00:08:49.000 --> 00:08:52.200
challenging the evidence and someone
withholding a decision.

00:08:52.780 --> 00:08:56.420
A licensing specialist can say a proposed
use isn't supported by the

00:08:56.420 --> 00:09:00.500
agreement. The decision owner then needs a
lawful alternative, different

00:09:00.500 --> 00:09:02.300
terms, or a different proposal.

00:09:02.840 --> 00:09:06.120
Calling that specialist uncommercial won't
change the license.

00:09:06.600 --> 00:09:10.360
I would rather have that disagreement in
preparation than discover it after

00:09:10.360 --> 00:09:12.880
the purchase has become somebody's success
story.

00:09:16.360 --> 00:09:20.240
Let's take a quick break. If the difficult
part in your organization is

00:09:20.240 --> 00:09:24.300
deciding who owns the work, I've built a
resource for that in the Operational

00:09:24.300 --> 00:09:28.060
ITAM Store. It's called Roles and
Operating Cadence.

00:09:28.420 --> 00:09:31.920
The product includes role charters with
authority boundaries and assessment

00:09:31.920 --> 00:09:37.000
exercises, plus a workbook for service
catalog, assignments, cadence, and

00:09:37.000 --> 00:09:41.620
workload. There are Word, PDF, and offline
HTML resources.

00:09:42.120 --> 00:09:46.060
Use it to work through who is accountable,
what they can decide, and how the

00:09:46.060 --> 00:09:48.860
work gets reviewed. Adapt it to your
organization.

00:09:48.860 --> 00:09:53.440
A role description still needs an actual
person with the authority and time

00:09:53.440 --> 00:09:57.440
to carry it out. You can review the
contents and selected preview at

00:09:57.440 --> 00:10:00.460
operational I T A M dot com slash store.

00:10:00.800 --> 00:10:03.880
This is my paid resource, and buying it
supports the show.

00:10:04.280 --> 00:10:08.180
The exercise at the end of this episode is
free and uses records you already

00:10:08.180 --> 00:10:12.100
have. If this conversation would help
someone who owns your next renewal,

00:10:12.420 --> 00:10:16.980
send them the episode. You can also visit
operational I T A M dot com for the

00:10:16.980 --> 00:10:19.900
podcast, transcripts, and practical
resources.

00:10:24.360 --> 00:10:26.120
Alright. Back to the decision.

00:10:26.580 --> 00:10:31.000
Before we finish our fictional case,
consider two real purchasing mechanisms.

00:10:31.920 --> 00:10:35.740
Microsoft's S Q L Server licensing
guidance says licenses with Software

00:10:35.740 --> 00:10:40.760
Assurance, or qualifying software
subscription licenses, include Azure
Hybrid

00:10:40.760 --> 00:10:44.880
Benefit. Software Assurance is Microsoft's
coverage program that provides

00:10:44.880 --> 00:10:47.900
specified benefits alongside eligible
licenses.

00:10:48.400 --> 00:10:50.260
That can change a cloud comparison.

00:10:50.380 --> 00:10:54.800
But you need the applicable product terms,
license eligibility, quantities,

00:10:55.200 --> 00:10:56.740
assignments, and coverage dates.

00:10:57.120 --> 00:11:00.440
You also need to establish whether rights
are already supporting another

00:11:00.440 --> 00:11:03.640
deployment and which simultaneous-use
conditions apply.

00:11:03.840 --> 00:11:07.280
A setting that enables a billing benefit
doesn't establish that you're

00:11:07.280 --> 00:11:10.900
entitled to use it. The asset specialist
validates the rights.

00:11:10.900 --> 00:11:14.200
The cloud team validates the deployment
and consumption.

00:11:15.080 --> 00:11:18.240
Finance compares the costs. Procurement
checks the agreement.

00:11:18.760 --> 00:11:20.660
Same decision, different evidence.

00:11:21.380 --> 00:11:26.260
Now Amazon Web Services. Its Compute
Savings Plans exchange lower eligible

00:11:26.260 --> 00:11:30.780
usage prices for an hourly spending
commitment over a one-year or three-year

00:11:30.780 --> 00:11:34.580
term, as described in the AWS Savings
Plans documentation.

00:11:35.120 --> 00:11:39.100
If engineering plans to reduce or retire
workloads, buying against

00:11:39.100 --> 00:11:42.640
yesterday's consumption can leave you with
a commitment the future workload

00:11:42.640 --> 00:11:47.240
doesn't use. Eligible usage elsewhere
might absorb it, subject to the plan's

00:11:47.240 --> 00:11:48.820
scope and sharing configuration.

00:11:49.280 --> 00:11:53.980
That needs checking. AWS also documents
limited return provisions.

00:11:54.340 --> 00:11:58.440
Don't build a long-term exit strategy
around a short purchase-return window.

00:11:58.720 --> 00:12:02.820
The practical question is what consumption
will remain after the approved

00:12:02.820 --> 00:12:06.300
architecture changes. Check that before
buying the commitment.

00:12:06.620 --> 00:12:10.860
Keep technical efficiency, commitment
utilization, and invoice reduction

00:12:10.860 --> 00:12:12.580
separate in the benefit report.

00:12:12.920 --> 00:12:16.340
These are current vendor mechanisms, not
assumptions about our fictional

00:12:16.340 --> 00:12:21.080
support-service contract. The common
lesson is why a low rate can't settle

00:12:21.080 --> 00:12:23.800
the decision on its own. Back to our case.

00:12:24.180 --> 00:12:28.620
We're comparing three years, using
constant prices, the same required service

00:12:28.620 --> 00:12:33.160
scope, and no discounting. This is an
illustrative cost comparison, not a

00:12:33.160 --> 00:12:34.360
complete investment appraisal.

00:12:34.360 --> 00:12:39.200
Finance would add the organization's
treatment of timing, taxes, inflation,

00:12:39.400 --> 00:12:43.890
and other material factors. At six hundred
thousand a year, staying costs one

00:12:43.890 --> 00:12:46.820
million eight hundred thousand dollars
over three years.

00:12:47.080 --> 00:12:50.560
The alternative costs one million four
hundred forty thousand in

00:12:50.560 --> 00:12:53.620
subscriptions, plus the hundred twenty
thousand transition.

00:12:54.200 --> 00:12:56.920
Total: one million five hundred sixty
thousand.

00:12:57.100 --> 00:13:00.820
That puts the alternative two hundred
forty thousand dollars lower in our

00:13:00.820 --> 00:13:04.820
base case. It is a modeled difference, not
a saving we've realized.

00:13:05.600 --> 00:13:08.420
Then procurement returns with a revised
incumbent offer.

00:13:08.740 --> 00:13:12.840
A three-year renewal at five hundred forty
thousand dollars a year, fixed for

00:13:12.840 --> 00:13:15.020
that term, for the same required scope.

00:13:15.340 --> 00:13:19.080
For this illustration, assume the supplier
will contract on those terms.

00:13:19.480 --> 00:13:22.926
The incumbent's three-year total is now
one million six hundred twenty

00:13:22.926 --> 00:13:27.143
thousand dollars. The alternative remains
one million five hundred sixty

00:13:27.143 --> 00:13:31.040
thousand. The difference has narrowed to
sixty thousand dollars over three

00:13:31.040 --> 00:13:33.240
years. Nobody did anything wrong.

00:13:33.540 --> 00:13:37.260
The evidence changed. Our recommendation
needs to change with it.

00:13:37.560 --> 00:13:39.260
Now test the migration assumption.

00:13:39.720 --> 00:13:44.000
In an illustrative delay scenario,
additional overlap and delivery effort add

00:13:44.000 --> 00:13:47.720
ninety thousand dollars beyond the
transition cost already included.

00:13:47.980 --> 00:13:51.400
The alternative becomes one million six
hundred fifty thousand dollars.

00:13:51.900 --> 00:13:55.080
That's thirty thousand more than the
revised incumbent option.

00:13:55.080 --> 00:13:57.460
We haven't proved migration is bad.

00:13:57.880 --> 00:14:00.520
We've identified what could reverse the
cost ranking.

00:14:00.940 --> 00:14:04.680
The project team must tell us whether that
delay scenario is credible and

00:14:04.680 --> 00:14:08.580
what could prevent it. Don't invent a
probability to make the arithmetic look

00:14:08.580 --> 00:14:12.020
sophisticated. Cost isn't the only
acceptance test.

00:14:12.460 --> 00:14:14.880
Can customers still reach support during
cutover?

00:14:15.340 --> 00:14:18.060
Can the team retrieve the required
historical records?

00:14:18.360 --> 00:14:21.660
Does the replacement meet security and
accessibility requirements?

00:14:22.200 --> 00:14:26.100
Establish how those questions will be
tested and who can accept the result.

00:14:26.600 --> 00:14:29.360
A valuable capability might justify paying
more.

00:14:29.820 --> 00:14:32.400
So might a credible reduction in
operational risk.

00:14:32.860 --> 00:14:36.980
Describe the benefit and its evidence
without manufacturing a dollar value.

00:14:37.300 --> 00:14:40.300
The executive should know what the
organization is buying with the

00:14:40.300 --> 00:14:44.260
difference. For our support service, I
would ask whether the change improves

00:14:44.260 --> 00:14:47.160
something customers or staff actually
experience.

00:14:47.640 --> 00:14:49.620
Can an agent find the right case history?

00:14:49.920 --> 00:14:52.680
Does the workflow reduce a verified source
of rework?

00:14:52.680 --> 00:14:57.180
Establish the baseline and an acceptance
test before calling the new feature

00:14:57.180 --> 00:15:01.260
valuable. A feature demonstrated by the
supplier is a candidate benefit.

00:15:01.580 --> 00:15:05.120
The service owner still has to establish
whether it solves their problem.

00:15:05.440 --> 00:15:08.940
For our worked case, assume testing hasn't
yet established that the

00:15:08.940 --> 00:15:11.320
replacement can handle a required
integration.

00:15:11.680 --> 00:15:14.100
The incumbent meets the present business
requirement.

00:15:14.320 --> 00:15:16.700
The revised price is contractually
available.

00:15:17.060 --> 00:15:20.520
The authorized owner chooses the three-
year renewal, accepting that

00:15:20.520 --> 00:15:24.220
commitment, with a funded evaluation of
the alternative before the next

00:15:24.220 --> 00:15:27.660
contractual decision window. That is our
fictional outcome.

00:15:28.080 --> 00:15:31.460
Another organization, with different
evidence, could responsibly choose

00:15:31.460 --> 00:15:34.660
migration. Now record the actual
authorization.

00:15:35.280 --> 00:15:36.800
Which service and legal entity?

00:15:37.120 --> 00:15:39.660
Which offer and term? What spending limit?

00:15:40.100 --> 00:15:42.420
What conditions must be met before
signature?

00:15:42.860 --> 00:15:46.220
Who implements the change, and when will
the outcome be reviewed?

00:15:46.220 --> 00:15:49.400
Record the rejected alternative and the
reason.

00:15:49.840 --> 00:15:53.820
In this case, the unresolved integration
and the narrow base-case advantage

00:15:53.820 --> 00:15:57.580
mattered. That protects the organization
from having to reconstruct the

00:15:57.580 --> 00:16:00.280
decision later from a collection of
meeting invitations.

00:16:00.820 --> 00:16:04.140
A conditional approval needs a condition
someone can verify.

00:16:04.620 --> 00:16:08.600
If legal clearance is required, identify
the reviewer and the document.

00:16:08.940 --> 00:16:12.120
If testing is required, identify the
acceptance criteria.

00:16:12.120 --> 00:16:16.960
Don't leave a phrase like "subject to
satisfactory checks" floating above a

00:16:16.960 --> 00:16:20.820
purchase order. And a bridge arrangement
is only an option if the supplier

00:16:20.820 --> 00:16:23.760
actually offers it and the authorized
parties agree.

00:16:24.280 --> 00:16:28.180
Price the extension, preserve necessary
rights and support, and write down

00:16:28.180 --> 00:16:29.980
what the extra time will accomplish.

00:16:30.220 --> 00:16:34.100
Otherwise, you've bought another deadline
with the same unanswered question

00:16:34.100 --> 00:16:37.580
attached. The meeting isn't finished when
the order is signed.

00:16:37.920 --> 00:16:41.520
In our case, procurement checks the
executed order against the approved

00:16:41.520 --> 00:16:45.620
offer. The service owner confirms the
expected service and configuration.

00:16:46.300 --> 00:16:49.220
Asset management updates the entitlement
and renewal records.

00:16:49.980 --> 00:16:52.800
Finance verifies the billing and the
agreed benefit treatment.

00:16:53.160 --> 00:16:57.020
The revised incumbent price is sixty
thousand dollars a year below the

00:16:57.020 --> 00:16:59.640
earlier six-hundred-thousand-dollar
renewal option.

00:16:59.840 --> 00:17:04.000
That is not automatically sixty thousand
below last year's actual spend.

00:17:04.300 --> 00:17:05.900
Those might be different baselines.

00:17:06.360 --> 00:17:08.480
Carry the comparison label into the
report.

00:17:08.480 --> 00:17:12.380
And don't let multiple teams count the
same benefit independently.

00:17:13.020 --> 00:17:17.020
Procurement's negotiated reduction and the
service owner's lower forecast may

00:17:17.020 --> 00:17:21.660
describe the same change. Give the change
one traceable record, credit the

00:17:21.660 --> 00:17:24.480
contributors, and have finance validate
the result.

00:17:25.000 --> 00:17:26.980
Now establish the review rhythm.

00:17:27.320 --> 00:17:30.840
My recommendation is to fit it to the
decision's risk and deadlines.

00:17:31.260 --> 00:17:34.680
A routine renewal inside approved limits
may need a short review.

00:17:34.680 --> 00:17:39.300
A material migration or uncertain
commitment needs closer attention.

00:17:39.780 --> 00:17:43.500
Set a review date and specific triggers
for returning to the decision owner.

00:17:43.860 --> 00:17:47.920
Those triggers could include a failed
acceptance test, demand outside the

00:17:47.920 --> 00:17:52.700
approved forecast, a missed notice
milestone, or a changed commercial offer.

00:17:53.120 --> 00:17:57.600
Give each trigger an action. An alert
without an owner is just another thing

00:17:57.600 --> 00:18:01.580
people can acknowledge. You don't need a
new committee for every invoice.

00:18:01.580 --> 00:18:05.920
You need a reliable way to identify the
decisions that cross boundaries,

00:18:06.200 --> 00:18:09.040
assemble the evidence, and reach someone
who can act.

00:18:09.440 --> 00:18:13.200
For a smaller organization, one person may
carry several of these roles.

00:18:13.680 --> 00:18:16.620
Keep the questions separate even when the
chairs aren't.

00:18:16.900 --> 00:18:21.140
Bring in specialist review where the
rights, obligations, or risks exceed

00:18:21.140 --> 00:18:23.360
that person's expertise or authority.

00:18:23.840 --> 00:18:25.640
Which brings us to today's principle.

00:18:26.640 --> 00:18:27.010
Accountability.

00:18:27.660 --> 00:18:30.000
Shared work still needs clear decision
authority.

00:18:30.000 --> 00:18:34.240
Being accountable means explaining the
choice, arranging the work that makes

00:18:34.240 --> 00:18:36.940
it real, and returning to the evidence
afterward.

00:18:37.380 --> 00:18:41.140
It doesn't require pretending you
personally know every license term or

00:18:41.140 --> 00:18:43.620
migration detail. Class dismissed.

00:18:44.340 --> 00:18:48.120
Here's your homework. Set aside about an
hour, using information you're

00:18:48.120 --> 00:18:49.760
already authorized to access.

00:18:50.180 --> 00:18:54.280
Choose one upcoming renewal. Write the
decision and the last date that

00:18:54.280 --> 00:18:57.720
preserves your options. Name the person
authorized to decide.

00:18:57.720 --> 00:19:02.640
List the available options, the evidence
each one still needs, and the person

00:19:02.640 --> 00:19:04.420
responsible for supplying it.

00:19:04.520 --> 00:19:07.480
Use the same scope and comparison period
for the costs.

00:19:07.960 --> 00:19:11.240
Then write the condition most likely to
change your recommendation.

00:19:11.820 --> 00:19:13.480
Don't write "more information."

00:19:13.880 --> 00:19:15.820
Write the specific missing answer.

00:19:16.120 --> 00:19:19.420
Finish with the implementation owner and
the evidence you'll check after

00:19:19.420 --> 00:19:23.400
approval. Take that page to the decision
owner before the meeting is booked.

00:19:23.780 --> 00:19:27.300
If you want help making those
responsibilities repeatable, you'll find
my

00:19:27.300 --> 00:19:31.080
Roles and Operating Cadence resource in
the Operational ITAM Store.

00:19:31.400 --> 00:19:32.620
The link is in the show notes.

00:19:33.060 --> 00:19:35.440
You can complete today's homework without
buying it.

00:19:35.660 --> 00:19:39.320
As we continue at The Decision Table, the
next question is how to prove the

00:19:39.320 --> 00:19:42.160
value of a decision after the presentation
is over.

00:19:42.540 --> 00:19:46.660
What changed, who benefited, and what can
finance actually verify?

00:19:46.960 --> 00:19:49.120
That's the direction I want to explore
next.

00:19:49.420 --> 00:19:52.860
The case files are open. One situation,
one page.

00:19:53.220 --> 00:19:55.760
The constraint, what you did, and what
happened.

00:19:55.760 --> 00:19:59.600
Remove company names and sensitive details
before sending it through the

00:19:59.600 --> 00:20:03.200
website. Send me one worth working, and
I'll build an episode around it.

00:20:03.500 --> 00:20:06.780
I'm Bill Van Nort, this is the Operational
ITAM Podcast.

00:20:07.320 --> 00:20:10.620
Put the choice in writing. Give the owner
usable evidence.

00:20:10.920 --> 00:20:13.480
Come back for the result. I'll talk to you
next week.

00:20:13.820 --> 00:20:14.140
Take care.