Agile Strategy (Roger Martin in conversation with Sohrab Salimi)

Introduction to Roger Martin

In this section, the speaker introduces Roger Martin, an author and expert in strategy. They mention his book "Playing to Win" and discuss his upcoming book "A New Way to Think."

Roger Martin's Background

• Roger Martin is the author of several books on strategy.

• He wrote "Playing to Win," which is considered a defining book on strategy.

• The speaker mentions that last year they spoke to him about his book "When More is Not Better."

• Roger has a background in academia and business consulting.

• He co-founded Monitor Company and later became the dean of the Rotman School of Management at the University of Toronto.

Roger Martin's Experience with Strategy

In this section, Roger Martin shares more about his experience with strategy and his passion for writing and advising on the topic.

Academic and Consulting Career

• Roger got interested in strategy during his time at Harvard Business School.

• He worked closely with Michael Porter, who was known for publishing competitive strategy concepts.

• To meet the demand for Porter's ideas, they formed Monitor Company.

• Later, he became the dean of the Rotman School of Management at the University of Toronto.

Current Focus

• After retiring from academia, Roger now focuses on writing and advising senior executives on strategy.

• He describes himself as a "strategy geek" who loves writing about it.

• His book "When More is Not Better" takes a holistic view of sustainability in organizations.

Linking Sustainability and Strategy

In this section, the speaker discusses how sustainability relates to strategy and highlights agile methodologies' embedded sense of sustainability.

Holistic Sustainability

• The speaker mentions that "When More is Not Better" emphasizes sustainability in a holistic way.

• Environmental sustainability is crucial, but it's not the only aspect to consider.

• The speaker finds agile methodologies attractive because they inherently promote sustainability.

• They mention that sustainable relationships with clients and avoiding unnecessary rework are essential elements of sustainability.

Taking a Holistic Approach to Strategy

In this section, the speaker emphasizes the importance of thinking holistically about strategy and considering the benefit of all players in the system.

Holistic Thinking

• The speaker encourages thinking holistically about strategy for long-term benefits.

• They mention that strategies should focus on creating sustainable relationships and avoiding short-term advantages.

• The goal is to benefit all players in the system rather than just seeking individual advantage.

Taking a Full Stakeholder Perspective

In this section, Roger Martin discusses the importance of taking a full stakeholder perspective rather than just focusing on shareholders.

• Strategy should consider the interests of all stakeholders, not just shareholders.

• It is important to balance the needs and expectations of different stakeholders in strategic decision-making.

Agile and Strategy Development

Roger Martin talks about his article on agile and strategy development and how it relates to his framework.

• Roger publishes an article every week on strategy, including one about agile and strategy development.

• The show notes will provide links to the articles for further reading.

• To find Roger's articles, search for "Roger Martin" on Medium.

Strategy in General: Myths and Perspectives

Roger shares his perspective on strategy in general, debunking some common myths and discussing how he approaches strategy.

• Many organizations have a bureaucratic view of strategy through strategic planning.

• Strategic planning often focuses on defining initiatives rather than making choices.

• Strategy is about making integrated choices that position a company for superior value delivery.

• A company's actual strategy may differ from what is stated in its strategic plan.

• Strategy should be based on actions taken, not just words or posters.

Importance of Strategy in Fast-Paced Environments

Roger discusses the importance of strategy in fast-paced environments where change is rapid.

• Due to the fast pace of change, many organizations neglect developing a good strategy.

• Some organizations rely on external consultants to develop their strategies.

• Roger emphasizes that everyone is doing strategy whether they realize it or not.

• CEOs play a crucial role in shaping and implementing the organization's strategy.

Reverse Engineering Current Strategy

Roger explains his approach to advising organizations on strategy by reverse engineering their current strategy.

• Reverse engineering involves understanding the choices that led to current actions.

• The goal is to migrate towards a more competitive and sustainable strategy.

• Making real choices and aligning actions with those choices is essential for effective strategy.

Challenges in Strategy Development

Roger discusses the challenges organizations face in developing and implementing effective strategies.

• The fast pace of change poses challenges for both startups and larger organizations.

