2024 MongoDB local NYC Product Update

MongoDB
arc beats above · slides in the middle · loops below · scroll → 3 LOOPS
SETUP TENSION ANALYSIS EVIDENCE RESOLUTION APPENDIX
HOVER FOR DETAILS · CLICK A SLIDE FOR FULLSCREEN · STEP 5
No image bound to this slide. Wire up imgproxy to display the rendered slide JPEG.

Deck intelligence map

5
coverage by narrative range · generated from this deck JSON

Slide inventory

87
every slide · same image gating as the playbook
01
Slide 1
front_matter
03
establish_context
04
size_opportunity
Open slide detailBeat · Market Size
05
The slide uses a simple bar diagram to represent different software categories (CRM, ERP, HRIS, etc.) and highlights the binary nature of competition.frame_problem
Open slide detailBeat · Market Size
06
The grid represents an account's total workload landscape, with one specific workload highlighted to emphasize the 'land and expand' or 'workload-by-workload' sframe_problem
07
summarize
08
The slide uses a grid-based visualization to show incremental progress across four stages. Each grid has columns labeled BL1-BL6.other
09
summarize
10
summarize
11
The chart uses a single line to represent ARR growth, with a distinct dot at the Jan '23 inflection point.quantify_impact
12
The chart uses a single line with a prominent data point marker at Jan '23 to signify a change in trajectory.quantify_impact
13
The chart uses a single line to represent ARR growth, with a distinct marker at Jan '21 to signify a strategic shift or milestone.illustrate_case
14
summarize
15
summarize
16
transition
Open slide detailBeat · Problem
17
This is a classic 'polyglot persistence' or 'data architecture' diagram showing how different database types (RDBMS, NoSQL, Search, etc.) interact with applicatpresent_framework
Open slide detailBeat · Problem
18
frame_problem
Open slide detailBeat · ProblemLoop · Cost Of Inaction
19
summarize
Open slide detailBeat · ProblemLoop · Cost Of Inaction
20
summarize
Open slide detailBeat · Solution
21
The slide illustrates a unified data platform architecture (likely MongoDB based on the leaf icon).present_framework
Open slide detailBeat · Solution
22
transition
Open slide detailBeat · Solution
23
frame_problem
Open slide detailBeat · Solution
24
summarize
Open slide detailBeat · Solution
25
summarize
Open slide detailBeat · Solution
26
The slide uses a code block to demonstrate the flexibility of the document model for modern AI-driven data structures.present_solution
27
illustrate_case
28
summarize
29
transition
30
The slide uses a before-and-after architectural comparison to highlight the efficiency of MongoDB Atlas.compare_options
31
summarize
32
illustrate_case
33
summarize
34
transition
35
The slide uses a green box to highlight the core database-related components (Vector Search and Database).frame_problem
36
summarize
37
The slide uses a 2x2 matrix framework to visualize market positioning.compare_peers
38
illustrate_case
39
summarize
40
transition
41
illustrate_case
42
The slide uses a simple linear flow diagram to illustrate the relationship between streaming transport, processing, and databases.present_framework
43
summarize
44
illustrate_case
45
transition
46
transition
47
The slide uses a split-screen diagram to contrast the centralized processing of cloud computing with the localized processing of edge computing.compare_options
48
summarize
49
frame_problem
50
The slide uses a hub-and-spoke style diagram to illustrate data flow between edge devices, an on-premise server, and the cloud.present_solution
51
summarize
52
summarize
53
summarize
55
compare_options
Open slide detailBeat · Competition
56
frame_problem
Open slide detailBeat · Competition
57
transition
Open slide detailBeat · Competition
58
The slide uses a grid layout to illustrate the fragmentation of the relational application ecosystem.establish_context
Open slide detailBeat · Competition
59
transition
Open slide detailBeat · Competition
60
plan_implementation
61
transition
62
The slide uses a chevron process flow to represent a linear migration journey.present_solution
63
illustrate_case
64
transition
65
The table uses checkmarks to indicate AI impact across six distinct modernization activities.quantify_impact
66
summarize
67
state_next_steps
68
summarize
69
summarize
70
summarize
Open slide detailBeat · Why NowLoop · Why Now
71
Minimalist slide focusing on a single core insight.frame_problem
Open slide detailBeat · Why NowLoop · Why Now
72
The slide displays a stack of four different market landscape diagrams from various sources (Madrona, CB Insights, etc.) layered on top of each other.present_framework
Open slide detailBeat · Why NowLoop · Why Now
73
The slide acts as a mood board or news aggregation of AI model releases from early 2024.summarize
Open slide detailBeat · Why NowLoop · Why Now
74
frame_problem
Open slide detailBeat · Why NowLoop · Why Now
75
summarize
Open slide detailBeat · Why NowLoop · Why Now
76
The slide uses a side-by-side comparison format to map customer requirements to MongoDB's value proposition.compare_options
Open slide detailBeat · Why NowLoop · Why Now
77
transition
Open slide detailBeat · Why NowLoop · Why Now
78
transition
Open slide detailLoop · Jobs To Be Done
79
The slide uses a grid of squares to represent business lines (BL1-BL6) within an account, highlighting a specific entry point.establish_context
Open slide detailLoop · Jobs To Be Done
80
The slide uses a grid-based visualization to imply scaling of teams/leads over time.present_solution
Open slide detailLoop · Jobs To Be Done
81
The slide uses a grid-based visualization to show adoption growth.summarize
Open slide detailLoop · Jobs To Be Done
82
summarize
83
illustrate_case
84
transition
85
present_solution
86
The slide uses a layered architecture diagram to show the integration of various AI tools and platforms with MongoDB.present_framework
87
Uses a puzzle-piece diagram to represent the four components of the solution.present_solution