impact-mapping

Impact Mapping And Why It Matters In Business

Impact mapping is a product development technique based on user design, mind mapping, and outcome-driven planning. Impact mapping is an agile technique intended to help teams connect individual product features that can impact the user behaviors while connecting to the key, guiding metrics for the business.

ComponentDescription
Concept NameImpact Mapping
OriginImpact Mapping was introduced by Gojko Adzic in his book “Impact Mapping” (2012).
OverviewImpact Mapping is a strategic planning technique that helps organizations align their activities with business goals. It visualizes the impact that various projects or initiatives can have on achieving specific business objectives. Impact Mapping is a collaborative tool that fosters communication and shared understanding among stakeholders.
Key ElementsBusiness Objectives: The high-level goals or outcomes that an organization aims to achieve.
Stakeholders: Individuals or groups who have an interest or role in the success of the project or initiative.
Deliverables: Tangible results or outputs that contribute to achieving business objectives.
Impacts: The desired changes in behavior or conditions that result from delivering the deliverables.
How It Works1. Define Business Objectives: Clearly articulate the specific business objectives that need to be achieved.
2. Identify Stakeholders: Identify and involve all relevant stakeholders, including users, customers, and team members.
3. Create a Visual Map: Develop an Impact Map that visually connects business objectives, deliverables, and impacts.
4. Link Deliverables to Impacts: For each business objective, link the deliverables and the desired impacts.
5. Focus on Deliverables: Concentrate on creating the deliverables that contribute most effectively to the desired impacts.
6. Iterate and Adapt: Impact Maps are dynamic and should be updated as the project progresses or as goals evolve.
ApplicationsStrategic Planning: Used to align projects and initiatives with organizational objectives.
Product Development: Helps product teams focus on features that provide the most value to users and the business.
Project Management: Ensures that projects deliver outcomes that matter.
BenefitsAlignment: Ensures that activities are closely aligned with business goals.
Clarity: Provides a clear and shared understanding of project objectives.
Stakeholder Engagement: Involves stakeholders in the planning process.
DrawbacksComplexity: Creating and maintaining Impact Maps can be time-consuming.
Assumptions: Relies on accurate assumptions about deliverables and their impacts.
Key TakeawayImpact Mapping is a collaborative and visual planning technique that links business objectives, deliverables, and impacts. It helps organizations focus on projects and initiatives that have the most significant positive effect on their business goals. Impact Maps are dynamic and should evolve as the project progresses or objectives change.

Understanding Impact Mapping 

Many product teams understand the importance of outcomes but nevertheless succumb to prioritising the development of much more tangible features.

Impact mapping was designed to help these teams gain clarity on outcomes that are comparatively hard to measure or appreciate. It is a collaborative methodology that seeks to help agile teams connect individual features to behaviours worth changing – all the while satisfying metrics that matter to the business.

Impact mapping combines elements of mind mapping and strategic planning and is prevalent among start-ups and large enterprises alike. Over the years, it has been adapted for use in:

  • Facilitating innovation workshops.
  • Aligning stakeholders with legacy enterprise projects.
  • Software delivery process improvement.
  • Instituting organizational-wide improvement.
  • Testing strategy definition.

The four key questions of Impact Mapping

Four key questions in the form of levels help stimulate conversation during product development. This conversation forms the basis of a visual and structured mind-map. 

The fifth and final level is not based on a question but instead on validating the solutions arrived it in the first four levels.

Let’s take a look at each below.

Level 1 –  Why are we doing this?

In other words, what goal is the project trying to achieve in the form of an objective? Why is this goal worth pursuing? The “why” can be made more tangible by articulating ambition. What is the timing of the goal and what difference does it seek to create?

For example, a business may have an ambition to increase average Net Promoter Score from 7 to 8 in the next 12 months.

Level 2 – Who can bring the organization closer to an objective? Alternatively, who might prevent the organization from achieving that objective?

Who are the actors who have the potential to impact the outcome? Identifying the most obvious actors is easy, but the real value lies in uncovering “second-degree” actors. In addition to external actors such as customers, consider internal actors such as key stakeholders, marketing, customer service, and administrative support roles.

Level 3 – How should the behaviour of actors change?