• Many executives claim they don't have time for strategy, but it is crucial.

• CEOs are responsible for driving the strategic direction of the organization.

• External consulting firms may not always provide the best strategies.

Importance of CEO's Role in Strategy

Roger emphasizes the importance of CEOs in shaping and driving the organization's strategy.

• CEOs are ultimately responsible for setting the strategic direction of the company.

• They should actively participate in strategy development rather than delegating it entirely to consultants or other team members.

The Importance of Thoughtful Decision-Making

In this section, the speaker emphasizes the importance of being thoughtful about strategic decisions and highlights the need to consider the impact of choices on overall results and aspirations.

Making Strategic Choices

• Being thoughtful about strategic decisions is crucial for achieving great results.

• Treating each decision as independent from others can lead to mediocre outcomes.

• It is important to evaluate the gap between desired aspirations and current results.

• Identifying problems and making a different set of choices can help bridge this gap.

Strategy as Problem-Solving

The speaker explains that strategy is not just about long meetings or separate activities but rather a problem-solving technique. They emphasize the need to make different choices to avoid repeating ineffective strategies.

Strategy as Problem-Solving

• Strategy should focus on solving the organization's biggest problem.

• Insanity is doing the same thing and expecting different results.

• Making a different set of choices is essential for positive and productive outcomes.

• Strategy should be integrated into daily operations for better alignment and effectiveness.

Balancing Time for Strategy

The speaker discusses the challenge of finding time for strategy as a CEO. They highlight the importance of consciously investing time in making better choices aligned with organizational aspirations.

Balancing Time for Strategy

• As a CEO, it's crucial to find time for strategy, whether conscious or not.

• Daily actions should align with key challenges and organizational aspirations.

• Investing time in strategy ensures better decision-making on a daily basis.

Aligning Aspirations with Where to Play & How to Win

The speaker emphasizes the importance of aligning aspirations with strategic choices and highlights the need to toggle between aspirations, where to play, and how to win decisions for effective strategy.

Aligning Aspirations with Strategic Choices

• Many aspirations may be unrealistic or inconsistent with organizational capabilities.

• Toggling between aspirations, where to play, and how to win decisions is crucial.

• Start by identifying what the organization would love to become before crafting a vision.

• Align daily activities with the aspiration to bridge the gap between strategy and operations.

New Section

In this section, the speaker discusses the limitations of linear thinking in strategy and emphasizes the importance of an iterative approach.

The Limitations of Linear Thinking

• The technocrats who dominate strategy tend to be too linear in their thinking.

• Linear thinking involves checking off boxes and creating constraints along the way.

• This approach makes it less likely to come up with innovative and effective strategies.

Embracing an Iterative Approach

• The speaker advocates for a more iterative strategy development process.

• Instead of following a linear checklist, one should circulate around different aspects of strategy.

• Start with an aspiration, then consider where to play and how to win.

• Continuously go back and forth between these elements, modifying as necessary based on feedback.

New Section

In this section, the speaker explains the importance of building necessary capabilities and management systems to support winning strategies.

Building Necessary Capabilities

• After determining where to play and how to win, it is crucial to assess if the organization has the required capabilities.

• If not, consider modifying the strategy or finding ways to build those capabilities.

Management Systems

• Effective management systems are essential for supporting winning strategies.

• It is important to evaluate if existing management systems align with the chosen strategy or if modifications are needed.

New Section

In this section, the speaker discusses feedback loops in strategy development and highlights their alignment with incremental and iterative approaches in product and organizational development.

Feedback Loops in Strategy Development

• Strategy development involves continuous feedback loops between different elements such as aspiration, where to play, how to win, etc.

• Decisions made based on these elements may lead to actions like running experiments or assessments.

Incremental and Iterative Approach

• The speaker emphasizes the alignment of feedback loops in strategy development with incremental and iterative approaches.

• This approach is commonly used in product development and organizational development within the agile space.

New Section

In this section, the speaker addresses concerns about making long-term decisions in a fast-moving environment and explores the connection between playing to win framework and agility.

Long-Term Decision Making

• Contrary to popular belief, many decisions made by organizations have long-term impacts.

