Crowdsourcing involves outsourcing tasks traditionally performed by employees to a large group of people through an open call. It can take two forms: adding capacity by splitting large jobs into smaller microtasks, or accessing expertise to tap into the wisdom of crowds. The document provides guidance on developing effective problem statements for crowdsourcing, including outlining the problem, past attempts to solve it, desired solutions, exclusions, success criteria, and deliverables. It also compares internal, hybrid, and external crowds and provides decision trees to help determine which approach is best suited for the problem.
The document discusses the benefits of internal crowdsourcing (IC), which involves harnessing the collective wisdom of a company's employees to generate ideas and solve problems. It identifies 5 major benefits of IC: 1) Fostering a culture of collaboration, 2) Collecting "low-hanging fruits" or easily solved problems, 3) Creating a common intellectual space, 4) Supporting external innovation programs, 5) Identifying emerging thought leaders within the company. Case studies are provided to illustrate how IC can help solve specific problems and identify new talent.
Much of the time, we view innovation through a lens of total newness, but teachings from a variety of industries and professions might hold the key to defining successful strategies, and positively influence the way innovation is executed in the enterprise space.
Consulting toolkit structuring the problemchrisdoran
The document provides guidance on using issue trees to structure problem solving. It discusses breaking problems down into smaller, more manageable issues. An issue tree has three purposes: to break problems into analyzable chunks; open up the solution space; and get everyone on the same page quickly. The document outlines eight steps to generate an issue tree, including writing the problem, brainstorming solutions, organizing the solutions logically into questions at different levels of generality/specificity, expanding and pruning the tree, and revisiting the problem. Productive brainstorming requires rules like deferring judgment and encouraging novel ideas.
Technology Venture Assessment - Thomas TriumphThomas Triumph
Initial thoughts on assessing technology ventures proposed to an incubator:
1) A structured evaluation process is necessary to improve accuracy in predicting success and yield higher returns, even with just one additional successful venture. 2) The document outlines several strategies for evaluating new ventures, including embracing both quantitative and qualitative factors, exploring all sides of opportunities, and using outside experts. 3) Key metrics for assessment are identified across categories like market potential, technical feasibility, competition, and return on investment. Weighted scoring of ventures allows comparison.
This document discusses wicked problems and open innovation approaches to solving them. It defines wicked problems as having unclear definitions and solutions, involving multiple stakeholders with differing views. Normal solutions do not work for wicked problems which can only be understood through attempting solutions. It advocates understanding stakeholders and problems by questioning assumptions and mapping relationships. It then suggests ideating solutions through diverse groups, experimenting with early adopters, and implementing through the early majority. The periodic table framework shown organizes these open innovation activities for addressing wicked challenges through collaboration with society.
The document discusses the benefits of internal crowdsourcing (IC), which involves harnessing the collective wisdom of a company's employees to generate ideas and solve problems. It identifies 5 major benefits of IC: 1) Fostering a culture of collaboration, 2) Collecting "low-hanging fruits" or easily solved problems, 3) Creating a common intellectual space, 4) Supporting external innovation programs, 5) Identifying emerging thought leaders within the company. Case studies are provided to illustrate how IC can help solve specific problems and identify new talent.
Much of the time, we view innovation through a lens of total newness, but teachings from a variety of industries and professions might hold the key to defining successful strategies, and positively influence the way innovation is executed in the enterprise space.
Consulting toolkit structuring the problemchrisdoran
The document provides guidance on using issue trees to structure problem solving. It discusses breaking problems down into smaller, more manageable issues. An issue tree has three purposes: to break problems into analyzable chunks; open up the solution space; and get everyone on the same page quickly. The document outlines eight steps to generate an issue tree, including writing the problem, brainstorming solutions, organizing the solutions logically into questions at different levels of generality/specificity, expanding and pruning the tree, and revisiting the problem. Productive brainstorming requires rules like deferring judgment and encouraging novel ideas.
Technology Venture Assessment - Thomas TriumphThomas Triumph
Initial thoughts on assessing technology ventures proposed to an incubator:
1) A structured evaluation process is necessary to improve accuracy in predicting success and yield higher returns, even with just one additional successful venture. 2) The document outlines several strategies for evaluating new ventures, including embracing both quantitative and qualitative factors, exploring all sides of opportunities, and using outside experts. 3) Key metrics for assessment are identified across categories like market potential, technical feasibility, competition, and return on investment. Weighted scoring of ventures allows comparison.
This document discusses wicked problems and open innovation approaches to solving them. It defines wicked problems as having unclear definitions and solutions, involving multiple stakeholders with differing views. Normal solutions do not work for wicked problems which can only be understood through attempting solutions. It advocates understanding stakeholders and problems by questioning assumptions and mapping relationships. It then suggests ideating solutions through diverse groups, experimenting with early adopters, and implementing through the early majority. The periodic table framework shown organizes these open innovation activities for addressing wicked challenges through collaboration with society.
Removing Uncertainty in your Decision MakingBusiness901
I had great pleasure having Eli Schragenheim on the Business901 Podcast. Eli has been part of the Theory of Constraints movement practically from the beginning. He started working with Dr. Goldratt as a programmer to program a game for adults that would teach them how to think over 25 years ago. During the podcast we dove into the subject of Uncertainty! A great discussion, that affects our everyday life and how it relates to forecasting and even our intuition.
The future of design thinking lecture 11Gavin Melles
The document discusses the future of design thinking. It explores whether design thinking is dead or what future it has. It examines the consequences of design thinking spreading to other areas like social innovation. It also looks at the promises and challenges of design thinking. Key points discussed include Tim Brown's hopes for using design thinking to solve social problems, the opportunities for design thinking to be relevant across disciplines, and the limitations and fears around design thinking becoming too generalized or dependent on certain leaders. The document considers different perspectives on the meaning and future of design thinking.
Howto Promote the Logical Thinking Process (LTP) using The Norovirus Approach...Seuils Labs
Version Française ICI:
http://slideshare.net/seuils/howto-promote-ltp-norovirus-approach-fr
"Logical Thinking Process (LTP) - The Norovirus Approach"
How to propagate the Logical Thinking Process (LTP) using a viral approach, modeled on the Norovirus.
Original story reproduced by H. William Dettmer with permission from author, Ronald N. Woehr.
French translation by Paul Merino @SEUILS with permission from H. William Dettmer.
HRSeminar KPI's: Geert Scheipers (academic director organizational performan...HRmagazine
In het vak ‘Beheerscontrole’ ligt de nadruk traditioneel op extrinsieke drijfveren die mensen aanzetten tot het realiseren van bedrijfsdoelstellingen. Denk daarbij aan ‘Pay-for-performance’, evaluatie-systemen, rapporteringen, budgetten,… Populaire publicaties van bijvoorbeeld Frederic Laloux (Reinventing organizations), Ricardo Semler (The 7 day weekend) of Vincent Nayar (Employee First, Customer second) tonen dat er andere culturen en bedrijfsfilosofieën zijn.
Maar betekent dit dan ook dat de pijlers van het vakgebied niet meer relevant zijn? Zijn indicatoren historisch erfgoed in management geworden? Vast niet, maar het is wel tijd om terug naar de bron van het vak te gaan en om de traditionele managementprocessen op een andere manier aan te pakken, zodat ze beter inspelen op de trends in onze marktomgeving en aantrekkelijk zijn voor de nieuwe generaties waarmee we samen werken.
In deze sessie vertrekt Geert Scheipers vanuit goed onderzoek rond sturen in organisaties, om te bekijken hoe men vanuit een doorleefde visie en inspiratie succesvolle, duurzame organisaties uit kan bouwen.
I've written an article (http://wp.me/pv1y4-q9) that summarises some of our Learning Points from a range of Customer and Staff Surveys. It describes 5 Survey Mistakes and how to avoid them. This is the supporting presentation.
This document discusses forward-looking and predictive metrics that can be used for recruiting. It begins by defining key terms like historical, real-time, and predictive metrics. It then discusses reasons for using traditional metrics, such as increased business results when data-driven decision making is used. Examples of predictive recruiting metrics are also provided, such as predicting changing source effectiveness and upcoming talent availability. The document concludes by outlining elements that make a predictive metric actionable, such as listing revenue impact and recommended actions.
An A3 report is a problem-solving tool used in lean companies like Toyota. It follows a standardized format on an 11x17 inch piece of paper to tell a story from background to proposed countermeasures. The A3 encourages identifying root causes, considering various solutions, planning implementation, and following up on results. It is not a rigid template but a flexible knowledge-sharing mechanism. Effective A3 reports ask and answer key questions at each step to fully understand issues and achieve goals.
Deeper thinking about what we've learned from Toyota, including using principles and rules, not tools. Posted by AME with permission from Jamie Flinchbaugh.
Tackling wicked problems: A social policy planning framework for addressing l...Kimberly Vardeman
The presentation introduces the concept of wicked problems and their application to library user experience design. It defines wicked problems as having no clear definition or solution, with ongoing consequences. Ten key characteristics of wicked problems are outlined. The presentation then discusses approaches to resolving wicked problems, including authoritative, collaborative, and competitive methods. A case study of redesigning a library website is used to illustrate how it posed a wicked problem with conflicting stakeholder perspectives. The presentation concludes by arguing the wicked problems model can change how user experience practitioners approach defining success and solutions.
The document discusses various tools that can be used for continuous improvement, including problem-solving cycles, brainstorming, cause and effect diagrams, checksheets, flow diagrams, and policy deployment. It provides brief explanations and examples of how to use each tool, with the problem-solving cycle presented as a multi-step model for identifying problems, defining them, exploring solutions, selecting options, implementing changes, and evaluating results.
This document summarizes the business case for employee referral programs (ERPs). It discusses how referrals produce the highest volume of applicants and the highest quality hires. Referral hires have higher retention rates and produce more profit than other sources. The document provides examples of companies that have achieved referral rates of 50% or more. It then outlines several strategic and tactical actions that can be taken to improve ERP results, such as prioritizing efforts, seeking referrals proactively, broadening eligibility, utilizing rewards, and using applicant tracking technology.
Why are all big companies so ineffective and why does nobody really like working there anymore? In this talk we will revisit work of Herbert Simon, one of the founders of Artificial Intelligence and 1978 Nobel Prize winner, and the model of problem-solving team effectiveness built upon it. This work combined with current interest in predictive behavioral analytics provides a prudent foundation for creating and sustaining vigorous and productive workplace.
Toyota has an eight-step problem solving process called Toyota Business Practices (TBP) that is used to implement the principles of the Toyota Way. The eight steps are: 1) clarify the problem and ideal solution, 2) assess the current situation, 3) prioritize smaller problems, 4) determine the root causes, 5) develop countermeasures, 6) implement the plan, 7) check the results, and 8) standardize successful solutions and spread them to other areas. This structured process uses the Plan-Do-Check-Act (PDCA) cycle to continuously improve processes through solving problems.
This document discusses managing priorities in complex environments. It suggests determining priorities based on importance rather than urgency, with importance defined by criteria like long-term impact and number of people affected. It recommends creating a plan with important tasks in priority order and time budgeted for each. Interruptions should be prevented unless truly important or from certain sources like one's boss. The document advises against multitasking and provides tips like doing hard tasks first and closing email to focus on one task at a time. Priorities are difficult to manage due to various pressures, but self-control is still possible.
201306 Five Routes to more Innovative Problem Solving MCKFrancisco Calzado
This document discusses using "flexons" as a framework for viewing complex problems through multiple lenses in order to generate more innovative solutions. It introduces five flexons or problem-solving frameworks derived from social and natural sciences: 1) Networks, 2) Evolutionary, 3) Decision-agent, 4) System-dynamics, and 5) Information-processing. The document provides examples of how each flexon can be applied and highlights that using multiple flexons together allows for a richer understanding of complex problems and identification of non-obvious solutions.
This document provides information on productive problem solving. It discusses what productive problem solving is, common impediments, and essential elements. It also outlines several problem solving methodologies and techniques, including the scientific method, brainstorming, FAST diagramming, and evaluating potential solutions. The goal is to provide a structured approach to defining problems, identifying root causes, generating alternatives, and selecting the best solution.
This document discusses achieving problem-solution fit by properly framing problems. It emphasizes spending more time understanding the problem before developing solutions. Proper problem framing involves gathering input from stakeholders, analyzing root causes, and reframing the problem as an opportunity. Developing a clear problem statement is important, as is considering different perspectives and how success would look. Mapping stakeholders and exploring problem types can provide useful context. Overall, the document stresses the importance of rigorous problem definition to develop effective solutions.
Removing Uncertainty in your Decision MakingBusiness901
I had great pleasure having Eli Schragenheim on the Business901 Podcast. Eli has been part of the Theory of Constraints movement practically from the beginning. He started working with Dr. Goldratt as a programmer to program a game for adults that would teach them how to think over 25 years ago. During the podcast we dove into the subject of Uncertainty! A great discussion, that affects our everyday life and how it relates to forecasting and even our intuition.
The future of design thinking lecture 11Gavin Melles
The document discusses the future of design thinking. It explores whether design thinking is dead or what future it has. It examines the consequences of design thinking spreading to other areas like social innovation. It also looks at the promises and challenges of design thinking. Key points discussed include Tim Brown's hopes for using design thinking to solve social problems, the opportunities for design thinking to be relevant across disciplines, and the limitations and fears around design thinking becoming too generalized or dependent on certain leaders. The document considers different perspectives on the meaning and future of design thinking.
Howto Promote the Logical Thinking Process (LTP) using The Norovirus Approach...Seuils Labs
Version Française ICI:
http://slideshare.net/seuils/howto-promote-ltp-norovirus-approach-fr
"Logical Thinking Process (LTP) - The Norovirus Approach"
How to propagate the Logical Thinking Process (LTP) using a viral approach, modeled on the Norovirus.
Original story reproduced by H. William Dettmer with permission from author, Ronald N. Woehr.
French translation by Paul Merino @SEUILS with permission from H. William Dettmer.
HRSeminar KPI's: Geert Scheipers (academic director organizational performan...HRmagazine
In het vak ‘Beheerscontrole’ ligt de nadruk traditioneel op extrinsieke drijfveren die mensen aanzetten tot het realiseren van bedrijfsdoelstellingen. Denk daarbij aan ‘Pay-for-performance’, evaluatie-systemen, rapporteringen, budgetten,… Populaire publicaties van bijvoorbeeld Frederic Laloux (Reinventing organizations), Ricardo Semler (The 7 day weekend) of Vincent Nayar (Employee First, Customer second) tonen dat er andere culturen en bedrijfsfilosofieën zijn.
Maar betekent dit dan ook dat de pijlers van het vakgebied niet meer relevant zijn? Zijn indicatoren historisch erfgoed in management geworden? Vast niet, maar het is wel tijd om terug naar de bron van het vak te gaan en om de traditionele managementprocessen op een andere manier aan te pakken, zodat ze beter inspelen op de trends in onze marktomgeving en aantrekkelijk zijn voor de nieuwe generaties waarmee we samen werken.
In deze sessie vertrekt Geert Scheipers vanuit goed onderzoek rond sturen in organisaties, om te bekijken hoe men vanuit een doorleefde visie en inspiratie succesvolle, duurzame organisaties uit kan bouwen.
I've written an article (http://wp.me/pv1y4-q9) that summarises some of our Learning Points from a range of Customer and Staff Surveys. It describes 5 Survey Mistakes and how to avoid them. This is the supporting presentation.
This document discusses forward-looking and predictive metrics that can be used for recruiting. It begins by defining key terms like historical, real-time, and predictive metrics. It then discusses reasons for using traditional metrics, such as increased business results when data-driven decision making is used. Examples of predictive recruiting metrics are also provided, such as predicting changing source effectiveness and upcoming talent availability. The document concludes by outlining elements that make a predictive metric actionable, such as listing revenue impact and recommended actions.
An A3 report is a problem-solving tool used in lean companies like Toyota. It follows a standardized format on an 11x17 inch piece of paper to tell a story from background to proposed countermeasures. The A3 encourages identifying root causes, considering various solutions, planning implementation, and following up on results. It is not a rigid template but a flexible knowledge-sharing mechanism. Effective A3 reports ask and answer key questions at each step to fully understand issues and achieve goals.
Deeper thinking about what we've learned from Toyota, including using principles and rules, not tools. Posted by AME with permission from Jamie Flinchbaugh.
Tackling wicked problems: A social policy planning framework for addressing l...Kimberly Vardeman
The presentation introduces the concept of wicked problems and their application to library user experience design. It defines wicked problems as having no clear definition or solution, with ongoing consequences. Ten key characteristics of wicked problems are outlined. The presentation then discusses approaches to resolving wicked problems, including authoritative, collaborative, and competitive methods. A case study of redesigning a library website is used to illustrate how it posed a wicked problem with conflicting stakeholder perspectives. The presentation concludes by arguing the wicked problems model can change how user experience practitioners approach defining success and solutions.
The document discusses various tools that can be used for continuous improvement, including problem-solving cycles, brainstorming, cause and effect diagrams, checksheets, flow diagrams, and policy deployment. It provides brief explanations and examples of how to use each tool, with the problem-solving cycle presented as a multi-step model for identifying problems, defining them, exploring solutions, selecting options, implementing changes, and evaluating results.
This document summarizes the business case for employee referral programs (ERPs). It discusses how referrals produce the highest volume of applicants and the highest quality hires. Referral hires have higher retention rates and produce more profit than other sources. The document provides examples of companies that have achieved referral rates of 50% or more. It then outlines several strategic and tactical actions that can be taken to improve ERP results, such as prioritizing efforts, seeking referrals proactively, broadening eligibility, utilizing rewards, and using applicant tracking technology.
Why are all big companies so ineffective and why does nobody really like working there anymore? In this talk we will revisit work of Herbert Simon, one of the founders of Artificial Intelligence and 1978 Nobel Prize winner, and the model of problem-solving team effectiveness built upon it. This work combined with current interest in predictive behavioral analytics provides a prudent foundation for creating and sustaining vigorous and productive workplace.
Toyota has an eight-step problem solving process called Toyota Business Practices (TBP) that is used to implement the principles of the Toyota Way. The eight steps are: 1) clarify the problem and ideal solution, 2) assess the current situation, 3) prioritize smaller problems, 4) determine the root causes, 5) develop countermeasures, 6) implement the plan, 7) check the results, and 8) standardize successful solutions and spread them to other areas. This structured process uses the Plan-Do-Check-Act (PDCA) cycle to continuously improve processes through solving problems.
This document discusses managing priorities in complex environments. It suggests determining priorities based on importance rather than urgency, with importance defined by criteria like long-term impact and number of people affected. It recommends creating a plan with important tasks in priority order and time budgeted for each. Interruptions should be prevented unless truly important or from certain sources like one's boss. The document advises against multitasking and provides tips like doing hard tasks first and closing email to focus on one task at a time. Priorities are difficult to manage due to various pressures, but self-control is still possible.
201306 Five Routes to more Innovative Problem Solving MCKFrancisco Calzado
This document discusses using "flexons" as a framework for viewing complex problems through multiple lenses in order to generate more innovative solutions. It introduces five flexons or problem-solving frameworks derived from social and natural sciences: 1) Networks, 2) Evolutionary, 3) Decision-agent, 4) System-dynamics, and 5) Information-processing. The document provides examples of how each flexon can be applied and highlights that using multiple flexons together allows for a richer understanding of complex problems and identification of non-obvious solutions.
This document provides information on productive problem solving. It discusses what productive problem solving is, common impediments, and essential elements. It also outlines several problem solving methodologies and techniques, including the scientific method, brainstorming, FAST diagramming, and evaluating potential solutions. The goal is to provide a structured approach to defining problems, identifying root causes, generating alternatives, and selecting the best solution.
This document discusses achieving problem-solution fit by properly framing problems. It emphasizes spending more time understanding the problem before developing solutions. Proper problem framing involves gathering input from stakeholders, analyzing root causes, and reframing the problem as an opportunity. Developing a clear problem statement is important, as is considering different perspectives and how success would look. Mapping stakeholders and exploring problem types can provide useful context. Overall, the document stresses the importance of rigorous problem definition to develop effective solutions.
This document outlines the PAID problem solving process, which consists of 5 steps: (1) Problem Statement - defining the problem in a single sentence, (2) Analyze the Problem - examining what is wrong and right, (3) Identify Likely Causes - considering what has changed and potential causes, (4) Define Actual Causes - determining the most likely explanation, and (5) proving the identified cause. The document provides guidance on techniques for each step such as brainstorming, questioning, and herringbones to thoroughly analyze problems and identify root causes.
The document discusses decision making and problem solving. It provides definitions of problem solving and decision making. The scope of discussion includes clarifying problems, understanding collective problem solving, examining decision making models, and applying creativity in the problem solving process. It outlines the problem solving procedure as define, information/measures, analyze, generate alternatives, select alternatives, and decide/implement. Analysis techniques like cause and effect diagrams and the 5 whys are also examined.
Lead User Innovation - Club de la Innovación Costa RicaInnovare
Un surfeador creó la cámara GoPro para tomar “selfies” desde las olas. Dos emprendedores alquilaron su sala para ayudarse con la renta y así nació Airbnb. Casos como estos nos inspiraron a aprender sobre Lead User Innovation, el método del profesor del MIT Eric von Hippel.
Tool & techniques decision making processMae Parcero
This document discusses tools and techniques for decision making. It defines tools as physical items used to achieve goals and techniques as systematic procedures or routines used to accomplish tasks.
It then describes several decision making tools and techniques: nominal group technique, Delphi technique, brainstorming, multivoting, Pareto analysis, fishbone diagrams, and PMI analysis. For each technique it provides a brief explanation of how it works and how it can be used to make decisions.
Finally, it states that when making decisions one should consider both the positives and negatives to avoid losses and allow for sustained growth, but that ultimately decisions must be made and the consequences accepted to remain in control.
This training document discusses developing problem solving skills. It is divided into three modules that build on each other: problem, problem solving skills, and advice/alternative approaches. The document defines what a problem is and discusses common types of problems that arise in the workplace. It also presents activities for participants to discuss problems they have faced and how they resolved them. Finally, it outlines various problem solving techniques like 5 Whys, appreciation/brainstorming, and root cause analysis that can be used to define problems, generate alternatives, and select solutions.
Thinking Tools - Empowering Students to Get the Job DoneWorldFuture2015
This document provides guidance on creative problem solving tools and techniques. It discusses both divergent and convergent thinking approaches. The divergent section includes guidelines for generating many novel ideas using techniques like brainstorming, brainwriting, and SCAMPER. The convergent section discusses focusing on the best ideas and provides guidelines for affirmative judgment. The document then provides examples of applying specific tools like attribute listing, morphological matrices, and hits and hot spots to structure problem solving.
Practical Experience with Christensen's Innovation Methodology JOBS(R) Jobs-t...vonreventlow
Clayton Christensen's Jobs-to-be-done approach describe a series of steps to create innovation systematically. This deck describes the application of the methodology to the creation of the Avaya Flare User Experience, the Avaya Digital Video Device and the related enterprise cloud offer. We found key for success is to add focus on emotions. And the result to be a condensed job description as more work is required to detail the solutions that it becomes testable against objectives and barriers.
This document provides guidance on product management techniques for discovering user needs and developing product ideas. It discusses how to understand users through interviews and observation to identify pain points. It also outlines a three-step process for proposing product changes: 1) deeply understand the problem, 2) identify an ideal solution, and 3) scope a practical solution. Additionally, it covers how to create clear product specifications that consider functionality, layout, text, and avoid issues that could complicate development. Examples of mockups, user flows, and other tools for visualizing and specifying products are also presented.
ISG: TechChange Presentation on M&E MIS SystemsMichael Klein
The document discusses planning and implementing an M&E (monitoring and evaluation) MIS (management information system) for projects. It notes that historically monitoring has taken a backseat to evaluation, but adaptive management and agile programming now demand iterative data collection. An M&E MIS can provide timely data for decision-makers if planned properly from the start with clear objectives, management responsibilities, and evaluation targets. Key steps include assessing existing systems, developing functional specifications, and managing organizational change. The tool's success depends on how problems are defined, how the system is used, and whether data collection and review processes are in place.
Lean Startup Customer Development InterviewFranck Debane
The document provides an overview of the Lean Startup methodology. It discusses:
1) Traditional approaches to starting companies often involve writing business plans, raising funding, and building products without customer feedback which leads to high failure rates.
2) Lean Startup flips this process by focusing first on discovering customer problems through interviews and validations, then rapidly building minimum viable products to test solutions with customers.
3) The goal is to gather feedback to learn which assumptions are valid and pivot as needed, rather than wasting resources on solutions customers don't want. This allows startups to succeed by developing products customers need.
The document discusses idea generation techniques and success factors. It defines idea generation as coming up with possible solutions to problems and opportunities. Several idea generation techniques are covered, including idea challenges, SCAMPER, opposite thinking, brainstorm cards, and analogy thinking. Success factors for idea generation include defining the problem well, involving the right people, setting constraints, considering timing, marketing ideas effectively, and planning crisis responses. The overall purpose of generating new ideas is to improve existing approaches and develop novel solutions.
The document discusses the challenges of translating mental models into virtual models. It outlines two main problems: 1) A mental model originator may have gaps or biases that prevent a clear shared understanding, and 2) Getting different individuals and disciplines on the same page due to varying communication styles and perspectives. The document proposes that finding consensus on requirements and representing the model through techniques like storyboarding can help address these problems, though developing a shared virtual representation of a mental model is a "wicked problem" with no definitive solution due to many complex variables.
The document discusses decision making and problem solving. It covers defining problems, gathering relevant information to analyze problems, and generating and selecting alternatives. The problem solving process involves defining the problem, collecting information and measures, analyzing the problem, generating alternatives, selecting alternatives, and deciding on and implementing a solution. Cause and effect diagrams like fishbone diagrams can be used to identify and analyze the root causes of problems. Collecting the right information through questions is important for fully understanding problems before attempting to solve them.
The document describes the process and methodology for an innovation hackathon. It involves 7 steps: 1) understand the customer, 2) define the customer, 3) define the problem, 4) come up with a solution, 5) validate assumptions, 6) build an MVP, and 7) get feedback on the MVP. Participants will form teams, come up with solutions to address customer problems, validate assumptions, and present their MVPs to receive feedback. The goal is to use lean startup methodology to experimentally test solutions.
This document provides an introduction to Lean Startup principles including customer development, minimum viable products, pivoting, and eliminating waste. It emphasizes that the majority of products fail because customers don't want them, not due to inability to build them. Lean focuses on learning what customers want through conversations rather than assumptions. Key steps are outlined such as conducting customer interviews and using a validation board to track progress.
The document discusses various problem solving tools and techniques, including:
- Problem analysis, which involves investigating a situation to understand the problem and recommend solutions. Key steps include identifying the problem, conducting background research, reporting findings, drawing conclusions, and making recommendations.
- Cause and effect analysis (fishbone diagrams), which help identify likely causes of a problem by considering various factors and brainstorming possible causes related to each factor.
- SWOT analysis, which evaluates strengths, weaknesses, opportunities, and threats to assess an organization's competitive position.
- SMART objectives, which provide a framework for setting specific, measurable, achievable, relevant, and timely goals.
- Gantt charts, which are bar charts
This document outlines an 11-step process for developing an app using design thinking principles. It discusses defining the problem, envisioning potential solutions, refining options through prototyping and user testing, and ultimately selecting a final solution. The key steps involve understanding the current reality, brainstorming what could be through concepts and business models, testing ideas through pretypes and experiments, and iterating based on feedback to identify the best option to implement. Design thinking is presented as a human-centered approach to problem-solving that generates innovative solutions through empirical means.
Brian Fitzsimmons on the Business Strategy and Content Flywheel of Barstool S...Neil Horowitz
On episode 272 of the Digital and Social Media Sports Podcast, Neil chatted with Brian Fitzsimmons, Director of Licensing and Business Development for Barstool Sports.
What follows is a collection of snippets from the podcast. To hear the full interview and more, check out the podcast on all podcast platforms and at www.dsmsports.net
IMPACT Silver is a pure silver zinc producer with over $260 million in revenue since 2008 and a large 100% owned 210km Mexico land package - 2024 catalysts includes new 14% grade zinc Plomosas mine and 20,000m of fully funded exploration drilling.
The APCO Geopolitical Radar - Q3 2024 The Global Operating Environment for Bu...APCO
The Radar reflects input from APCO’s teams located around the world. It distils a host of interconnected events and trends into insights to inform operational and strategic decisions. Issues covered in this edition include:
Anny Serafina Love - Letter of Recommendation by Kellen Harkins, MS.AnnySerafinaLove
This letter, written by Kellen Harkins, Course Director at Full Sail University, commends Anny Love's exemplary performance in the Video Sharing Platforms class. It highlights her dedication, willingness to challenge herself, and exceptional skills in production, editing, and marketing across various video platforms like YouTube, TikTok, and Instagram.
The Genesis of BriansClub.cm Famous Dark WEb PlatformSabaaSudozai
BriansClub.cm, a famous platform on the dark web, has become one of the most infamous carding marketplaces, specializing in the sale of stolen credit card data.
B2B payments are rapidly changing. Find out the 5 key questions you need to be asking yourself to be sure you are mastering B2B payments today. Learn more at www.BlueSnap.com.
HOW TO START UP A COMPANY A STEP-BY-STEP GUIDE.pdf46adnanshahzad
How to Start Up a Company: A Step-by-Step Guide Starting a company is an exciting adventure that combines creativity, strategy, and hard work. It can seem overwhelming at first, but with the right guidance, anyone can transform a great idea into a successful business. Let's dive into how to start up a company, from the initial spark of an idea to securing funding and launching your startup.
Introduction
Have you ever dreamed of turning your innovative idea into a thriving business? Starting a company involves numerous steps and decisions, but don't worry—we're here to help. Whether you're exploring how to start a startup company or wondering how to start up a small business, this guide will walk you through the process, step by step.
Best practices for project execution and deliveryCLIVE MINCHIN
A select set of project management best practices to keep your project on-track, on-cost and aligned to scope. Many firms have don't have the necessary skills, diligence, methods and oversight of their projects; this leads to slippage, higher costs and longer timeframes. Often firms have a history of projects that simply failed to move the needle. These best practices will help your firm avoid these pitfalls but they require fortitude to apply.
Storytelling is an incredibly valuable tool to share data and information. To get the most impact from stories there are a number of key ingredients. These are based on science and human nature. Using these elements in a story you can deliver information impactfully, ensure action and drive change.
At Techbox Square, in Singapore, we're not just creative web designers and developers, we're the driving force behind your brand identity. Contact us today.
Structural Design Process: Step-by-Step Guide for BuildingsChandresh Chudasama
The structural design process is explained: Follow our step-by-step guide to understand building design intricacies and ensure structural integrity. Learn how to build wonderful buildings with the help of our detailed information. Learn how to create structures with durability and reliability and also gain insights on ways of managing structures.
SATTA MATKA SATTA FAST RESULT KALYAN TOP MATKA RESULT KALYAN SATTA MATKA FAST RESULT MILAN RATAN RAJDHANI MAIN BAZAR MATKA FAST TIPS RESULT MATKA CHART JODI CHART PANEL CHART FREE FIX GAME SATTAMATKA ! MATKA MOBI SATTA 143 spboss.in TOP NO1 RESULT FULL RATE MATKA ONLINE GAME PLAY BY APP SPBOSS
The 10 Most Influential Leaders Guiding Corporate Evolution, 2024.pdfthesiliconleaders
In the recent edition, The 10 Most Influential Leaders Guiding Corporate Evolution, 2024, The Silicon Leaders magazine gladly features Dejan Štancer, President of the Global Chamber of Business Leaders (GCBL), along with other leaders.
The 10 Most Influential Leaders Guiding Corporate Evolution, 2024.pdf
We the People of the Crowd
1. Eugene Ivanov (2021) 1
We the People of the Crowd
A short introduction to crowdsourcing
2. What Is Crowdsourcing?
Eugene Ivanov (2021) 2
Simplifying Jeff Howe’s original
definition, I define crowdsourcing
as outsourcing a job to a crowd
of external contributors
[Crowdsourcing is] “the act of taking a job traditionally
performed by a designated agent (usually an employee) and
outsourcing it to an undefined, generally large group of
people in the form of an open call.”
(Jeff Howe, 2006)
3. Two Forms of Crowdsourcing
Eugene Ivanov (2021) 3
https://www.qmarkets.net/blog/what-is-crowdsourcing-and-how-can-it-add-value-to-your-enterprise/?utm_content=119105595&utm_medium=social&utm_source=linkedin&hss_channel=lcp-930816
While there is a lot of outsourceable jobs,
crowdsourcing can be divided in two major
forms: adding capacity and accessing expertise
4. Adding Capacity (Microtasking): From Small Parts to the Whole
Eugene Ivanov (2021) 4
Adding capacity (microtasking) is the
process of splitting a large job into
small, usually identical, parts. A crowd
is then asked to assemble these
smaller tasks into a larger whole
5. Adding Capacity: The Benefits of a Multiplier Effect
Eugene Ivanov (2021) 5
Adding capacity provides the benefits of
a multiplier effect: using multiple
contributors in parallel allows the whole
job to be completed faster as a result
6. Accessing Expertise (Crowdsourced Innovation)
Eugene Ivanov (2021) 6
https://www.qmarkets.net/blog/what-is-crowdsourcing-and-how-can-it-add-value-to-your-enterprise/?utm_content=119105595&utm_medium=social&utm_source=linkedin&hss_channel=lcp-930816
Accessing expertise is the process of exploring
the proverbial “wisdom of crowds.” It is used to
help firms achieve an important objective, like
designing a new product or optimizing
performance
7. Crowdsourced Innovation: The Value of Extreme Value
Eugene Ivanov (2021) 7
Idea Value
Crowd
Experts
Probability
of
getting
an
idea Accessing expertise is a realization of the
“value of extreme value” concept. While
experts usually provide solutions that are
more valuable on average than those
provided by the crowd, it is the crowd
that often comes up with an extremely
valuable, sometimes completely
unorthodox, solution
8. 5 Characteristics of a Problem Suitable for Crowdsourcing
Eugene Ivanov (2021) 8
The problem must be relevant to your business, so
that solving it would result in creating an
appreciable value (ideally measurable in $$ terms).
Ideally, the problem should be such that even
a partial solution to it would still result in
creating an appreciable value for your
business.
The problem could be formulated as a small,
specific, and actionable question/task that can
be answered/accomplished within weeks or
months, not years.
You can articulate specific, ideally quantitative,
requirements that every successful solution
must meet.
If solving the problem requires sharing internal
information with external parties, the data must
be appropriately prepared (i.e., decontextualized,
deanonymized, etc.), ideally well in advance.
Five major
characteristics
of a problem
making it
suitable for a
successful
crowdsourcing
campaign
9. 6 Steps to Developing Effective Problem Statement: Overview
Eugene Ivanov (2021) 9
Title F Title D
Title E
Title B
This is a sample text.
Insert your desired
text here.
This is a sample text.
Insert your desired
text here.
This is a sample
text. Insert your
desired text
here.
This is a
sampletext.
Insert your
desired text
here.
This is a sample
text. Insert your
desired text
here.
06 What is the form/format
the desired solution should
be presented in?
DELIVERABLES
5 Outline criteria that every
successful solution should
meet.
SUCCESS
CRITERIA
4 Can you describe solutions
you know you will not
accept?
EXCLUSIONS
1
Describe your problem
(pain point). What is the
origin of the problem?
PAIN
2
Have you already tried to
solve this problem? Why
were these efforts
unsuccessful?
PAST
3
Describe a desired
solution to your problem.
SOLUTION
1
PAIN
2
PAST
3
SOLUTION
4
EXCLUSIONS
5
SUCCESS
CRITERIA
6
DELIVERABLES
Correctly defining the problem-to-be-solved
is the key prerequisite for a successful
crowdsourcing campaign. Presented here are
six most important components of effective
problem statement
10. Step 1 - Pain
Eugene Ivanov (2021) 10
Finding the cause of a problem is not always easy
- and confusing symptoms and the cause of the
pain is a common mistake. A simple root cause
(“fishbone”) analysis is usually enough to
correctly define the origin of the problem.
Otherwise, you’ll be looking for the right answers
to the wrong question.
PAIN
Title F Title D
Title E
Title B
This is a sample text.
Insert your desired
text here.
This is a sample text.
Insert your desired
text here.
This is a sample
text. Insert your
desired text
here.
This is a
sampletext.
Insert your
desired text
here.
This is a sample
text. Insert your
desired text
here.
1
PAIN
2
PAST
3
SOLUTION
4
EXCLUSIONS
5
SUCCESS
CRITERIA
6
DELIVERABLES
11. Step 2 - Past
Eugene Ivanov (2021) 11
Title F Title D
Title E
Title B
This is a sample text.
Insert your desired
text here.
This is a sample text.
Insert your desired
text here.
This is a sample
text. Insert your
desired text
here.
This is a
sampletext.
Insert your
desired text
here.
This is a sample
text. Insert your
desired text
here.
1
PAIN
2
PAST
3
SOLUTION
4
EXCLUSIONS
5
SUCCESS
CRITERIA
6
DELIVERABLES
Describing past efforts to solve a problem is
useful in two ways. First, knowing about prior
unsuccessful attempts can help better understand
the nature of the problem. Second, this prevents
re-inventing a wheel that doesn’t work.
PAST
12. Step 3 - Solution
Eugene Ivanov (2021) 12
Title F Title D
Title E
Title B
This is a sample text.
Insert your desired
text here.
This is a sample text.
Insert your desired
text here.
This is a sample
text. Insert your
desired text
here.
This is a
sampletext.
Insert your
desired text
here.
This is a sample
text. Insert your
desired text
here.
1
PAIN
2
PAST
3
SOLUTION
4
EXCLUSIONS
5
SUCCESS
CRITERIA
6
DELIVERABLES
Describing a potential solution helps define the
scope of the project. You can approach this by first
outlining an ideal solution (the solution of your
dreams) and then subtracting everything you can
live without. Alternatively, you can define your
minimally viable solution and then suggest
improvements and/or add-ons.
SOLUTION
13. Step 4 - Exclusions
Eugene Ivanov (2021) 13
Title F Title D
Title E
Title B
This is a sample text.
Insert your desired
text here.
This is a sample text.
Insert your desired
text here.
This is a sample
text. Insert your
desired text
here.
This is a
sampletext.
Insert your
desired text
here.
This is a sample
text. Insert your
desired text
here.
1
PAIN
2
PAST
3
SOLUTION
4
EXCLUSIONS
5
SUCCESS
CRITERIA
6
DELIVERABLES
This could be as simple as: “We are not interested
in any solution requiring an investment of more
than a $1,000.” However, it’s very important to
warn potential Solvers about unacceptable
solutions. There is nothing worse than rejecting a
solution based on the requirement(s) you did not
disclose at the outset.
EXCLUSIONS
14. Step 5 – Success Criteria
Eugene Ivanov (2021) 14
Title F Title D
Title E
Title B
This is a sample text.
Insert your desired
text here.
This is a sample text.
Insert your desired
text here.
This is a sample
text. Insert your
desired text
here.
This is a
sampletext.
Insert your
desired text
here.
This is a sample
text. Insert your
desired text
here.
1
PAIN
2
PAST
3
SOLUTION
4
EXCLUSIONS
5
SUCCESS
CRITERIA
6
DELIVERABLES
Defining success criteria in the Problem
Statement allows potential Solvers to know from
the outset what they are expected to do to solve
the problem. Besides, it makes the evaluation of
the future solutions straightforward and
transparent.
SUCCESS CRITERIA
15. Step 6 – Deliverables
Eugene Ivanov (2021) 15
Title F Title D
Title E
Title B
This is a sample text.
Insert your desired
text here.
This is a sample text.
Insert your desired
text here.
This is a sample
text. Insert your
desired text
here.
This is a
sampletext.
Insert your
desired text
here.
This is a sample
text. Insert your
desired text
here.
1
PAIN
2
PAST
3
SOLUTION
4
EXCLUSIONS
5
SUCCESS
CRITERIA
6
DELIVERABLES
This part of the Problem Statement is more
important that it may seem. For example, Solvers
may believe that all they need to do is to write a
proposal, whereas you want a prototype. Or a Solver
thinks that you need a prototype (and decides not to
participate), while all you need is an idea. Excluding
any misunderstanding regarding the solution format
is crucial.
DELIVERABLES
16. Eugene Ivanov (2021) 16
Crowd Ecosystem
External Crowd
Hybrid Crowd
Internal
Crowd
Crowd Composition Platform
Internal Employees • Internal communication
channels (email, Slack, MS
Teams, etc.)
• Internal innovation portals
Hybrid Customers, suppliers,
academic and business
partners, etc. in addition to
employees
• External communication
channels (email, Google docs,
etc.)
• Internal innovation portals
External Anyone with Internet access • Open innovation portals
• Open innovation intermediaries
Different types of crowds, their
composition, and means of reaching
17. Strength:
• Diversity of responses
Eugene Ivanov (2021) 17
Internal vs. External Crowds
Internal & Hybrid External
Weakness:
• Lack of breadth and diversity of
responses due to groupthink
Objective Internal & Hybrid External
Generate new product or service ideas + +++
Solve complex technical/business problems ++ +++
Solve “company-specific” problems +++ ++
Optimize internal processes and operations +++ +
Strength:
• Easy to access
• High-quality contributions
Weakness:
• High level of “noise”
• Could be expensive
Comparative benefits and
drawbacks of external vs.
internal/hybrid crowds
18. Eugene Ivanov (2021) 18
Crowdsourcing Decision Tree-1: Internal vs. External
External
Crowdsourcing
Internal
Crowdsourcing
YES
YES
YES
YES
YES
NO
NO
NO
Do you have a well-
defined
problem/task?
Is highly
sensitive IP
involved?
Do you have
a budget of
≥$15K?
Do you want to
optimize an
internal process?
Are you looking
for the diversity
of responses?
The choice between internal
and external crowdsourcing.
19. Eugene Ivanov (2021) 19
Crowdsourcing Decision Tree-2: Crowdsourcing vs. Co-Creation
Adding Capacity
(Microtasking)
YES
NO
CO-CREATION APPROACHES:
• Engaging customers, suppliers
• Joint ventures
• Engaging startups, CVC
• Etc.
YES
Accessing Expertise
(Crowdsourced
Innovation)
YES
Can you formulate your
‘job-to-be-done’ as a
problem or a task that is
Specific
Measurable
Achievable
Relevant
Time-bound?
Does your task require assembling
large number of small identical
contributions?
Does your problem require
a unique solution?
CROWDSOCURCING
The choice between crowdsourcing
and co-creation and between different
types of crowdsourcing
20. Eugene Ivanov (2021) 20
Crowdsourcing Decision Tree-3: Selecting a Platform
What kind of
a problem do
you want to
solve?
Solve a technical or business
problem
Get customer insight; user
testing
Solve a data science-related
problem
Buy, sell, or exchange IP;
find a partner
Find on-demand expert
InnoCentive
HeroX
Hyvecrowd
Topcoder
Kaggle
DrivenData
Yet2.com
Innoget
Tynax
YourEncore
Maven
Presans
MindSumo
Chaordix
Dscout