WEBVTT

00:00:01.900 --> 00:00:05.200
Preparation gives technology partners time to explore solution

00:00:05.200 --> 00:00:07.320
options before the Cost of Delay Game.

00:00:07.880 --> 00:00:10.700
That helps create a more equitable playing field when requests

00:00:10.700 --> 00:00:11.280
are compared.

00:00:12.040 --> 00:00:15.260
The pre-game process begins with the invitation, about four

00:00:15.260 --> 00:00:16.160
weeks before the round.

00:00:17.280 --> 00:00:19.920
Plan roughly five business days for each of four activities.

00:00:20.560 --> 00:00:23.120
They generally happen in order for each sponsor, although

00:00:23.120 --> 00:00:24.180
some work can overlap.

00:00:24.980 --> 00:00:28.140
These are expected preparation steps, with occasional exceptions.

00:00:34.467 --> 00:00:36.327
First, confirm participation.

00:00:37.387 --> 00:00:38.667
Respond within five business days.

00:00:39.307 --> 00:00:42.167
Without a response, the team assumes you are not participating.

00:00:42.807 --> 00:00:46.167
If you respond within ten days, the team may still try to

00:00:46.167 --> 00:00:46.467
accommodate you.

00:00:53.067 --> 00:00:56.627
Second, prepare your request using the approved PowerPoint

00:00:56.627 --> 00:00:56.987
template.

00:00:57.987 --> 00:01:00.827
Follow its instructions so the solution architects have the

00:01:00.827 --> 00:01:02.427
information they need for the review.

00:01:08.733 --> 00:01:12.813
Third, take part in a one-hour technical scoping conversation.

00:01:13.733 --> 00:01:16.513
The solution architects walk through your request and ask

00:01:16.513 --> 00:01:18.893
questions about how a solution could meet your needs.

00:01:19.833 --> 00:01:22.533
That conversation gives them the context to draft a potential

00:01:22.533 --> 00:01:23.313
solution afterward.

00:01:29.833 --> 00:01:33.733
Fourth, give the solution architects time to draft a potential

00:01:33.733 --> 00:01:34.113
solution.

00:01:35.013 --> 00:01:37.013
This is working time after the sponsor review.

00:01:37.733 --> 00:01:40.053
They use what they learn to explore how the request could

00:01:40.053 --> 00:01:40.473
be delivered.

00:01:41.193 --> 00:01:43.713
A follow-up conversation with the sponsor is not expected

00:01:43.713 --> 00:01:44.453
during this step.

00:01:50.700 --> 00:01:53.500
A request is ready for the game when the solution architect

00:01:53.500 --> 00:01:56.420
review is complete and the PowerPoint has been submitted.

00:01:56.940 --> 00:01:57.320
Start early.

00:01:58.040 --> 00:02:00.460
Give your technology partners time to think through solution

00:02:00.460 --> 00:02:04.080
options so everyone arrives better prepared for a fair comparison.

00:02:10.167 --> 00:02:17.167
[Instrumental music rises, then fades.]