• Examples include choosing an ERP system or adopting a specific technology platform.

• It is important to recognize the long-term implications of decisions even in a fast-paced environment.

Modifiability and Agility

• In volatile, uncertain, complex, and ambiguous (VUCA) environments, strategies should be modifiable.

• Strategies should allow for iteration, feedback, and modification based on changing circumstances.

• While some choices may be irreversible, it is crucial to consider how much flexibility is built into the strategy.

New Section

In this section, the speaker discusses how good strategies involve making bets while considering industry dynamics and aligning with clients' needs.

Making Bets in Strategy

• Good strategies require making choices that may box an organization into a particular direction.

• These choices are often necessary for success but should align with industry dynamics and client needs.

Industry Dynamics

• The speaker mentions Salesforce's decision not to sell licenses as an example of a strategic choice aligned with software-as-a-service (SaaS) industry dynamics.

• Strategies need to adapt to changes in the industry landscape.

New Section

In this section, the speaker provides insights on time frames for strategy development and connecting playing to win framework with agility principles.

Time Frames for Strategy Development

• The speaker acknowledges that time frames for strategy development may vary across industries.

• It is important to consider the specific context and dynamics of each industry when determining time frames.

Connecting Playing to Win with Agility

• The speaker is interested in exploring how the playing to win framework aligns with agility principles and values.

• Specifically, they want to understand how the framework connects with agile ways of working beyond specific frameworks like Scrum.

Challenges of Building a Copper Mine

The speaker discusses the challenges and timeframes involved in building a copper mine.

Timeline for Copper Extraction

• Negotiations with stakeholders in Latin America and Asian countries can take several years.

• Infrastructure development and other preparations may require 15 to 20 years.

• The actual extraction of copper may not begin until 20 to 50 years after the initial decision to build the mine.

• Billions of dollars, possibly around $10 billion, need to be invested in the project.

Importance of Cost Position

• The cost position of the mine is crucial for long-term profitability.

• A high-cost mine may struggle during periods of low copper prices, potentially leading to bankruptcy.

• Being the lowest-cost producer can result in significant profits when copper prices are favorable.

Agile Execution and Strategy Creation

The speaker explores the relationship between agile execution and strategy creation, highlighting similarities and potential gaps.

Agile as a Reaction Against Technocracy

• Agile methodologies originated as a response to increasing technocracy in software development.

• It emphasizes iterative processes, customer involvement, and organic approaches rather than rigid planning.

Strategy as a Revolt Against Technocracy

• The speaker's view of strategy aligns with agile principles as both reject technocratic approaches.

• Traditional strategy development often involves lengthy meetings, ranking initiatives without iteration.

• Engaging customers throughout the process is essential for successful outcomes.

Summary

The transcript covers two main topics. Firstly, it discusses the challenges associated with building a copper mine, including negotiation timelines, infrastructure development requirements, and cost considerations. Secondly, it explores the relationship between agile execution and strategy creation. Both topics highlight the importance of customer involvement and iterative processes.

Agile vs Decision Making

In this section, the speaker discusses the similarities and differences between agile methodology and decision-making processes.

Attitudinal Similarity between Agile and Decision Making

• The speaker believes that there is an attitudinal similarity between being agile and making decisions.

• Agile originated in software development but has now expanded to other areas, while decision-making focuses on determining what a company should or should not do.

• Despite their different purposes, the mindset behind both approaches is nearly identical.

Revolt Against Technocracy

• The agile movement can be seen as a revolt against technocracy.

• It challenges the mechanistic view of the economy and organizations, which assumes that specific actions will always yield predictable outcomes.

• However, in reality, things are much more complex than this mechanistic perspective suggests.

Arrogance in Technocratic Approach

• The speaker criticizes the arrogance associated with the technocratic approach.

• He mentions an economist named Leontief who won a Nobel Prize for his input-output models of the US economy.

• Leontief's models claimed to accurately predict how different sectors of the economy interacted, which the speaker finds overly presumptuous.

Complexity of Adaptive Systems

• The speaker emphasizes that it is impossible to fully understand and predict how complex adaptive systems work.

