The Hidden Pitfalls of Naïve Realism in Problem Solving, Risk Management, and Decision Making

Naïve realism—the unconscious belief that our perception of reality is objective and universally shared—acts as a silent saboteur in professional and personal decision-making. While this mindset fuels confidence, it also blinds us to alternative perspectives, amplifies cognitive biases, and undermines collaborative problem-solving. This blog post explores how this psychological trap distorts critical processes and offers actionable strategies to counteract its influence, drawing parallels to frameworks like the Pareto Principle and insights from risk management research.

Problem Solving: When Certainty Breeds Blind Spots

Naïve realism convinces us that our interpretation of a problem is the only logical one, leading to overconfidence in solutions that align with preexisting beliefs. For instance, teams often dismiss contradictory evidence in favor of data that confirms their assumptions. A startup scaling a flawed product because early adopters praised it—while ignoring churn data—exemplifies this trap. The Pareto Principle’s “vital few” heuristic can exacerbate this bias by oversimplifying complex issues. Organizations might prioritize frequent but low-impact problems, neglecting rare yet catastrophic risks, such as cybersecurity vulnerabilities masked by daily operational hiccups.

Functional fixedness, another byproduct of naïve realism, stifles innovation by assuming resources can only be used conventionally. To mitigate this pitfall, teams should actively challenge assumptions through adversarial brainstorming, asking questions like “Why will this solution fail?” Involving cross-functional teams or external consultants can also disrupt echo chambers, injecting fresh perspectives into problem-solving processes.

Risk Management: The Illusion of Objectivity

Risk assessments are inherently subjective, yet naïve realism convinces decision-makers that their evaluations are purely data-driven. Overreliance on historical data, such as prioritizing minor customer complaints over emerging threats, mirrors the Pareto Principle’s “static and historical bias” pitfall.

Reactive devaluation further complicates risk management. Organizations can counteract these biases by appropriately leveraging risk management to drive subjectivity out while better accounting for uncertainty. Simulating worst-case scenarios, such as sudden supplier price hikes or regulatory shifts, also surfaces blind spots that static models overlook.

Decision Making: The Myth of the Rational Actor

Even in data-driven cultures, subjectivity stealthily shapes choices. Leaders often overestimate alignment within teams, mistaking silence for agreement. Individuals frequently insist their assessments are objective despite clear evidence of self-enhancement bias. This false consensus erodes trust and stifles dissent with the assumption that future preferences will mirror current ones.

Organizations must normalize dissent through anonymous voting or “red team” exercises to dismantle these myths, including having designated critics scrutinize plans. Adopting probabilistic thinking, where outcomes are assigned likelihoods instead of binary predictions, reduces overconfidence.

Acknowledging Subjectivity: Three Practical Steps

1. Map Mental Models

Mapping mental models involves systematically documenting and challenging assumptions to ensure compliance, quality, and risk mitigation. For example, during risk assessments or deviation investigations, teams should explicitly outline their assumptions about processes, equipment, and personnel. Statements such as “We assume the equipment calibration schedule is sufficient to prevent deviations” or “We assume operator training is adequate to avoid errors” can be identified and critically evaluated.

Foster a culture of continuous improvement and accountability by stress-testing assumptions against real-world data—such as audit findings, CAPA (Corrective and Preventive Actions) trends, or process performance metrics—to reveal gaps that might otherwise go unnoticed. For instance, a team might discover that while calibration schedules meet basic requirements, they fail to account for unexpected environmental variables that impact equipment accuracy.

By integrating assumption mapping into routine GMP activities like risk assessments, change control reviews, and deviation investigations, organizations can ensure their decision-making processes are robust and grounded in evidence rather than subjective beliefs. This practice enhances compliance and strengthens the foundation for proactive quality management.

2. Institutionalize ‘Beginner’s Mind’

A beginner’s mindset is about approaching situations with openness, curiosity, and a willingness to learn as if encountering them for the first time. This mindset challenges the assumptions and biases that often limit creativity and problem-solving. In team environments, fostering a beginner’s mindset can unlock fresh perspectives, drive innovation, and create a culture of continuous improvement. However, building this mindset in teams requires intentional strategies and ongoing reinforcement to ensure it is actively utilized.

What is a Beginner’s Mindset?

