A tailored course, built for your situation
Sources and Specific Examples on Hand When Peers Push Back
Build unshakable reasoning for governance choices that others challenge
The situation this course is for
Who this is for
IC-level practitioner in a corporate venture arm navigating governance tensions between innovation speed and compliance rigor
Who this is not for
Those looking for boilerplate compliance templates or high-level strategy overviews without tactical depth
What you walk away with
- Articulate the rationale behind governance decisions using cited standards and real-world precedents
- Respond confidently when challenged, with examples from comparable ventures and energy-sector edge cases
- Structure decision memos that preempt pushback by anchoring in documented risk criteria
- Reference authoritative sources at the right level of detail, neither too vague nor overly technical
- Build repeatable reasoning patterns that scale across new investment types
The 12 modules (with all 144 chapters)
- Defensible vs. default governance
- Three venture-stage moments that trigger scrutiny
- Energy-sector precedent: carbon project oversight
- How the firm Ventures differs from fintech models
- Decision memo anatomy: the unchallenged version
- When speed doesn't mean skipping steps
- Case: rejected investment with flawed rationale
- Case: approved investment with strong justification
- Signal types that trigger peer review
- Documenting assumptions before escalation
- Mapping risk appetite to decision depth
- First artefact: draft decision scaffold
- ISO 31000 in venture risk decisions
- Using OECD guidance without over-citing
- SEC disclosures as precedent in capital cases
- When to use internal risk taxonomy
- Citing internal audit findings appropriately
- Energy transition frameworks: IPCC vs. IEA
- How to footnote without slowing down
- Three examples from clean tech due diligence
- Balancing speed and traceability
- Avoiding ‘because we said so’
- Sourcing from upstream ESG commitments
- Second artefact: source-backed recommendation
- ‘But we’ve never done this before’
- ‘This slows us down’ with counter-case
- ‘Other teams aren’t held to this’
- ‘We can fix it later’ myth
- ‘The regulator won’t care’ flaw
- ‘It’s just a pilot’ fallacy
- ‘We need to move fast’ vs. fiduciary duty
- ‘This is too conservative’ rebuttal
- ‘We’re different’ as excuse
- ‘It worked for them’ illusion
- ‘We’re not public yet’ risk
- Third artefact: objection-response matrix
- From risk appetite to decision gate
- Linking capital size to scrutiny level
- How technology maturity triggers governance
- When IP ownership demands deeper review
- Country risk flowing into due diligence
- Partner structure affecting oversight
- Precedent: failed JV from lack of chain
- The ‘why three times’ drill
- Using threshold rules to justify depth
- Documenting reasoning in real time
- Connecting governance to exit planning
- Fourth artefact: rationale chain template
- How to cite past deals correctly
- When precedent doesn’t apply
- Updating reasoning for inflation
- Energy transition changing old norms
- Venture stage alters precedent value
- Cross-sector lessons: biotech to cleantech
- What not to reuse from old memos
- How the firm’s culture shapes precedent
- Using competitor moves as counterpoint
- When silence is precedent
- How regulators cite past cases
- Fifth artefact: precedent brief
- Lead with consequence, not process
- Positioning risk as upside guardrail
- Using visuals that guide reasoning
- Headline-driven memo structure
- Paragraph order that builds inevitability
- Avoiding defensive language
- Tone: confident but open
- Subject lines that reduce friction
- Minimizing redlines with clarity
- How execs skim and where to place key points
- Using past wins as social proof
- Sixth artefact: influence-optimized memo
- Distilling LCA reports for governance
- When to bring in engineers pre-decision
- Summarizing cybersecurity assessments
- Using NEOM data center standards
- Carbon accounting thresholds
- How CCUS project complexity changes review
- Avoiding ‘throw it over the wall’
- Translating technical risk into business terms
- Setting gates based on tech maturity
- When to require third-party validation
- Using the firm research outputs in due diligence
- Seventh artefact: technical annex brief
- Energy transition strategy as risk lens
- Profitability goals shaping oversight level
- Sustainability commitments as filters
- How ‘gigastallion’ aspirations affect governance
- Localization influencing partner risk
- Long-term shareholder expectations
- Avoiding buzzword compliance
- Using leadership statements authentically
- Connecting to upstream planning cycles
- When to reference Saudi Vision metrics
- Linking governance to value creation
- Eighth artefact: strategy alignment brief
- Preparing for unplanned review
- What to bring to an escalation call
- How to reframe without backtracking
- Using documented assumptions as anchor
- When to admit uncertainty
- Keeping tone consistent under pressure
- How fast is too fast to escalate
- Avoiding overcorrection
- Building coalitions before escalation
- Using peer review as validation
- Post-mortem as credibility builder
- Ninth artefact: escalation response pack
- Identifying decision archetypes
- Creating rationale libraries
- Tagging patterns by risk type
- How to version reasoning over time
- Sharing templates without losing control
- Building team-wide consistency
- Using patterns in onboarding
- Avoiding ‘template fatigue’
- When to deviate from pattern
- Tracking pattern effectiveness
- Linking patterns to audit readiness
- Tenth artefact: reasoning pattern library
- The ‘assumptions upfront’ section
- Three types of critical assumptions
- How often to revisit them
- Using assumption logs in reviews
- When assumptions become liabilities
- Aligning assumptions across teams
- Challenging your own assumptions
- Using red teaming selectively
- Documenting rejected assumptions
- Making assumptions version-controlled
- Linking assumptions to exit conditions
- Eleventh artefact: assumption register
- Assembling the complete package
- Checklist for self-review
- How to get feedback without inviting rewrites
- Versioning artefacts for traceability
- Storing outputs for future reference
- Using artefacts in future deals
- When to declassify old decisions
- Measuring artefact impact over time
- Updating artefacts as context shifts
- Handing off with confidence
- Using artefacts in promotion packets
- Twelfth artefact: final defensible decision package
How this maps to your situation
- When a new investment triggers cross-functional scrutiny
- Before a governance decision goes to leadership review
- After a peer challenges a due diligence call
- When onboarding a new team member into governance role
Before vs. after
What's included with your purchase
- 12 modules with 12 chapters each (144 chapters)
- Downloadable templates and worked examples for every module
- Hand-built implementation playbook delivered alongside course access
- 30-day money-back guarantee
Delivery and format
- Course and learning environment access provisioned within 24 hours of purchase
- Hand-built implementation playbook delivered alongside course access
Format: Text-based modules and chapters in the Art of Service learning environment, plus downloadable templates and worked examples for every chapter, plus the hand-built implementation playbook delivered alongside course access.
Time investment: Approximately 3 hours per module, designed for just-in-time learning during active governance cycles.
How this compares to the alternatives
Unlike generic compliance courses, this program focuses on the specific intersection of venture governance and energy-sector risk, with artefacts tailored to capital allocation in innovation arms of industrial firms.
Frequently asked
Within 24 hours your account in the learning environment is provisioned and the tailored implementation playbook is delivered alongside it.