• He argues against assuming that equations can accurately describe such systems.

• Making choices in an uncertain world requires acknowledging uncertainty and continuously adjusting based on feedback.

Making Choices in Strategy

• The speaker highlights that making choices is inevitable, even in an uncertain world.

• Not making a choice is still a choice itself.

• It is better to consciously make choices based on what would have to be true for them to be good choices and adjust if necessary.

Adjusting and Agile Mindset

• Both decision-making and agile methodologies require continuous adjustment.

• People who are accustomed to a technocratic approach may find this adjustment process scary and uncomfortable.

• However, once they understand the benefits of adjusting and shortening odds of success, they become more comfortable with it.

Agile Mindset in Strategy

In this section, the speaker further explores the agile mindset in the context of strategy.

Making Bets and Shortening Odds

• The speaker suggests that strategy is about making bets and shortening odds of success.

• Rather than aiming for absolute certainty, it is about increasing the chances of success by continuously adjusting and adapting.

Comfort with Adjustments

• People who embrace an agile mindset in strategy are comfortable with adjustments.

• They understand that changes are inevitable and see them as opportunities for improvement rather than disasters.

Agile Approach in Software Development

• The speaker discusses how an agile approach to software development handles change requests from customers.

• Instead of considering changes as disasters or setbacks, agile practitioners view them as part of life's unfolding nature.

• They inspect and adapt to changes, ensuring that they align with customer needs.

Complexity and Arrogance

This section delves into the complexity of systems and criticizes arrogance in assuming complete understanding.

Complexity Beyond Predictability

• The speaker emphasizes that systems are much more complex than can be predicted or understood fully.

• This complexity applies to both software development and decision-making processes.

Technocratic Arrogance

• The speaker criticizes the arrogance associated with a technocratic approach.

• He believes that claiming complete understanding or predicting outcomes accurately is overly presumptuous.

Making Choices in Uncertainty

In this section, the speaker discusses the importance of making choices in an uncertain world.

Making Choices in Uncertainty

• The speaker acknowledges that making choices in an uncertain world is challenging.

• Not making a choice is still a choice, and it is better to consciously make choices based on what would have to be true for them to be good choices.

Adjusting Based on Feedback

• Continuous adjustment is crucial when making choices in uncertainty.

• If the things that would have to be true for a choice to be good are not aligning with reality, adjustments should be made accordingly.

Agile and Adjustments

This section explores the relationship between agile methodologies and continuous adjustments.

Making Choices and Admitting Error

• Making choices in an uncertain world does not guarantee being absolutely right.

• However, not making choices or refusing to admit error is also problematic.

• It is better to make conscious choices and adjust based on feedback rather than avoiding decisions altogether.

Consistency with Agile Methodologies

• The speaker believes that this approach aligns with agile methodologies' principles of continuous adjustment and adaptation.

• Agile practitioners understand the need for constant refinement and are comfortable with it.

Embracing Change Requests

In this section, the speaker discusses how change requests are handled within agile methodologies.

Disruptive Nature of Change Requests

• The speaker highlights how change requests can disrupt predefined plans or processes.

• In traditional approaches like waterfall, changes are often seen as disruptions because they were not expected or accounted for.

Expecting Changes in Agile Methodologies

• Agile methodologies embrace change as part of the process.

• Unlike traditional approaches, they anticipate changes and incorporate them into ongoing development initiatives.

Defined Approach vs. Change Requests

This section contrasts the defined approach with agile methodologies in terms of handling change requests.

Disruption of Defined Approach

• The speaker points out that change requests disrupt predefined plans and processes.

• In a defined approach, changes are not expected or accounted for, leading to disruptions when they occur.

Agile Methodologies and Change Management

• Agile methodologies, on the other hand, embrace change management as an integral part of the process.

• They anticipate and accommodate change requests, allowing for flexibility and adaptation throughout development initiatives.

New Section

In this section, the speaker discusses the importance of not being arrogant when predicting the future and emphasizes the need for logical thinking and feedback loops in decision-making.

Predicting the Future and Arrogance

