Exercise 2 (Green) - Labels and Unpacking Them
•Download as DOCX, PDF•
0 likes•85 views
This document provides instructions for an exercise to practice identifying and unpacking labels. The green partner is instructed to build a plain skyscraper and receive feedback from their partner, asking questions to understand the meaning behind any labels used. They are then told to provide feedback on their partner's ornate creation, using an evaluative label like "decorative" or "elaborate." The partners repeat the process of building, receiving feedback, and giving feedback to get more practice unpacking the meaning behind different labels.
Report
Share
Report
Share
Recommended
Exercise 2 (Blue) - Labels and Unpacking Them
Blue partner is instructed to build an ornate creation and critique their partner's plain creation using evaluative labels like "plain", "ordinary", or "boring". The blue partner should then ask for clarification on the labels to unpack their meaning and understand their partner's perspective, repeating the process until comfortable unpacking different labels.
Exercise 3 (Blue) - Truth Triggers
This document provides secret instructions for an exercise called "Truth Triggers" between two partners, a blue partner and an unknown partner. The exercise involves building something using colors then giving and receiving feedback on each other's creations in order to experience and defuse truth triggers. When receiving feedback, the blue partner is instructed to pay attention to their physical and emotional reactions to identify what being triggered feels like, then use techniques to defuse the trigger such as considering what their partner doesn't know or interpreting the data differently before responding calmly.
Exercise 5 - Identity Triggers
1) Partners build something representing themselves and share the creations with each other.
2) Partners take turns providing aggressive feedback on each other's creations. The goal is for the listener to internalize the feedback and feel like it is a critique of themselves, triggering an identity reaction.
3) The listener practices techniques to look objectively at the feedback by examining their feelings, stories, the actual feedback, and limits of what doesn't apply to help defuse the identity trigger. The exercise can be repeated as needed.
Exercise 3 (Green) - Truth Triggers
This document provides instructions for an exercise called "Truth Triggers" that involves two partners building a 2D structure and giving each other feedback. The goal is to experience and defuse truth triggers. Partner A builds something and describes it, then receives feedback from Partner B, paying attention to any physical or emotional reactions, before using techniques to avoid triggers. Partner A then provides feedback to Partner B's creation, using evaluation or coaching and acting strongly disapproving of their choice. The exercise can be repeated as many times as desired until comfortable with triggers and defusing techniques.
Exercise 4 (Green) - Relationship Triggers
This exercise involves partners competing against each other by giving each other feedback on models they created. One partner will give two pieces of feedback to the other - one true suggestion to improve the model's speed involving adding a red piece, and one false suggestion involving adding a blue piece. The goal is to determine which feedback is true and convince their partner to incorporate it, while also identifying the root cause of any conflicts that arise at a systems level.
Exercise 1 - Feedback and Mirror Types
The document provides instructions for an exercise to practice different types of feedback and mirrors. Partners take turns building something with plastic bricks, then describing their creation. They practice giving each other coaching feedback by suggesting improvements, evaluation feedback by commenting on physical aspects, and appreciation feedback by expressing gratitude. Finally, partners take turns acting as supportive mirrors by reassuring each other and honest mirrors by offering honest opinions about each other's creations. The goal is to get familiar with these feedback and mirror techniques.
Learning Feedback with LEGO - The Building Blocks of Giving and Receiving Fee...
This document provides guidance on effectively giving and receiving feedback. It discusses the different types of feedback (appreciation, coaching, evaluation) and mirrors (supportive, honest). It also covers common feedback triggers related to truth, relationships, and identity. Strategies are presented for unpacking labels, addressing triggers, and having a productive feedback conversation using techniques like active listening and problem solving. The overall message is that feedback is important for growth but often fails due to poor delivery; following best practices can help overcome challenges and make feedback more effective.
SXSW 2016 takeaways
The document summarizes key takeaways from the SXSW conference. Some of the main topics discussed include: 1) The importance of designing technology with purpose and creating positive human experiences. 2) How collaboration between companies can drive innovation. 3) The value of not being constrained by audiences and taking creative risks. 4) The growing role of virtual and augmented reality. 5) How the rate of technological change is accelerating exponentially. 6) How cognitive computing is being applied across many domains to solve problems. 7) Emerging technologies like self-driving cars that are closer to widespread use than perceived. 8) How ubiquitous computing is already integrating technology into many aspects of life. 9) The growing role of robots and focus on
Recommended
Exercise 2 (Blue) - Labels and Unpacking Them
Blue partner is instructed to build an ornate creation and critique their partner's plain creation using evaluative labels like "plain", "ordinary", or "boring". The blue partner should then ask for clarification on the labels to unpack their meaning and understand their partner's perspective, repeating the process until comfortable unpacking different labels.
Exercise 3 (Blue) - Truth Triggers
This document provides secret instructions for an exercise called "Truth Triggers" between two partners, a blue partner and an unknown partner. The exercise involves building something using colors then giving and receiving feedback on each other's creations in order to experience and defuse truth triggers. When receiving feedback, the blue partner is instructed to pay attention to their physical and emotional reactions to identify what being triggered feels like, then use techniques to defuse the trigger such as considering what their partner doesn't know or interpreting the data differently before responding calmly.
Exercise 5 - Identity Triggers
1) Partners build something representing themselves and share the creations with each other.
2) Partners take turns providing aggressive feedback on each other's creations. The goal is for the listener to internalize the feedback and feel like it is a critique of themselves, triggering an identity reaction.
3) The listener practices techniques to look objectively at the feedback by examining their feelings, stories, the actual feedback, and limits of what doesn't apply to help defuse the identity trigger. The exercise can be repeated as needed.
Exercise 3 (Green) - Truth Triggers
This document provides instructions for an exercise called "Truth Triggers" that involves two partners building a 2D structure and giving each other feedback. The goal is to experience and defuse truth triggers. Partner A builds something and describes it, then receives feedback from Partner B, paying attention to any physical or emotional reactions, before using techniques to avoid triggers. Partner A then provides feedback to Partner B's creation, using evaluation or coaching and acting strongly disapproving of their choice. The exercise can be repeated as many times as desired until comfortable with triggers and defusing techniques.
Exercise 4 (Green) - Relationship Triggers
This exercise involves partners competing against each other by giving each other feedback on models they created. One partner will give two pieces of feedback to the other - one true suggestion to improve the model's speed involving adding a red piece, and one false suggestion involving adding a blue piece. The goal is to determine which feedback is true and convince their partner to incorporate it, while also identifying the root cause of any conflicts that arise at a systems level.
Exercise 1 - Feedback and Mirror Types
The document provides instructions for an exercise to practice different types of feedback and mirrors. Partners take turns building something with plastic bricks, then describing their creation. They practice giving each other coaching feedback by suggesting improvements, evaluation feedback by commenting on physical aspects, and appreciation feedback by expressing gratitude. Finally, partners take turns acting as supportive mirrors by reassuring each other and honest mirrors by offering honest opinions about each other's creations. The goal is to get familiar with these feedback and mirror techniques.
Learning Feedback with LEGO - The Building Blocks of Giving and Receiving Fee...
This document provides guidance on effectively giving and receiving feedback. It discusses the different types of feedback (appreciation, coaching, evaluation) and mirrors (supportive, honest). It also covers common feedback triggers related to truth, relationships, and identity. Strategies are presented for unpacking labels, addressing triggers, and having a productive feedback conversation using techniques like active listening and problem solving. The overall message is that feedback is important for growth but often fails due to poor delivery; following best practices can help overcome challenges and make feedback more effective.
SXSW 2016 takeaways
The document summarizes key takeaways from the SXSW conference. Some of the main topics discussed include: 1) The importance of designing technology with purpose and creating positive human experiences. 2) How collaboration between companies can drive innovation. 3) The value of not being constrained by audiences and taking creative risks. 4) The growing role of virtual and augmented reality. 5) How the rate of technological change is accelerating exponentially. 6) How cognitive computing is being applied across many domains to solve problems. 7) Emerging technologies like self-driving cars that are closer to widespread use than perceived. 8) How ubiquitous computing is already integrating technology into many aspects of life. 9) The growing role of robots and focus on
Design Thinking Wallet Worksheets
This document provides instructions for participants to go through a design thinking process to design something useful for a partner. The process involves: 1) Examining and interviewing the partner to gain empathy, 2) Reframing the problem based on insights from interviews, 3) Generating alternative solutions, 4) Sharing solutions and getting feedback, 5) Iterating designs based on feedback, 6) Building a solution for the partner to interact with, and 7) Getting final feedback on the solution. The overall goal is for participants to use empathy, ideation, and feedback to design something meaningful that meets a partner's needs.
Exercise 4 (Blue) - Relationship Triggers
This document provides instructions for an exercise between partners that aims to trigger and defuse relationship issues while competing for candy bars. Partners will build models and give each other feedback with one true suggestion about improving the model and one false suggestion. The goal is to determine which feedback is true and convince the other partner to implement it, while also reflecting on the root causes of any conflicts that arise.
Exercise 6 - The Feedback Conversation
The document describes an exercise for partners to have a feedback conversation. It involves three phases:
1) Brainstorming a problem to solve together in 5 minutes. 2) Collaborating to build something that solves the problem in 10 minutes using imagination. 3) Having a feedback conversation about the collaboration for 10 minutes, with each partner opening to give and receive feedback with the goal of improving their partnership. The purpose is to have real discussions about how each partner performed and areas for improvement.
Stanford Peace Innovation Lab: ITBA Argentina workshop day 2
The document provides an overview of designing interventions using behavior design and design thinking approaches. It discusses the Fogg behavior model which examines how motivation, ability and triggers influence behaviors. Participants will create a design brief, prototype a solution based on the brief, and test the prototype's effectiveness. The goal is to help participants apply a process of empathizing with users, defining problems, ideating solutions, prototyping, and testing to design interventions that influence behaviors.
How to give a Creative Presentation in 10 minutes by Two pens
This is a primer for people who are put under the gun to present creative work in on-the-fly situations. Ten minutes can be well spent, if you do Creative Director Cynthia Hartwig's tricks. Or work you've spent weeks designing, writing and creating, will be deep-sixed faster than you can remove yourself from the room. Includes tips on recapping the creative brief, appointing a Meeting Czar (someone who runs the meeting and drives decisions) and presenting so that everybody can see that little, teeny mouse-type (assuming it's important). This deck is a supplement to How to Rock a Presentation by Cynthia Hartwig at Two Pens.
How to write a killer agency creative brief
The document provides tips on how to write an effective agency brief in 3 parts:
1) What makes a great brief including understanding the customer and fueling creative ideas.
2) How to uncover the 4 key creative triggers - the problem, customer insight, compelling message, and how to communicate it.
3) How to give constructive creative feedback by thinking like the customer, focusing on what works, and providing clear guidance for improvements.
SVD 2 Customer Discovery
This document provides an introduction to design thinking and the design thinking process. It outlines a workshop where participants will work through steps to gain empathy for a user, define problems, ideate solutions, prototype ideas, and get feedback in order to redefine problems and iterate on solutions. The goal is for participants to design something useful and meaningful for a partner by following the design thinking process of empathy, defining problems based on user needs, ideating solutions, prototyping, and getting feedback to improve designs.
Data science + design thinking a perfect blend to achieve the best user expe...
As data scientists, we invest much of our time on the business problem, the data, the statistics, the algorithm, and the model. But we can’t afford to overlook one very important component: the customer. A great AI and ML model with a poorly designed user experience is ultimately is going to fail. The world’s best data products are born from a perfect blend of data science and amazing user experience. Design thinking is a methodology for creative problem solving developed at the Stanford d.school and is used by world-class design firms like IDEO and many of the world’s leading brands like Apple, Google, Samsung, and GE.
Michael Radwin prepares a recipe for applying design thinking to the development of AI/ML products. You’ll discover deep customer empathy and fall in love with the customer’s problem (not the team’s solution), and you’ll learn to go broad and narrow, focusing on what matters most to customers. Michael shows you how to get customers involved in the development process by running rapid experiments and quick prototypes. These lessons blending data science and design thinking can be applied to products that leverage supervised and unsupervised machine learning models, as well as “old-school” AI expert systems.
What you'll learn
Discover deep customer empathy for the customer’s problem (not the team’s solution)
Learn to go broad and narrow, focusing on what matters most to customers and how to get customers involved in the development process by running rapid experiments and quick prototypes
The Saboteur in Your Retrospectives: Handout
The document discusses cognitive biases and provides tips for recognizing and mitigating biases in retrospectives. It recommends being aware of biases, talking to others to understand different perspectives, focusing on controllable factors, recording decisions made to avoid hindsight bias, and building trust within the team. The document warns against making excuses that blame others, using only positive or negative frames, trying to manipulate people, feeling bad about not predicting outcomes, seeking unnecessary information, and making hurried decisions under pressure. Lastly, it acknowledges that biases are part of human nature but taking time for self-reflection can help prevent developing self-loathing.
The Developer's Guide to Learning
This document provides an overview of effective learning strategies for developers. It discusses that learning involves multiple mechanisms beyond just memorization. While discomfort can be good for learning, learners have different styles that appeal to visual, auditory, physical senses. However, research shows that tailoring solely to learning styles has limited benefits. The document emphasizes developing theories of action and evaluating assumptions through experiments. It also explains the importance of both explicit and implicit knowledge as well as neuroplasticity. Overall, it encourages learners to challenge their comfort zones through novelty, varied practice techniques, and conscious evaluation of what they are learning.
The Whys and Hows of Impostor Syndrome and the Illusion of Transparency
Impostor Syndrome is a quiet and subversive force in a lot of developer's lives. They feel like they're faking their way through their job, and they silently panic as they wait for everyone to find out they don't really know what they're doing. It can be crippling, and left alone it can develop into an anxiety disorder, or worse. If you can relate, or even if you just want to learn how to be a little more confident in yourself, come and listen as we cover what Impostor Syndrome is, some theories why it happens, and strategies you can use to eliminate it (that's right, you actually can)!
Let's Talk About Mental Health Handout
This document provides guidance on discussing mental health issues with others. It suggests using experiential language to describe how one is feeling without judgment. If a person expresses clear intent to harm themselves or others, one should call for help. The goal is support, not fixing problems. Sample scripts are given for asking for help, offering help, explaining feelings, and checking in. Different types of interactions are outlined, emphasizing respect and care for both parties. Resources on mental health nonprofits, workbooks, and hotlines are listed.
Let's Talk About Mental Health
It’s a great time to be in technology. And yet despite the improvement in our tools, we somehow don’t spend time talking about how to maintain our most important tool - the one between our ears. Your mental health is arguably the single most important factor in your ability to perform well, avoid burnout, and build resiliency, but we shroud the topic in secrecy, stigma, and co-opted clinical language that makes us think we know what's going on. We often don't even speak of what we feel to family and friends until we're facing a crisis.
We need to change all of that. You don't have to stay in the dark, and you *don't* have to suffer alone. In this talk we’ll start with some basics about mental health, then cover the most common mental health challenges facing developers, and then learn about some techniques to supercharge your brain by improving your mental hygiene (whether you have a psychological disorder or not). Most importantly, you’ll learn how to have a conversation with your coworkers (and other people in your life) about supporting each other and finding your best selves.
Feedback Workshop KCDC2018
This document outlines a presentation on giving and receiving feedback using LEGO as a metaphor. It discusses how much time is spent on performance reviews and the pitfalls of current feedback practices. It then categorizes different types of feedback and explores why people want or fear certain types. The rest of the document provides exercises and guidance for giving feedback, including addressing triggers, focusing on interests over positions, and using a conversational arc.
Let's Talk About Mental Health - KCDC 2018
It’s a great time to be in technology. And yet despite the improvement in our tools, we somehow don’t spend time talking about how to maintain our most important tool - the one between our ears. Your mental health is arguably the single most important factor in your ability to perform well, avoid burnout, and build resiliency, but we shroud the topic in secrecy, stigma, and co-opted clinical language that makes us think we know what's going on. We often don't even speak of what we feel to family and friends until we're facing a crisis.
We need to change all of that. You don't have to stay in the dark, and you *don't* have to suffer alone. In this talk we’ll start with some basics about mental health, then cover the most common mental health challenges facing developers, and then learn about some techniques to supercharge your brain by improving your mental hygiene (whether you have a psychological disorder or not). Most importantly, you’ll learn how to have a conversation with your coworkers (and other people in your life) about supporting each other and finding your best selves.
Let's Talk About Mental Health Handout - KCDC 2018
This document discusses best practices for talking about and supporting mental health. It provides guidance on using experiential language to describe personal experiences, asking direct questions if a crisis is suspected, and offering support through scripts. The scripts cover asking for support, offering support to others, explaining feelings, and casual check-ins. Different types of interactions are outlined, such as asking for future help, responding in a crisis, and normal conversations. Resources for learning more about mental health and treatment options are also listed.
Let's Talk About Mental Health Handout - NDC Oslo 2018
This document provides guidance on discussing mental health issues with others. It suggests using experiential language to describe how one is feeling without judgment. When concerned about someone's safety, it's important to ask direct questions and call for help if they express intent to harm themselves or others. Scripts are presented for asking for support, offering support, explaining one's feelings, and checking in. Interaction types give examples of how to supportively engage if someone is in crisis or wants to discuss their mental health. Resources listed at the end can help with mental health screening and treatment options.
Let's Talk About Mental Health - NDC Oslo 2018
It’s a great time to be in technology. And yet despite the improvement in our tools, we somehow don’t spend time talking about how to maintain our most important tool - the one between our ears. Your mental health is arguably the single most important factor in your ability to perform well, avoid burnout, and build resiliency, but we shroud the topic in secrecy, stigma, and co-opted clinical language that makes us think we know what's going on. We often don't even speak of what we feel to family and friends until we're facing a crisis.
We need to change all of that. You don't have to stay in the dark, and you *don't* have to suffer alone. In this talk we’ll start with some basics about mental health, then cover the most common mental health challenges facing developers, and then learn about some techniques to supercharge your brain by improving your mental hygiene (whether you have a psychological disorder or not). Most importantly, you’ll learn how to have a conversation with your coworkers (and other people in your life) about supporting each other and finding your best selves.
Let's Talk About Mental Health Handout - Nebraska.Code 2018
This document discusses best practices for talking about and supporting mental health. It provides guidance on using experiential language to describe personal experiences, asking direct questions if a crisis is suspected, and offering support through scripts. The scripts cover asking for support, offering support, explaining feelings, and casual check-ins. Different types of interactions are outlined, such as asking for future help, responding in a crisis, and normal conversations. Resources for mental health information and support are also listed.
Let's Talk About Mental Health - Nebraska.Code 2018
It’s a great time to be in technology. And yet despite the improvement in our tools, we somehow don’t spend time talking about how to maintain our most important tool - the one between our ears. Your mental health is arguably the single most important factor in your ability to perform well, avoid burnout, and build resiliency, but we shroud the topic in secrecy, stigma, and co-opted clinical language that makes us think we know what's going on. We often don't even speak of what we feel to family and friends until we're facing a crisis.
We need to change all of that. You don't have to stay in the dark, and you *don't* have to suffer alone. In this talk we’ll start with some basics about mental health, then cover the most common mental health challenges facing developers, and then learn about some techniques to supercharge your brain by improving your mental hygiene (whether you have a psychological disorder or not). Most importantly, you’ll learn how to have a conversation with your coworkers (and other people in your life) about supporting each other and finding your best selves.
The Developer's Guide to Learning - 200OK 2018
The ability to learn things is an essential part of the developer’s toolkit, which is only getting more important as we march into the future. New technologies and new tools are released constantly. Even if you’re on a fixed tech stack on a long-running project, you need to evaluate and adapt to new versions of your tools and new software idioms as they're released.
The thing is, we’re never really taught HOW to learn things - we’re expected to just figure it out ourselves. It is my opinion that this is Really Terrible. If you share that opinion, do something about it by coming to this talk! Do you wonder about learning types? We'll cover those. Do you wonder how learning a new framework is different than learning best practices for that framework? We’ll discuss that, too! We’ll also talk about the neuroscience of learning, how your brain connects cause and effect, the tricks your memory plays on you, and more. By the end, you’ll hopefully have the tools you need to learn anything efficiently and effectively.
The Developer's Guide to Learning - Codestock 2018
The ability to learn things is an essential part of the developer’s toolkit, which is only getting more important as we march into the future. New technologies and new tools are released constantly. Even if you’re on a fixed tech stack on a long-running project, you need to evaluate and adapt to new versions of your tools and new software idioms as they're released.
The thing is, we’re never really taught HOW to learn things - we’re expected to just figure it out ourselves. It is my opinion that this is Really Terrible. If you share that opinion, do something about it by coming to this talk! Do you wonder about learning types? We'll cover those. Do you wonder how learning a new framework is different than learning best practices for that framework? We’ll discuss that, too! We’ll also talk about the neuroscience of learning, how your brain connects cause and effect, the tricks your memory plays on you, and more. By the end, you’ll hopefully have the tools you need to learn anything efficiently and effectively.
More Related Content
Similar to Exercise 2 (Green) - Labels and Unpacking Them
Design Thinking Wallet Worksheets
This document provides instructions for participants to go through a design thinking process to design something useful for a partner. The process involves: 1) Examining and interviewing the partner to gain empathy, 2) Reframing the problem based on insights from interviews, 3) Generating alternative solutions, 4) Sharing solutions and getting feedback, 5) Iterating designs based on feedback, 6) Building a solution for the partner to interact with, and 7) Getting final feedback on the solution. The overall goal is for participants to use empathy, ideation, and feedback to design something meaningful that meets a partner's needs.
Exercise 4 (Blue) - Relationship Triggers
This document provides instructions for an exercise between partners that aims to trigger and defuse relationship issues while competing for candy bars. Partners will build models and give each other feedback with one true suggestion about improving the model and one false suggestion. The goal is to determine which feedback is true and convince the other partner to implement it, while also reflecting on the root causes of any conflicts that arise.
Exercise 6 - The Feedback Conversation
The document describes an exercise for partners to have a feedback conversation. It involves three phases:
1) Brainstorming a problem to solve together in 5 minutes. 2) Collaborating to build something that solves the problem in 10 minutes using imagination. 3) Having a feedback conversation about the collaboration for 10 minutes, with each partner opening to give and receive feedback with the goal of improving their partnership. The purpose is to have real discussions about how each partner performed and areas for improvement.
Stanford Peace Innovation Lab: ITBA Argentina workshop day 2
The document provides an overview of designing interventions using behavior design and design thinking approaches. It discusses the Fogg behavior model which examines how motivation, ability and triggers influence behaviors. Participants will create a design brief, prototype a solution based on the brief, and test the prototype's effectiveness. The goal is to help participants apply a process of empathizing with users, defining problems, ideating solutions, prototyping, and testing to design interventions that influence behaviors.
How to give a Creative Presentation in 10 minutes by Two pens
This is a primer for people who are put under the gun to present creative work in on-the-fly situations. Ten minutes can be well spent, if you do Creative Director Cynthia Hartwig's tricks. Or work you've spent weeks designing, writing and creating, will be deep-sixed faster than you can remove yourself from the room. Includes tips on recapping the creative brief, appointing a Meeting Czar (someone who runs the meeting and drives decisions) and presenting so that everybody can see that little, teeny mouse-type (assuming it's important). This deck is a supplement to How to Rock a Presentation by Cynthia Hartwig at Two Pens.
How to write a killer agency creative brief
The document provides tips on how to write an effective agency brief in 3 parts:
1) What makes a great brief including understanding the customer and fueling creative ideas.
2) How to uncover the 4 key creative triggers - the problem, customer insight, compelling message, and how to communicate it.
3) How to give constructive creative feedback by thinking like the customer, focusing on what works, and providing clear guidance for improvements.
SVD 2 Customer Discovery
This document provides an introduction to design thinking and the design thinking process. It outlines a workshop where participants will work through steps to gain empathy for a user, define problems, ideate solutions, prototype ideas, and get feedback in order to redefine problems and iterate on solutions. The goal is for participants to design something useful and meaningful for a partner by following the design thinking process of empathy, defining problems based on user needs, ideating solutions, prototyping, and getting feedback to improve designs.
Data science + design thinking a perfect blend to achieve the best user expe...
As data scientists, we invest much of our time on the business problem, the data, the statistics, the algorithm, and the model. But we can’t afford to overlook one very important component: the customer. A great AI and ML model with a poorly designed user experience is ultimately is going to fail. The world’s best data products are born from a perfect blend of data science and amazing user experience. Design thinking is a methodology for creative problem solving developed at the Stanford d.school and is used by world-class design firms like IDEO and many of the world’s leading brands like Apple, Google, Samsung, and GE.
Michael Radwin prepares a recipe for applying design thinking to the development of AI/ML products. You’ll discover deep customer empathy and fall in love with the customer’s problem (not the team’s solution), and you’ll learn to go broad and narrow, focusing on what matters most to customers. Michael shows you how to get customers involved in the development process by running rapid experiments and quick prototypes. These lessons blending data science and design thinking can be applied to products that leverage supervised and unsupervised machine learning models, as well as “old-school” AI expert systems.
What you'll learn
Discover deep customer empathy for the customer’s problem (not the team’s solution)
Learn to go broad and narrow, focusing on what matters most to customers and how to get customers involved in the development process by running rapid experiments and quick prototypes
Similar to Exercise 2 (Green) - Labels and Unpacking Them (8)
Stanford Peace Innovation Lab: ITBA Argentina workshop day 2
Stanford Peace Innovation Lab: ITBA Argentina workshop day 2
How to give a Creative Presentation in 10 minutes by Two pens
How to give a Creative Presentation in 10 minutes by Two pens
Data science + design thinking a perfect blend to achieve the best user expe...
Data science + design thinking a perfect blend to achieve the best user expe...
More from Arthur Doler
The Saboteur in Your Retrospectives: Handout
The document discusses cognitive biases and provides tips for recognizing and mitigating biases in retrospectives. It recommends being aware of biases, talking to others to understand different perspectives, focusing on controllable factors, recording decisions made to avoid hindsight bias, and building trust within the team. The document warns against making excuses that blame others, using only positive or negative frames, trying to manipulate people, feeling bad about not predicting outcomes, seeking unnecessary information, and making hurried decisions under pressure. Lastly, it acknowledges that biases are part of human nature but taking time for self-reflection can help prevent developing self-loathing.
The Developer's Guide to Learning
This document provides an overview of effective learning strategies for developers. It discusses that learning involves multiple mechanisms beyond just memorization. While discomfort can be good for learning, learners have different styles that appeal to visual, auditory, physical senses. However, research shows that tailoring solely to learning styles has limited benefits. The document emphasizes developing theories of action and evaluating assumptions through experiments. It also explains the importance of both explicit and implicit knowledge as well as neuroplasticity. Overall, it encourages learners to challenge their comfort zones through novelty, varied practice techniques, and conscious evaluation of what they are learning.
The Whys and Hows of Impostor Syndrome and the Illusion of Transparency
Impostor Syndrome is a quiet and subversive force in a lot of developer's lives. They feel like they're faking their way through their job, and they silently panic as they wait for everyone to find out they don't really know what they're doing. It can be crippling, and left alone it can develop into an anxiety disorder, or worse. If you can relate, or even if you just want to learn how to be a little more confident in yourself, come and listen as we cover what Impostor Syndrome is, some theories why it happens, and strategies you can use to eliminate it (that's right, you actually can)!
Let's Talk About Mental Health Handout
This document provides guidance on discussing mental health issues with others. It suggests using experiential language to describe how one is feeling without judgment. If a person expresses clear intent to harm themselves or others, one should call for help. The goal is support, not fixing problems. Sample scripts are given for asking for help, offering help, explaining feelings, and checking in. Different types of interactions are outlined, emphasizing respect and care for both parties. Resources on mental health nonprofits, workbooks, and hotlines are listed.
Let's Talk About Mental Health
It’s a great time to be in technology. And yet despite the improvement in our tools, we somehow don’t spend time talking about how to maintain our most important tool - the one between our ears. Your mental health is arguably the single most important factor in your ability to perform well, avoid burnout, and build resiliency, but we shroud the topic in secrecy, stigma, and co-opted clinical language that makes us think we know what's going on. We often don't even speak of what we feel to family and friends until we're facing a crisis.
We need to change all of that. You don't have to stay in the dark, and you *don't* have to suffer alone. In this talk we’ll start with some basics about mental health, then cover the most common mental health challenges facing developers, and then learn about some techniques to supercharge your brain by improving your mental hygiene (whether you have a psychological disorder or not). Most importantly, you’ll learn how to have a conversation with your coworkers (and other people in your life) about supporting each other and finding your best selves.
Feedback Workshop KCDC2018
This document outlines a presentation on giving and receiving feedback using LEGO as a metaphor. It discusses how much time is spent on performance reviews and the pitfalls of current feedback practices. It then categorizes different types of feedback and explores why people want or fear certain types. The rest of the document provides exercises and guidance for giving feedback, including addressing triggers, focusing on interests over positions, and using a conversational arc.
Let's Talk About Mental Health - KCDC 2018
It’s a great time to be in technology. And yet despite the improvement in our tools, we somehow don’t spend time talking about how to maintain our most important tool - the one between our ears. Your mental health is arguably the single most important factor in your ability to perform well, avoid burnout, and build resiliency, but we shroud the topic in secrecy, stigma, and co-opted clinical language that makes us think we know what's going on. We often don't even speak of what we feel to family and friends until we're facing a crisis.
We need to change all of that. You don't have to stay in the dark, and you *don't* have to suffer alone. In this talk we’ll start with some basics about mental health, then cover the most common mental health challenges facing developers, and then learn about some techniques to supercharge your brain by improving your mental hygiene (whether you have a psychological disorder or not). Most importantly, you’ll learn how to have a conversation with your coworkers (and other people in your life) about supporting each other and finding your best selves.
Let's Talk About Mental Health Handout - KCDC 2018
This document discusses best practices for talking about and supporting mental health. It provides guidance on using experiential language to describe personal experiences, asking direct questions if a crisis is suspected, and offering support through scripts. The scripts cover asking for support, offering support to others, explaining feelings, and casual check-ins. Different types of interactions are outlined, such as asking for future help, responding in a crisis, and normal conversations. Resources for learning more about mental health and treatment options are also listed.
Let's Talk About Mental Health Handout - NDC Oslo 2018
This document provides guidance on discussing mental health issues with others. It suggests using experiential language to describe how one is feeling without judgment. When concerned about someone's safety, it's important to ask direct questions and call for help if they express intent to harm themselves or others. Scripts are presented for asking for support, offering support, explaining one's feelings, and checking in. Interaction types give examples of how to supportively engage if someone is in crisis or wants to discuss their mental health. Resources listed at the end can help with mental health screening and treatment options.
Let's Talk About Mental Health - NDC Oslo 2018
It’s a great time to be in technology. And yet despite the improvement in our tools, we somehow don’t spend time talking about how to maintain our most important tool - the one between our ears. Your mental health is arguably the single most important factor in your ability to perform well, avoid burnout, and build resiliency, but we shroud the topic in secrecy, stigma, and co-opted clinical language that makes us think we know what's going on. We often don't even speak of what we feel to family and friends until we're facing a crisis.
We need to change all of that. You don't have to stay in the dark, and you *don't* have to suffer alone. In this talk we’ll start with some basics about mental health, then cover the most common mental health challenges facing developers, and then learn about some techniques to supercharge your brain by improving your mental hygiene (whether you have a psychological disorder or not). Most importantly, you’ll learn how to have a conversation with your coworkers (and other people in your life) about supporting each other and finding your best selves.
Let's Talk About Mental Health Handout - Nebraska.Code 2018
This document discusses best practices for talking about and supporting mental health. It provides guidance on using experiential language to describe personal experiences, asking direct questions if a crisis is suspected, and offering support through scripts. The scripts cover asking for support, offering support, explaining feelings, and casual check-ins. Different types of interactions are outlined, such as asking for future help, responding in a crisis, and normal conversations. Resources for mental health information and support are also listed.
Let's Talk About Mental Health - Nebraska.Code 2018
It’s a great time to be in technology. And yet despite the improvement in our tools, we somehow don’t spend time talking about how to maintain our most important tool - the one between our ears. Your mental health is arguably the single most important factor in your ability to perform well, avoid burnout, and build resiliency, but we shroud the topic in secrecy, stigma, and co-opted clinical language that makes us think we know what's going on. We often don't even speak of what we feel to family and friends until we're facing a crisis.
We need to change all of that. You don't have to stay in the dark, and you *don't* have to suffer alone. In this talk we’ll start with some basics about mental health, then cover the most common mental health challenges facing developers, and then learn about some techniques to supercharge your brain by improving your mental hygiene (whether you have a psychological disorder or not). Most importantly, you’ll learn how to have a conversation with your coworkers (and other people in your life) about supporting each other and finding your best selves.
The Developer's Guide to Learning - 200OK 2018
The ability to learn things is an essential part of the developer’s toolkit, which is only getting more important as we march into the future. New technologies and new tools are released constantly. Even if you’re on a fixed tech stack on a long-running project, you need to evaluate and adapt to new versions of your tools and new software idioms as they're released.
The thing is, we’re never really taught HOW to learn things - we’re expected to just figure it out ourselves. It is my opinion that this is Really Terrible. If you share that opinion, do something about it by coming to this talk! Do you wonder about learning types? We'll cover those. Do you wonder how learning a new framework is different than learning best practices for that framework? We’ll discuss that, too! We’ll also talk about the neuroscience of learning, how your brain connects cause and effect, the tricks your memory plays on you, and more. By the end, you’ll hopefully have the tools you need to learn anything efficiently and effectively.
The Developer's Guide to Learning - Codestock 2018
The ability to learn things is an essential part of the developer’s toolkit, which is only getting more important as we march into the future. New technologies and new tools are released constantly. Even if you’re on a fixed tech stack on a long-running project, you need to evaluate and adapt to new versions of your tools and new software idioms as they're released.
The thing is, we’re never really taught HOW to learn things - we’re expected to just figure it out ourselves. It is my opinion that this is Really Terrible. If you share that opinion, do something about it by coming to this talk! Do you wonder about learning types? We'll cover those. Do you wonder how learning a new framework is different than learning best practices for that framework? We’ll discuss that, too! We’ll also talk about the neuroscience of learning, how your brain connects cause and effect, the tricks your memory plays on you, and more. By the end, you’ll hopefully have the tools you need to learn anything efficiently and effectively.
What Makes You DO Stuff? The Psychology of Motivation - Codestock 2018
Are you sick of the words "motivation", "empowerment", "engagement", or "incentivize"? Are you convinced that any attempt to actually motivate you, your coworkers, or your employees is doomed to end in a dystopian Dilbert-like nightmare? Do you suspect some of your coworkers - or even you - might be motivated by something other than money (and might even be replicants)? No need for a Voight-Kampff test... just come learn about the psychology of motivation, and how your brain responds to it! We'll cover the history of motivation theory, some more modern concepts that aren't often talked about, and then offer some suggestions about how to use your new knowledge to help your company - or at least you - finally get rid of those "Teamwork!" posters on the walls.
What Makes You DO Stuff? The Psychology of Motivation - Handout - Codestock 2018
This document provides a detailed list of ways to promote Type I motivation, which involves autonomy, mastery, and purpose. It recommends using frequent feedback instead of praise, paying above average wages fairly, allowing employee choice in projects and tasks, instituting paid time for self-directed work, running an autonomy audit, focusing feedback on effort not just talent, and animating teams with a sense of purpose rather than using rewards. The full list covers strategies for hiring, measuring performance, promoting autonomy, mastery, and purpose to encourage intrinsic motivation.
Let's Talk About Mental Health - DevUp 2017
It’s a great time to be in technology. Computers keep getting better. More and more devices keep getting connected to the internet. Javascript frameworks are multiplying like bacteria. And yet despite the improvement in our tools, we somehow don’t spend time talking about how to maintain our most important tool - the one between our ears.
Constantly feeling worn down, experiencing anxiety over making decisions, and burning out are not just facts of a developer’s life! They’re challenges that can be dealt with. In this talk we’ll cover the most common mental health challenges facing developers, and then learn about some techniques to supercharge your brain by improving your mental hygiene (whether you have a psychological disorder or not). Most importantly, you’ll learn how to have a conversation with your coworkers (and other people in your life) about supporting each other and finding your best selves.
Let's Talk About Mental Health - Handout - DevUp 2017
This document discusses mental health and provides guidance on how to support those experiencing mental health issues or crisis. It suggests using experiential language to describe how an individual feels without judgment. When concerned about someone's safety, it's important to ask directly if they are safe or need help. Scripts are presented for asking for support, offering support, explaining feelings, and checking in. Different types of interactions are outlined, emphasizing clear communication, respecting boundaries, and focusing on needs rather than problem-solving. Resources for learning more about mental health and getting help are also listed.
The Developer's Guide to Learning Effectively
The ability to learn things is an essential part of the developer’s toolkit, which is only getting more important as we march into the future. New technologies and new tools are released constantly - there will probably be at least one new Javascript framework released just in the time it takes you to read this abstract. Even if you’re on a fixed tech stack on a long-running project, you need to evaluate and adapt to new versions of your tools and new software idioms as they're released.
The thing is, we’re never really taught HOW to learn things - we’re expected to just figure it out ourselves. It is my opinion that this is Really Terrible. If you share that opinion, do something about it by coming to this talk! We’ll cover the types of learning and how to find which ones work for you. Do you wonder how learning a new framework is different than learning best practices for that framework? We’ll discuss that, too! We’ll also talk about the neuroscience of learning, how your brain connects cause and effect, the tricks your memory plays on you, and more. By the end, you’ll hopefully have the tools you need to learn anything efficiently and effectively.
The Saboteur in Your Retrospectives: How Your Brain Works Against You - The H...
The document discusses cognitive biases and provides tips for recognizing and mitigating biases in retrospectives. It recommends being aware of biases, talking to others to understand different perspectives, focusing on controllable factors, recording decisions made to avoid hindsight bias, and building trust within the team. The document cautions against making excuses that blame others, using only positive or negative frames, trying to manipulate people, feeling bad about not predicting outcomes, seeking unnecessary information, and making hurried decisions under pressure.
More from Arthur Doler (20)
The Whys and Hows of Impostor Syndrome and the Illusion of Transparency
The Whys and Hows of Impostor Syndrome and the Illusion of Transparency
Let's Talk About Mental Health Handout - KCDC 2018
Let's Talk About Mental Health Handout - KCDC 2018
Let's Talk About Mental Health Handout - NDC Oslo 2018
Let's Talk About Mental Health Handout - NDC Oslo 2018
Let's Talk About Mental Health Handout - Nebraska.Code 2018
Let's Talk About Mental Health Handout - Nebraska.Code 2018
Let's Talk About Mental Health - Nebraska.Code 2018
Let's Talk About Mental Health - Nebraska.Code 2018
The Developer's Guide to Learning - Codestock 2018
The Developer's Guide to Learning - Codestock 2018
What Makes You DO Stuff? The Psychology of Motivation - Codestock 2018
What Makes You DO Stuff? The Psychology of Motivation - Codestock 2018
What Makes You DO Stuff? The Psychology of Motivation - Handout - Codestock 2018
What Makes You DO Stuff? The Psychology of Motivation - Handout - Codestock 2018
Let's Talk About Mental Health - Handout - DevUp 2017
Let's Talk About Mental Health - Handout - DevUp 2017
The Saboteur in Your Retrospectives: How Your Brain Works Against You - The H...
The Saboteur in Your Retrospectives: How Your Brain Works Against You - The H...
Recently uploaded
Understanding of Self - Applied Social Psychology - Psychology SuperNotes
A proprietary approach developed by bringing together the best of learning theories from Psychology, design principles from the world of visualization, and pedagogical methods from over a decade of training experience, that enables you to: Learn better, faster!
Assignment 1 (Introductions to Microsoft Power point 2019) kiran.pptx
its for fresers to microsoft joiner
Aggression - Applied Social Psychology - Psychology SuperNotes
A proprietary approach developed by bringing together the best of learning theories from Psychology, design principles from the world of visualization, and pedagogical methods from over a decade of training experience, that enables you to: Learn better, faster!
ProSocial Behaviour - Applied Social Psychology - Psychology SuperNotes
A proprietary approach developed by bringing together the best of learning theories from Psychology, design principles from the world of visualization, and pedagogical methods from over a decade of training experience, that enables you to: Learn better, faster!
The Secret Warrior - Help Share a Parent or Loved Ones’ Cancer Diagnosis with...
The Secret Warrior - Help Share a Parent or Loved Ones’ Cancer Diagnosis with...CANSA The Cancer Association of South Africa
You may be stressed about revealing your cancer diagnosis to your child or children.
Children love stories and these often provide parents with a means of broaching tricky subjects and so the ‘The Secret Warrior’ book was especially written for CANSA TLC, by creative writer and social worker, Sally Ann Carter.
Find out more:
https://cansa.org.za/resources-to-help-share-a-parent-or-loved-ones-cancer-diagnosis-with-a-child/The Six Working Genius Short Explanation
Working Genius is based on premise that in the task continuum each of us have pain point.
7 Habits of Highly Effective People.pptx
Covey says most people look for quick fixes. They see a big success and want to know how he did it, believing (and hoping) they can do the same following a quick bullet list.
But real change, the author says, comes not from the outside in, but from the inside out. And the most fundamental way of changing yourself is through a paradigm shift.
That paradigm shift is a new way of looking at the world. The 7 Habits of Highly Effective People presents an approach to effectiveness based on character and principles.
The first three habits indeed deal with yourself because it all starts with you. The first three habits move you from dependence from the world to the independence of making your own world.
Habits 4, 5 and 6 are about people and relationships. The will move you from independence to interdependence. Such, cooperating to achieve more than you could have by yourself.
The last habit, habit number 7, focuses on continuous growth and improvement.
Recently uploaded (9)
Understanding of Self - Applied Social Psychology - Psychology SuperNotes
Understanding of Self - Applied Social Psychology - Psychology SuperNotes
Assignment 1 (Introductions to Microsoft Power point 2019) kiran.pptx
Assignment 1 (Introductions to Microsoft Power point 2019) kiran.pptx
Aggression - Applied Social Psychology - Psychology SuperNotes
Aggression - Applied Social Psychology - Psychology SuperNotes
1-CIE-IGCSE-Additional-Mathematics-Topical-Past-Paper-Functions.pdf
1-CIE-IGCSE-Additional-Mathematics-Topical-Past-Paper-Functions.pdf
ProSocial Behaviour - Applied Social Psychology - Psychology SuperNotes
ProSocial Behaviour - Applied Social Psychology - Psychology SuperNotes
The Secret Warrior - Help Share a Parent or Loved Ones’ Cancer Diagnosis with...
The Secret Warrior - Help Share a Parent or Loved Ones’ Cancer Diagnosis with...
Exercise 2 (Green) - Labels and Unpacking Them
- 1. THESE INSTRUCTIONS ARE SECRET – DON’T LET YOUR PARTNER SEE THEM! Exercise 2 – Labels and Unpacking Them Green Partner Goals Identifyingandunpackinglabels. Building Phase (Time: 10 minutes) Buildsomethingthatisveryplain –for example askyscraper.Don’taddany bricksbesideswhatyouneed,and avoiddecorations. Feedback Phase (Time: 10 minutes) 1) Introduce Your Creation Take a minute todescribe whatyou’ve builttoyourpartner,and letthemdothe same. You will be receiving feedbackfirst. 2) Receive Feedback Whenyour partnergivesyoufeedback,askforclarificationontheirlabels.Asanexample:“Whatdidyou meanby plain?” Keepaskinguntil youfeel you’ve gottenthroughtheirinterpretationtotheirdata.Thenrestate your partner’sposition,askingthemif youunderstanditcorrectly. 3) Offer Feedback Your partner’screationwill be veryornate.Use Evaluationtocritique itsornateness,makingsure toinclude a label.Here’ssome suggestionstogetyoustarted: Decorative Ornamental Showy Elaborate 4) Repeat Repeatthe exercise asmanytimesasyouwant,choosingdifferentlabels,untilyoufeelcomfortable asking questionstounpacka label.