At its core, a beginner’s mindset involves setting aside preconceived notions and viewing problems or opportunities with fresh eyes. Unlike experts who may rely on established knowledge or routines, individuals with a beginner’s mindset embrace uncertainty and ask fundamental questions such as “Why do we do it this way?” or “What if we tried something completely different?” This perspective allows teams to challenge the status quo, uncover hidden opportunities, and explore innovative solutions that might be overlooked.

For example, adopting this mindset in the workplace might mean questioning long-standing processes that no longer serve their purpose or rethinking how resources are allocated to align with evolving goals. By removing the constraints of “we’ve always done it this way,” teams can approach challenges with curiosity and creativity.

How to Build a Beginner’s Mindset in Teams

Fostering a beginner’s mindset within teams requires deliberate actions from leadership to create an environment where curiosity thrives. Here are some key steps to build this mindset:

Model Curiosity and Openness
Leaders play a critical role in setting the tone for their teams. By modeling curiosity—asking questions, admitting gaps in knowledge, and showing enthusiasm for learning—leaders demonstrate that it is safe and encouraged to approach work with an open mind. For instance, during meetings or problem-solving sessions, leaders can ask questions like “What haven’t we considered yet?” or “What would we do if we started from scratch?” This signals to team members that exploring new ideas is valued over rigid adherence to past practices.
Encourage Questioning Assumptions
Teams should be encouraged to question their assumptions regularly. Structured exercises such as “assumption audits” can help identify ingrained beliefs that may no longer hold true. By challenging assumptions, teams open themselves up to new insights and possibilities.
Create Psychological Safety
A beginner’s mindset flourishes in environments where team members feel safe taking risks and sharing ideas without fear of judgment or failure. Leaders can foster psychological safety by emphasizing that mistakes are learning opportunities rather than failures. For example, during project reviews, instead of focusing solely on what went wrong, leaders can ask, “What did we learn from this experience?” This shifts the focus from blame to growth and encourages experimentation.
Rotate Roles and Responsibilities
Rotating team members across roles or projects is an effective way to cultivate fresh perspectives. When individuals step into unfamiliar areas of responsibility, they are less likely to rely on habitual thinking and more likely to approach tasks with curiosity and openness. For instance, rotating quality assurance personnel into production oversight roles can reveal inefficiencies or risks that might have been overlooked due to overfamiliarity within silos.
Provide Opportunities for Learning
Continuous learning is essential for maintaining a beginner’s mindset. Organizations should invest in training programs, workshops, or cross-functional collaborations that expose teams to new ideas and approaches. For example, inviting external speakers or consultants to share insights from other industries can inspire innovative thinking within teams by introducing them to unfamiliar concepts or methodologies.
Use Structured Exercises for Fresh Thinking
Design Thinking exercises or brainstorming techniques like “reverse brainstorming” (where participants imagine how to create the worst possible outcome) can help teams break free from conventional thinking patterns. These activities force participants to look at problems from unconventional angles and generate novel solutions.

Ensuring Teams Utilize a Beginner’s Mindset

Building a beginner’s mindset is only half the battle; ensuring it is consistently applied requires ongoing reinforcement:

Integrate into Processes: Embed beginner’s mindset practices into regular workflows such as project kickoffs, risk assessments, or strategy sessions. For example, make it standard practice to start meetings by revisiting assumptions or brainstorming alternative approaches before diving into execution plans.
Reward Curiosity: Recognize and reward behaviors that reflect a beginner’s mindset—such as asking insightful questions, proposing innovative ideas, or experimenting with new approaches—even if they don’t immediately lead to success.
Track Progress: Use metrics like the number of new ideas generated during brainstorming sessions or the diversity of perspectives incorporated into decision-making processes to measure how well teams utilize a beginner’s mindset.
Reflect Regularly: Encourage teams to reflect on using the beginner’s mindset through retrospectives or debriefs after significant projects and events. Questions like “How did our openness to new ideas impact our results?” or “What could we do differently next time?” help reinforce the importance of maintaining this perspective.

Organizations can ensure their teams consistently leverage the power of a beginner’s mindset by cultivating curiosity, creating psychological safety, and embedding practices that challenge conventional thinking into daily operations. This drives innovation and fosters adaptability and resilience in an ever-changing business landscape.

3. Revisit Assumptions by Practicing Strategic Doubt

Assumptions are the foundation of decision-making, strategy development, and problem-solving. They represent beliefs or premises we take for granted, often without explicit evidence. While assumptions are necessary to move forward in uncertain environments, they are not static. Over time, new information, shifting circumstances, or emerging trends can render them outdated or inaccurate. Periodically revisiting core assumptions is essential to ensure decisions remain relevant, strategies stay robust, and organizations adapt effectively to changing realities.