• The speaker highlights that some people can be arrogant when trying to predict the future.

• It is important to acknowledge that one cannot accurately predict the future.

• Spending more time and doing detailed analysis does not guarantee accurate predictions.

Analysis Paralysis and Logical Thinking

• Getting trapped in analysis paralysis is a choice that hinders progress.

• Instead of over-analyzing, it is better to make a choice based on available information and logic.

• Feedback loops should be implemented to evaluate whether choices were good or not.

• If needed, adjustments can be made based on new information gathered from actions taken.

Two Types of Analysis: Market Evaluation vs. Logical Thinking

• There are two types of analysis: market evaluation (time-consuming and cost-intensive) and logical thinking.

• Logical thinking involves considering current and future business aspects in a rational manner.

• Decisions can be made based on logical thinking while still allowing for evaluation.

Balancing Logic and Action in Agile Space

• Some people in agile space tend to avoid making decisions, leading to indecisiveness.

• Making no decision is also a decision itself.

• It is essential to find a balance between taking action based on logic and avoiding excessive analysis.

New Section

In this section, the speaker expands on their perspective regarding analysis. They differentiate between logical structure and data-driven analysis, emphasizing the importance of having logic behind choices.

Analysis as Logical Structure with Data Application

• Analysis is not just a single thing but can be divided into two components: logical structure and data application.

• Logical structure provides a framework for applying data.

• For example, the logical structure may suggest that bigger factories have lower costs due to spreading fixed costs across production units.

Adding Data to Logical Structure

• To perform analysis, data is added to the logical structure.

• In the example of factory costs, one would gather data from various plants of different sizes to determine if costs are indeed lower in larger plants.

Logic Behind Choices

• The speaker emphasizes that there should always be logic behind choices, regardless of the amount of analysis conducted.

• Successful entrepreneurs often rely more on logical thinking than extensive analysis.

• Logic-based decisions challenge established players and can lead to disruptive innovations.

Logic vs. Analysis in Different Contexts

• The level of analysis required depends on the context.

• Large publicly traded companies with shareholders and boards require more analysis due to their conservative nature.

• Entrepreneurs can rely more on logic as they have greater freedom to take risks and make decisions based on their own reasoning.

Balance Between Data and Situation

• Finding a balance between available data and situational context is crucial in business strategy.

• It is important to assess how much data is needed and how much connection should be made based on the situation at hand.

New Section

In this section, the speaker discusses their approach when dealing with clients. They prioritize understanding the logic behind choices rather than relying solely on financial projections or past successes.

Importance of Logic in Investment Decisions

• When investing in startups, the speaker focuses on understanding the logic behind their business model rather than relying solely on financial projections.

• Financial spreadsheets are considered speculative as they pertain to the future, which is uncertain.

Logic as a Prerequisite for Investment

• The speaker requires startups to explain their logic behind their "where to play" and "how to win" strategies.

• Financial projections and past successes are secondary considerations compared to the underlying logic.

Logic Over Financial Projections

• Even if a startup has impressive financial projections or a track record of success, without a solid logical foundation, it is unlikely to receive investment.

The Balance Between Data and Action

In this section, the speaker discusses the importance of finding a balance between relying on comprehensive data and taking action. They emphasize that waiting for complete proof before making a move can hinder progress.

Finding the Right Balance

• It is important to strike a balance between needing enough data and analytics to feel comfortable, but not insisting on comprehensive proof before taking action.

• Waiting for everything to be proven in advance can prevent you from doing anything.

• Being open to inklings and having some level of responsibility can help protect your interests.

Belief in Innovation

• Steve Jobs believed that when it comes to innovation, you need to believe in something before it becomes seeable.

• Many organizations require seeing data before believing in an opportunity, but innovations often come from believing in something without prior evidence.

• Jeff Bezos selling books online was not something people would have thought possible until he did it.

Acting Primarily on Logic

• When working in the field of innovation, it is necessary to make decisions based primarily on logic rather than waiting for comprehensive data analytics.

• Incremental steps can be taken along the way while acting primarily on logical reasoning.

Developing Logic for Innovation