Put differently, how does behaviour have to change to change the overall impact? This is the part that many organizations struggle with. Indeed, actors will not voluntarily change their behaviour so that the business can become more profitable.

Insight into behavioural outcomes needs to be earnt through rigorous qualitative and quantitative research. The pains and gains of the current actor workflow must be well understood to selectively identify behaviours worth changing. Does the outcome need to be higher, lower, faster, or slower?

Outcomes should always be reframed as a challenge. If an actor wants to purchase event tickets without calling a call centre, the team can reframe it as: “How might we enable event participants to purchase tickets from their smartphone?”

Reframing also helps product teams avoid reverting to discussing specific features out of habit.

Level 4 – What can the product team do to support the desired impacts?

Now is the time to consider the features (deliverables) that will support an outcome. This can be achieved by running cross-functional ideation sessions involving stakeholders from across the company. 

Note that the inclusion of a feature on the map does not stipulate that it must be executed. The primary goal here is to create a list of potential courses of action.

For the previous example of an event goer ordering tickets without calling a call centre, the actor is most likely to be a smartphone app that sells tickets. Here, the outcome that alters customer behaviour is a more convenient means of ordering tickets. Ultimately, a successful outcome signifies that the business has reached its objectives and made an impact.

Level 5 – Determining whether the solution is worth implementing

Solutions must be validated through qualitative and quantitative experiments. Importantly, multiple experiments should consider every aspect of the solution, from feasibility to validity to usability.

Then, worthwhile solutions can be prioritized using a framework such as the ICE Scoring Model. 

Drawbacks of Impact Mapping

Potential for Oversimplification:

  • Reductionist Approach: Impact Mapping can sometimes oversimplify complex business goals, user needs, and the paths to achieve them, potentially overlooking nuanced details.
  • Risk of Misinterpreting Goals and Needs: The high-level view provided by Impact Mapping may lead to a misinterpretation of deeper, underlying goals and user needs.

Dependency on Accurate Initial Assumptions:

  • Relies Heavily on Initial Assumptions: The effectiveness of Impact Mapping is contingent on the accuracy of the initial goals and assumptions, which can be flawed or too broad.
  • Challenges with Dynamic Environments: In rapidly changing environments, initial assumptions may quickly become outdated, rendering the impact map less effective.

Resource and Time Intensive:

  • Requires Significant Time and Collaboration: Creating an effective impact map demands substantial time and effort, involving collaboration among various stakeholders.
  • Potential for Extensive Debates and Discussions: The process of aligning on goals, actors, impacts, and deliverables can lead to lengthy discussions, which may delay the project initiation.

Limited Scope and Focus:

  • Focuses Mainly on Planning Stages: Impact Mapping is primarily a planning tool and does not provide detailed guidance on execution or iterative development.
  • May Not Cover All Aspects of Product Development: Certain aspects like technical feasibility, resource allocation, and detailed design elements are not typically addressed in Impact Mapping.

When to Use Impact Mapping

Suitable Scenarios:

  • Early Stages of Product Development: Particularly useful in the initial planning phase of product or software development to align goals and expected outcomes.
  • Strategic Planning and Goal Alignment: Helpful for aligning various stakeholders on strategic goals and the means to achieve them.

Strategic Application:

  • Product Roadmapping: Can be effectively used for roadmapping, helping to prioritize features and activities based on their potential impact on goals.
  • Aligning Teams on Objectives: Useful for ensuring that all team members understand and work towards common objectives.

How to Use Impact Mapping

Implementing the Method:

  1. Define the Goal: Clearly articulate the primary goal or problem to be addressed.
  2. Identify Actors: Determine who can influence or is affected by the goal (e.g., users, internal stakeholders).
  3. Map Out Impacts: Identify how these actors can help or hinder the achievement of the goal.
  4. List Deliverables: Determine what can be created or changed to influence the actors and achieve the impacts.

Best Practices:

  • Involve a Diverse Group of Stakeholders: Include a range of perspectives to ensure a comprehensive understanding of the goal and potential impacts.
  • Keep the Map Agile: Be prepared to update and adapt the impact map as new information becomes available or circumstances change.
  • Focus on Measurable Impacts: Wherever possible