Why Revisiting Assumptions Matters

Assumptions often shape the trajectory of decisions and strategies. When left unchecked, they can lead to flawed projections, misallocated resources, and missed opportunities. For example, Kodak’s assumption that film photography would dominate forever led to its downfall in the face of digital innovation. Similarly, many organizations assume their customers’ preferences or market conditions will remain stable, only to find themselves blindsided by disruptive changes. Revisiting assumptions allows teams to challenge these foundational beliefs and recalibrate their approach based on current realities.

Moreover, assumptions are frequently made with incomplete knowledge or limited data. As new evidence emerges, whether through research, technological advancements, or operational feedback, testing these assumptions against reality is critical. This process ensures that decisions are informed by the best available information rather than outdated or erroneous beliefs.

How to Periodically Revisit Core Assumptions

Revisiting assumptions requires a structured approach integrating critical thinking, data analysis, and collaborative reflection.

1. Document Assumptions from the Start

The first step is identifying and articulating assumptions explicitly during the planning stages of any project or strategy. For instance, a team launching a new product might document assumptions about market size, customer preferences, competitive dynamics, and regulatory conditions. By making these assumptions visible and tangible, teams create a baseline for future evaluation.

2. Establish Regular Review Cycles

Revisiting assumptions should be institutionalized as part of organizational processes rather than a one-off exercise. Build assumption audits into the quality management process. During these sessions, teams critically evaluate whether their assumptions still hold true in light of recent data or developments. This ensures that decision-making remains agile and responsive to change.

3. Use Feedback Loops

Feedback loops provide real-world insights into whether assumptions align with reality. Organizations can integrate mechanisms such as surveys, operational metrics, and trend analyses into their workflows to continuously test assumptions.

4. Test Assumptions Systematically

Not all assumptions carry equal weight; some are more critical than others. Teams can prioritize testing based on three parameters: severity (impact if the assumption is wrong), probability (likelihood of being inaccurate), and cost of resolution (resources required to validate or adjust).

5. Encourage Collaborative Reflection

Revisiting assumptions is most effective when diverse perspectives are involved. Bringing together cross-functional teams—including leaders, subject matter experts, and customer-facing roles—ensures that blind spots are uncovered and alternative viewpoints are considered. Collaborative workshops or strategy recalibration sessions can facilitate this process by encouraging open dialogue about what has changed since the last review.

6. Challenge Assumptions with Data

Assumptions should always be validated against evidence rather than intuition alone. Teams can leverage predictive analytics tools to assess whether their assumptions align with emerging trends or patterns.

How Organizations Can Ensure Assumptions Are Utilized Effectively

To ensure revisited assumptions translate into actionable insights, organizations must integrate them into decision-making processes:

Monitor Continuously: Establish systems for continuously monitoring critical assumptions through dashboards or regular reporting mechanisms. This allows leadership to identify invalidated assumptions promptly and course-correct before significant risks materialize.

Update Strategies and Goals: Adjust goals and objectives based on revised assumptions to maintain alignment with current realities.

Refine KPIs: Key Performance Indicators (KPIs) should evolve alongside updated assumptions to reflect shifting priorities and external conditions. Metrics that once seemed relevant may need adjustment as new data emerges.

Embed Assumption Testing into Culture: Encourage teams to view assumption testing as an ongoing practice rather than a reactive measure. Leaders can model this behavior by openly questioning their own decisions and inviting critique from others.

From Certainty to Curious Inquiry

Naïve realism isn’t a personal failing but a universal cognitive shortcut. By recognizing its influence—whether in misapplying the Pareto Principle or dismissing dissent—we can reframe conflicts as opportunities for discovery. The goal isn’t to eliminate subjectivity but to harness it, transforming blind spots into lenses for sharper, more inclusive decision-making.

The path to clarity lies not in rigid certainty but in relentless curiosity.

Defining Values, with Speaking Out as an example

Which espoused values and desired behaviors will best enable an organization to live its quality purpose? There’s been a lot of writing and thought on this, and for this post, I am going to start with ISO 10018-2020 “Quality management — Guidance for people engagement” and develop an example of a value to build in your organization.

ISO 10018-2020 gives 6 areas:

