WEBVTT 00:00:00.000 --> 00:00:01.960 You know that feeling of dread when you check 00:00:01.960 --> 00:00:05.360 your inbox? You finally see it, that brutal one 00:00:05.360 --> 00:00:07.519 out of 10 customer satisfaction score. Right. 00:00:07.879 --> 00:00:10.199 But it's two days late. And by the time you've 00:00:10.199 --> 00:00:12.119 read it, that customer has already moved on. 00:00:12.199 --> 00:00:14.199 They're frustrated and they're gone forever. 00:00:14.720 --> 00:00:18.480 That delay, that two day window is just absolutely 00:00:18.480 --> 00:00:21.820 fatal to growth, especially today. We're here 00:00:21.820 --> 00:00:25.100 to talk about the solution. Workflow automation. 00:00:25.120 --> 00:00:29.039 Okay. It turns that fatal manual delay into a 00:00:29.039 --> 00:00:32.240 professional systematic two -second response. 00:00:32.939 --> 00:00:35.079 Welcome back to the Deep Dive. Today, we are 00:00:35.079 --> 00:00:37.579 extracting the blueprint for intelligent business 00:00:37.579 --> 00:00:39.240 workflow automation. And we're not just, you 00:00:39.240 --> 00:00:41.140 know, summarizing a guide. We are taking the 00:00:41.140 --> 00:00:43.979 actual battle experience from a builder, someone 00:00:43.979 --> 00:00:46.060 who's lived this and deployed these systems under 00:00:46.060 --> 00:00:47.960 pressure. And our mission for you, the listener, 00:00:48.060 --> 00:00:52.579 is simple, but it's also deeply ambitious. We're 00:00:52.579 --> 00:00:54.500 building a system that doesn't just save customer 00:00:54.500 --> 00:00:56.520 feedback in some spreadsheet. It has to do more. 00:00:56.740 --> 00:00:59.500 It must think. It needs to tell you precisely 00:00:59.500 --> 00:01:02.520 and immediately when a customer is angry and 00:01:02.520 --> 00:01:05.400 requires a human to step in. We'll cover the 00:01:05.400 --> 00:01:08.060 exact tools, the visual building blocks, and 00:01:08.060 --> 00:01:10.540 the vital daily checks that make this whole system 00:01:10.540 --> 00:01:13.019 truly crash -proof. OK, let's unpack this blueprint. 00:01:13.280 --> 00:01:15.340 When we talk about automation, I think a lot 00:01:15.340 --> 00:01:18.200 of people still picture those expensive, complex 00:01:18.200 --> 00:01:21.879 robots or massive enterprise software. But what 00:01:21.879 --> 00:01:24.780 is workflow automation in its simplest, most 00:01:24.780 --> 00:01:27.310 useful form? Honestly, it's just setting up a 00:01:27.310 --> 00:01:30.549 dependable chain of actions. If action A happens 00:01:30.549 --> 00:01:33.989 in app one, let's say a form is submitted, the 00:01:33.989 --> 00:01:36.750 system automatically does action B in app two. 00:01:37.090 --> 00:01:39.230 Like updating a database. Exactly, like updating 00:01:39.230 --> 00:01:41.430 a database. That is the core of it, and it's 00:01:41.430 --> 00:01:43.370 surprisingly accessible. So if the technology 00:01:43.370 --> 00:01:46.250 is that straightforward, why are manual processes 00:01:46.250 --> 00:01:49.469 such a dangerous blocker to growth? Well, manual 00:01:49.469 --> 00:01:52.959 work introduces two huge failure points. human 00:01:52.959 --> 00:01:55.799 mistakes, and critical speed delays. Automation 00:01:55.799 --> 00:01:57.980 just eliminates that human error. Think about 00:01:57.980 --> 00:02:00.739 just typing a customer's phone number or email 00:02:00.739 --> 00:02:05.079 address. A simple typo, and you've lost goodwill. 00:02:05.299 --> 00:02:07.519 You've lost any follow -up potential, and your 00:02:07.519 --> 00:02:10.819 data is wrong. Instantly. And speed is everything 00:02:10.819 --> 00:02:13.419 now. It's completely non -negotiable. Non -negotiable. 00:02:13.520 --> 00:02:16.620 If you get a critical 1 out of 10 score, the 00:02:16.620 --> 00:02:19.159 system has to identify that severity and flag 00:02:19.159 --> 00:02:21.939 it in two seconds. That prevents customer churn 00:02:21.939 --> 00:02:25.419 before it can even really start. And maybe more 00:02:25.419 --> 00:02:28.879 importantly, it frees up your brain. Stop doing 00:02:28.879 --> 00:02:31.759 that boring, repetitive copy paste work. Use 00:02:31.759 --> 00:02:33.960 that time for strategic thinking, new ideas, 00:02:34.419 --> 00:02:36.939 better service. actual growth. So the biggest 00:02:36.939 --> 00:02:39.219 blocker that manual work creates isn't just the 00:02:39.219 --> 00:02:42.199 volume of work, it's the mistakes and those fatal 00:02:42.199 --> 00:02:44.659 speed delays. And this is where it gets really 00:02:44.659 --> 00:02:46.199 interesting for the person listening right now 00:02:46.199 --> 00:02:47.979 who doesn't code. I mean, previously, if you 00:02:47.979 --> 00:02:49.740 wanted your software to talk to other software, 00:02:49.879 --> 00:02:51.780 you had, what, two high -cost choices? That's 00:02:51.780 --> 00:02:53.759 right. You either hired expensive programmers 00:02:53.759 --> 00:02:56.280 or you used high -cost tools like Zapier, especially 00:02:56.280 --> 00:02:58.960 if you had a lot of data volume. And tools like 00:02:58.960 --> 00:03:01.439 NAN were basically born to break that wall down. 00:03:01.599 --> 00:03:04.280 They're the engine of this whole no -code revolution. 00:03:04.419 --> 00:03:06.699 They democratize the power. So you don't need 00:03:06.699 --> 00:03:09.439 to learn Python or JavaScript. No. All you need 00:03:09.439 --> 00:03:12.199 is just basic logical thinking. If the customer 00:03:12.199 --> 00:03:14.340 fills out this form, then send that message. 00:03:14.960 --> 00:03:17.280 This puts the power of a software engineer into 00:03:17.280 --> 00:03:19.599 the hands of a normal business person. I really 00:03:19.599 --> 00:03:23.039 like the analogy of building the system with 00:03:23.039 --> 00:03:26.259 Lego blocks of data. It makes a complex idea 00:03:26.259 --> 00:03:28.319 feel really tangible. That's exactly how it works 00:03:28.319 --> 00:03:29.939 visually. These functional blocks are called 00:03:29.939 --> 00:03:33.259 nodes. Each node is a very specific action. So 00:03:33.259 --> 00:03:35.000 you might have a type form node to get data, 00:03:35.379 --> 00:03:37.800 an Airtable node to write the data, and then 00:03:37.800 --> 00:03:40.080 a Trello node to send an alert. So your job is 00:03:40.080 --> 00:03:42.419 literally just drawing the lines between these 00:03:42.419 --> 00:03:45.080 action blocks to create a flow of data. And, 00:03:45.159 --> 00:03:46.759 you know, the satisfaction isn't just seeing 00:03:46.759 --> 00:03:49.400 that map, it's knowing the map is actively working 00:03:49.400 --> 00:03:53.419 24 -7 to prevent customer churn. That usefulness, 00:03:53.479 --> 00:03:56.500 that's the real moment of wonder. And that visual 00:03:56.500 --> 00:03:58.770 map... It provides something critical. It's an 00:03:58.770 --> 00:04:01.770 immediate audit trail. If something breaks, you 00:04:01.770 --> 00:04:03.770 don't go hunting through text files. You just 00:04:03.770 --> 00:04:05.909 look at the flow and you see the red block instantly. 00:04:06.270 --> 00:04:08.090 So that simplicity, that visual map, it gives 00:04:08.090 --> 00:04:10.449 you an audit trail and you don't get lost in 00:04:10.449 --> 00:04:12.669 complex text. Now let's get into the tech stack. 00:04:13.449 --> 00:04:16.490 A professional self -monitoring system like this 00:04:16.490 --> 00:04:20.490 really needs four essential players, your core 00:04:20.490 --> 00:04:23.470 automation team. Okay, number one, type form. 00:04:23.569 --> 00:04:25.810 This is your front end. It collects customer 00:04:25.810 --> 00:04:28.389 information in a beautiful, easy way, making 00:04:28.389 --> 00:04:30.790 sure people actually finish the form. Number 00:04:30.790 --> 00:04:33.449 two is Airtable. This is your smart spreadsheet, 00:04:33.589 --> 00:04:36.170 and it has to be the single source of truth. 00:04:36.269 --> 00:04:38.089 And we should really emphasize why it's better 00:04:38.089 --> 00:04:40.910 than something like Google Sheets. Airtable forces 00:04:40.910 --> 00:04:43.449 you to define data types. It's a relational database. 00:04:43.949 --> 00:04:47.189 So this prevents ambiguous data, like putting 00:04:47.189 --> 00:04:49.370 text into a number field, which is critical for 00:04:49.370 --> 00:04:51.329 a machine to read it correctly. Number three, 00:04:51.529 --> 00:04:54.170 then. is Trello, and this is the action center. 00:04:54.589 --> 00:04:57.470 So when that bad critical data arrives, a card 00:04:57.470 --> 00:05:00.050 just pops up here for the team to deal with immediately. 00:05:00.610 --> 00:05:02.810 It moves data from just being stored to being 00:05:02.810 --> 00:05:05.709 an active assignment. And finally, number four, 00:05:06.069 --> 00:05:09.050 NA8N. This is the brain. It's the connective 00:05:09.050 --> 00:05:11.290 tissue. This is where you actually build the 00:05:11.290 --> 00:05:13.529 automation that connects typeform, Airtable, 00:05:13.629 --> 00:05:16.709 and Trello together. Now, a really crucial decision 00:05:16.709 --> 00:05:19.569 for stability is cloud versus self -hosted. So 00:05:19.569 --> 00:05:21.910 if I'm a beginner, why shouldn't I just download 00:05:21.910 --> 00:05:24.250 NAN onto my own computer? I mean, it's cheaper, 00:05:24.449 --> 00:05:26.689 right? It seems cheaper. And while self -hosting 00:05:26.689 --> 00:05:28.970 gives you control, we strongly recommend the 00:05:28.970 --> 00:05:31.829 cloud version for beginners. The reason is, if 00:05:31.829 --> 00:05:34.509 you install NAN on your computer, the automation 00:05:34.509 --> 00:05:36.709 only runs when your computer is on and awake. 00:05:36.769 --> 00:05:39.600 So if your laptop goes to sleep at 2 a .m., you 00:05:39.600 --> 00:05:42.060 miss customer submissions. Meaning you lose the 00:05:42.060 --> 00:05:44.180 data and you could lose the customer. Exactly. 00:05:44.339 --> 00:05:46.079 The cloud is like the light that never goes out. 00:05:46.160 --> 00:05:49.800 It runs 247, 365, and it also handles all the 00:05:49.800 --> 00:05:52.339 heavy technical stuff. Security updates, backups, 00:05:52.779 --> 00:05:55.160 scaling, it does it for you so you can focus 00:05:55.160 --> 00:05:57.060 on your workflow, not on maintaining servers. 00:05:57.370 --> 00:05:59.569 And when you first look at the NAN interface, 00:05:59.769 --> 00:06:02.829 the key areas are nodes for building, workflows 00:06:02.829 --> 00:06:05.889 for saving your work, and then that vital executions 00:06:05.889 --> 00:06:08.269 tab. That tab is your professional dashboard. 00:06:08.670 --> 00:06:11.550 It shows you the history and flags any errors. 00:06:12.129 --> 00:06:14.509 Airtable's reliance on structured field types, 00:06:14.850 --> 00:06:17.689 which stops that ambiguous data. That's the key 00:06:17.689 --> 00:06:19.689 difference from a normal spreadsheet. Now we 00:06:19.689 --> 00:06:21.750 get into the actual building blocks, and this 00:06:21.750 --> 00:06:24.910 starts with a golden non -negotiable rule. Garbage 00:06:24.910 --> 00:06:27.529 in, garbage out. That's right. If your input 00:06:27.529 --> 00:06:29.709 forms are messy, your automation is going to 00:06:29.709 --> 00:06:32.290 get confused, it'll misclassify data, or it'll 00:06:32.290 --> 00:06:34.269 just stop working entirely. It will. And that's 00:06:34.269 --> 00:06:36.649 why we need three core pillars for clean input 00:06:36.649 --> 00:06:39.329 right in type form. OK, pillar one, the quantitative 00:06:39.329 --> 00:06:42.069 key. This has to be a 1 to 10 rating or an opinion 00:06:42.069 --> 00:06:44.689 scale. We need numbers because they are the easiest 00:06:44.689 --> 00:06:47.329 thing for the automation brain for any end to 00:06:47.329 --> 00:06:50.329 understand and compare. Pillar two, qualitative 00:06:50.329 --> 00:06:52.689 insight. You have to include a long text question 00:06:52.689 --> 00:06:55.139 for the why. We use the automation to process 00:06:55.139 --> 00:06:57.720 the number, but we need the human story to understand 00:06:57.720 --> 00:07:00.480 the context behind that number. And pillar three, 00:07:01.100 --> 00:07:04.000 the identity marker. You must always get the 00:07:04.000 --> 00:07:06.720 email. Without an email, your sister has no idea 00:07:06.720 --> 00:07:09.339 who said what, and you can't close the loop to 00:07:09.339 --> 00:07:12.199 fix their problem. And you can even use Typeform's 00:07:12.199 --> 00:07:14.699 built -in logic jumps to make the form think 00:07:14.699 --> 00:07:17.199 ahead of time. So if a user gives a 1 out of 00:07:17.199 --> 00:07:19.740 10 score, the form could immediately jump to 00:07:19.740 --> 00:07:21.740 an extra question asking for their phone number. 00:07:21.819 --> 00:07:23.959 Ah, so you're getting more context before it 00:07:23.959 --> 00:07:26.660 even hits the automation. Exactly. More detail 00:07:26.660 --> 00:07:29.459 before the data even hits NANM. You know, speaking 00:07:29.459 --> 00:07:32.160 of fatal missteps, let's talk about the destination 00:07:32.160 --> 00:07:34.519 database, Airtable. It can also be a failure 00:07:34.519 --> 00:07:36.399 point if it's set up wrong. You know, I still 00:07:36.399 --> 00:07:38.360 wrestle with prompt drift myself when I'm building 00:07:38.360 --> 00:07:40.699 complex systems. But a simpler mistake I often 00:07:40.699 --> 00:07:42.759 made early on was just forgetting to hit the 00:07:42.759 --> 00:07:44.959 publish button in type form after making a change. 00:07:45.079 --> 00:07:48.019 A tiny, fatal step. Oh, that happens to everyone. 00:07:48.120 --> 00:07:50.660 And once that clean data is flowing, your Airtable 00:07:50.660 --> 00:07:52.680 structure has to be built like a database, not 00:07:52.680 --> 00:07:55.779 just a prettier Excel. Field types matter so 00:07:55.779 --> 00:07:58.220 much for automation. You need the specific email 00:07:58.220 --> 00:08:00.600 field type. And crucially, you have to set the 00:08:00.600 --> 00:08:04.000 score column to number and integer. Why is forcing 00:08:04.000 --> 00:08:07.019 that integer field type so critical? Because 00:08:07.019 --> 00:08:09.860 if the score is set to text, the automation just 00:08:09.860 --> 00:08:12.500 sees a string of characters. It can't understand 00:08:12.500 --> 00:08:14.540 that the number 5 is smaller than the number 00:08:14.540 --> 00:08:16.959 7. So it can't compare them. It can't reliably 00:08:16.959 --> 00:08:19.910 compare values or do any math. to execute the 00:08:19.910 --> 00:08:22.649 intelligent logic. So making the score an integer 00:08:22.649 --> 00:08:25.649 field type allows the automation brain, N, A, 00:08:25.670 --> 00:08:29.310 N, to reliably compare values and do math. And 00:08:29.310 --> 00:08:31.250 that's the whole basis for making a decision. 00:08:31.750 --> 00:08:34.049 Now we focus on connecting and thinking. So the 00:08:34.049 --> 00:08:36.149 first step is setting the trigger. We add the 00:08:36.149 --> 00:08:38.409 typeform trigger node in N, A, N. This is the 00:08:38.409 --> 00:08:40.710 system's ear. And it's just listening for that 00:08:40.710 --> 00:08:43.330 submit click to wake N, N up. And you always 00:08:43.330 --> 00:08:45.389 want to test that connection immediately. OK. 00:08:45.549 --> 00:08:48.250 And next, we map the data into Airtable. When 00:08:48.250 --> 00:08:50.529 you add the Airtable node, mapping is how you 00:08:50.529 --> 00:08:52.830 connect the incoming Typeform fields to the right 00:08:52.830 --> 00:08:55.710 Airtable columns. And here's a pro -secret that 00:08:55.710 --> 00:08:58.570 moves you from like a hobbyist to a professional. 00:08:59.590 --> 00:09:01.730 Use expressions instead of just typing. Okay, 00:09:01.730 --> 00:09:03.590 what does that mean? You click the little gear 00:09:03.590 --> 00:09:06.669 icon next to the field. This dynamically references 00:09:06.669 --> 00:09:10.090 the exact data stream coming from Typeform. It 00:09:10.090 --> 00:09:13.129 prevents errors if you, say, later rename a column 00:09:13.129 --> 00:09:16.029 in Airtable. Instead of typing customer email, 00:09:16.250 --> 00:09:18.350 You select the variable for that field. It makes 00:09:18.350 --> 00:09:21.370 the mapping robust. Then comes the intelligence, 00:09:22.049 --> 00:09:25.070 the IF node. This node is what fundamentally 00:09:25.070 --> 00:09:27.990 transforms a passive copy machine into a system 00:09:27.990 --> 00:09:30.409 that actually thinks. Yeah, we teach a system 00:09:30.409 --> 00:09:32.990 to make a dynamic decision. We set the logic. 00:09:33.429 --> 00:09:35.389 And we can make it complex, not just its score 00:09:35.389 --> 00:09:37.289 is smaller than seven. We could group conditions 00:09:37.289 --> 00:09:41.110 like F core 7 and D, AI sentiment, angry. And 00:09:41.110 --> 00:09:43.330 that creates two different paths immediately. 00:09:43.490 --> 00:09:46.090 Two distinct paths. The true branch, the critical 00:09:46.090 --> 00:09:48.330 words go straight to Trello. And the false branch, 00:09:48.629 --> 00:09:50.590 so score 7 to 10, the happy customers, they're 00:09:50.590 --> 00:09:53.049 just saved in Airtable. Correct. For the happy 00:09:53.049 --> 00:09:55.789 customers, the workflow just stops cleanly. We 00:09:55.789 --> 00:09:57.990 use a dedicated no operation node at the end 00:09:57.990 --> 00:10:00.070 of that false branch. Now, it isn't strictly 00:10:00.070 --> 00:10:02.210 necessary for it to function, but it's a pro 00:10:02.210 --> 00:10:04.409 move for clean debugging. It shows you exactly 00:10:04.409 --> 00:10:06.600 where the workflow completed successfully. And 00:10:06.600 --> 00:10:09.220 this is where we can really maximize the intelligent 00:10:09.220 --> 00:10:12.620 part. We could add an AI value using the OpenAI 00:10:12.620 --> 00:10:15.220 node right after the typeform trigger, but why 00:10:15.220 --> 00:10:17.840 add AI if we already have the 1 to 10 score? 00:10:17.960 --> 00:10:19.960 Because a 9 out of 10 score could still have 00:10:19.960 --> 00:10:23.059 a really mean comment, right? Or a 6 out of 10 00:10:23.059 --> 00:10:25.879 could have a passive sarcastic response that 00:10:25.879 --> 00:10:28.879 a simple number check would miss. We use a focused 00:10:28.879 --> 00:10:31.259 LLM prompt to catch that nuance. Can you give 00:10:31.259 --> 00:10:33.700 us a real example of that prompt? Sure, something 00:10:33.700 --> 00:10:36.600 simple like, you are a customer expert. Read 00:10:36.600 --> 00:10:38.639 this customer feedback. Tell me if the overall 00:10:38.639 --> 00:10:42.519 tone is happy, neutral, or angry. Only answer 00:10:42.519 --> 00:10:45.480 with one single word. Ah, I see. And this is 00:10:45.480 --> 00:10:48.679 critical because it gives the IF node the brain 00:10:48.679 --> 00:10:51.950 structure data. happy or angry, that a human 00:10:51.950 --> 00:10:55.090 rushing through might miss. The IF node fundamentally 00:10:55.090 --> 00:10:57.649 transforms a passive system into an intelligent 00:10:57.649 --> 00:11:00.970 one by shifting from just copying data to dynamic 00:11:00.970 --> 00:11:03.690 decision -making based on these complex thresholds. 00:11:03.769 --> 00:11:07.029 Exactly. And now we address the final most crucial 00:11:07.029 --> 00:11:10.289 element, monitoring and stability. Right. Building 00:11:10.289 --> 00:11:12.210 automation is like planting a tree. You can't 00:11:12.210 --> 00:11:14.450 just plant it and walk away. It needs care. Things 00:11:14.450 --> 00:11:18.059 break. It's inevitable. Passwords expire. Typeform 00:11:18.059 --> 00:11:20.899 updates its security, Airtable renames a field. 00:11:21.720 --> 00:11:24.460 A daily routine five -minute check prevents you 00:11:24.460 --> 00:11:27.120 from losing 50 customer feedbacks without you 00:11:27.120 --> 00:11:30.220 even knowing it happened. That routine is the 00:11:30.220 --> 00:11:32.659 difference between a reliable system and an abandoned 00:11:32.659 --> 00:11:34.600 project. And that's where the executions tab 00:11:34.600 --> 00:11:37.360 saves you. The green circle is your best friend 00:11:37.360 --> 00:11:42.340 perfect data flow, but the red X It's not a reason 00:11:42.340 --> 00:11:45.299 to panic. No, not at all. It's N8n showing you 00:11:45.299 --> 00:11:48.059 exactly where the pipe is leaking with pinpoint 00:11:48.059 --> 00:11:50.659 precision. Experts build systems that handle 00:11:50.659 --> 00:11:53.740 failure gracefully. The red X shows you the exact 00:11:53.740 --> 00:11:57.320 failed node. Common errors are like... 401 unauthorized, 00:11:57.679 --> 00:11:59.399 which just means you need to reconnect your password 00:11:59.399 --> 00:12:01.759 in that one node. Or maybe a field not found 00:12:01.759 --> 00:12:04.220 error because a column in error table was renamed. 00:12:04.519 --> 00:12:06.139 Right. Or sometimes you might even get a data 00:12:06.139 --> 00:12:08.399 format error if a customer, you know, includes 00:12:08.399 --> 00:12:10.480 weird characters or tries to put text where a 00:12:10.480 --> 00:12:12.779 number should be. But clicking that failed execution 00:12:12.779 --> 00:12:14.980 shows you the exact red node and the cause. So 00:12:14.980 --> 00:12:17.879 this daily five minute routine ensures the system 00:12:17.879 --> 00:12:21.340 never stays broken for long. That regular monitoring 00:12:21.340 --> 00:12:23.840 is what transforms this from a weekend hobby 00:12:23.840 --> 00:12:26.500 into a professional -grade machine that can scale. 00:12:27.299 --> 00:12:29.720 We have moved from the stress of manual burnout 00:12:29.720 --> 00:12:32.759 to building a professional self -monitoring thinking 00:12:32.759 --> 00:12:35.299 machine that works reliably while you sleep. 00:12:36.139 --> 00:12:38.220 The key ingredients are that structured input, 00:12:38.899 --> 00:12:41.620 visual logic with the IF node, and continuous 00:12:41.620 --> 00:12:44.409 daily monitoring. So don't just, you know, read 00:12:44.409 --> 00:12:46.629 about this deep dive. If this is relevant to 00:12:46.629 --> 00:12:48.809 you or your business, open your laptop today. 00:12:49.169 --> 00:12:51.610 Sign up for a free trial of Anyton and just start 00:12:51.610 --> 00:12:53.710 drawing your first lines between those nodes. 00:12:54.330 --> 00:12:56.990 The feeling when your system runs its first complex 00:12:56.990 --> 00:12:59.659 logic without you touching it? It's incredibly 00:12:59.659 --> 00:13:02.379 satisfying. And the real test of an expert professional 00:13:02.379 --> 00:13:04.899 system isn't when the data is perfect and flows 00:13:04.899 --> 00:13:07.480 smoothly. It's when you build in the safety nets 00:13:07.480 --> 00:13:09.980 for the truly unexpected, like when a customer 00:13:09.980 --> 00:13:12.919 types a weird emoji into a text field or a password 00:13:12.919 --> 00:13:15.860 silently expires. Knowing how your system will 00:13:15.860 --> 00:13:17.940 handle that ambiguity, that is the difference 00:13:17.940 --> 00:13:20.419 between hoping it works and knowing it works. 00:13:20.620 --> 00:13:22.019 We'll see you next time on The Deep Dive.