, identify impacts that are measurable, so progress towards goals can be concretely assessed.

  • Iterative Review: Regularly review and revise the impact map throughout the project lifecycle to ensure it remains relevant and aligned with project goals.

What to Expect from Implementing Impact Mapping

Enhanced Goal Alignment and Clarity:

  • Improved Understanding of Goals: Provides a clear visualization of the relationship between goals, stakeholders, desired impacts, and potential deliverables.
  • Alignment Across Teams: Helps align different teams and stakeholders around common objectives and understanding how their work contributes to these goals.

Strategic Planning Benefits:

  • Focused Efforts: Aids in focusing efforts on activities that are most likely to impact the desired outcomes, reducing waste on less effective initiatives.
  • Informed Decision-Making: Facilitates informed decision-making in prioritizing features or actions based on their potential impact.

Potential Challenges:

  • Initial Resistance to Adoption: There may be resistance or skepticism, particularly if stakeholders are accustomed to traditional planning methods.
  • Balancing Detail and High-Level Overview: Striking the right balance between providing sufficient detail and maintaining a high-level overview can be challenging.

Overall, Impact Mapping is a strategic planning tool that offers a visual and structured way to align project goals with actions. While it provides clarity and focus, its effectiveness relies on accurate assumptions, regular updates, and the involvement of diverse stakeholders. Balancing its high-level approach with detailed considerations of feasibility and execution is key to its successful application.

Impact mapping example

In this final section, we will outline some general examples of impact mapping with respect to a variety of common business goals.

Goal – Increase user retention by 25%

Consider a company with a goal to increase user retention in its workplace management platform.

How can it minimize churn? On a theoretical map, the company will list the following actors, impact, and deliverables:

  • Active users (actor) → increase monthly active users (MAU) and daily active users (DAU) (impact) → gamification, in-app messages (deliverables).
  • Future users (actor) → increase onboarding completion rate (impact) → one click sign-up process on social media, sign-up progress bar (deliverables).
  • Customer support (actor) → enhance user assistance (impact) → live-chat functionality (deliverable).

Goal – Improve user experience

In the second example, a company such as Duolingo that operates a language learning platform wants to improve the product experience for its users.

The impact map for this business may look something like this:

  • Teachers (actor) → improve quality of online classes (impact) → spatial audio, HD video, software integration (deliverables).
  • Engineering team (actor) → increase frequency of feature releases (impact) → continuous delivery investment, process automation (deliverables).
  • Students (actor) → teacher review system (impact)  five-star rating feature (deliverable).

Goal – Increase number of active players to 1 million

In the third example, we have an online gaming platform that wants to increase the number of active players to the 1 million mark:

  • Players (actor) → word-of-mouth recommendation to friends and family, posting about the game on social media, live streaming (impacts) → personalization, viral content, more compelling gameplay, referral incentivization (deliverables).
  • Advertisers (actor) → bulk invitations, banner advertising (impacts)
  • Internal (actor) → engage industry network, create public relations event and send invites (impacts).

Goal – Increase school environment to 450 students

Impact mapping can also be used in the education sector.

In this example, a small school has received grant money from the government to build a new classroom wing. To be profitable, the school needs to attract additional students up to a total of 450.

  • Marketing and enrolment coordinator (actor) → advertise, devote more time to recruitment, contract outreach candidates (impacts) → social media posts, email marketing, automate aspects of enrolment process (deliverables).
  • Current parents (actor) → recommend the school to friends and family, identify potential outreach candidates, generate awareness in local neighborhood (impacts) → provide shareable information, bumper stickers, testimonials, and suitable candidates (deliverables).
  • Faculty (actor) → word-of-mouth recommendation to friends, family, other teachers, publicize student and school achievements, improve student test scores and outcomes (impacts)  shareable information, social media campaigns, tailored lesson plans, software and other technology integration (deliverables).

Goal – Increase revenue to $2 million by the end of the year

Sticking with the education theme, our last example is an online learning platform that wants to increase revenue to $2 million:

  • Prospective students (actor) → purchase a course (impact) → free course preview, limited time discount (deliverables).
  • Current students (actor) → purchase additional courses, recommend courses to friends (impacts) → coupons, gamification, weekly emails, shareable information for social media, certificates/awards for course completion (deliverables).
  • Instructors (actor) → develop new/topical courses (impact) → provide instructional documentation, streamline creation process with technology (deliverables). 
  • Internal engineering team (actor) → rollout features more frequently, reduce operation costs (impacts) → improve release process, incorporate adaptive streaming algorithms, improve on-demand scaling (deliverables).