Context of the organization and quality culture
Leadership
Planning and Strategy
Knowledge and Awareness
Competence
Improvement

This list is pretty well aligned to other models, including the Malcolm Baldrige Excellence Framework (NIST), EFQM Excellence Model, SIQ Model for Performance Excellence, and such tools as the PDA Culture of Quality Assessment.

A concept that we find in ISO 10018-2020 (and everywhere else) is the handling of errors, mistakes, everyday problems and ‘niggles’, near misses, critical incidents, and failures; to ensure they are reported and recorded honestly and transparently. That the time is taken for these to be discussed openly and candidly, viewed as opportunities for learning how to prevent their recurrence by improving systems but also as potentially protective of potentially larger and more consequential failures or errors. The team takes the time and effort to engage in ‘second order’ problem-solving. ‘First order’ problem solving is the quick fixing of issues as they appear so as to stop them disrupting normal workflow. ‘Second order’ problem solving involves identifying the root causes of problems and taking action to address these rather than their signs and symptoms. The team takes ownership of mistakes instead of blaming, accusing, or scapegoating individual team members. The team proactively seeks to identify errors and problems it may have missed in its processes or outputs by seeking feedback and asking for help from external stakeholders, e.g. colleagues in other teams, and customers, and also by engaging in frequent experimentation and testing.

We can tackle this in two ways. The first is to define all the points above as a value. The second would be to look at themes for this and the other aspects of robust quality culture and come up with a set of standard values, for example:

Accountable
Ownership
Action Orientated
Speak up

Don’t be afraid to take a couple of approaches to get values that really sing in your organization.

Values can be easily written in the following format:

Value: A one or two-word title for each value
Definition: A two or three sentence description that clearly states what this value means in your organization
Desired Behaviors: “I statement” behaviors that simply state activities. The behaviors we choose reinforce the values’ definitions by describing exactly how you want members of the organization to interact.
- Is this observable behavior? Can we assess someone’s demonstration of this behavior by watching and/or listening to their interactions? By seeing results?
- Is this behavior measurable? Can we reliably “score” this behavior? Can we rank how individual models or demonstrates this behavior?

For the rest of this post, I am going to focus on how you would write a value statement for Speak Up.

First, ask two questions:

Specific to your organization’s work environment, how would you define “Speak Up.”
What phrase or sentences describe what you mean by “Speak Up.”

Then broaden by considering how fellow leaders and team members would act to demonstrate “Speak Up”, as you defined it.

How would leaders and team members act so that, when you observe them, you would see a demonstration of Speaking Up? Note three or four behaviors that would clearly demonstrate your definition.

Next, answer these questions exclusively from your team member’s perspective:

How would employees define Speaking Out?
How would their definition differ from yours? Why?
What behaviors would employees feel they must model to demonstrate Speaking Out properly?
How would their modeled behaviors differ from yours? Why?

This process allows us to create common alignment based on a shared purpose.

By going through this process we may end up with a Value that looks like this:

Value: Speaking Out
Definition: Problems are reported and recorded honestly and transparently. Employees are not afraid to speak up, identify quality issues, or challenge the status quo for improved quality; they believe management will act on their suggestions.
Desired Behaviors:
- I hold myself accountable for raising problems and issues to my team promptly.
- I attack process and problems, not people.
- I work to anticipate and fend off the possibility of failures occurring.
- I approach admissions of errors and lack of knowledge/skill with support.

Managing Events Systematically

Being good at problem-solving is critical to success in an organization. I’ve written quite a bit on problem-solving, but here I want to tackle the amount of effort we should apply.

Not all problems should be treated the same. There are also levels of problems. And these two aspects can contribute to some poor problem-solving practices.

It helps to look at problems systematically across our organization. The iceberg analogy is a pretty popular way to break this done focusing on Events, Patterns, Underlying Structure, and Mental Model.

Events

Events start with the observation or discovery of a situation that is different in some way. What is being observed is a symptom and we want to quickly identify the problem and then determine the effort needed to address it.

This is where Art Smalley’s Four Types of Problems comes in handy to help us take a risk-based approach to determining our level of effort.

Type 1 problems, Troubleshooting, allows us to set problems with a clear understanding of the issue and a clear pathway. Have a flat tire? Fix it. Have a document error, fix it using good documentation practices.

It is valuable to work the way through common troubleshooting and ensure the appropriate linkages between the different processes, to ensure a system-wide approach to problem solving.

