1 00:00:00,720 --> 00:00:05,760 In the last 50 or we started talking about an imaginary insurance company remember we had said that 2 00:00:05,760 --> 00:00:12,000 we would have a customer who would fill out some form handoff to our form receiver the form receiver 3 00:00:12,000 --> 00:00:17,640 would make a copy of that form and hand one individual copy of the form to each of our different departments. 4 00:00:17,640 --> 00:00:23,470 And so then our departments would somehow inspect that form and decide how to process the form internally. 5 00:00:23,490 --> 00:00:26,710 Now in this video we're going to continue with this analogy a little bit more. 6 00:00:26,760 --> 00:00:31,920 Remember the idea here is that once you understand this analogy will then be able to apply every step 7 00:00:31,920 --> 00:00:36,330 inside this flow to our different parts of this redux cycle thing over here. 8 00:00:36,450 --> 00:00:39,990 And trust me at the end of the day it's going to make this process a lot more clear. 9 00:00:39,990 --> 00:00:42,480 So let me tell you a little bit more about this analogy here. 10 00:00:42,540 --> 00:00:45,230 We're going to develop it a little bit further. 11 00:00:45,240 --> 00:00:50,520 Now I want to start to think about what would happen when a form or a copy of a form is taken and handed 12 00:00:50,580 --> 00:00:55,910 off to some very specific department like let's say in this case the policies Department. 13 00:00:56,280 --> 00:01:02,560 So here's probably what would happen internally a form would come in that maybe has the intent of signing 14 00:01:02,560 --> 00:01:04,050 up for a new policy. 15 00:01:04,060 --> 00:01:08,770 So remember the customer gave us this thing the former receiver made a copy of it and then handed off 16 00:01:08,770 --> 00:01:10,460 to the policy department. 17 00:01:10,720 --> 00:01:16,870 Well chances are that internally the policies Department has a list of everyone who has a policy. 18 00:01:16,930 --> 00:01:17,670 That's their job. 19 00:01:17,680 --> 00:01:22,810 They're supposed to maintain a list of all customers who hold an active policy. 20 00:01:23,290 --> 00:01:28,600 So we would imagine that the policies department would take in this form see that this customer is trying 21 00:01:28,600 --> 00:01:35,030 to sign up for a new policy and then maybe add them onto this list right here of people who hold a policy. 22 00:01:35,530 --> 00:01:40,180 So they would say All right we've got another person who just signed up for a policy and will say that 23 00:01:40,390 --> 00:01:44,740 Juliet Juliet now holds a policy in addition to Fred Jane. 24 00:01:44,770 --> 00:01:47,410 Alex in Alexandria. 25 00:01:47,410 --> 00:01:49,120 Now this right here definitely makes a lot of sense. 26 00:01:49,120 --> 00:01:55,510 We are saying that the policies Department maintains a list internally of everyone who has a policy 27 00:01:56,220 --> 00:01:58,900 but I'm going to throw a little wrench in this flow right here. 28 00:01:58,900 --> 00:01:59,110 All right. 29 00:01:59,110 --> 00:02:01,920 I'm going to put in a little odd piece. 30 00:02:02,410 --> 00:02:08,650 Let's imagine that we have some management team at our company and for some reason this management team 31 00:02:08,860 --> 00:02:13,720 always comes knocking on the door of the policies department and they always come around and say hey 32 00:02:13,750 --> 00:02:16,100 tell me a list who has a policy right now. 33 00:02:16,360 --> 00:02:21,460 Maybe the management team needs to know who has a policy so that they can collect some metrics about 34 00:02:21,460 --> 00:02:26,220 how many policies are active and how the number of policies are changing over time. 35 00:02:26,290 --> 00:02:31,030 So management eventually starts to get a little bit frustrated with having to go knock on the door or 36 00:02:31,030 --> 00:02:35,170 the policies department all the time because they're tired of having to walk over there or knock on 37 00:02:35,170 --> 00:02:37,040 the door or say hey give me this list. 38 00:02:37,150 --> 00:02:40,490 Get the list and then tape record some metric using it. 39 00:02:40,510 --> 00:02:44,920 So in order to address the fact that the management team doesn't want to have to go knock on the door 40 00:02:44,980 --> 00:02:47,060 or the policies department all the time. 41 00:02:47,170 --> 00:02:53,550 We're going to make a little change to where our list of customers with policies is stored. 42 00:02:53,590 --> 00:02:58,300 We're going to say that rather than the policies Department internally having like a big binder or a 43 00:02:58,300 --> 00:03:03,970 big sheet of paper that lists all these customers they're going to instead store that list of policies 44 00:03:04,000 --> 00:03:10,070 inside of a central repository of company data that is stored outside of their department. 45 00:03:10,840 --> 00:03:16,480 So in this separate repository of data is going to be all of the information about who currently has 46 00:03:16,540 --> 00:03:23,230 a policy and a list of all the claims that have ever been filed and maybe a list of all of our money 47 00:03:23,260 --> 00:03:27,380 or what the current balance of the company is and how much cash we have on hand. 48 00:03:27,820 --> 00:03:34,390 So now the management team can very easily go and get a list of policies and see who has a policy and 49 00:03:34,390 --> 00:03:40,120 record some metrics around that management team can also now very easily look at the claims history 50 00:03:40,150 --> 00:03:45,190 or all the accounting information and the management team can do that with having without having to 51 00:03:45,400 --> 00:03:48,690 go and knock on the door of each of these different departments. 52 00:03:48,700 --> 00:03:54,340 However now we're in a little bit of a bind because at some point in time the policies Department is 53 00:03:54,340 --> 00:03:58,320 going to get some form that says hey I want to sign up for a new policy. 54 00:03:58,540 --> 00:04:03,990 So they are probably going to need to somehow update this list of policies right here. 55 00:04:04,390 --> 00:04:09,760 So we'll say that any time that the form receiver makes a copy as a form and hands it off to the policy 56 00:04:09,760 --> 00:04:10,610 department. 57 00:04:10,780 --> 00:04:17,260 This former senior person is also going to go to the central repository of data peer for the entire 58 00:04:17,260 --> 00:04:18,150 company. 59 00:04:18,220 --> 00:04:24,220 They're going to find the list of policies and they're going to hand it in to the policies Department 60 00:04:24,310 --> 00:04:25,800 along with that form. 61 00:04:25,900 --> 00:04:29,980 And so the former CEO right here is essentially saying hey we just got a new form. 62 00:04:30,040 --> 00:04:31,620 I need you to process this thing. 63 00:04:31,630 --> 00:04:35,210 And by the way here's a list of all of our current policies. 64 00:04:35,230 --> 00:04:37,960 So now the policies Department will look at that form. 65 00:04:38,110 --> 00:04:42,670 They'll update the list of policies and then when they are done doing that update they're going to go 66 00:04:42,760 --> 00:04:46,550 and pass it back to this central repository appear. 67 00:04:46,820 --> 00:04:51,070 So now the idea here is that the management team can very easily see all the data. 68 00:04:51,280 --> 00:04:55,960 And any time that the policies department needs to update that data they're going to get their list 69 00:04:55,960 --> 00:05:01,580 of policies they're going to update the list of policies and then update the central repository list 70 00:05:01,610 --> 00:05:03,910 of policies right here as well. 71 00:05:03,910 --> 00:05:04,180 All right. 72 00:05:04,180 --> 00:05:07,910 So I know that this analogy is getting really intense and very intense. 73 00:05:07,990 --> 00:05:12,850 But I just got one or two more steps to go through and then we're going to be able to apply all this 74 00:05:12,850 --> 00:05:14,890 information back to a redux cycle. 75 00:05:14,890 --> 00:05:19,460 So another quick pause and we're going to develop this analogy just a little bit more in the next video.