Case Studies

Enhancing a City’s Public Transportation System

Situation: A city wants to improve its public transportation system to encourage more people to use it and reduce road traffic.

Impact Mapping Application:

  • Goal: Increase daily public transportation ridership by 30% in the next year.
  • Actors: Commuters, tourists, local businesses.
  • Impacts: Commuters find routes more efficient; tourists find the system easy to navigate; local businesses see increased foot traffic from stops.
  • Deliverables: Mobile app with real-time tracking, route optimization, partnerships with tourist spots for discounts, integration with local businesses for promotions.

Launching a New Fitness App

Situation: A tech company is launching a fitness app and wants to maximize user engagement and retention.

Impact Mapping Application:

  • Goal: Achieve 100,000 active monthly users within six months.
  • Actors: Fitness enthusiasts, personal trainers, beginners seeking a fitness regime.
  • Impacts: Enthusiasts find advanced modules; trainers can host virtual classes; beginners find easy-to-follow regimes.
  • Deliverables: Advanced workout modules, feature for trainers to host sessions, beginner-friendly tutorials, integration with wearables.

Reducing Environmental Footprint of a Manufacturing Company

Situation: A manufacturing company wants to reduce its environmental footprint.

Impact Mapping Application:

  • Goal: Reduce carbon emissions by 40% over the next three years.
  • Actors: Production team, suppliers, customers.
  • Impacts: Production team adopts eco-friendly methods; suppliers provide sustainable materials; customers receive products with eco-friendly packaging.
  • Deliverables: Energy-efficient machinery, sustainable sourcing strategy, eco-friendly packaging design, customer awareness campaigns.

Boosting Sales in a Retail Store

Situation: A retail store is experiencing stagnant sales and wants to rejuvenate its revenue streams.

Impact Mapping Application:

  • Goal: Increase monthly sales by 25% in the next quarter.
  • Actors: Regular customers, potential customers, sales staff.
  • Impacts: Regular customers avail loyalty benefits; potential customers get attracted to promotions; sales staff upsell effectively.
  • Deliverables: Loyalty program, promotional sales, staff training programs, revamped store layout.

Promoting a New Menu in a Restaurant

Situation: A restaurant has launched a new menu and wants to promote it to maximize its reach and sales.

Impact Mapping Application:

  • Goal: Increase orders from the new menu by 50% in the next two months.
  • Actors: Regular diners, food bloggers, online food delivery platforms.
  • Impacts: Regular diners try new dishes; food bloggers review and promote the menu; increased orders via delivery platforms.
  • Deliverables: Special offers for regular diners, collaboration with food bloggers for reviews, promotional offers on delivery platforms.

Increasing Enrollment in an Online Course

Situation: An educational institution has launched a new online course and wants to maximize enrollments.

Impact Mapping Application:

  • Goal: Achieve 10,000 enrollments in the next semester.
  • Actors: Students, educational counselors, parents.
  • Impacts: Students find course content appealing; counselors recommend the course; parents see value in the course for their children’s future.
  • Deliverables: Engaging course content, partnerships with educational counselors, webinars for parents on course benefits.

Key takeaways:

  • Impact Mapping combines mind mapping and strategic planning to help teams identify behaviours that will help them reach their objectives.
  • Impact Mapping is a popular and successful framework used in small and large businesses. It is most prevalent in software development but can also be seen in organization-wide improvement and stakeholder alignment with legacy systems.
  • Central to Impact Mapping is the collaborative creation of a visual mind-map based on four key questions that stimulate conversation and develop potential solutions. The fifth level then instructs product teams to evaluate and prioritize solutions based on experimentation.