Corrective maintenance is a great example of troubleshooting as it involved restoring the original state of an asset. It includes documentation, a return to service and analysis of data. From that analysis of data problems are identified which require going deeper into problem-solving. It should have appropriate tie-ins to evaluate when the impact of an asset breaking leads to other problems (for example, impact to product) which can also require additional problem-solving.

It can be helpful for the organization to build decision trees that can help folks decide if a given problem stays as troubleshooting or if it it also requires going to type 2, “gap from standard.”

Type 2 problems, gap from standard, means that the actual result does not meet the expected and there is a potential of not meeting the core requirements (objectives) of the process, product, or service. This is the place we start deeper problem-solving, including root cause analysis.

Please note that often troubleshooting is done in a type 2 problem. We often call that a correction. If the bioreactor cannot maintain temperature during a run, that is a type 2 problem but I am certainly going to immediately apply troubleshooting as well. This is called a correction.

Take documentation errors. There is a practice in place, part of good documentation practices, for addressing troubleshooting around documents (how to correct, how to record a comment, etc). By working through the various ways documentation can go wrong, applying which ones are solved through troubleshooting and don’t involve type 2 problems, we can create a lot of noise in our system.

Trends/Patterns

Core to the quality system is trending, looking for possible signals that require additional effort. Trending can help determine where problems lay and can also drive up the level of effort necessary.

Underlying Structure

Root Cause Analysis is about finding the underlying structure of the problem that defines the work applied to a type 2 problem.

Not all problems require the same amount of effort, and type 2 problems really have a scale based on consequences, that can help drive the level of effort. This should be based on the impact to the organization’s ability to meet the quality objectives, the requirements behind the product or service.

For example, in the pharma world there are three major criteria:

safety, rights, or well-being of patients (including subjects and participants human and non-human)
data integrity (includes confidence in the results, outcome, or decision dependent on the data)
ability to meet regulatory requirements (which stem from but can be a lot broader than the first two)

These three criteria can be sliced and diced a lot of ways, but serve our example well.

To these three criteria we add a scale of possible harm to derive our criticality, an example can look like this:

Classification	Description
Critical	The event has resulted in, or is clearly likely to result in, any one of the following outcomes: significant harm to the safety, rights, or well-being of subjects or participants (human or non-human), or patients; compromised data integrity to the extent that confidence in the results, outcome, or decision dependent on the data is significantly impacted; or regulatory action against the company.
Major	The event(s), were they to persist over time or become more serious, could potentially, though not imminently, result in any one of the following outcomes: harm to the safety, rights, or well-being of subjects or participants (human or non-human), or patients; compromised data integrity to the extent that confidence in the results, outcome, or decision dependent on the data is significantly impacted.
Minor	An isolated or recurring triggering event that does not otherwise meet the definitions of Critical or Major quality impacts.

Example of Classification of Events in a Pharmaceutical Quality System

This level of classification will drive the level of effort on the investigation, as well as drive if the CAPA addresses underlying structures alone or drives to addressing the mental models and thus driving culture change.

Mental Model

Here is where we address building a quality culture. In CAPA lingo this is usually more a preventive action than a corrective action. In the simplest of terms, corrective actions is address the underlying structures of the problem in the process/asset where the event happened. Preventive actions deal with underlying structures in other (usually related) process/assets or get to the Mindsets that allowed the underlying structures to exist in the first place.

By applying this system perspective to our problem solving, by realizing that not everything needs a complete rebuild of the foundation, by looking holistically across our systems, we can ensure that we are driving a level of effort to truly build the house of quality.

Dealing with Emotional Ambivalence

Ambivalence, the A in VUCA, is a concept that quality professionals struggle with. We often call it “navigating the gray” or something similar. It is a skill we need to grow into, and definitely an area that should be central to your development program.

There is a great article in Harvard Business Review on “Embracing the Power of Ambivalence” that I strongly recommend folks read. This article focuses on emotional ambivalence, the feeling of being “torn” and discusses the return to the office. I’m not focusing on that topic (though like everyone I have strong opinions), instead I think the practices described there are great to think about as we develop a culture of quality.

Mindsets and Attitudes

Mindsets are lenses or frames of mind that orient individuals to particular sets of associations and expectations. Mindsets help individuals make sense of complex information by offering them simple schematics about themselves and objects in their world. For employees, mindsets provide scaffolding for understanding the broad nature of their work. Mindsets can be intentionally and adaptively changed through targeted interventions, so the goal is to build the processes to assess, monitor and shape as part of our quality systems.

