Skip to content
How to ThinkIn the Age of AI

The values conflict log

~11 min read

Core Primitive

Record instances where values conflicted and what you chose to understand your hierarchy.

The gap between your professed values and your revealed ones

You say you value honesty. You also say you value kindness. On a Tuesday afternoon, a friend shows you the novel they have been writing for three years and asks for your genuine opinion. The prose is overwritten, the plot meanders, and the central character is a thinly veiled self-portrait lacking the self-awareness to be interesting. You have two values in your hands. One says tell the truth. The other says protect the person you care about from pain. You cannot fully honor both. Whatever you do next — soften the truth, deliver it straight, dodge the question, find something genuine to praise while omitting the rest — constitutes a choice. And that choice, whether you recognize it or not, is a data point about which value actually outranks the other in your operating hierarchy.

Testing your hierarchy through real decisions established the principle: actual choices reveal your real value hierarchy better than abstract reflection. That lesson asked you to start noticing the gap between what you say you value and what your behavior demonstrates you value. This lesson gives you the instrument for capturing that data systematically. The values conflict log is not a journal. It is not a diary. It is a structured record of every moment when two things you care about pulled you in opposing directions, what you chose, and what that choice teaches you about the architecture of your value system. Over weeks and months, the log becomes an empirical map — not of who you wish you were, but of who you actually are when competing goods force a decision.

Why conflicts are the only reliable data

You could try to determine your value hierarchy by sitting down and ranking your values from most to least important. Milton Rokeach pioneered this approach in the late 1960s with his Value Survey, which asked participants to rank-order two sets of values — eighteen terminal values (end-states like freedom, equality, and inner harmony) and eighteen instrumental values (modes of conduct like honesty, courage, and responsibility). The forced-ranking method was elegant: by requiring participants to place every value in a strict order, it eliminated the tendency to rate everything as "very important" and forced genuine prioritization.

But Rokeach himself noted a persistent problem. People's stated rankings often diverged from their behavior. A participant who ranked "equality" highest might, in practice, make choices that consistently prioritized "a comfortable life" or "family security." The ranking reflected aspirational identity rather than operational hierarchy. This is not hypocrisy. It is a structural limitation of introspective self-report. When you sit in a quiet room and contemplate your values in the abstract, you are not accessing the same decision-making system that operates when you are standing in your friend's living room holding their manuscript with the clock ticking and their hopeful expression aimed at you. The quiet-room self uses deliberative reasoning. The real-time self uses emotion, habit, social pressure, and whatever heuristic fires fastest. Your value hierarchy lives in the second system, not the first.

This is why conflicts are irreplaceable as data. A value that never collides with another value is a value that has never been tested. You can claim that integrity is your highest value, and as long as integrity never costs you anything — never conflicts with loyalty, or financial security, or social belonging — the claim is unfalsifiable. It is only when integrity demands that you report a friend's misconduct, or refuse a lucrative contract that requires shading the truth, or publicly disagree with your boss in a meeting where silence would be safer, that the hierarchy reveals itself. The conflict is the test. The choice is the result. The log is where you record both so that the data accumulates rather than evaporating.

The structure of a useful entry

A values conflict log works only if each entry captures enough information to be interpretable later. Too little structure and you end up with a vague emotional journal. Too much structure and the overhead kills the practice before it generates meaningful data. The format that balances these constraints has four fields.

The first field is the date. Temporal patterns matter. You may discover that certain values dominate on workdays and different ones on weekends, that your hierarchy shifts when you are fatigued versus rested, or that seasonal pressures — tax season, the holidays, performance review cycles — systematically reorganize which values take priority. Without dates, these patterns are invisible.

The second field names the two values that collided. Be precise. "Work versus life" is too vague to be useful. "Professional competence versus physical health" is better. "Delivering a thorough analysis for the client versus sleeping enough to function well tomorrow" is best. The more specific the description, the more clearly you will see, across entries, which pairs of values collide repeatedly and which conflicts are one-time events. Shalom Schwartz's research on value structures is illuminating here: Schwartz demonstrated across dozens of cultures that certain value types are systematically opposed. Self-enhancement values (achievement, power) tend to conflict with self-transcendence values (benevolence, universalism). Openness to change (self-direction, stimulation) tends to conflict with conservation (security, conformity, tradition). These are not random collisions. They are structural tensions built into the architecture of human motivation. Your log will likely confirm Schwartz's circumplex model with your own data — you will see the same value pairs colliding again and again, because the tensions are not accidental but inherent.

