🚀 Advanced — Building Solutions

What it is: Diagnosis of the structural errors that doom corporate innovation programs before they deliver measurable value.

Why Learn: Avoiding the same mistakes saves 12–18 months of wasted work and preserves the program’s internal credibility.

Key concepts: sponsorship without commitment, vanity KPIs, isolation from operations, lack of a formal mandate, absence of a diversified portfolio.

What it is: The McKinsey three horizons framework applied to the corporate innovation portfolio: defend the core (H1), expand adjacencies (H2), create the future (H3).

Why Learn: Without this model, the program stays stuck in H1 and never creates real competitive differentiation.

Key concepts: 70/20/10 investment allocation, different metrics for each horizon, balanced portfolio, separate H1 vs. H3 teams.

What it is: The 5 elements no program can survive without: C-level sponsorship, a clear mandate, a dedicated team, a protected budget, and a stage-gate process.

Why Learn: Launching a program without these elements is a recipe for failure. Knowing the minimum requirements lets you negotiate what matters.

Key concepts: program charter, innovation committee, separate exploration budget, part-time vs. dedicated team, physical/virtual innovation space.

What it is: An adaptation of the classic stage-gate process for innovation projects, with advancement criteria based on hypothesis validation instead of a complete business case.

Why Learn: Rigid stage-gate kills H3. The adapted version allows progress with controlled uncertainty and invests only in what it learns.

Key concepts: decision gates (kill/pivot/continue), learning metrics, staged investment tickets, criteria for each horizon.

What it is: First 90 days strategy: choose and deliver visible results that build credibility for larger, longer initiatives.

Why Learn: Without quick wins, the first 6 months look like “doing nothing,” and the program gets canceled before it matures.

Key concepts: selection criteria (visible impact, low complexity, high speed), a 30-60-90-day plan, communication of results to the C-level.

What it is: A three-layer metrics system—activity (input), learning (process), and value (output)—that demonstrates the program’s impact to different stakeholders.

Why Learn: Measuring activity alone (number of workshops) does not convince finance. Measuring only the final result does not capture intermediate progress.

Key concepts: innovation accounting, innovation funnel metrics, innovator NPS, revenue from new businesses as a % of the total, validation speed.

What it is: Profile, motivation, and behaviors that define a real intrapreneur versus a creative employee or a "paper intrapreneur."

Why Learn: Identifying and nurturing the right people is more effective than trying to turn everyone into intrapreneurs.

Key concepts: tolerance for ambiguity, results orientation, ability to sell internally, internal influence network, responsible autonomy.

What it is: How to map potential intrapreneurs, create internal acceleration programs, and develop an entrepreneurial mindset within the corporation.

Why Learn: Without an active identification process, the best talent remains hidden or frustrated and leaves for external startups.

Key concepts: innovation bootcamps, hackathons as a filter, internal pitches, mentoring with external founders, rotations at partner startups.

What it is: Mechanisms that give innovation teams real autonomy without exposing the company to unnecessary legal, financial, or reputational risks.

Why Learn: Autonomy without guardrails leads to chaos; excessive guardrails stifle innovation. Balance is possible and necessary.

Key concepts: innovation sandbox, pre-approvals by risk category, simplified confidentiality agreements, progress report vs. audit.

What it is: Financial and non-financial incentive models that motivate and retain intrapreneurs, including virtual equity, performance bonuses, and public recognition.

Why Learn: Intrapreneurs have the option to leave. Without proper incentives, the company trains talent for competitors and startups.

Key concepts: phantom equity, milestone bonuses, an innovation career path (IC track), visibility with senior leadership, public recognition.

What it is: How to build multidisciplinary teams for innovation projects, balancing technical, business, design, and execution skills.

Why Learn: Homogeneous teams create blind spots. Diversity of perspective is the main accelerator of innovation, according to Harvard Business Review.

Key concepts: two-pizza team (Amazon), T-shaped professionals, knowledge broker role, cognitive vs. demographic diversity, anti-groupthink.

What it is: The most common mistakes that destroy intrapreneurship initiatives: support in name only, returning to the core business at the first obstacle, and internal politics as a blocker.