Key highlights of Impact Mapping:

  • Definition: Impact Mapping is an agile product development technique that connects individual product features to user behaviors and aligns them with key business metrics. It is a collaborative methodology based on user design, mind mapping, and outcome-driven planning.
  • Importance: Impact Mapping helps product teams gain clarity on outcomes that are challenging to measure or appreciate. It ensures that development efforts are aligned with achieving meaningful business objectives.
  • Application: Impact Mapping is prevalent in various contexts, including facilitating innovation workshops, aligning stakeholders with legacy enterprise projects, improving software delivery processes, instituting organizational-wide improvements, and defining testing strategies.
  • Four Key Questions: Impact Mapping stimulates conversation during product development with four key questions:
    1. Why are we doing this? Identifying the objective and ambition of the project.
    2. Who can bring the organization closer to the objective? Identifying actors and stakeholders.
    3. How should the behavior of actors change? Understanding the desired behavior changes.
    4. What can the product team do to support the desired impacts? Identifying potential features or deliverables.
  • Validation and Prioritization: Solutions generated through Impact Mapping must be validated through qualitative and quantitative experiments. Solutions can then be prioritized using frameworks like the ICE Scoring Model.
  • Examples: Impact Mapping can be applied to various business goals, such as increasing user retention, improving user experience, increasing the number of active players, increasing school enrollment, and boosting revenue.
  • Collaborative and Agile: Impact Mapping fosters collaboration among teams and stakeholders and aligns with agile principles of iterative development and continuous feedback. It ensures that product development efforts are outcome-driven and aligned with business goals.

Connected Agile & Lean Frameworks

AIOps

aiops
AIOps is the application of artificial intelligence to IT operations. It has become particularly useful for modern IT management in hybridized, distributed, and dynamic environments. AIOps has become a key operational component of modern digital-based organizations, built around software and algorithms.

AgileSHIFT

AgileSHIFT
AgileSHIFT is a framework that prepares individuals for transformational change by creating a culture of agility.

Agile Methodology

agile-methodology
Agile started as a lightweight development method compared to heavyweight software development, which is the core paradigm of the previous decades of software development. By 2001 the Manifesto for Agile Software Development was born as a set of principles that defined the new paradigm for software development as a continuous iteration. This would also influence the way of doing business.

Agile Program Management

agile-program-management
Agile Program Management is a means of managing, planning, and coordinating interrelated work in such a way that value delivery is emphasized for all key stakeholders. Agile Program Management (AgilePgM) is a disciplined yet flexible agile approach to managing transformational change within an organization.

Agile Project Management

agile-project-management
Agile project management (APM) is a strategy that breaks large projects into smaller, more manageable tasks. In the APM methodology, each project is completed in small sections – often referred to as iterations. Each iteration is completed according to its project life cycle, beginning with the initial design and progressing to testing and then quality assurance.

Agile Modeling

agile-modeling
Agile Modeling (AM) is a methodology for modeling and documenting software-based systems. Agile Modeling is critical to the rapid and continuous delivery of software. It is a collection of values, principles, and practices that guide effective, lightweight software modeling.

Agile Business Analysis

agile-business-analysis
Agile Business Analysis (AgileBA) is certification in the form of guidance and training for business analysts seeking to work in agile environments. To support this shift, AgileBA also helps the business analyst relate Agile projects to a wider organizational mission or strategy. To ensure that analysts have the necessary skills and expertise, AgileBA certification was developed.

Agile Leadership

agile-leadership
Agile leadership is the embodiment of agile manifesto principles by a manager or management team. Agile leadership impacts two important levels of a business. The structural level defines the roles, responsibilities, and key performance indicators. The behavioral level describes the actions leaders exhibit to others based on agile principles. 

Andon System

andon-system
The andon system alerts managerial, maintenance, or other staff of a production process problem. The alert itself can be activated manually with a button or pull cord, but it can also be activated automatically by production equipment. Most Andon boards utilize three colored lights similar to a traffic signal: green (no errors), yellow or amber (problem identified, or quality check needed), and red (production stopped due to unidentified issue).

Bimodal Portfolio Management

bimodal-portfolio-management
Bimodal Portfolio Management (BimodalPfM) helps an organization manage both agile and traditional portfolios concurrently. Bimodal Portfolio Management – sometimes referred to as bimodal development – was coined by research and advisory company Gartner. The firm argued that many agile organizations still needed to run some aspects of their operations using traditional delivery models.

Business Innovation Matrix