The third field records which value you chose to honor. This is the behavioral data — the actual revealed preference. Note that "chose" does not mean "felt good about." You may choose professional competence over physical health and feel guilty about it. The guilt is informative, but the choice is the primary datum. The guilt suggests that you recognize the subordinated value as genuinely important, which is different from a case where you choose one value over another without any internal friction. Both are data. Both belong in the log.

The fourth field is a brief reflection — one to three sentences — on what the choice revealed. This is where the log becomes more than a record and starts functioning as an analytical instrument. Why did this value win? Was it because you genuinely believe it is more important, or because the social consequences of the alternative were more immediately visible? Was the choice consistent with previous entries, or did it surprise you? Did the decision feel like an expression of your deepest self, or like a capitulation to circumstance? Leon Festinger's cognitive dissonance theory predicts that after making a difficult choice between two attractive options, you will retroactively inflate the value of the chosen option and deflate the value of the rejected one. The reflection field is your defense against this distortion — by writing your reasoning while the dissonance is still fresh, before the rationalization machinery has finished its work, you capture a more honest account of the decision than memory alone would preserve.

The dissonance signal and the writing cure

The discomfort you feel during a genuine values conflict is not incidental. It is diagnostic. Festinger's cognitive dissonance theory holds that when two cognitions are inconsistent — when you believe both values matter but your behavior can honor only one — the resulting psychological tension motivates you to reduce the inconsistency, either by changing a belief, changing the behavior, or constructing a justification that reconciles the two. That tension is the signal that a real conflict occurred, as opposed to a trivial preference. If choosing between two options produces no discomfort at all, one value clearly dominated and the other was never truly engaged. The intensity of the dissonance is roughly proportional to the closeness of the two values in your operative hierarchy. Values that are far apart produce easy choices with little residual tension. Values that are close produce agonizing choices with persistent doubt. Your log should note the intensity, because it tells you where the fault lines in your hierarchy run closest together — where the ranking is most uncertain and most likely to shift with new experience.

James Pennebaker's expressive writing research explains why the act of logging itself has value beyond mere record-keeping. Pennebaker demonstrated that writing about emotionally difficult experiences — including internal conflicts and value dilemmas — produces measurable improvements in both psychological and physical health. The mechanism is cognitive integration: translating turbulent experience into structured language forces the writer to organize it into a coherent narrative, reducing the cognitive load of carrying the unresolved conflict as a background process. Each log entry asks you to take a moment of genuine internal tension and render it in structured prose. The writing does not resolve the conflict. But it moves the conflict from the domain of ambient discomfort into the domain of explicit knowledge, where it can be examined, compared, and used as input for deliberate hierarchy refinement.

Patterns emerge from accumulation

A single values conflict log entry is a data point. Ten entries are a dataset. Fifty entries are a map. The power of the log is not in any individual entry but in the patterns that emerge when you review the accumulated record over weeks and months.

The first pattern to look for is dominance. Which value appears on the winning side most frequently? If you have fifteen entries and "personal autonomy" won twelve of them — over loyalty, over financial security, over social approval, over comfort — then autonomy is not merely a value you hold. It is a load-bearing pillar of your decision-making architecture. You can state with empirical confidence, grounded in observed behavior rather than introspective guessing, that it occupies a top-tier position in your hierarchy.

The second pattern is chronic subordination. Which value consistently loses? You may discover that "creativity," which you have always identified as a core value, consistently loses to "financial security" whenever the two collide. That does not mean creativity is unimportant to you. It means that in the operative hierarchy — the one that governs behavior — security outranks creativity. Whether you want to change that ranking is a separate question. The log's job is to show you the ranking as it is, not as you wish it were.

The third pattern is recurrence. Which specific conflict pairs keep appearing? If "honesty versus kindness" shows up every week, that is a structural feature of your life — a recurring context that forces the same two values into collision. Recurring conflicts represent decision categories rather than individual decisions. Once you have resolved the category — decided which value generally prevails and under what conditions — future decisions in that category become lookups rather than deliberations. The cognitive savings compound over time.

