Datadog · conference-presentation
Datadog | Investor Day Presentation Deck | 102 slides
102 pages · 4 arc beats · 2 loops
Datadog | Investor Day Presentation Deck | 102 slides
Datadog · 2021-10 arc beats above · slides in the middle · loops below · scroll → 2 LOOPS
15101520253035404550556065707580859095100102
Deck intelligence map
4 coverage by narrative range · generated from this deck JSON
Narrative range 8 total
Metadata
Components
Metrics
Tools
Frameworks
Beats
Loops
Problem Statement 2 slides 100% 2/2 slides 100% 2/2 slides · 6 hits — 0/2 slides
— 0/2 slides
50% 1/2 slides 100% 2/2 slides — 0/2 slides
Solution 2 slides 100% 2/2 slides 100% 2/2 slides · 5 hits — 0/2 slides
— 0/2 slides
50% 1/2 slides 100% 2/2 slides — 0/2 slides
Market Sizing 2 slides 100% 2/2 slides 100% 2/2 slides · 6 hits — 0/2 slides
— 0/2 slides
50% 1/2 slides 100% 2/2 slides — 0/2 slides
Product 2 slides 100% 2/2 slides 100% 2/2 slides · 7 hits — 0/2 slides
— 0/2 slides
100% 2/2 slides 100% 2/2 slides — 0/2 slides
Slide inventory
102 every slide · same image gating as the playbook
08
Uses a 2x2 grid layout to show trends in technology, scale, releases, and team structure.diagnose_problem
Open slide detailBeat · Problem Statement
10
The slide uses a hub-and-spoke visual metaphor to demonstrate platform integration breadth.present_framework
Open slide detailBeat · Solution
12
The slide uses a stepped, layered visual to represent product expansion over time.present_solution
13
The slide uses a vertical stacking approach to show product expansion over time.summarize
16
The diagram uses a hub-and-spoke layout to show the integration of three distinct domains into a central DevSecOps function.frame_situation
Open slide detailBeat · Market Sizing
17
The diagram uses a hub-and-spoke layout to illustrate the relationship between a core product and adjacent market opportunities.present_framework
20
The slide uses a progression of architectural stacks to illustrate the shift in infrastructure management.frame_problem
21
The chart uses a curve to represent the shift from static to dynamic infrastructure.establish_context
22
The slide uses a visual metaphor of 'spaghetti' data to illustrate the pain point of legacy tagging systems.diagnose_problem
23
The visualization uses a honeycomb grid layout to represent host status, likely CPU utilization.present_solution
25
The slide uses a screenshot of a monitoring tool (likely Datadog or similar) to illustrate a feature benefit.present_solution
27
The central hub features the Datadog mascot, with surrounding hexagons representing specific product categories.present_solution
29
The visualization uses color-coded hexagons to represent CPU utilization levels across different availability zones.analyze_data
30
The slide uses a horizontal spectrum to categorize technology stacks by age/modernity.establish_context
Open slide detailBeat · Product
32
The chart illustrates the shift from single-product adoption to multi-product platform adoption over time.analyze_data
33
The central icon is the Datadog logo, surrounded by various infrastructure providers.present_solution
35
The slide is a screenshot of a web page, not a standard presentation slide.establish_context
36
The slide uses a process diagram to illustrate the CI/CD flow followed by a comparison list of benefits vs challenges.frame_situation
37
Uses a timeline-like visual to represent the shift from production-only observability to earlier development stages.present_solution
39
The slide demonstrates how APM tools visualize distributed traces to identify performance bottlenecks.illustrate_case
40
The slide uses a grid of four screenshots to demonstrate the breadth of the APM tool's capabilities.illustrate_case
41
The diagram illustrates a service dependency graph with performance metrics for each node.analyze_data
42
The slide uses a split-screen layout to categorize features by Client Side vs Server Side, with years indicating release dates.present_solution
43
The slide uses a split-view architecture to categorize monitoring tools by environment (Client vs Server) with a central integration point (Log Management).present_solution
44
The chart illustrates the expansion of the APM product suite over time.analyze_data
45
The slide uses a modular layout to map AI detection capabilities to specific product outcomes.present_framework
46
The slide displays a specific incident report for a Kubernetes control plane component.diagnose_problem
47
The slide uses a screenshot of the Datadog UI to illustrate the 'Insights' feature, highlighting its ability to surface anomalies like log error outliers, profipresent_solution
48
The slide displays three distinct root cause analysis examples, including a dependency diagram and an error rate spike chart.diagnose_problem
49
The slide uses a modular layout to map AI detection capabilities (Anomalies, Rare Events, etc.) to specific product functional areas.present_solution
51
The diagram uses a funnel-like structure to represent data ingestion and processing.present_framework
52
The diagram is a simple triangle representing the integration of three observability pillars.present_framework
54
Uses a binary choice framework to highlight the limitations of legacy log management solutions.frame_problem
56
The chart lacks Y-axis labels, emphasizing the trend over specific values.analyze_data
58
The central diagram uses a hexagonal structure to represent the transformation, reduction, and routing of data.present_framework
Open slide detailLoop · Cost Of Inaction
60
The slide uses a hub-and-spoke/network diagram to show how point solutions are siloed within a traditional firewall perimeter.frame_problem
Open slide detailLoop · Cost Of Inaction
61
Uses visual metaphors (clear network vs. blurred/obscured view) to represent the lack of integration.diagnose_problem
Open slide detailLoop · Cost Of Inaction
62
The slide uses a hub-and-spoke style diagram to illustrate unification.present_solution
Open slide detailLoop · Cost Of Inaction
63
Uses a torn-paper visual metaphor to represent the gap between teams.diagnose_problem
Open slide detailLoop · Cost Of Inaction
64
The slide uses icons to represent the merging of siloed Security and DevOps teams.propose_solution
Open slide detailLoop · Cost Of Inaction
66
The slide uses a mapping framework to illustrate product synergy.present_framework
67
The slide uses a simple two-column layout to categorize security modules.present_framework
70
The diagram uses a hub-and-spoke layout with hexagonal nodes.present_framework
Open slide detailLoop · Voice Of Customer
71
The slide uses a 3x2 grid layout to present six distinct value points.summarize
Open slide detailLoop · Voice Of Customer
72
The slide uses a honeycomb/hexagonal grid to organize product categories.present_framework
Open slide detailLoop · Voice Of Customer
73
The slide uses a funnel-like process flow to demonstrate platform integration.present_framework
Open slide detailLoop · Voice Of Customer
74
The slide demonstrates product adoption expansion within a single customer account.illustrate_case
Open slide detailLoop · Voice Of Customer
75
The slide highlights the expansion of product usage (from 1 to 7) alongside a significant increase in ARR.illustrate_case
Open slide detailLoop · Voice Of Customer
76
The slide uses a hexagonal grid layout to present benefits.summarize
Open slide detailLoop · Voice Of Customer
77
The chart shows a steady upward trend in retention over the period.analyze_data
Open slide detailLoop · Voice Of Customer
79
The slide uses a hexagonal icon grid to categorize services, with sub-pricing tables underneath each category.other
81
The slide uses a flow diagram to contrast 'Ingest Everything' with 'Choose: What to retain / How long to retain it'.present_solution
82
The slide uses a 'before-after' style layout to show different personas using the same platform.present_solution
84
The slide uses a stacked area chart to illustrate growth over time.present_solution
85
The chart shows a clear correlation between product adoption and revenue growth.illustrate_case
86
The slide illustrates product adoption and revenue expansion over time.illustrate_case
87
The pyramid structure uses hexagons to represent different tiers of the sales strategy.present_framework
88
The slide uses a branching structure to show how a single 'Solutions Engineering' function evolved into multiple specialized roles over time.plan_implementation
89
The charts illustrate both the absolute growth in customer base and the increasing revenue contribution from customers with >$100k ARR.analyze_data
92
The slide uses a chevron-based timeline to illustrate product expansion over time.present_solution
98
The chart highlights Datadog in purple to distinguish it from the grey bars of competitors.compare_peers
101
Includes a disclosure note regarding a change in MRR definition applied retroactively.analyze_data
102
The table reconciles GAAP operating income to Non-GAAP operating income by adding back share-based compensation, amortization of intangibles, and adjusting for appendix