Attitudes are the beliefs and feelings that drive individuals’ intentions and actions. Attitudes are the lens through which individuals make sense of their surroundings and impart consistency to guide their behavior .

Mindset influences attitudes, which influence behaviors, which influence actions, which influence results, which influence performance. And performance leas to changes in mindsets, and is a continuous improvement loop.

Since behaviors drive the actions we want to see, they are often a great pivot point. By thinking and working on mindsets and attitudes we are targeting the fourth and second leverage points.

Another way to think about this is we are developing habits. The same three factors apply:

Start small: If you have ever tried to tackle multiple resolutions all at once, you know it is next to impossible. Often, the habits will lack cohesion with one another, leading to more stress and less progress. The cognitive load increases, and the brain processes things in a more scattered, less congruent manner. It’s better to focus on one new habit at a time.
Enact the new habit daily: We can’t predict how long a specific habit will take to form, but all the research I’ve seen indicates that the more often people account on the new behavior, the more likely it is to become routine.
Weave into existing processes: When we blend the new behavior with current activities, it’s easier to latch on to, which make sit become an unconscious action more quickly.

Habits are contagious within social contexts, but scaling positive pressure on an organization level is a big challenge.

Another way to view this is in the framework of experiences, build beliefs, which lead to actions and give us results. By building this into our systems we can make sure the appropriate processes are in place to make sure these new habits stick. Building a quality culture is a multi-year journey requiring incremental, layered and additive formation.

This formation comes through building the mindsets that lead to the behaviors we want to see. Following the ISPE’s recommendations there are four good behaviors we can target (these are not the only ones nor are they exhaustive).

Accountability: Employees consistently see quality and compliance as their personal responsibilities. Establishing clear individual accountability for quality and compliance is a foundational step in helping shape quality mindset and cultural excellence. Accountability should be communicated consistently through job descriptions, onboarding, current good manufacturing practice (cGMP) training, and performance goals, and be supported by coaching, capability development programs, rewards, and recognition. Leaders should hold themselves and others accountable for performing to quality and compliance standards
Ownership: Employees have sufficient authority to make decisions and feel trusted to do their jobs well. Individual ownership of quality and compliance is a primary driver for shaping quality mindset. When individuals are fully engaged, empowered, and taking action to improve product quality, organizations typically benefit from continuous improvement and faster decision-making.
Action orientation: Employees regularly identify issues and intervene to minimize potential negative effects on quality and compliance. Establishing the expectation that individuals demonstrate action orientation helps shape quality mindset and foster cultural excellence. Leaders should promote and leverage proactive efforts (e.g., risk assessments, Gemba walks, employee suggestions) to reinforce support for the desired behavior. Additionally, it is important that rewards and recognition be aligned to support proactive efforts, rather than reactive fire-fighting efforts.
Speak up: Employees are not afraid to speak up, identify quality issues, or challenge the status quo for improved quality; they believe management will act on their suggestions. Empowering individuals to speak up and raise quality issues help foster quality mindset. Leaders should support this by modeling the desired behavior, building trust, and creating an environment in which individuals feel comfortable raising quality issues, engaging front-line personnel in problem solving, and involving employees in continuous-improvement activities.

Creating a high level action plan of experience -> Target Belief -> Target Action ->Target Result might look like this:

Sources

Aguire, D., von Post, R & Alpern, M. (2013). Culture’s role in enabling organization change. PWC
Ajzen, I. (2005). Attitudes, personality and behavior. (2nd ed.). Berkshire, GBR: McGraw-Hill Professional Publishing
Ball, K., Jeffrey, R.W., Abbott, G., McNaughton, S.A. & Crawford, D (2010). Is Healthy behavior contagious: associations with social norms with physical activity and healthy eating. International Journal of Behavioural Nutrition and Physical Activity, 7 (86)
Fujita, K., Gollwitzer, P. M., & Oettingen, G. (2007) . Mindsets and pre-conscious open-mindedness to incidental information. Journal of Experimental Social Psychology, 43(1), 48-61.
Gollwitzer, P. M. (1990). Action phases and mind-sets. In E. T. Higgins & R. M. Sorrentino (Eds.), Handbook of motivation and cognition: Foundations of social behavior, Vol. 2, pp. 53-92). New York, NY, US: The Guilford Press.