business-innovation
Business innovation is about creating new opportunities for an organization to reinvent its core offerings, revenue streams, and enhance the value proposition for existing or new customers, thus renewing its whole business model. Business innovation springs by understanding the structure of the market, thus adapting or anticipating those changes.

Business Model Innovation

business-model-innovation
Business model innovation is about increasing the success of an organization with existing products and technologies by crafting a compelling value proposition able to propel a new business model to scale up customers and create a lasting competitive advantage. And it all starts by mastering the key customers.

Constructive Disruption

constructive-disruption
A consumer brand company like Procter & Gamble (P&G) defines “Constructive Disruption” as: a willingness to change, adapt, and create new trends and technologies that will shape our industry for the future. According to P&G, it moves around four pillars: lean innovation, brand building, supply chain, and digitalization & data analytics.

Continuous Innovation

continuous-innovation
That is a process that requires a continuous feedback loop to develop a valuable product and build a viable business model. Continuous innovation is a mindset where products and services are designed and delivered to tune them around the customers’ problem and not the technical solution of its founders.

Design Sprint

design-sprint
A design sprint is a proven five-day process where critical business questions are answered through speedy design and prototyping, focusing on the end-user. A design sprint starts with a weekly challenge that should finish with a prototype, test at the end, and therefore a lesson learned to be iterated.

Design Thinking

design-thinking
Tim Brown, Executive Chair of IDEO, defined design thinking as “a human-centered approach to innovation that draws from the designer’s toolkit to integrate the needs of people, the possibilities of technology, and the requirements for business success.” Therefore, desirability, feasibility, and viability are balanced to solve critical problems.

DevOps

devops-engineering
DevOps refers to a series of practices performed to perform automated software development processes. It is a conjugation of the term “development” and “operations” to emphasize how functions integrate across IT teams. DevOps strategies promote seamless building, testing, and deployment of products. It aims to bridge a gap between development and operations teams to streamline the development altogether.

Dual Track Agile

dual-track-agile
Product discovery is a critical part of agile methodologies, as its aim is to ensure that products customers love are built. Product discovery involves learning through a raft of methods, including design thinking, lean start-up, and A/B testing to name a few. Dual Track Agile is an agile methodology containing two separate tracks: the “discovery” track and the “delivery” track.

eXtreme Programming

extreme-programming
eXtreme Programming was developed in the late 1990s by Ken Beck, Ron Jeffries, and Ward Cunningham. During this time, the trio was working on the Chrysler Comprehensive Compensation System (C3) to help manage the company payroll system. eXtreme Programming (XP) is a software development methodology. It is designed to improve software quality and the ability of software to adapt to changing customer needs.

Feature-Driven Development

feature-driven-development
Feature-Driven Development is a pragmatic software process that is client and architecture-centric. Feature-Driven Development (FDD) is an agile software development model that organizes workflow according to which features need to be developed next.

Gemba Walk

gemba-walk
A Gemba Walk is a fundamental component of lean management. It describes the personal observation of work to learn more about it. Gemba is a Japanese word that loosely translates as “the real place”, or in business, “the place where value is created”. The Gemba Walk as a concept was created by Taiichi Ohno, the father of the Toyota Production System of lean manufacturing. Ohno wanted to encourage management executives to leave their offices and see where the real work happened. This, he hoped, would build relationships between employees with vastly different skillsets and build trust.

GIST Planning

gist-planning
GIST Planning is a relatively easy and lightweight agile approach to product planning that favors autonomous working. GIST Planning is a lean and agile methodology that was created by former Google product manager Itamar Gilad. GIST Planning seeks to address this situation by creating lightweight plans that are responsive and adaptable to change. GIST Planning also improves team velocity, autonomy, and alignment by reducing the pervasive influence of management. It consists of four blocks: goals, ideas, step-projects, and tasks.

ICE Scoring

ice-scoring-model
The ICE Scoring Model is an agile methodology that prioritizes features using data according to three components: impact, confidence, and ease of implementation. The ICE Scoring Model was initially created by author and growth expert Sean Ellis to help companies expand. Today, the model is broadly used to prioritize projects, features, initiatives, and rollouts. It is ideally suited for early-stage product development where there is a continuous flow of ideas and momentum must be maintained.