Why Learn: Knowing the pitfalls helps anticipate conflicts and create safeguards before problems arise.

Key concepts: organizational antibodies, innovators perceived as a threat, middle management as a blocker, lack of air cover from the sponsor.

What it is: The model by Henry Chesbrough, which defines open innovation as the intentional use of external and internal knowledge flows to accelerate your own innovation.

Why Learn: Understanding the theoretical foundation helps you defend the strategy internally and choose the right mechanisms for openness.

Key concepts: outside-in vs. inside-out, coupled model, IP licensing, spinoffs, R&D joint ventures.

What it is: How to structure and run startup acceleration programs for corporations: selection, mentoring, PoCs, and investment or acquisition potential.

Why Learn: Well-designed corporate accelerators provide access to emerging technologies 3-5 years ahead of the competition.

Key concepts: corporate accelerator, PoC (proof of concept) with a real budget, selection criteria, managing startup vs. corporation expectations, corporate venture.

What it is: Company-university partnership models for applied research, master’s and doctoral theses guided by business problems, and technology transfer.

Why Learn: University partnerships provide access to cutting-edge research at marginal cost, with the possibility of exclusive rights to the results.

Key concepts: shared intellectual property, academic NDA, EMBRAPII, commissioned research, researcher in residence.

What it is: Structure and operation of a corporate venture capital arm: when it makes sense, how to structure the fund, investment thesis criteria, and portfolio management.

Why Learn: CVC is one of the most powerful open innovation tools, but it requires clear governance and a clear mandate so it doesn’t become “strategic investment without a strategy.”

Key concepts: strategic vs. financial return, deal flow, portfolio diversity, follow-on investment, right of first refusal in M&A.

What it is: How to manage the culture clash between startup speed and corporate processes, protecting the startup from being stifled by bureaucracy.

Why Learn: Most PoCs fail not because of a lack of technology, but because of an inability to navigate a corporation's internal processes.

Key concepts: dedicated internal sponsor, fast-track procurement, simplified NDA, clear definition of success criteria before the PoC.

What it is: How to position yourself and get value from regional innovation ecosystems (such as Porto Digital, Cubo, CESAR, Tecnosinos) and international ones (Silicon Valley, Tel Aviv, Berlin).

Why Learn: Being part of an active ecosystem multiplies access to talent, startups, capital, and trends ahead of the curve.

Key concepts: anchor company, innovation hub, presence at key events, strategic community sponsorship, corporate residency program.

What it is: James March’s seminal framework (1991) on the tension between exploring new knowledge (exploration) and deepening what you already know how to do well (exploitation).

Why Learn: Companies that only explore die from inefficiency; those that only exploit die from irrelevance. Balance is the core competency.

Key concepts: competency trap, success trap, organizational learning, dynamic capabilities, adaptive capacity.

What it is: A model that physically separates exploration and exploitation units, with different metrics, processes, cultures, and leadership, integrated at the top.

Why Learn: When a culture of exploration and exploitation coexist on the same team, exploitation always wins—it’s more urgent and easier to measure.

Key concepts: internal spin-off, separate lab, independent P&L, C-level integration, different success metrics by unit.

What it is: An alternative model in which the same people switch between exploitation and exploration depending on the context, without rigid structural separation.

Why Learn: For smaller companies or those that can't create separate units, contextual ambidexterity is the practical way to innovate without paralyzing the core business.

Key concepts: 20% time (Google), alternating rules, context switching cost, "day job + innovation," leader’s calendar design.

What it is: How CEOs and C-level executives manage the tension between exploration and exploitation: agenda allocation, signaling priorities, and arbitrating conflicts.

Why Learn: Without ambidextrous leadership, the most urgent issue always kills the important one. The CEO is the only person who can protect exploration from short-term pressures.

Key concepts: CEO as chief ambidexter, calendar allocation (where does the CEO spend their time?), board discussion portfolio, innovation storytelling for Wall Street.

What it is: How to create two coexisting measurement systems—one for the current business (results) and another for the new business (learning and validated hypotheses).

Why Learn: Applying mature-business metrics to exploration is fatal. An internal startup can’t be evaluated by EBITDA in year 1.

