@openpresentation/opf 0.10.1 → 0.11.0
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/dist/{catalogs-DoVmvDr7.d.ts → catalogs-atkOF4Vy.d.ts} +2 -2
- package/dist/catalogs.d.ts +2 -2
- package/dist/catalogs.js +1 -1
- package/dist/{chunk-TU7I3KSB.js → chunk-6FU2KICU.js} +306 -306
- package/dist/{chunk-ZIL7MGZU.js → chunk-CHKJ4QHQ.js} +223 -73
- package/dist/{chunk-EWJNRHXA.js → chunk-EQHZ3ZO4.js} +3 -3
- package/dist/{chunk-PQJRDNA6.js → chunk-FTWNWFIV.js} +72 -1
- package/dist/{chunk-FHGJX5QK.js → chunk-FWA5XB45.js} +33 -12
- package/dist/{chunk-D3GQIREP.js → chunk-GN52EE3P.js} +133 -12
- package/dist/composition-Tv9Wm3Oh.d.ts +691 -0
- package/dist/composition.d.ts +1 -676
- package/dist/composition.js +1 -1
- package/dist/docs.js +38 -8
- package/dist/examples.d.ts +1 -1
- package/dist/index.d.ts +65 -4
- package/dist/index.js +204 -6
- package/dist/lint.d.ts +3 -3
- package/dist/lint.js +5 -5
- package/dist/pagination.d.ts +2 -2
- package/dist/pagination.js +5 -5
- package/dist/{presentation-BMTdX6O1.d.ts → presentation-Ct42Mitb.d.ts} +51 -8
- package/dist/repo-readme.js +1 -1
- package/dist/{schemas-BYe5y8-i.d.ts → schemas-CiVmUT2p.d.ts} +6 -0
- package/dist/schemas.d.ts +1 -1
- package/dist/schemas.js +1 -1
- package/dist/spec/catalogs/narratives/board-meeting.json +21 -21
- package/dist/spec/catalogs/narratives/business-narrative.json +8 -8
- package/dist/spec/catalogs/narratives/business-review.json +12 -12
- package/dist/spec/catalogs/narratives/capacity-planning.json +8 -8
- package/dist/spec/catalogs/narratives/challenge-resolution.json +7 -7
- package/dist/spec/catalogs/narratives/classic-story.json +7 -7
- package/dist/spec/catalogs/narratives/company-intro.json +9 -9
- package/dist/spec/catalogs/narratives/conference-talk.json +1 -1
- package/dist/spec/catalogs/narratives/early-startup-pitch.json +12 -12
- package/dist/spec/catalogs/narratives/educate.json +9 -9
- package/dist/spec/catalogs/narratives/employee-review.json +8 -8
- package/dist/spec/catalogs/narratives/failure-analysis.json +10 -10
- package/dist/spec/catalogs/narratives/focus.json +12 -12
- package/dist/spec/catalogs/narratives/golden-circle.json +1 -1
- package/dist/spec/catalogs/narratives/innovation.json +9 -9
- package/dist/spec/catalogs/narratives/justice.json +11 -11
- package/dist/spec/catalogs/narratives/marketing-strategy.json +11 -11
- package/dist/spec/catalogs/narratives/performance-improvement-plan.json +8 -8
- package/dist/spec/catalogs/narratives/performance-review.json +11 -11
- package/dist/spec/catalogs/narratives/persuade.json +7 -7
- package/dist/spec/catalogs/narratives/persuasive-sales.json +8 -8
- package/dist/spec/catalogs/narratives/pitch-deck.json +3 -3
- package/dist/spec/catalogs/narratives/problem-solution.json +2 -2
- package/dist/spec/catalogs/narratives/product-launch.json +10 -10
- package/dist/spec/catalogs/narratives/project-proposal.json +10 -10
- package/dist/spec/catalogs/narratives/qbr.json +3 -3
- package/dist/spec/catalogs/narratives/rags-to-riches.json +7 -7
- package/dist/spec/catalogs/narratives/reveal.json +8 -8
- package/dist/spec/catalogs/narratives/scqa.json +1 -1
- package/dist/spec/catalogs/narratives/status-update.json +6 -6
- package/dist/spec/catalogs/narratives/strategic-advisory.json +7 -7
- package/dist/spec/catalogs/narratives/strategic-narrative.json +1 -1
- package/dist/spec/catalogs/narratives/survey-analysis.json +10 -10
- package/dist/spec/catalogs/narratives/survival-story.json +10 -10
- package/dist/spec/catalogs/narratives/transformation-arc.json +1 -1
- package/dist/spec/catalogs/narratives/trend-analysis.json +7 -7
- package/dist/spec/catalogs/narratives/underdog-victory.json +8 -8
- package/dist/spec/catalogs/narratives/venture-pitch.json +12 -12
- package/dist/spec/catalogs/narratives/weekly-progress.json +10 -10
- package/dist/spec/openapi.yaml +5 -0
- package/dist/spec/schemas/opf.schema.json +83 -12
- package/dist/types.d.ts +3 -3
- package/dist/validator.d.ts +7 -4
- package/dist/validator.js +4 -4
- package/package.json +1 -1
|
@@ -23,7 +23,7 @@
|
|
|
23
23
|
"id": "logo",
|
|
24
24
|
"name": "Logo",
|
|
25
25
|
"description": "Cover slide with the company name, logo, and one-line positioning. Simple, branded, confident.",
|
|
26
|
-
"layoutHint": "title
|
|
26
|
+
"layoutHint": "title",
|
|
27
27
|
"instructions": "Establish presence",
|
|
28
28
|
"slideType": "text"
|
|
29
29
|
},
|
|
@@ -33,7 +33,7 @@
|
|
|
33
33
|
"description": "Open by naming a large, undeniable shift in the world. Tech, regulatory, behavioral. The shift is the reason this company exists — investors should feel its weight before they hear about the product.",
|
|
34
34
|
"instructions": "Highlight market transformation",
|
|
35
35
|
"slideType": "text",
|
|
36
|
-
"layoutHint": "text-1x
|
|
36
|
+
"layoutHint": "text-1x"
|
|
37
37
|
},
|
|
38
38
|
{
|
|
39
39
|
"id": "past-struggle",
|
|
@@ -41,7 +41,7 @@
|
|
|
41
41
|
"description": "Show what the world tried to do about the problem before the shift, and why those approaches fell short. Honest credit to predecessors makes the new game more credible.",
|
|
42
42
|
"instructions": "Emphasize previous challenges",
|
|
43
43
|
"slideType": "text",
|
|
44
|
-
"layoutHint": "text-1x
|
|
44
|
+
"layoutHint": "text-1x"
|
|
45
45
|
},
|
|
46
46
|
{
|
|
47
47
|
"id": "innovative-breakthrough",
|
|
@@ -49,7 +49,7 @@
|
|
|
49
49
|
"description": "Present the founding insight or breakthrough that makes a new approach possible. This is the 'secret' the company is built on — name it plainly.",
|
|
50
50
|
"instructions": "Present innovative solution",
|
|
51
51
|
"slideType": "text",
|
|
52
|
-
"layoutHint": "text-1x
|
|
52
|
+
"layoutHint": "text-1x"
|
|
53
53
|
},
|
|
54
54
|
{
|
|
55
55
|
"id": "unique-offering",
|
|
@@ -57,7 +57,7 @@
|
|
|
57
57
|
"description": "Detail the product or service. Lead with the customer-visible thing they touch; the architecture can wait. Show why this offering is structurally different from the past struggle.",
|
|
58
58
|
"instructions": "Detail product or service",
|
|
59
59
|
"slideType": "text",
|
|
60
|
-
"layoutHint": "text-1x
|
|
60
|
+
"layoutHint": "text-1x"
|
|
61
61
|
},
|
|
62
62
|
{
|
|
63
63
|
"id": "costly-issues",
|
|
@@ -65,7 +65,7 @@
|
|
|
65
65
|
"description": "Quantify the pain customers experience without your offering. Time, dollars, opportunity cost. Specific numbers convert sympathy into urgency.",
|
|
66
66
|
"instructions": "Quantify problems faced",
|
|
67
67
|
"slideType": "text",
|
|
68
|
-
"layoutHint": "text-1x
|
|
68
|
+
"layoutHint": "text-1x"
|
|
69
69
|
},
|
|
70
70
|
{
|
|
71
71
|
"id": "effective-solutions",
|
|
@@ -73,7 +73,7 @@
|
|
|
73
73
|
"description": "Demonstrate the customer outcome your offering produces. Before/after numbers from early users, even small N. Early-stage pitches are won by leading indicators, not by trailing ones.",
|
|
74
74
|
"instructions": "Demonstrate benefits",
|
|
75
75
|
"slideType": "text",
|
|
76
|
-
"layoutHint": "text-1x
|
|
76
|
+
"layoutHint": "text-1x"
|
|
77
77
|
},
|
|
78
78
|
{
|
|
79
79
|
"id": "unit-economics",
|
|
@@ -81,7 +81,7 @@
|
|
|
81
81
|
"description": "Explain the financial model. Cost to acquire, gross margin, payback. Investors don't expect maturity — they expect that you've thought about it.",
|
|
82
82
|
"instructions": "Explain financial model",
|
|
83
83
|
"slideType": "text",
|
|
84
|
-
"layoutHint": "text-1x
|
|
84
|
+
"layoutHint": "text-1x"
|
|
85
85
|
},
|
|
86
86
|
{
|
|
87
87
|
"id": "talented-team",
|
|
@@ -89,7 +89,7 @@
|
|
|
89
89
|
"description": "Introduce the founders and key early hires. Show why this team uniquely sees and can execute on this opportunity. Insight beats résumé at the seed stage.",
|
|
90
90
|
"instructions": "Introduce key players",
|
|
91
91
|
"slideType": "text",
|
|
92
|
-
"layoutHint": "text-1x
|
|
92
|
+
"layoutHint": "text-1x"
|
|
93
93
|
},
|
|
94
94
|
{
|
|
95
95
|
"id": "traction",
|
|
@@ -97,7 +97,7 @@
|
|
|
97
97
|
"description": "Showcase the early signal: pilots, design partners, waitlist, retention data, anything credible. Frame it honestly — investors at this stage discount inflation aggressively.",
|
|
98
98
|
"instructions": "Showcase accomplishments",
|
|
99
99
|
"slideType": "text",
|
|
100
|
-
"layoutHint": "text-1x
|
|
100
|
+
"layoutHint": "text-1x"
|
|
101
101
|
},
|
|
102
102
|
{
|
|
103
103
|
"id": "investment-opportunity",
|
|
@@ -105,13 +105,13 @@
|
|
|
105
105
|
"description": "Detail the round size, structure, and use of funds. Tie the raise to specific milestones it takes the company to. Specificity here signals operational maturity.",
|
|
106
106
|
"instructions": "Detail funding needs",
|
|
107
107
|
"slideType": "text",
|
|
108
|
-
"layoutHint": "text-1x
|
|
108
|
+
"layoutHint": "text-1x"
|
|
109
109
|
},
|
|
110
110
|
{
|
|
111
111
|
"id": "closing-logo",
|
|
112
112
|
"name": "Closing Logo",
|
|
113
113
|
"description": "Close on the brand and contact info. Leave the room with the line you most want repeated when the partner pitches you to the rest of the firm.",
|
|
114
|
-
"layoutHint": "title
|
|
114
|
+
"layoutHint": "title",
|
|
115
115
|
"instructions": "Leave a lasting impression",
|
|
116
116
|
"slideType": "text"
|
|
117
117
|
}
|
|
@@ -25,7 +25,7 @@
|
|
|
25
25
|
"description": "Introduce the topic in a way that respects the audience's time and curiosity. Frame why this question is worth asking, and signal the shape of the journey ahead without giving away the destination.",
|
|
26
26
|
"instructions": "Introduce the topic",
|
|
27
27
|
"slideType": "text",
|
|
28
|
-
"layoutHint": "text-1x
|
|
28
|
+
"layoutHint": "text-1x"
|
|
29
29
|
},
|
|
30
30
|
{
|
|
31
31
|
"id": "surprising-fact",
|
|
@@ -33,7 +33,7 @@
|
|
|
33
33
|
"description": "Lead with a single curious fact that recasts how the audience thinks about the topic. The fact should be small, specific, and unforgettable — the cognitive door the rest of the talk walks through.",
|
|
34
34
|
"instructions": "Share a curious fact",
|
|
35
35
|
"slideType": "text",
|
|
36
|
-
"layoutHint": "text-1x
|
|
36
|
+
"layoutHint": "text-1x"
|
|
37
37
|
},
|
|
38
38
|
{
|
|
39
39
|
"id": "experiment",
|
|
@@ -41,7 +41,7 @@
|
|
|
41
41
|
"description": "Walk through a method, study, or thought experiment that probes the surprising fact. Show how knowledge here gets made — the audience should feel like they're shoulder-to-shoulder with the investigator.",
|
|
42
42
|
"instructions": "Explain a tried method",
|
|
43
43
|
"slideType": "text",
|
|
44
|
-
"layoutHint": "text-1x
|
|
44
|
+
"layoutHint": "text-1x"
|
|
45
45
|
},
|
|
46
46
|
{
|
|
47
47
|
"id": "amusing-anecdote",
|
|
@@ -49,7 +49,7 @@
|
|
|
49
49
|
"description": "Drop in a story or moment from the field that brings the topic to human scale. Personality and humor here keep the audience leaning forward; technical depth without warmth loses the room.",
|
|
50
50
|
"instructions": "Relay an interesting story",
|
|
51
51
|
"slideType": "text",
|
|
52
|
-
"layoutHint": "text-1x
|
|
52
|
+
"layoutHint": "text-1x"
|
|
53
53
|
},
|
|
54
54
|
{
|
|
55
55
|
"id": "intriguing-information",
|
|
@@ -57,7 +57,7 @@
|
|
|
57
57
|
"description": "Layer in the more complex data or detail. By this point the audience is invested enough to do real work alongside you. Visualize generously — make the numbers tangible.",
|
|
58
58
|
"instructions": "Share complex data",
|
|
59
59
|
"slideType": "text",
|
|
60
|
-
"layoutHint": "text-1x
|
|
60
|
+
"layoutHint": "text-1x"
|
|
61
61
|
},
|
|
62
62
|
{
|
|
63
63
|
"id": "skeptical-scrutiny",
|
|
@@ -65,7 +65,7 @@
|
|
|
65
65
|
"description": "Question the easy interpretations. Challenge the audience's defaults and your own. Showing where the evidence is contested is what separates a teacher from a publicist.",
|
|
66
66
|
"instructions": "Encourage questioning of accepted truths",
|
|
67
67
|
"slideType": "text",
|
|
68
|
-
"layoutHint": "text-1x
|
|
68
|
+
"layoutHint": "text-1x"
|
|
69
69
|
},
|
|
70
70
|
{
|
|
71
71
|
"id": "extraordinary-explanation",
|
|
@@ -73,7 +73,7 @@
|
|
|
73
73
|
"description": "Present the most counterintuitive or beautiful explanation the topic offers. Take your time here — this is the payoff slide the audience came for.",
|
|
74
74
|
"instructions": "Break down unusual research findings",
|
|
75
75
|
"slideType": "text",
|
|
76
|
-
"layoutHint": "text-1x
|
|
76
|
+
"layoutHint": "text-1x"
|
|
77
77
|
},
|
|
78
78
|
{
|
|
79
79
|
"id": "unconventional-use",
|
|
@@ -81,13 +81,13 @@
|
|
|
81
81
|
"description": "Show an unexpected application or implication of the idea. Surprise reinforces the lesson and gives the audience a story to retell tomorrow.",
|
|
82
82
|
"instructions": "Expand on unique aspects",
|
|
83
83
|
"slideType": "text",
|
|
84
|
-
"layoutHint": "text-1x
|
|
84
|
+
"layoutHint": "text-1x"
|
|
85
85
|
},
|
|
86
86
|
{
|
|
87
87
|
"id": "captivating-conclusion",
|
|
88
88
|
"name": "Captivating Conclusion",
|
|
89
89
|
"description": "Close with a thoughtful, slightly poetic wrap-up. Echo the surprising fact, name the lesson, and leave the audience with a new question instead of a tidy answer.",
|
|
90
|
-
"layoutHint": "title
|
|
90
|
+
"layoutHint": "title",
|
|
91
91
|
"instructions": "Provide a thoughtful wrap-up",
|
|
92
92
|
"slideType": "text"
|
|
93
93
|
}
|
|
@@ -23,7 +23,7 @@
|
|
|
23
23
|
"id": "introduction",
|
|
24
24
|
"name": "Introduction",
|
|
25
25
|
"description": "Open with the period covered and the spirit of the conversation: collaborative, honest, growth-focused. Frame the meeting so both sides know what to expect.",
|
|
26
|
-
"layoutHint": "title
|
|
26
|
+
"layoutHint": "title",
|
|
27
27
|
"instructions": "Name & date",
|
|
28
28
|
"slideType": "text"
|
|
29
29
|
},
|
|
@@ -33,7 +33,7 @@
|
|
|
33
33
|
"description": "Review job execution against the role's expectations. Specific examples, dated. Avoid characterizing the person; describe the work and its impact.",
|
|
34
34
|
"instructions": "Review job execution",
|
|
35
35
|
"slideType": "text",
|
|
36
|
-
"layoutHint": "text-1x
|
|
36
|
+
"layoutHint": "text-1x"
|
|
37
37
|
},
|
|
38
38
|
{
|
|
39
39
|
"id": "achievements",
|
|
@@ -41,7 +41,7 @@
|
|
|
41
41
|
"description": "Acknowledge what went well. Name the projects, the moves, the moments where the employee made a difference. Specific recognition lands harder than generic praise.",
|
|
42
42
|
"instructions": "Acknowledge success",
|
|
43
43
|
"slideType": "text",
|
|
44
|
-
"layoutHint": "text-1x
|
|
44
|
+
"layoutHint": "text-1x"
|
|
45
45
|
},
|
|
46
46
|
{
|
|
47
47
|
"id": "feedback",
|
|
@@ -49,7 +49,7 @@
|
|
|
49
49
|
"description": "Provide constructive feedback grounded in observation. Distinguish patterns from one-offs. Tell the employee something they can act on, not something they can only feel.",
|
|
50
50
|
"instructions": "Provide positive remarks",
|
|
51
51
|
"slideType": "text",
|
|
52
|
-
"layoutHint": "text-1x
|
|
52
|
+
"layoutHint": "text-1x"
|
|
53
53
|
},
|
|
54
54
|
{
|
|
55
55
|
"id": "constructive-criticism",
|
|
@@ -57,7 +57,7 @@
|
|
|
57
57
|
"description": "Suggest improvements in language that respects the employee's intelligence. Pair each piece of criticism with a concrete example and a specific behavior change you'd like to see.",
|
|
58
58
|
"instructions": "Suggest improvements",
|
|
59
59
|
"slideType": "text",
|
|
60
|
-
"layoutHint": "text-1x
|
|
60
|
+
"layoutHint": "text-1x"
|
|
61
61
|
},
|
|
62
62
|
{
|
|
63
63
|
"id": "development-opportunities",
|
|
@@ -65,7 +65,7 @@
|
|
|
65
65
|
"description": "Highlight growth areas and the experiences that could stretch the employee. Frame development as an investment, not a fix.",
|
|
66
66
|
"instructions": "Highlight growth areas",
|
|
67
67
|
"slideType": "text",
|
|
68
|
-
"layoutHint": "text-1x
|
|
68
|
+
"layoutHint": "text-1x"
|
|
69
69
|
},
|
|
70
70
|
{
|
|
71
71
|
"id": "goals",
|
|
@@ -73,13 +73,13 @@
|
|
|
73
73
|
"description": "Outline next-period goals together. Specific, measurable, with explicit support. The strongest goals are co-authored, not handed down.",
|
|
74
74
|
"instructions": "Outline next steps",
|
|
75
75
|
"slideType": "text",
|
|
76
|
-
"layoutHint": "text-1x
|
|
76
|
+
"layoutHint": "text-1x"
|
|
77
77
|
},
|
|
78
78
|
{
|
|
79
79
|
"id": "mentoring",
|
|
80
80
|
"name": "Mentoring",
|
|
81
81
|
"description": "Encourage continued learning through mentorship, training, peer pairings. Close the review with the message that growth is a shared responsibility, not a one-way evaluation.",
|
|
82
|
-
"layoutHint": "title
|
|
82
|
+
"layoutHint": "title",
|
|
83
83
|
"instructions": "Encourage continuous learning",
|
|
84
84
|
"slideType": "text"
|
|
85
85
|
}
|
|
@@ -26,7 +26,7 @@
|
|
|
26
26
|
"description": "Set an empathetic, accountable tone before any analysis. Acknowledge the impact on the people in the room and the customers affected. Authenticity here earns you the credibility you'll need for the rest of the deck.",
|
|
27
27
|
"instructions": "Set an empathetic tone",
|
|
28
28
|
"slideType": "text",
|
|
29
|
-
"layoutHint": "text-1x
|
|
29
|
+
"layoutHint": "text-1x"
|
|
30
30
|
},
|
|
31
31
|
{
|
|
32
32
|
"id": "incident-breakdown",
|
|
@@ -34,7 +34,7 @@
|
|
|
34
34
|
"description": "Walk through what happened, in time order. Stick to facts: what systems, what users, what timeline. No causal claims yet — just an accurate, neutral reconstruction the audience can trust.",
|
|
35
35
|
"instructions": "Detail the failure",
|
|
36
36
|
"slideType": "text",
|
|
37
|
-
"layoutHint": "text-1x
|
|
37
|
+
"layoutHint": "text-1x"
|
|
38
38
|
},
|
|
39
39
|
{
|
|
40
40
|
"id": "impact-analysis",
|
|
@@ -42,7 +42,7 @@
|
|
|
42
42
|
"description": "Quantify the damage. Customer-hours lost, revenue at risk, SLA breaches, downstream knock-ons. Be specific and direct; vague impact statements undermine the rest of the post-mortem.",
|
|
43
43
|
"instructions": "Describe failure's effects",
|
|
44
44
|
"slideType": "text",
|
|
45
|
-
"layoutHint": "text-1x
|
|
45
|
+
"layoutHint": "text-1x"
|
|
46
46
|
},
|
|
47
47
|
{
|
|
48
48
|
"id": "root-cause",
|
|
@@ -50,7 +50,7 @@
|
|
|
50
50
|
"description": "Trace the failure to its underlying cause, not the most visible symptom. Use a 'five whys' or fishbone framing if useful. Distinguish between the proximate trigger and the systemic conditions that allowed it.",
|
|
51
51
|
"instructions": "Analyze underlying reasons",
|
|
52
52
|
"slideType": "text",
|
|
53
|
-
"layoutHint": "text-1x
|
|
53
|
+
"layoutHint": "text-1x"
|
|
54
54
|
},
|
|
55
55
|
{
|
|
56
56
|
"id": "proposed-solutions",
|
|
@@ -58,7 +58,7 @@
|
|
|
58
58
|
"description": "Present the corrective actions you're taking. Lead with the highest-leverage fix; sequence the rest. For each action, name an owner and a date — solutions without owners are aspirations.",
|
|
59
59
|
"instructions": "Suggest corrective measures",
|
|
60
60
|
"slideType": "text",
|
|
61
|
-
"layoutHint": "text-1x
|
|
61
|
+
"layoutHint": "text-1x"
|
|
62
62
|
},
|
|
63
63
|
{
|
|
64
64
|
"id": "action-plan",
|
|
@@ -66,7 +66,7 @@
|
|
|
66
66
|
"description": "Lay out the rollout: what ships when, how it's verified, who signs off. Show that 'fixed' has a definition and a deadline, not just intent.",
|
|
67
67
|
"instructions": "Map out steps",
|
|
68
68
|
"slideType": "text",
|
|
69
|
-
"layoutHint": "text-1x
|
|
69
|
+
"layoutHint": "text-1x"
|
|
70
70
|
},
|
|
71
71
|
{
|
|
72
72
|
"id": "evaluate-outcome",
|
|
@@ -74,7 +74,7 @@
|
|
|
74
74
|
"description": "Define the metrics that will tell you the fix worked. Pre/post comparisons, monitoring SLOs, error budgets — whatever proves the failure mode is closed and not just deferred.",
|
|
75
75
|
"instructions": "Assess corrective actions",
|
|
76
76
|
"slideType": "text",
|
|
77
|
-
"layoutHint": "text-1x
|
|
77
|
+
"layoutHint": "text-1x"
|
|
78
78
|
},
|
|
79
79
|
{
|
|
80
80
|
"id": "lessons-learned",
|
|
@@ -82,7 +82,7 @@
|
|
|
82
82
|
"description": "Distill the broader lessons that outlive this specific incident. What does the team or organization now know that it didn't before? What patterns will you watch for elsewhere?",
|
|
83
83
|
"instructions": "Reflect on failure lessons",
|
|
84
84
|
"slideType": "text",
|
|
85
|
-
"layoutHint": "text-1x
|
|
85
|
+
"layoutHint": "text-1x"
|
|
86
86
|
},
|
|
87
87
|
{
|
|
88
88
|
"id": "preventive-measures",
|
|
@@ -90,13 +90,13 @@
|
|
|
90
90
|
"description": "List the systemic safeguards being added — process changes, automated checks, on-call procedures, review gates. Show how this category of failure becomes harder to recur, not just this specific instance.",
|
|
91
91
|
"instructions": "List safeguards",
|
|
92
92
|
"slideType": "text",
|
|
93
|
-
"layoutHint": "text-1x
|
|
93
|
+
"layoutHint": "text-1x"
|
|
94
94
|
},
|
|
95
95
|
{
|
|
96
96
|
"id": "closing-thoughts",
|
|
97
97
|
"name": "Closing Thoughts",
|
|
98
98
|
"description": "Close with humility and forward momentum. Re-affirm accountability, thank the audience for their patience, and signal confidence in the path forward without overclaiming.",
|
|
99
|
-
"layoutHint": "title
|
|
99
|
+
"layoutHint": "title",
|
|
100
100
|
"instructions": "Empathize, trust, and encourage",
|
|
101
101
|
"slideType": "text"
|
|
102
102
|
}
|
|
@@ -26,7 +26,7 @@
|
|
|
26
26
|
"description": "Open with a brief framing of what this update is for and what you intend to leave the audience with. Set the tone — long-term, candid, principle-driven.",
|
|
27
27
|
"instructions": "Overview and objectives",
|
|
28
28
|
"slideType": "text",
|
|
29
|
-
"layoutHint": "text-1x
|
|
29
|
+
"layoutHint": "text-1x"
|
|
30
30
|
},
|
|
31
31
|
{
|
|
32
32
|
"id": "accomplishments",
|
|
@@ -34,7 +34,7 @@
|
|
|
34
34
|
"description": "Showcase the period's most material wins, briefly. The audience came for what's next; wins earn permission for the harder slides ahead, but they aren't the headline.",
|
|
35
35
|
"instructions": "Showcase recent achievements",
|
|
36
36
|
"slideType": "text",
|
|
37
|
-
"layoutHint": "text-1x
|
|
37
|
+
"layoutHint": "text-1x"
|
|
38
38
|
},
|
|
39
39
|
{
|
|
40
40
|
"id": "potential",
|
|
@@ -42,7 +42,7 @@
|
|
|
42
42
|
"description": "Detail the market and customer opportunities ahead. Size them honestly and connect them to the work already underway. Potential without specifics reads as wishful.",
|
|
43
43
|
"instructions": "Detail market opportunities",
|
|
44
44
|
"slideType": "text",
|
|
45
|
-
"layoutHint": "text-1x
|
|
45
|
+
"layoutHint": "text-1x"
|
|
46
46
|
},
|
|
47
47
|
{
|
|
48
48
|
"id": "competitive-edge",
|
|
@@ -50,7 +50,7 @@
|
|
|
50
50
|
"description": "Reveal the strategic positioning that gives the business its advantage. Frame it as a structural moat, not a list of features. The audience should be able to repeat the moat in their own words.",
|
|
51
51
|
"instructions": "Reveal strategic positioning",
|
|
52
52
|
"slideType": "text",
|
|
53
|
-
"layoutHint": "text-1x
|
|
53
|
+
"layoutHint": "text-1x"
|
|
54
54
|
},
|
|
55
55
|
{
|
|
56
56
|
"id": "long-term-vision",
|
|
@@ -58,7 +58,7 @@
|
|
|
58
58
|
"description": "Emphasize the long-term view that anchors decisions. Quarters serve years; years serve decades. Anchor the audience in the time horizon you actually run the business on.",
|
|
59
59
|
"instructions": "Emphasize focused future orientation",
|
|
60
60
|
"slideType": "text",
|
|
61
|
-
"layoutHint": "text-1x
|
|
61
|
+
"layoutHint": "text-1x"
|
|
62
62
|
},
|
|
63
63
|
{
|
|
64
64
|
"id": "performance-metrics",
|
|
@@ -66,7 +66,7 @@
|
|
|
66
66
|
"description": "Illuminate the indicators that show the long-term thesis is working. Choose metrics that compound — retention, NPS, unit economics — over those that flatter.",
|
|
67
67
|
"instructions": "Illuminate growth indicators",
|
|
68
68
|
"slideType": "text",
|
|
69
|
-
"layoutHint": "text-1x
|
|
69
|
+
"layoutHint": "text-1x"
|
|
70
70
|
},
|
|
71
71
|
{
|
|
72
72
|
"id": "growth-achievement",
|
|
@@ -74,7 +74,7 @@
|
|
|
74
74
|
"description": "Certify the tangible progress against the long-term plan. Year-over-year, cohort behavior, expanded reach. Growth, in this beat, is evidence that the strategy is real.",
|
|
75
75
|
"instructions": "Certify tangible progress",
|
|
76
76
|
"slideType": "text",
|
|
77
|
-
"layoutHint": "text-1x
|
|
77
|
+
"layoutHint": "text-1x"
|
|
78
78
|
},
|
|
79
79
|
{
|
|
80
80
|
"id": "strategic-framework",
|
|
@@ -82,7 +82,7 @@
|
|
|
82
82
|
"description": "Explain the principles that guide decisions. Customer obsession, long-term thinking, frugality, ownership — whatever the actual operating discipline is. Principles are the connective tissue between strategy and behavior.",
|
|
83
83
|
"instructions": "Explain decision principles",
|
|
84
84
|
"slideType": "text",
|
|
85
|
-
"layoutHint": "text-1x
|
|
85
|
+
"layoutHint": "text-1x"
|
|
86
86
|
},
|
|
87
87
|
{
|
|
88
88
|
"id": "expansion",
|
|
@@ -90,7 +90,7 @@
|
|
|
90
90
|
"description": "Detail the next areas of growth: products, segments, geographies. Tie each to the principles above so the audience sees expansion as continuity rather than scatter.",
|
|
91
91
|
"instructions": "Detail growth potential",
|
|
92
92
|
"slideType": "text",
|
|
93
|
-
"layoutHint": "text-1x
|
|
93
|
+
"layoutHint": "text-1x"
|
|
94
94
|
},
|
|
95
95
|
{
|
|
96
96
|
"id": "future-objectives",
|
|
@@ -98,7 +98,7 @@
|
|
|
98
98
|
"description": "Forecast the targets and commitments for the period ahead. Be specific enough to be held accountable. Vague objectives are how strategies erode.",
|
|
99
99
|
"instructions": "Forecast upcoming targets",
|
|
100
100
|
"slideType": "text",
|
|
101
|
-
"layoutHint": "text-1x
|
|
101
|
+
"layoutHint": "text-1x"
|
|
102
102
|
},
|
|
103
103
|
{
|
|
104
104
|
"id": "acknowledgment",
|
|
@@ -106,13 +106,13 @@
|
|
|
106
106
|
"description": "Recognize the contributions of teams, customers, and partners that made the period possible. Specific names land harder than blanket thanks.",
|
|
107
107
|
"instructions": "Recognize contributions and successes",
|
|
108
108
|
"slideType": "text",
|
|
109
|
-
"layoutHint": "text-1x
|
|
109
|
+
"layoutHint": "text-1x"
|
|
110
110
|
},
|
|
111
111
|
{
|
|
112
112
|
"id": "closing-remarks",
|
|
113
113
|
"name": "Closing Remarks",
|
|
114
114
|
"description": "Recap the focus, thank the audience, and inspire the work ahead. End with the line you most want quoted in tomorrow's newsletter.",
|
|
115
|
-
"layoutHint": "title
|
|
115
|
+
"layoutHint": "title",
|
|
116
116
|
"instructions": "Recap, thank, inspire",
|
|
117
117
|
"slideType": "text"
|
|
118
118
|
}
|
|
@@ -44,7 +44,7 @@
|
|
|
44
44
|
"id": "invitation",
|
|
45
45
|
"name": "Invitation",
|
|
46
46
|
"description": "Close by inviting the audience to share the belief — to buy, build, join, or evangelize. The strongest invitations don't argue; they assume alignment and offer a way in.",
|
|
47
|
-
"layoutHint": "title
|
|
47
|
+
"layoutHint": "title"
|
|
48
48
|
}
|
|
49
49
|
]
|
|
50
50
|
}
|
|
@@ -24,7 +24,7 @@
|
|
|
24
24
|
"id": "opening",
|
|
25
25
|
"name": "Opening",
|
|
26
26
|
"description": "Set the stage. Tell the audience they're about to see something that matters, without yet showing it. The pause before the reveal is part of the reveal.",
|
|
27
|
-
"layoutHint": "title
|
|
27
|
+
"layoutHint": "title",
|
|
28
28
|
"instructions": "Set the stage",
|
|
29
29
|
"slideType": "text"
|
|
30
30
|
},
|
|
@@ -34,7 +34,7 @@
|
|
|
34
34
|
"description": "Announce the product. One image, one name, one sentence. Anything more competes with the moment. The slide should feel like the curtain going up.",
|
|
35
35
|
"instructions": "Announce product",
|
|
36
36
|
"slideType": "text",
|
|
37
|
-
"layoutHint": "text-1x
|
|
37
|
+
"layoutHint": "text-1x"
|
|
38
38
|
},
|
|
39
39
|
{
|
|
40
40
|
"id": "demonstration",
|
|
@@ -42,7 +42,7 @@
|
|
|
42
42
|
"description": "Show the product in real use. Choose a single defining workflow that captures what the product does and how it feels. Live beats canned wherever possible.",
|
|
43
43
|
"instructions": "Showcase the product",
|
|
44
44
|
"slideType": "text",
|
|
45
|
-
"layoutHint": "text-1x
|
|
45
|
+
"layoutHint": "text-1x"
|
|
46
46
|
},
|
|
47
47
|
{
|
|
48
48
|
"id": "wow-factor",
|
|
@@ -50,7 +50,7 @@
|
|
|
50
50
|
"description": "Highlight the cutting-edge feature that earns the headline. One thing, presented well — the audience should leave able to repeat it in a sentence.",
|
|
51
51
|
"instructions": "Highlight cutting-edge features",
|
|
52
52
|
"slideType": "text",
|
|
53
|
-
"layoutHint": "text-1x
|
|
53
|
+
"layoutHint": "text-1x"
|
|
54
54
|
},
|
|
55
55
|
{
|
|
56
56
|
"id": "differentiation",
|
|
@@ -58,7 +58,7 @@
|
|
|
58
58
|
"description": "Make the contrast with existing alternatives unmistakable. Use comparisons that the audience already understands; don't argue against straw versions of the competition.",
|
|
59
59
|
"instructions": "Distinctive factors",
|
|
60
60
|
"slideType": "text",
|
|
61
|
-
"layoutHint": "text-1x
|
|
61
|
+
"layoutHint": "text-1x"
|
|
62
62
|
},
|
|
63
63
|
{
|
|
64
64
|
"id": "revolution",
|
|
@@ -66,7 +66,7 @@
|
|
|
66
66
|
"description": "Reframe the category. Show how the product changes what the playing field looks like, not just where you sit on it. This is the slide pundits will quote.",
|
|
67
67
|
"instructions": "Change in the playing field",
|
|
68
68
|
"slideType": "text",
|
|
69
|
-
"layoutHint": "text-1x
|
|
69
|
+
"layoutHint": "text-1x"
|
|
70
70
|
},
|
|
71
71
|
{
|
|
72
72
|
"id": "excitement",
|
|
@@ -74,7 +74,7 @@
|
|
|
74
74
|
"description": "Build anticipation around what's next: availability, partnerships, what the audience can imagine doing with the product. Excitement is how the room exits the keynote into the world.",
|
|
75
75
|
"instructions": "Build anticipation",
|
|
76
76
|
"slideType": "text",
|
|
77
|
-
"layoutHint": "text-1x
|
|
77
|
+
"layoutHint": "text-1x"
|
|
78
78
|
},
|
|
79
79
|
{
|
|
80
80
|
"id": "call-to-action",
|
|
@@ -82,13 +82,13 @@
|
|
|
82
82
|
"description": "Give the audience the action that channels the excitement. Pre-order, try it, tell others. Be specific so the energy converts into behavior.",
|
|
83
83
|
"instructions": "Urge to explore",
|
|
84
84
|
"slideType": "text",
|
|
85
|
-
"layoutHint": "text-1x
|
|
85
|
+
"layoutHint": "text-1x"
|
|
86
86
|
},
|
|
87
87
|
{
|
|
88
88
|
"id": "gratitude",
|
|
89
89
|
"name": "Gratitude",
|
|
90
90
|
"description": "Thank the team that built it and the audience that came. Brief, sincere, not perfunctory. The closing thanks is the period at the end of the keynote.",
|
|
91
|
-
"layoutHint": "title
|
|
91
|
+
"layoutHint": "title",
|
|
92
92
|
"instructions": "Thank the audience",
|
|
93
93
|
"slideType": "text"
|
|
94
94
|
}
|
|
@@ -26,7 +26,7 @@
|
|
|
26
26
|
"description": "Set the stage with a moment that earns the audience's full attention. Speak in the moral register the rest of the talk will require. Avoid throat-clearing — open as if the speech were already underway.",
|
|
27
27
|
"instructions": "Set the stage",
|
|
28
28
|
"slideType": "text",
|
|
29
|
-
"layoutHint": "text-1x
|
|
29
|
+
"layoutHint": "text-1x"
|
|
30
30
|
},
|
|
31
31
|
{
|
|
32
32
|
"id": "give-context",
|
|
@@ -34,7 +34,7 @@
|
|
|
34
34
|
"description": "Place the issue in its historical and current context. What promises were made, what has and hasn't been kept. Context turns the speech from opinion into accountability.",
|
|
35
35
|
"instructions": "Put in historical and current context",
|
|
36
36
|
"slideType": "text",
|
|
37
|
-
"layoutHint": "text-1x
|
|
37
|
+
"layoutHint": "text-1x"
|
|
38
38
|
},
|
|
39
39
|
{
|
|
40
40
|
"id": "highlight-inequality",
|
|
@@ -42,7 +42,7 @@
|
|
|
42
42
|
"description": "Show specific, undeniable examples of the inequality at issue. Concrete moments and people, not abstractions. The audience should feel the gap between what is and what was promised.",
|
|
43
43
|
"instructions": "Show examples of inequality",
|
|
44
44
|
"slideType": "text",
|
|
45
|
-
"layoutHint": "text-1x
|
|
45
|
+
"layoutHint": "text-1x"
|
|
46
46
|
},
|
|
47
47
|
{
|
|
48
48
|
"id": "share-dream",
|
|
@@ -50,7 +50,7 @@
|
|
|
50
50
|
"description": "Describe the future you envision in vivid, specific detail. The dream must be both ambitious and recognizable — a world the audience can picture themselves living in.",
|
|
51
51
|
"instructions": "Describe your vision",
|
|
52
52
|
"slideType": "text",
|
|
53
|
-
"layoutHint": "text-1x
|
|
53
|
+
"layoutHint": "text-1x"
|
|
54
54
|
},
|
|
55
55
|
{
|
|
56
56
|
"id": "create-urgency",
|
|
@@ -58,7 +58,7 @@
|
|
|
58
58
|
"description": "Explain why the time for change is now. The cost of waiting, the moment that won't return. Urgency converts shared vision into shared movement.",
|
|
59
59
|
"instructions": "Explain the need for immediate change",
|
|
60
60
|
"slideType": "text",
|
|
61
|
-
"layoutHint": "text-1x
|
|
61
|
+
"layoutHint": "text-1x"
|
|
62
62
|
},
|
|
63
63
|
{
|
|
64
64
|
"id": "another-dream",
|
|
@@ -66,7 +66,7 @@
|
|
|
66
66
|
"description": "Layer additional visions of the future in parallel structure. Repetition and rhythm build momentum the way a single image cannot.",
|
|
67
67
|
"instructions": "Continue to elaborate on your vision",
|
|
68
68
|
"slideType": "text",
|
|
69
|
-
"layoutHint": "text-1x
|
|
69
|
+
"layoutHint": "text-1x"
|
|
70
70
|
},
|
|
71
71
|
{
|
|
72
72
|
"id": "emphasize-unity",
|
|
@@ -74,7 +74,7 @@
|
|
|
74
74
|
"description": "Speak to the collective power of the audience together. Name common ground that crosses lines the issue normally divides. Unity is the engine that turns dream into march.",
|
|
75
75
|
"instructions": "Talk about collective power",
|
|
76
76
|
"slideType": "text",
|
|
77
|
-
"layoutHint": "text-1x
|
|
77
|
+
"layoutHint": "text-1x"
|
|
78
78
|
},
|
|
79
79
|
{
|
|
80
80
|
"id": "last-dream",
|
|
@@ -82,7 +82,7 @@
|
|
|
82
82
|
"description": "Deliver one more, fully realized vision of the world you're calling for. Specific enough to be remembered, expansive enough to inspire.",
|
|
83
83
|
"instructions": "Further share dreams of ideal in-depth",
|
|
84
84
|
"slideType": "text",
|
|
85
|
-
"layoutHint": "text-1x
|
|
85
|
+
"layoutHint": "text-1x"
|
|
86
86
|
},
|
|
87
87
|
{
|
|
88
88
|
"id": "call-to-action",
|
|
@@ -90,7 +90,7 @@
|
|
|
90
90
|
"description": "Ask the audience to participate in the change. Be specific about what 'doing something' looks like — show, march, give, vote, organize. Vague CTAs produce vague action.",
|
|
91
91
|
"instructions": "Ask audience to participate in change",
|
|
92
92
|
"slideType": "text",
|
|
93
|
-
"layoutHint": "text-1x
|
|
93
|
+
"layoutHint": "text-1x"
|
|
94
94
|
},
|
|
95
95
|
{
|
|
96
96
|
"id": "show-determination",
|
|
@@ -98,13 +98,13 @@
|
|
|
98
98
|
"description": "Encourage persistence in the face of resistance. Acknowledge what will be hard. Determination, named honestly, is more durable than easy optimism.",
|
|
99
99
|
"instructions": "Encourage persistence",
|
|
100
100
|
"slideType": "text",
|
|
101
|
-
"layoutHint": "text-1x
|
|
101
|
+
"layoutHint": "text-1x"
|
|
102
102
|
},
|
|
103
103
|
{
|
|
104
104
|
"id": "create-hope",
|
|
105
105
|
"name": "Create Hope",
|
|
106
106
|
"description": "Close on hope grounded in evidence: progress already made, victories already won, ground already moved. Hope as a conclusion lands strongest when it sounds like it has been earned.",
|
|
107
|
-
"layoutHint": "title
|
|
107
|
+
"layoutHint": "title",
|
|
108
108
|
"instructions": "Inspire hope for future",
|
|
109
109
|
"slideType": "text"
|
|
110
110
|
}
|