Fight Your Brain: Innovate!
Outline/Structure of the Talk
- Introduction (2 - 3 min talk)
- Creativity vs Innovation (7 - 8 min)
Look at a famous example of innovation and see that creativity is not as important as we may think. - What is a cognitive bias? (7 - 8 min)
Presentation of the dual process theory with two small mind exercises and further discussion of why and how cognitive biases exist. - Presentation of a few biases (10 min)
I use small exercises where I interact with the audience so that participant can experience the biases I am presenting. - Some reflection on how to fight biases (7 - 8 min)
Talk about the way we can actively fight this biases and reduce their influence on our decisions if that is even possible and show that creating a culture of experimentation is essential. - Q&A
Learning Outcome
- Innovation is not the same as creativity. You don't have to conceive new ideas to innovate you have to try ideas.
- Everyone is therefore a potential innovator and the more thought diversity the more potential for innovation.
- We are irrational beings and some of the decision we make are affected by cognitive biases
- These biases are a self inflicted limit on innovation
- Creating a culture of experimentation where every idea is welcome is a key component of innovation
Target Audience
Anyone with an interest for how the brain works.
schedule Submitted 2 years ago
People who liked this proposal, also liked:
-
keyboard_arrow_down
hannah deutscher - From retail to redux - my journey of becoming a developHER
20 Mins
Talk
Beginner
Almost everyone has had a pivotal moment that, on reflection, you realise was the catalyst for you to change the course of your life.
After working in retail for over 15 years, I had one of these moments that lead me to persue a career as a developer, through the developHER program at MYOB.
I will be sharing my story of successes, failures and many MANY learnings which I hope can help or inspire you or someone you know on their tech journey.
-
keyboard_arrow_down
Prashant Sagar - Why you should all kill your agile ceremonies?
20 Mins
Talk
Advanced
We all started our agile journey with some recommended template practices years ago. Over many many retros some of the practices persevered, pivoted or perished. In this talk I would like to share a team's experiment on why and what happens when you hit the hard reset button.
-
keyboard_arrow_down
Mark Barber / Simon Bristow - Lean Change at MYOB
Mark BarberAgile CoachAdaptovateSimon BristowChampion, Business Agility Transformation460degreesschedule 2 years ago
90 Mins
Case Study
Advanced
Lean change management is an approach to organisational improvement and transformation that uses lean startup principles to drive change. Collaboration, feedback and experimentation allow us to make small and incremental changes that we can measure and learn from and counters the big bang approach that so often makes change painful. Embarking on a journey of discovery and change, we have adopted lean change management and applied it in ways that have created real change at MYOB. We will share our experiences to give you the tools to both assess if lean change is suitable for your organisations, and how to get started if it is.
-
keyboard_arrow_down
Mark Barber - Measuring for Team Effectiveness
45 Mins
Talk
Intermediate
To make our products great, we can use the build-measure-learn cycle to drive continuous improvement with a lean startup approach. An approach to making our teams great is the plan-do-check-act cycle. Both "measure" and "check" imply the use of data to inform our decisions. To counter the common retrospective anti-patterns we see around actions that never get done, we can take these principles and ensure we are really adapting and not just inspecting. When running improvement experiments to improve the way the team works it is crucial to use some form of data to verify that the change has moved you toward your target condition. To do this effectively, we need to go beyond output focused measures and focus on metrics that tell us about the outcomes we are trying to reach. We can’t, and shouldn’t, measure everything, so I will explore what to measure, and discuss some common ways of capturing, visualising and using the data for team effectiveness. These aren’t metrics for managers and they aren’t metrics to compare teams.
Public Feedback