Key concepts: dual dashboard, leading vs. lagging indicators, innovation accounting (Ries), discovery vs. delivery metrics.

What it is: Analysis of real cases of successful ambidexterity: Amazon (AWS as exploration), Apple (iPhone while selling iPod), Natura (open innovation alongside its cosmetics core).

Why Learn: Concrete cases translate abstract concepts into repeatable practical decisions.

Key concepts: Amazon’s model for new initiatives (Working Backwards), Apple as a platform company, Natura Startups, Magazine Luiza, and its digital ecosystem.

What it is: How to use generative and analytical AI to accelerate trend research, competitor analysis, weak signal mapping, and market insight generation.

Why Learn: Manual research that used to take weeks now takes hours. Innovators who use AI at this stage have a structural speed advantage.

Key concepts: AI-powered horizon scanning, trend clustering, signal vs. noise, automated patent analysis, synthetic research participants.

What it is: Techniques for using LLMs as brainstorming partners, expanding ideas, identifying contradictions, offering constructive criticism, and drawing cross-industry analogies.

Why Learn: AI doesn't replace human creativity, but it eliminates the blank page problem and expands the solution space explored.

Key concepts: expansion prompts, diverge-converge with AI, SCAMPER+LLM, steelman critique, automated morphological analogy.

What it is: How AI shortens the prototyping cycle: generating mockups, simulating personas, running synthetic hypothesis tests, and quickly analyzing user feedback.

Why Learn: Prototyping that used to take days now takes hours. Whoever validates faster learns more and invests less in the wrong directions.

Key concepts: AI-generated wireframes, synthetic user testing, hypothesis vs. real data (when AI isn’t enough), pair testing with AI + a real user.

What it is: How to use AI to automate program management tasks: proposal screening, progress reports, mentor matching, portfolio analysis.

Why Learn: An innovation manager who uses AI for operational tasks frees up 30-40% of their time for what really matters: facilitating and making decisions.

Key concepts: AI-assisted proposal scoring, automated progress reports, mentor-project matching, automated portfolio dashboard.

What it is: The real risks of using AI in innovation processes: amplified confirmation bias, homogenized ideas, dependence on historical data, and IP and privacy issues.

Why Learn: Using AI without understanding its limits creates a false sense of security and leads to decisions based on outputs that seem reliable but aren’t.

Key concepts: AI confirmation bias, idea homogenization, hallucinations in critical contexts, intellectual property of outputs, data sovereignty.

What it is: How to build AI fluency on the innovation team: a learning path, essential tools, a culture of experimentation, and adoption measurement.

Why Learn: It's not enough to have access to the tools — the team needs to know when and how to use them to deliver real value, not just novelty.

Key concepts: AI fluency ladder, tools for each stage of the process, “AI office hours,” adoption and impact measurement, AI community of practice.

What it is: Analysis of Amazon’s innovation system—Working Backwards, two-pizza mechanisms, 6-pagers, Leadership Principles—as a coherent set of practices.

Why Learn: Amazon is the most studied case of systematic innovation. Understanding the whole system is more useful than copying isolated practices.

Key concepts: Internal Press Release, Two Pizza Teams, 6-pager, Day 1 culture, customer obsession as an operating principle.

What it is: Comparison of two Brazilian cases: Nubank (a startup that became an innovative incumbent) and Magazine Luiza (an incumbent that transformed into a technology company).

Why Learn: Brazilian case studies show what works in the local cultural, regulatory, and economic context—more applicable than American case studies as-is.

Key concepts: platform shift (Magalu), localized customer obsession, Nubank engineering culture, scale with low marginal cost.

What it is: Analysis of emblematic failures—Kodak, Nokia, GE Digital—and the common patterns that led each to miss obvious innovation opportunities.

Why Learn: Learning from others’ failures is cheaper than learning from your own. The patterns repeat and can be avoided.

Key concepts: innovator's dilemma (Christensen), organizational inertia, incumbency trap, protecting the existing business at the cost of the future.

What it is: How large incumbents have led successful digital transformations: DBS Bank (banking), Haier (industrial), Natura (FMCG).

Why Learn: Digital transformation without an innovation culture fails. These cases show how culture and technology need to change together.