Innovation Funnel

innovation-funnel
An innovation funnel is a tool or process ensuring only the best ideas are executed. In a metaphorical sense, the funnel screens innovative ideas for viability so that only the best products, processes, or business models are launched to the market. An innovation funnel provides a framework for the screening and testing of innovative ideas for viability.

Innovation Matrix

types-of-innovation
According to how well defined is the problem and how well defined the domain, we have four main types of innovations: basic research (problem and domain or not well defined); breakthrough innovation (domain is not well defined, the problem is well defined); sustaining innovation (both problem and domain are well defined); and disruptive innovation (domain is well defined, the problem is not well defined).

Innovation Theory

innovation-theory
The innovation loop is a methodology/framework derived from the Bell Labs, which produced innovation at scale throughout the 20th century. They learned how to leverage a hybrid innovation management model based on science, invention, engineering, and manufacturing at scale. By leveraging individual genius, creativity, and small/large groups.

Lean vs. Agile

lean-methodology-vs-agile
The Agile methodology has been primarily thought of for software development (and other business disciplines have also adopted it). Lean thinking is a process improvement technique where teams prioritize the value streams to improve it continuously. Both methodologies look at the customer as the key driver to improvement and waste reduction. Both methodologies look at improvement as something continuous.

Lean Startup

startup-company
A startup company is a high-tech business that tries to build a scalable business model in tech-driven industries. A startup company usually follows a lean methodology, where continuous innovation, driven by built-in viral loops is the rule. Thus, driving growth and building network effects as a consequence of this strategy.

Minimum Viable Product

minimum-viable-product
As pointed out by Eric Ries, a minimum viable product is that version of a new product which allows a team to collect the maximum amount of validated learning about customers with the least effort through a cycle of build, measure, learn; that is the foundation of the lean startup methodology.

Leaner MVP

leaner-mvp
A leaner MVP is the evolution of the MPV approach. Where the market risk is validated before anything else

Kanban

kanban
Kanban is a lean manufacturing framework first developed by Toyota in the late 1940s. The Kanban framework is a means of visualizing work as it moves through identifying potential bottlenecks. It does that through a process called just-in-time (JIT) manufacturing to optimize engineering processes, speed up manufacturing products, and improve the go-to-market strategy.

Jidoka

jidoka
Jidoka was first used in 1896 by Sakichi Toyoda, who invented a textile loom that would stop automatically when it encountered a defective thread. Jidoka is a Japanese term used in lean manufacturing. The term describes a scenario where machines cease operating without human intervention when a problem or defect is discovered.

PDCA Cycle

pdca-cycle
The PDCA (Plan-Do-Check-Act) cycle was first proposed by American physicist and engineer Walter A. Shewhart in the 1920s. The PDCA cycle is a continuous process and product improvement method and an essential component of the lean manufacturing philosophy.

Rational Unified Process

rational-unified-process
Rational unified process (RUP) is an agile software development methodology that breaks the project life cycle down into four distinct phases.

Rapid Application Development

rapid-application-development
RAD was first introduced by author and consultant James Martin in 1991. Martin recognized and then took advantage of the endless malleability of software in designing development models. Rapid Application Development (RAD) is a methodology focusing on delivering rapidly through continuous feedback and frequent iterations.

Retrospective Analysis

retrospective-analysis
Retrospective analyses are held after a project to determine what worked well and what did not. They are also conducted at the end of an iteration in Agile project management. Agile practitioners call these meetings retrospectives or retros. They are an effective way to check the pulse of a project team, reflect on the work performed to date, and reach a consensus on how to tackle the next sprint cycle. These are the five stages of a retrospective analysis for effective Agile project management: set the stage, gather the data, generate insights, decide on the next steps, and close the retrospective.

Scaled Agile

scaled-agile-lean-development
Scaled Agile Lean Development (ScALeD) helps businesses discover a balanced approach to agile transition and scaling questions. The ScALed approach helps businesses successfully respond to change. Inspired by a combination of lean and agile values, ScALed is practitioner-based and can be completed through various agile frameworks and practices.

SMED

smed
The SMED (single minute exchange of die) method is a lean production framework to reduce waste and increase production efficiency. The SMED method is a framework for reducing the time associated with completing an equipment changeover.