The fourth pattern is drift. When you compare your entries from month one to month four, do the same values keep winning, or has the hierarchy shifted? The value hierarchy is dynamic established that your value hierarchy is dynamic. The log lets you observe that dynamism directly. If "achievement" dominated your early entries but "connection" has been winning more recently, you are watching your hierarchy reorganize in real time — information you cannot get any other way.

The decision journal tradition

The values conflict log belongs to a broader tradition of structured decision recording. Daniel Kahneman has advocated for decision journals as a corrective to hindsight bias — the tendency to retroactively believe that you "knew all along" what the right choice was. By recording your reasoning before the outcome is known, you create a record that your future self cannot retroactively edit. Your values conflict log applies this mechanism to an inner domain. Instead of tracking investment decisions and financial outcomes, you are tracking value conflicts and their experiential consequences. When you review a six-month-old entry and notice that you chose financial security over creative risk, how do you feel about that choice now? Does it produce a sense of alignment, or lingering regret? The retrospective evaluation — possible only because the log preserved the original context — is where hierarchy refinement actually happens. You are not just recording choices. You are building a feedback loop between your present decisions and your future evaluations of those decisions.

The Third Brain

An AI assistant with access to your values conflict log can perform analyses that are difficult or impossible to do manually. After you have accumulated twenty or thirty entries, ask your AI to identify the three values that win most frequently, the three that lose most frequently, and the three conflict pairs that recur most often. Ask it to flag any entries where the same value won and lost in the same week — situations where your hierarchy appeared inconsistent, which may indicate context-dependent variation rather than a stable ranking. Ask it to compare your stated top values (from whatever ranking exercise you have done) with your revealed top values as shown in the log data. The gap between those two lists, if it exists, is the gap between aspiration and operation — and closing that gap is the work of this entire phase.

The AI can also help you notice conflicts you missed. Describe your day in a few sentences — the meetings you attended, the decisions you made, the trade-offs you accepted — and ask it to identify any values conflicts embedded in those events that you did not consciously register. Many values conflicts operate below the threshold of awareness. You chose to answer emails during your child's soccer game without ever framing it as a conflict between professional responsiveness and family presence. But it was one. The AI can surface these invisible conflicts and prompt you to log them, expanding the dataset beyond the conflicts dramatic enough to trigger conscious recognition.

From logging to distinguishing

You now have a practice that transforms values conflicts from sources of unexamined anxiety into structured data points that accumulate into a map of your operative value hierarchy. The log does not tell you what to value. It tells you what you do value, as revealed by your actual behavior in moments of genuine tension. Over time, it shows you which values are load-bearing and which are decorative, which conflict pairs define the recurring fault lines in your decision-making, and whether your hierarchy is stable or in motion.

But the log will also surface a subtler question. Some of the values you record will be things you pursue for their own sake — ends in themselves that need no further justification. Others will turn out to be means to other ends — values that matter not intrinsically but because they serve some deeper value that you have not yet named. The next lesson, Terminal versus instrumental values, introduces Rokeach's distinction between terminal and instrumental values: the difference between values you hold as ultimate destinations and values you hold as vehicles for reaching those destinations. That distinction will change how you read your conflict log, because a conflict between two instrumental values has a different structure — and a different resolution strategy — than a conflict between a terminal value and an instrumental one.


Sources:

  1. Rokeach, M. (1973). The Nature of Human Values. Free Press.
  2. Schwartz, S. H. (1992). "Universals in the Content and Structure of Values: Theoretical Advances and Empirical Tests in 20 Countries." Advances in Experimental Social Psychology, 25, 1-65.
  3. Festinger, L. (1957). A Theory of Cognitive Dissonance. Stanford University Press.
  4. Pennebaker, J. W. (1997). "Writing About Emotional Experiences as a Therapeutic Process." Psychological Science, 8(3), 162-166.
  5. Kahneman, D. (2011). Thinking, Fast and Slow. Farrar, Straus and Giroux.
  6. Schwartz, S. H., & Boehnke, K. (2004). "Evaluating the Structure of Human Values with Confirmatory Factor Analysis." Journal of Research in Personality, 38(3), 230-255.
  7. Tetlock, P. E. (1986). "A Value Pluralism Model of Ideological Reasoning." Journal of Personality and Social Psychology, 50(4), 819-827.
  8. Pennebaker, J. W., & Smyth, J. M. (2016). Opening Up by Writing It Down: How Expressive Writing Improves Health and Eases Emotional Pain. Guilford Press.