Key concepts: digital first vs. digital only, culture change before tech change, micro-enterprise model (Haier), platform vs. product.

What it is: Methodology for systematically documenting and learning from internal innovation projects—both successes and failures.

Why Learn: Without structured documentation, learning stays in people’s heads and leaves when they do. The case study turns experience into organizational capital.

Key concepts: internal case template, after-action review, blameless postmortem, innovation library, storytelling for internal dissemination.

What it is: Synthesis of the elements that consistently appear in successful innovation programs: sponsorship, mandate, iteration, learning from failure, and selective scaling.

Why Learn: Identifying the invariants helps you replicate what matters and avoid wasting time copying what is incidental to the case context.

Key concepts: pattern matching vs. cargo culting, principles vs. practices, what to adapt vs. what to preserve, innovation maturity assessment.

What it is: The fundamental difference between evaluating optimization projects (classic ROI) and innovation projects, where value is uncertain, payback takes longer, and risk is asymmetric.

Why Learn: Applying classic ROI to innovation kills H2 and H3 before they have a chance. Understanding the difference is a prerequisite for defending the portfolio.

Key concepts: real option value, uncertainty vs. risk, expected value with a fat-tail distribution, cost of not innovating.

What it is: Eric Ries’s framework for measuring progress in startups and innovation: define the baseline, tune the engine, and pivot or persevere based on learning metrics.

Why Learn: Innovation accounting brings financial language to conversations about uncertain innovation, allowing you to defend it rigorously without using the wrong ROI.

Key concepts: learning milestones, actionable vs. vanity metrics, cohort analysis, hypothesis baseline, unit economics metrics in the early stages.

What it is: How to structure an innovation portfolio dashboard with different metrics for each horizon: H1 (financial results), H2 (traction and growth), H3 (learning and hypotheses).

Why Learn: A single dashboard with H1 metrics kills H3. Stakeholders need visibility appropriate to each type of initiative.

Key concepts: portfolio dashboard, stage-appropriate metrics, innovation funnel (ideas → concepts → pilots → scale), reporting to the board.

What it is: How to quantify and communicate innovation's strategic value (future positioning, reduced disruption risk, talent attraction) beyond direct financial value.

Why Learn: Innovation that doesn't fit the financial ROI may still have enormous strategic value. Knowing how to articulate it is essential to defending the portfolio.

Key concepts: strategic option value, risk-adjusted value creation, competitive moat building, talent attraction premium, call option on the future.

What it is: Financial storytelling techniques for presenting the value of the innovation program to financial audiences who think in terms of payback period and EBITDA.

Why Learn: Finance speaks a different language from innovators. Translating correctly is what secures the budget for the next cycle.

Key concepts: analogy with R&D (% of revenue), market benchmark, opportunity cost of not innovating, phased payback (real options), TAM projection.

What it is: Systematic process for reviewing the innovation portfolio and deciding which initiatives should be ended, accelerated, pivoted, or maintained at their current pace.

Why Learn: A portfolio that never kills anything becomes a graveyard of zombie projects that consume resources and attention without delivering value.

Key concepts: quarterly portfolio review, kill criteria (not learning), acceleration criteria, zombie project, portfolio concentration vs. diversification.

What it is: A precise definition of scaling in innovation: increasing impact while preserving the essence of the validated model, versus merely expanding geographically or in volume without learning.

Why Learn: Many initiatives scale before validating the model, consuming enormous resources to discover problems that a smaller pilot would have revealed.