In this section, the speaker explores where the logic for innovation comes from and how snippets of information and analogies play a role.

Drawing from Analogy

• Much of the logic for innovation comes from drawing analogies between different contexts or industries.

• Seeing something in one place and applying it to another can lead to innovative ideas.

Non-Comprehensive Data

• Innovation does not always rely on comprehensive data but can be driven by snippets of information.

• Steve Jobs found inspiration in calligraphy and applied that understanding to computer screen design.

• Johnny Ive's choice of colors for the iMac was influenced by a camera company's use of vibrant colors.

Developing Capacity for Innovation

• To innovate, one needs the ability to see how the same rules or principles can be applied in different contexts.

• Understanding human behavior and twisting existing rules can lead to new applications and innovations.

The Impact of Logic and Intuition

In this section, the speaker discusses how logic and intuition play a role in innovation.

Not Random, Not Deterministic

• The development of innovative ideas is not random but also not deterministic in a technocratic way.

• Johnny Ive's decision to introduce vibrant colors to computers was based on his observation of cameras with unique color choices.

Collaboration and Production

• Steve Jobs collaborated with Johnny Ive on the design of the iMac, which eventually went into production as one of Apple's signature pieces.

New Section

In this section, the speaker discusses the decision-making process and the importance of looking at patterns in human behavior to make strategic choices.

Why Aren't We Producing?

• The speaker mentions a conversation where they asked why they weren't producing something.

• The response was that their predecessor was unsure about the idea being too radical.

• This led to the decision not to pursue it further.

New Section

In this section, the speaker talks about the value of looking at patterns and rules of human behavior when making strategic choices.

Aiming for Patterns

• Instead of solely focusing on gathering large amounts of data, it is beneficial to analyze patterns in similar or different industries.

• These patterns can help inform strategic choices for an organization.

New Section

The speaker introduces two topics related to time: strategy and OKRs (Objectives and Key Results).

Strategy and OKRs

• The speaker refers to an article they wrote about strategy and OKRs.

• Many organizations claim to be agile and use OKRs, but there is a distinction between them.

• Strategy and OKRs are not the same thing.

New Section

The speaker shares their thoughts on OKRs and strategy, highlighting their differences and how they connect.

Thoughts on OKRs and Strategy

• Setting OKRs alone does not guarantee success in achieving objectives.

• There needs to be a logical connection between objectives, strategies, and key results.

• Simply firing people who don't meet key indicators without addressing underlying issues is not effective.

New Section

The speaker discusses their popular article on OKRs and strategy, sharing their observations and insights.

Observations on OKRs

• The speaker's article on OKRs gained significant attention.

• They observed a pattern of organizations setting OKRs but not achieving desired outcomes.

• Merely setting goals without a logical strategy behind them is insufficient.

New Section

The speaker emphasizes the importance of having a strategy that aligns with objectives to achieve key results.

Aligning Strategy and Objectives

• Objectives should be supported by a "where to play, how to win" strategy.

• Setting objectives without a feasible strategy will not lead to success.

• Silicon Valley's obsession with OKRs can perpetuate ineffective practices.

New Section

The speaker highlights the flaws in relying solely on OKRs and the need for a better approach.

Flaws in the OKR System

• Many organizations blame individuals for not achieving key results instead of questioning the effectiveness of their model.

• Simply replacing people who don't meet key results is not a sustainable solution.

• A better model involves defining key results after developing a viable strategy.

New Section

The speaker discusses their perspective on OKRs as part of an overall strategic approach.

OKRs and Strategy Compatibility

• OKRs are not inherently incompatible with strategy but are necessary yet insufficient on their own.

• Blindly following models without considering logic and reasoning will not yield desired outcomes.

New Section

The speaker emphasizes the importance of evaluating whether existing models produce desired results.

Evaluating Models

• It is crucial to assess whether current models are producing desired outcomes.

• Blaming individuals or constantly replacing them does not address underlying issues with the model itself.

• A new way of thinking involves questioning and improving existing models.

New Section

The speaker encourages a shift in mindset towards evaluating the effectiveness of models and seeking better alternatives.

Seeking Better Models