Put it into practice

Exercise

Create a values conflict log. Use whatever medium has the lowest friction for you — a dedicated page in your notebook, a running note on your phone, a simple document. The structure for each entry has four fields: the date, the two values that collided, which value you chose to honor, and a one-to-three-sentence reflection on what the choice revealed about your hierarchy. Over the next two weeks, record every values conflict you notice, no matter how minor. A conflict between efficiency and thoroughness at work counts. A conflict between honesty and kindness in a conversation counts. A conflict between rest and productivity on a Saturday morning counts. At the end of two weeks, review the log and look for patterns: which values consistently win, which consistently lose, and which conflicts recur.

More on putting it into practice

See it in action

You receive an invitation to speak at a prestigious conference on the same weekend your daughter has her first piano recital. You value professional recognition and you value being present for your family. In the abstract, you would say family comes first. But the conference is a career-defining opportunity — the kind that does not come twice — and the recital is one of many your daughter will have. You feel the pull in both directions, and the discomfort is acute precisely because both values are real. You choose the recital. You write in your conflict log: "March 14. Professional recognition vs. family presence. Chose family presence. The deciding factor was imagining myself at the conference knowing I had missed the recital — the professional high would be contaminated by guilt. When I imagined myself at the recital having declined the conference, I felt loss but not shame. That asymmetry tells me presence ranks above recognition when the stakes are personal milestones." Six weeks later, a similar conflict arises — a client dinner versus your anniversary — and you do not deliberate. The log entry from March already resolved this category of conflict. You decline the dinner in thirty seconds.

Watch for the failure mode

You only log the dramatic conflicts — career versus family, integrity versus profit — and ignore the small daily ones. But the small conflicts are where your hierarchy actually operates. The decision to skip a workout to finish a project is a conflict between health and achievement. The decision to say yes to a social invitation when you wanted to read is a conflict between connection and solitude. By filtering for drama, you get a log that reflects the person you think you are in extraordinary moments rather than the person you actually are in ordinary ones. The log becomes aspirational fiction rather than empirical data.

Make it stick

Start your values conflict log today using the four-field structure from the exercise. Commit to maintaining it for thirty days. After the first week, review your entries and notice whether any value appears on the winning side more than three times — that is a strong candidate for your top-tier hierarchy. After thirty days, bring the log into your next values review (The bi-annual values review) as primary data. The log will also feed directly into Values and regret analysis on regret analysis, where you will examine whether the values you chose to honor were the ones that reduced regret over time.

Practice

Track Value Conflicts in a Notion Database

Build a structured conflict log in Notion to capture real-time value collisions over two weeks, then analyze patterns to reveal your actual hierarchy versus your assumed one.

15 minutesAdvanced
  1. 1Open Notion and create a new database titled 'Values Conflict Log' with four properties: Date (date type), Values in Conflict (text), Choice Made (select type with options for each of your core values), and Reflection (text).
  2. 2Set up a template for new entries by clicking the dropdown next to 'New' and selecting 'New template,' then pre-populate the Values in Conflict field with a prompt like 'Value A vs. Value B' and the Reflection field with 'What does this choice reveal about my hierarchy?'
  3. 3Each time you notice a value conflict over the next two weeks—whether choosing efficiency over thoroughness at work, honesty over kindness in conversation, or rest over productivity on weekends—immediately create a new entry in Notion using your template, taking 2-3 minutes to complete all four fields while the experience is fresh.
  4. 4After two weeks, create a new Notion page titled 'Conflict Analysis' and add three linked database views: one filtered and sorted by 'Choice Made' to see which values consistently win, one grouped by 'Values in Conflict' to identify recurring conflicts, and one timeline view by date to spot temporal patterns.
  5. 5Write a 5-7 sentence synthesis below your database views describing the gap between your stated values hierarchy and your revealed hierarchy, noting which values you thought were important but rarely chose, which conflicts drain your energy through repetition, and what single adjustment to your hierarchy would reduce the most friction.

Common questions about this lesson

More around this idea