1 00:00:00,000 --> 00:00:10,800 What if you could compare two long documents in seconds, and instantly see what changed, 2 00:00:10,800 --> 00:00:14,159 what improved, and what slipped behind? 3 00:00:14,159 --> 00:00:20,000 In this session, we'll drop in a proposal and a progress report, and watch how Cloud 4 00:00:20,000 --> 00:00:24,079 highlights the differences with just a few prompts. 5 00:00:24,079 --> 00:00:27,579 Let's begin. 6 00:00:27,579 --> 00:00:33,819 When we upload documents into Cloud, it reads them as structured information, not just plain 7 00:00:33,819 --> 00:00:35,459 text. 8 00:00:35,459 --> 00:00:44,860 This means it understands sections like Objectives, Risks, Timelines, Milestones, and Impact Estimates. 9 00:00:44,860 --> 00:00:50,639 By loading both PDFs, Cloud can look at them side-by-side and begin forming connections 10 00:00:50,639 --> 00:00:55,020 between planned expectations and actual progress. 11 00:00:55,020 --> 00:01:05,739 Cloud confirms that both documents are processed and ready for analysis. 12 00:01:05,739 --> 00:01:10,500 At the high level, we want Cloud to summarize the biggest differences. 13 00:01:10,500 --> 00:01:16,819 This includes how the project's goals align with its current progress, whether the expected 14 00:01:16,819 --> 00:01:21,860 impact is being achieved, and whether the timeline is shifting. 15 00:01:21,860 --> 00:01:29,019 Cloud also picks out details that humans might overlook, like changes in risk severity 16 00:01:29,019 --> 00:01:33,860 or unexpected dependencies emerging during development. 17 00:01:33,860 --> 00:01:39,940 This gives us a quick snapshot of whether the project is generally on track or starting 18 00:01:39,940 --> 00:01:42,660 to fall behind. 19 00:01:42,660 --> 00:01:49,180 Cloud returns a summarized comparison showing key shifts, such as reduced impact, delayed 20 00:01:49,180 --> 00:01:59,660 timelines, and new risks, helping us quickly understand overall project alignment. 21 00:01:59,660 --> 00:02:05,139 Now let's move from the high-level view into deeper category-specific analysis. 22 00:02:05,139 --> 00:02:10,660 Here Cloud compares planned milestones with completed ones. 23 00:02:10,660 --> 00:02:16,339 For example, the proposal describes core features and a structured timeline, while the report 24 00:02:16,339 --> 00:02:22,100 tells us which modules are actually finished and which ones are delayed. 25 00:02:22,100 --> 00:02:28,580 Cloud also compares the risks listed in the proposal with the risks emerging in the report. 26 00:02:28,580 --> 00:02:34,699 This is especially valuable because it reveals gaps between early assumptions and real-world 27 00:02:34,699 --> 00:02:39,179 challenges, like integration delays or scaling issues. 28 00:02:39,179 --> 00:02:42,779 We also get a clear picture of the project's impact. 29 00:02:42,779 --> 00:02:48,940 The proposal estimated up to a 40% reduction in workload, whereas the report shows a smaller 30 00:02:48,940 --> 00:02:50,820 improvement so far. 31 00:02:50,820 --> 00:02:58,419 Finally, Cloud highlights timeline changes, helping us understand whether delays are isolated 32 00:02:58,419 --> 00:03:04,300 or part of a broader pattern. 33 00:03:04,300 --> 00:03:11,979 After analyzing the details, Cloud can distill everything into a clear, executive summary. 34 00:03:11,979 --> 00:03:19,259 This is extremely useful for project managers or stakeholders who need a concise overview 35 00:03:19,259 --> 00:03:22,460 without reading both documents end-to-end. 36 00:03:22,460 --> 00:03:28,460 Cloud highlights what has changed, what still aligns with the proposal, what new risks have 37 00:03:28,460 --> 00:03:34,300 appeared, and what next steps should be prioritized to keep the project moving. 38 00:03:34,300 --> 00:03:40,500 This allows decision makers to quickly understand the project's status and respond with informed 39 00:03:40,500 --> 00:03:43,300 actions. 40 00:03:43,300 --> 00:03:48,179 To make the information easier to share or present, we can also ask Cloud to format the 41 00:03:48,179 --> 00:03:50,580 comparison as a table. 42 00:03:50,580 --> 00:03:55,779 Tables are especially powerful for spotting misalignment because you can directly compare 43 00:03:55,779 --> 00:04:00,619 objectives, timelines, risks, and milestones side-by-side. 44 00:04:00,619 --> 00:04:08,619 This structured view helps teams quickly identify which areas need clarification, escalation, 45 00:04:08,619 --> 00:04:10,979 or additional resources. 46 00:04:10,979 --> 00:04:17,820 It also creates a simple document that can be shared across teams for alignment. 47 00:04:17,820 --> 00:04:23,720 And finally, we ask Cloud to generate insights that go beyond what's written. 48 00:04:23,720 --> 00:04:27,700 This is where Cloud's reasoning becomes especially helpful. 49 00:04:27,700 --> 00:04:36,100 It can detect patterns, infer causes of delays, highlight dependencies between challenges, 50 00:04:36,100 --> 00:04:41,980 and even identify whether the project might require reprioritization. 51 00:04:41,980 --> 00:04:49,459 These inferred insights often reveal issues that are not explicitly stated, but are implied 52 00:04:49,459 --> 00:04:52,859 through differences in the two documents. 53 00:04:52,859 --> 00:04:58,660 This level of analysis would typically take a human hours of review, but Cloud delivers 54 00:04:58,660 --> 00:05:00,500 it in seconds. 55 00:05:00,500 --> 00:05:08,179 With just a few prompts, Cloud helps us compare two complex documents, analyze progress, identify 56 00:05:08,179 --> 00:05:11,739 gaps, and extract actionable insights. 57 00:05:11,739 --> 00:05:17,619 This workflow dramatically reduces review time and gives teams a clearer picture of 58 00:05:17,619 --> 00:05:19,059 project health. 59 00:05:19,059 --> 00:05:20,059 Thanks for tuning in. 60 00:05:20,059 --> 00:05:29,739 I'll see you in the next video.