• Falling in love with models can lead to blaming external factors instead of questioning the model's efficacy.

• In the case of OKRs, blaming individuals for not achieving key results is common.

• A better approach involves examining the model itself and considering alternative strategies.

New Section

The speaker discusses their perspective on OKRs as part of an overall strategic approach.

Key Results and Strategy

• Key results should be defined based on a strategy that makes achieving them possible.

• Simply setting objectives without a logical strategy will not lead to success.

• OKRs are necessary but not sufficient for achieving desired outcomes.

New Section

The speaker compares overemphasizing agile practices without considering logic to ineffective outcomes.

Overemphasizing Agile Practices

• Overemphasizing agile practices without logical reasoning leads to ineffective outcomes.

• Blindly following methodologies without critical thinking hinders success.

• It is important to strike a balance between methodology and strategic thinking.

The Role of OKR Model in Organizations

In this section, the speaker discusses the role of the OKR (Objectives and Key Results) model in organizations.

The Technocratic Model of OKRs

• The speaker mentions that following the OKR model like a dogma can lead to it becoming a technocratic model.

• The technocratic model disregards feedback loops and focuses on determining objectives and expecting them to be executed without considering adjustments or learning from the process.

Integrating Objectives with Strategy

• The speaker emphasizes the importance of connecting objectives with the overall strategy and goals of an organization.

• They mention that "where to play" and "how to win" are two missing pieces that can be integrated into OKRs to align them with strategic planning.

Further Reading on OKRs

• The speaker refers to an article they wrote about integrating objectives with strategy, which gained significant readership.

• Interested individuals can refer to this article for more information on how to integrate objectives effectively.

Considerations for Transformation Initiatives

This section focuses on important considerations for transformation initiatives within organizations.

Four Important Points for Transformation

1. Clear Strategy: Having a clear strategy is crucial when embarking on a transformation journey.

2. Patience: Being patient is essential as transformations often take time and cannot be rushed.

3. Resilience: Building resilience is necessary as there will be challenges and setbacks along the way.

4. Growth: Emphasizing growth allows organizations to continuously evolve during their transformation process.

Importance of Patience in Agile Transformations

• Many clients want their agile transformations completed within a short timeframe, but true transformation takes time.

• The speaker highlights that if something is labeled as a transformation, it implies significant change, which cannot happen quickly.

• They share their experience of being part of a transformation that took 20 years to achieve.

A Balanced Approach

• The speaker suggests that while patience is required, it is important not to view the transformation as a long dark tunnel.

• They advocate for focusing on progress and consistent improvement rather than fixating on the time it takes to reach the end goal.

• An example is given of transforming a business school over 15 years, where small changes were made each year until a significant transformation was achieved.

The Meaning of Transformation and Agile

In this section, the speaker discusses their perspective on what true transformation means and how it relates to agile methodologies.

Transformation Implies Dramatic Change

• The speaker emphasizes that if something is labeled as a transformation, it should imply significant and dramatic change.

• They suggest that if an improvement effort is intended instead, using different terminology would be more appropriate.

Speed of Transformation

• The speaker states that true transformations rarely happen quickly and cites their experience with a 20-year transformation process.

• They highlight the nonsensical nature of expecting rapid transformations when the end result will be vastly different from the starting point.

Balancing Patience and Progress

• While acknowledging the need for patience in transformations, the speaker encourages organizations not to view it as a never-ending journey.

• They propose focusing on consistent progress towards a completely different state rather than fixating on reaching an endpoint.

Transforming Business Schools: A Case Study

This section presents a case study of transforming a business school over several years.

Transforming Rotman School of Management

• The speaker shares their experience leading the transformation of Rotman School of Management over 15 years.

• Initially considered subpar compared to other schools within the university, they aimed for an utter transformation.

• Their approach involved making small changes each year to avoid overwhelming stakeholders and resistance.

• The goal was for the change to be so gradual that after 15 years, the school would be unrecognizable compared to its previous state.

Recognition of Transformation

• The speaker mentions being recognized as the Business School Dean of the Year after completing their 15-year transformation journey.

• They highlight how the school's transformation was significant enough that it became a point of pride for the university.