Spotify Model

spotify-model
The Spotify Model is an autonomous approach to scaling agile, focusing on culture communication, accountability, and quality. The Spotify model was first recognized in 2012 after Henrik Kniberg, and Anders Ivarsson released a white paper detailing how streaming company Spotify approached agility. Therefore, the Spotify model represents an evolution of agile.

Test-Driven Development

test-driven-development
As the name suggests, TDD is a test-driven technique for delivering high-quality software rapidly and sustainably. It is an iterative approach based on the idea that a failing test should be written before any code for a feature or function is written. Test-Driven Development (TDD) is an approach to software development that relies on very short development cycles.

Timeboxing

timeboxing
Timeboxing is a simple yet powerful time-management technique for improving productivity. Timeboxing describes the process of proactively scheduling a block of time to spend on a task in the future. It was first described by author James Martin in a book about agile software development.

Scrum

what-is-scrum
Scrum is a methodology co-created by Ken Schwaber and Jeff Sutherland for effective team collaboration on complex products. Scrum was primarily thought for software development projects to deliver new software capability every 2-4 weeks. It is a sub-group of agile also used in project management to improve startups’ productivity.

Scrumban

scrumban
Scrumban is a project management framework that is a hybrid of two popular agile methodologies: Scrum and Kanban. Scrumban is a popular approach to helping businesses focus on the right strategic tasks while simultaneously strengthening their processes.

Scrum Anti-Patterns

scrum-anti-patterns
Scrum anti-patterns describe any attractive, easy-to-implement solution that ultimately makes a problem worse. Therefore, these are the practice not to follow to prevent issues from emerging. Some classic examples of scrum anti-patterns comprise absent product owners, pre-assigned tickets (making individuals work in isolation), and discounting retrospectives (where review meetings are not useful to really make improvements).

Scrum At Scale

scrum-at-scale
Scrum at Scale (Scrum@Scale) is a framework that Scrum teams use to address complex problems and deliver high-value products. Scrum at Scale was created through a joint venture between the Scrum Alliance and Scrum Inc. The joint venture was overseen by Jeff Sutherland, a co-creator of Scrum and one of the principal authors of the Agile Manifesto.

Six Sigma

six-sigma
Six Sigma is a data-driven approach and methodology for eliminating errors or defects in a product, service, or process. Six Sigma was developed by Motorola as a management approach based on quality fundamentals in the early 1980s. A decade later, it was popularized by General Electric who estimated that the methodology saved them $12 billion in the first five years of operation.

Stretch Objectives

stretch-objectives
Stretch objectives describe any task an agile team plans to complete without expressly committing to do so. Teams incorporate stretch objectives during a Sprint or Program Increment (PI) as part of Scaled Agile. They are used when the agile team is unsure of its capacity to attain an objective. Therefore, stretch objectives are instead outcomes that, while extremely desirable, are not the difference between the success or failure of each sprint.

Toyota Production System

toyota-production-system
The Toyota Production System (TPS) is an early form of lean manufacturing created by auto-manufacturer Toyota. Created by the Toyota Motor Corporation in the 1940s and 50s, the Toyota Production System seeks to manufacture vehicles ordered by customers most quickly and efficiently possible.

Total Quality Management

total-quality-management
The Total Quality Management (TQM) framework is a technique based on the premise that employees continuously work on their ability to provide value to customers. Importantly, the word “total” means that all employees are involved in the process – regardless of whether they work in development, production, or fulfillment.

Waterfall

waterfall-model
The waterfall model was first described by Herbert D. Benington in 1956 during a presentation about the software used in radar imaging during the Cold War. Since there were no knowledge-based, creative software development strategies at the time, the waterfall method became standard practice. The waterfall model is a linear and sequential project management framework. 

Read Also: Continuous InnovationAgile MethodologyLean StartupBusiness Model InnovationProject Management.

Read Next: Agile Methodology, Lean Methodology, Agile Project Management, Scrum, Kanban, Six Sigma.

Main Guides:

Main Case Studies:

Discover more from FourWeekMBA

Subscribe now to keep reading and get access to the full archive.

Continue reading

Scroll to Top
FourWeekMBA