Key concepts: premature scaling (the #1 cause of startup failure), product-market fit before scaling, healthy unit economics, growth vs. scaling.

What it is: Structured process for transitioning from pilot to scale: go/no-go criteria, phased scale-up plan, transition risk management, integration with the core business.

Why Learn: The transition from pilot → scale kills more initiatives than the pilot itself. It’s the most neglected phase of innovation programs.

Key concepts: scale-up criteria, phased rollout, integrated change management, handover to operations, preservation of the DNA that worked.

What it is: How to manage resistance and adoption as an innovation expands from the pioneering team to the entire organization.

Why Learn: Technical innovations scale easily; organizational innovations face cultural resistance. Without change management, the rollout fails.

Key concepts: innovation adoption curve (Rogers), early majority as a realistic scaling target, change champions, communication of “what changes for me?”, resistance as data.

What it is: The organizational enablers needed to scale: technology, processes, people, structure, and governance that support rapid growth without collapse.

Why Learn: Scaling without infrastructure is like building on sand—the initiative grows until the structure breaks.

Key concepts: technical debt management, process standardization without bureaucratization, scaling hiring plan, API-first integration, architectural modularity.

What it is: How to preserve the values and behaviors that made the initiative work as the team grows from 5 to 50 to 500 people.

Why Learn: Culture dilution is the biggest scaling risk. What worked with 10 people is often lost with 100 without active management.

Key concepts: culture carriers, hiring as a culture gate, rituals that scale, documenting the “why,” not just the “how,” leadership as a cultural example.

What it is: Which metrics to track during the scaling process to identify bottlenecks, adoption issues, and deviations from the original model before they become irreversible.

Why Learn: Scaling without monitoring is like driving in the dark. Problems detected early cost 10x less to fix than after they become the norm.

Key concepts: adoption rate by segment, innovators’ NPS, time-to-value in the rollout, defection rate (who returns to the old way), impact on business KPIs.

What it is: How to structure the innovation committee: membership, meeting frequency, standard agenda, decision criteria, and the committee's formal authority.

Why Learn: A poorly structured committee becomes bureaucracy that slows everything down. A well-structured committee is the portfolio’s main accelerator.

Key concepts: ideal composition (CEO, CFO, CHRO, innovation lead), monthly vs. quarterly meetings, portfolio review agenda, authority to kill/fund, decision minutes.

What it is: A framework of objective criteria for deciding when to end an innovation initiative, distinguishing a genuinely dead project from one that needs more time.

Why Learn: Ending initiatives early is one of the most valuable skills — it frees up resources for better initiatives and avoids the emotional and financial cost of zombie projects.

Key concepts: kill criteria vs. success criteria, sunk cost fallacy, falsified vs. untested hypothesis, pivot as an alternative to kill, how to communicate the shutdown.

What it is: Structure of the innovation funnel with clear stages — idea, concept, MVP, pilot, scale — and transition gates between each phase with the required criteria and resources.

Why Learn: Without a visible funnel, the portfolio looks like a black box to stakeholders. A clear funnel sets realistic expectations and enables proactive management.

Key concepts: conversion rate by stage, average time per step, investment escalation by phase, funnel as a communication tool with the board.

What it is: A minimal set of policies that enable innovation without creating bureaucracy: intellectual property policy, use of exploration budget, confidentiality rules, failure policy.

Why Learn: A lack of clear policies creates fear of acting. Excessive policies create paralysis. The minimum necessary is the sweet spot.

Key concepts: “celebrated failure policy” (vs. tolerated), IP ownership framework, simplified expense policy, internal NDA, autonomy with accountability.

What it is: Mapping innovation governance roles: Innovation Lead, Portfolio Manager, Project Sponsor, Committee, and how each relates to the others.

Why Learn: Overlapping roles cause conflict and slow things down. Gaps lead to initiatives with no owner. Role clarity is a prerequisite for speed.

Key concepts: Innovation RACI, separation of powers (who proposes vs. who approves), decision escalation, accountability vs. responsibility.

What it is: How to create transparency around the innovation portfolio for different audiences—teams, middle management, C-level, and the board—without exposing sensitive information prematurely.

Why Learn: Transparency drives engagement. Opacity creates distrust. The right level of openness differs for each audience.

Key concepts: portfolio page (one page with the status of everything), monthly innovation update, narrative of completed projects, show-and-tell of learnings.

What it is: Etienne Wenger's concept of a community of practice: a group of people who share an interest in an area and deepen their knowledge through ongoing interaction.

Why Learn: Communities of practice spread an innovation culture virally and organically, much faster than formal training.

Key concepts: three elements (domain, community, practice), legitimate peripheral participation, shared tacit know-how, community vs. team vs. network.

What it is: Step by step, here's how to create an internal innovation community of practice: identify the initial core group, define the domain, create meeting rituals, and generate value for members.

Why Learn: CoPs that don’t deliver value to members die within 3 months. Well-nurtured CoPs last for years and become the backbone of the culture.

Key concepts: core vs. periphery, regular meetings (the right cadence), value for members vs. value for the company, content curation, distributed leadership.

What it is: Catalog of proven rituals for innovation communities: demo days, lightning talks, kill-a-project workshops, failure friday, innovation newsletter.

Why Learn: Rituals create a sense of belonging and provide context for informal learning, which research in L&D shows is more powerful than formal training.

Key concepts: the right cadence for each type of ritual, voluntary vs. mandatory participation, what not to do (mandatory meetings with no value), a culture of intellectual generosity.

What it is: How to capture and share the knowledge generated by the community: an internal wiki, case library, newsletter, messaging channel, and onboarding system for new members.

Why Learn: Knowledge stored in people’s heads disappears when they leave. Active management turns human capital into lasting organizational capital.

Key concepts: tacit vs. explicit knowledge, internal knowledge base, onboarding new members, knowledge curator, "bus factor" of a CoP.

What it is: How to identify, train, and support innovation ambassadors across different areas of the company who spread the culture and serve as local points of contact for the central program.

Why Learn: A central program cannot reach the entire company. Ambassadors are innovation’s “last mile”—they take the message where the program cannot reach.

Key concepts: selection criteria (informal influence, not job title), ambassador kit, ambassador network, recognition and support, rotation to refresh the group.

What it is: How to measure the real impact of a community of practice: engagement, spread of practices, time to adopt new concepts, member NPS, and influence on the portfolio.

Why Learn: Communities are diffuse by nature. Without measurement, it’s impossible to defend the investment and identify what’s working.

Key concepts: community health metrics, social network analysis (who talks to whom), diffusion of practices measured by adoption, quarterly NPS among members.

What it is: How generative AI is becoming basic infrastructure for innovation—not a specific tool, but a layer that enables all the other tools and processes.

Why Learn: Companies that treat AI as a productivity tool lose to those that use it to reinvent their business model.

Key concepts: AI-native company, foundation models as a platform, marginal cost of experimentation tending toward zero, democratized access to the ability to innovate.

What it is: The trend of moving innovation from centralized hubs to the entire organization, enabled by low-code tools, AI, and methods accessible to non-specialists.

Why Learn: Distributed innovation multiplies the capacity to innovate without growing the core team — anyone with access to the right tools can be an innovator.

Key concepts: citizen innovator, low-code innovation, embedded innovation vs. central lab, federation model; the central team’s role shifts from doing to enabling.

What it is: How the ESG and positive impact agenda is becoming a driver of innovation—not just a regulatory constraint, but a source of new business models and competitive advantage.

Why Learn: Companies innovating for sustainability are creating the business models of the next decade. Those that ignore it are creating strategic liabilities.

Key concepts: innovation for good, circular economy models, corporate social innovation, B impact assessment, sustainability as a product feature vs. compliance.

What it is: How the innovation cycle is structurally accelerating—and what companies need to change in their structure, processes, and culture to compete at the new speed.

Why Learn: Competitive advantage used to last decades. Today it lasts years or months. Those who don't learn how to learn quickly lose to those who do.

Key concepts: time-to-learn as a core metric, organizational clock speed, compressing the validation cycle, continuous discovery as an ongoing practice.

What it is: How the innovation professional's role is evolving: from workshop facilitator to innovation systems architect, AI integrator, and portfolio manager.

Why Learn: The market will increasingly reward professionals who deliver systematic results, not just enthusiasm for innovation.

Key concepts: innovation architect, T-shaped + AI fluency, portfolio thinking, influence without authority, ability to move between strategy and execution.

What it is: A framework for building a personal innovation agenda: what to learn next, how to stay up to date, how to build your reputation in the ecosystem, and how to plan your next career moves.

Why Learn: The course ends, but the journey continues. Those with a continuous learning routine pull ahead of those who only apply what they learned yesterday.

Key concepts: personal learning agenda, communities to join, how to write about and share what you learn, reverse mentoring, practical next steps.