Timestamps are provided in [t=XXXXs] format.

Importance of Growth in Transformation

In this section, the speaker emphasizes the importance of growth in driving successful transformation. They explain that a non-growing entity is unlikely to succeed in a transformation and that growth is necessary to overcome resistance from stakeholders.

Growth as a Catalyst for Transformation

• The speaker highlights that their previous experiences with successful transformations were all in growing entities.

• They assert that growth "greases the wheels" of transformation and recommend against attempting a transformation in a non-growing entity.

• In such cases, stakeholders who need to contribute resources for the transformation are more likely to resist.

Overcoming Resistance from Stakeholders

In this section, the speaker discusses how they managed resistance from stakeholders during transformations. They explain that by not taking resources away from others, they were able to minimize opposition and maintain progress.

Minimizing Opposition

• The speaker shares their approach of not taking resources away from others during transformations.

• While some individuals may have been unhappy seeing additional resources allocated elsewhere, they did not actively oppose the transformation.

• Instead, there might have been some temporary dissatisfaction or moping but no significant resistance.

Balancing Aggressiveness and Patience

Here, the speaker addresses criticism regarding their level of aggressiveness when advocating for patience. They highlight their track record of successfully transforming various organizations and emphasize the importance of focusing on sound direction and progress rather than rushing towards completion.

Transforming Organizations Successfully

• The speaker mentions their experience with successfully transforming organizations like Tennis Canada, Sick Kids Hospital, and School Financial.

• They emphasize practicing what they preach by implementing changes within organizations they are involved with.

Sound Direction and Progress

• The speaker contrasts the mindset of technocrats, who prioritize completing tasks quickly, with that of agile individuals.

• They believe that both playing to win and agile mentalities focus on ensuring a sound direction and making progress towards it.

• By prioritizing these two aspects, individuals can sleep soundly knowing they are on the right track.

Strategy vs. Agile Mentality

In this section, the speaker discusses the perceived conflict between strategy and an agile mentality. They argue that while many strategists are technocrats, there is no inherent conflict between strategy and agility.

Dominance of Technocracy in Strategy

• The speaker acknowledges that many strategists are technocrats who favor rigid procedures.

• This dominance of technocracy may lead some agile-minded individuals to view strategy negatively.

No Inherent Conflict

• The speaker asserts that there is no inherent conflict between strategy and an agile mentality.

• They advocate for utilizing the alliance between agility and playing to win mentalities rather than seeing them as fundamentally different approaches.

Logic Behind Direction and Making Progress

Here, the speaker emphasizes the importance of having a logical direction and making progress towards it. They highlight adaptability as a key factor for success in a changing environment.

Logic Behind Direction

• The speaker stresses the need for a logical rationale behind the chosen direction for an organization or project.

• Having a clear understanding of why certain decisions were made helps guide progress effectively.

Adaptability in Changing Environments

• The speaker references Darwin's concept of survival not being solely about fitness but also adaptability.

• They argue that organizations must embrace adaptability to thrive in dynamic environments.

Fighting Together for Change

In this section, the speaker expresses their commitment to fighting for change alongside others who share a similar mindset. They discuss the importance of momentum and long-term efforts in making a difference.

Fighting for Change

• The speaker acknowledges the need for collective effort in driving change.

• They express willingness to join forces with others who are aligned with their goals.

Momentum and Long-Term Efforts

• The speaker emphasizes the significance of maintaining momentum in effecting change.

• They believe that as long as progress is visible, they will be able to overcome challenges and achieve their objectives.

Future Collaboration and Strategy Course

Here, the speaker discusses future collaboration opportunities and mentions an upcoming strategy course. They express enthusiasm for continuing conversations on strategy and agile approaches.

Future Collaboration Opportunities

• The speaker expresses interest in future collaborations and interviews related to their new book.

• They appreciate the enjoyable nature of these conversations and value an alliance between agile mentality and playing to win mentality.

Upcoming Strategy Course

• The speaker mentions an upcoming strategy course they will be conducting.

• While they cannot guarantee availability, interested individuals can check for information on Disco platform.