Your T-Shirt Drawer Isn't Just Messy: A Peanuto Analogy for Seeing the Hidden Structures of Everyday Bias

Why Your T-Shirt Drawer Is a Mirror of Hidden Bias

Think about your t-shirt drawer right now. Maybe it's a chaotic jumble of colors, fabrics, and memories. You have a system, but it's never quite worked: you fold shirts, stack them, and then the act of pulling one out collapses the entire pile. You find yourself wearing the same five shirts on rotation because the others are buried. This isn't just a storage problem—it's a structural one. The design of the drawer (deep, dark, with no dividers) and your mental rules ("I'll fold it neatly so I can see everything") combine to create a system that systematically hides some shirts and elevates others. This is exactly how everyday bias operates in workplaces, communities, and even our own minds. Bias isn't always a deliberate, malicious choice. More often, it's the product of hidden structures: the way we organize information, the shortcuts our brains use, the unspoken norms in a team, and the incentives baked into processes that reward certain behaviors over others. The Peanuto analogy helps us map the t-shirt drawer onto bias by identifying four key structures: the 'folded-over' assumptions (shirts folded in half that look different than they are), the 'precarious stacks' (layers of privilege that are unstable), the 'invisible sorting rules' (the order we impose without realizing it), and the 'bottom-of-the-drawer effect' (the perspectives we never see).

The Folded-Over Assumption: When We See Only Half the Shirt

Imagine a t-shirt folded in half with the design facing up. You see the graphic, but you don't see the faded collar, the small stain on the back, or the worn-out tag. In the same way, when we make quick judgments about people—based on their resume, their accent, or a single interaction—we see only the folded-over side. The rest is hidden. For example, in a hiring process, if a recruiter quickly scans a resume and sees a gap in employment, they might assume the candidate lacks drive. But the 'hidden side' could be caregiving responsibilities, a health issue, or a intentional career break for skill-building. The folded-over assumption leads us to act on incomplete information, reinforcing biases about who is 'qualified' or 'committed.' The first step in the Peanuto method is to consciously unfold the shirt—to ask, "What am I not seeing?" before forming a conclusion. This simple act disrupts the automatic pattern.

Precarious Stacks: How Privilege Accumulates Unsteadily

A stack of t-shirts looks orderly, but the more shirts you add, the more unstable it becomes. One wrong pull and the whole stack topples. This mirrors how privilege works: certain advantages—like a supportive family, a degree from a respected institution, or fluency in a dominant language—stack up, creating a seemingly stable platform. But for someone without those advantages, the stack is already precarious. A single event—like a health crisis or a layoff—can topple everything. In teamwork, precarious stacks show up when meetings are dominated by those with more 'stack' (e.g., louder voices, longer tenure), while others hesitate to speak. Recognizing precarious stacks means understanding that stability is not evenly distributed. The Peanuto method encourages us to 'redistribute the stack' by actively creating space for quieter voices, offering scaffolding (like meeting agendas shared in advance), and questioning norms that assume everyone starts from the same base.

Invisible Sorting Rules: The Order We Impose Without Thinking

When you organize your t-shirt drawer, you probably sort by some rule: color, sleeve length, or how often you wear it. But the rule itself is invisible until you look for it. In organizations, invisible sorting rules are the criteria we use to decide who gets promoted, which projects get funded, or who is invited to key meetings. Often, these rules are not written down; they're based on cultural fit, face time, or who speaks up most in meetings. For instance, a team might say they value 'innovation,' but the sorting rule might actually favor ideas presented in a slick deck over those born from hands-on experience. To see invisible sorting rules, we need to step back and observe the pattern: who is consistently left out? What criteria are actually rewarded? By making the rule visible, we can decide whether it's fair or whether it needs to be redesigned.

How the Peanuto Framework Unfolds the Drawer: Core Concepts

The Peanuto framework is built on the idea that bias is not a character flaw but a design problem. Just as you can redesign a drawer with dividers, labeling, and a better folding technique, you can redesign the structures that produce bias. The framework has three core concepts: noticing, naming, and nudging. Noticing is the practice of catching yourself in the moment when a bias pattern might be at play. Naming is giving that pattern a specific label (like 'folded-over assumption') so you can talk about it with others. Nudging is making a small change to the process—like asking everyone to write down ideas before a discussion—that shifts the outcome toward fairness. These concepts are not about perfection; they are about progress. The goal is to make the hidden structures visible and to create environments where everyone's 'shirt' has an equal chance of being seen.

Noticing: The Art of Catching the Fold

Noticing is the hardest skill because our brains are wired for efficiency. We rely on heuristics—mental shortcuts—to navigate the world. The key is not to stop using shortcuts (we can't), but to become aware of when a shortcut might be leading us astray. One practical technique is the 'three-second pause.' Before making a decision about a person or an idea, stop for three seconds and ask: "What am I assuming right now? What might I be missing?" This pause is enough to interrupt the automatic fold. Another method is to keep a 'bias log' for a week. Every time you catch yourself making a quick judgment (positive or negative), write it down, along with the context. Over time, you'll see patterns. For example, you might notice that you tend to assume younger colleagues are less experienced, or that you trust ideas from certain departments more. Noticing is not about blame; it's about data. With data, you can start to see the hidden structures.

Naming: Creating a Shared Vocabulary for Hidden Structures

Once you notice a pattern, naming it gives you power over it. The Peanuto framework provides simple, memorable names for common bias structures: 'folded-over assumption' (seeing only partial information), 'precarious stack' (uneven distribution of advantage), 'invisible sorting rule' (unspoken criteria), and 'bottom-of-the-drawer effect' (systematic neglect). When a team can say, "I think we're making a folded-over assumption about this candidate's career gap," they move from vague discomfort to specific, actionable feedback. Naming also reduces defensiveness because it depersonalizes the issue. It's not about accusing someone of being biased; it's about pointing out a structural pattern that anyone could fall into. This shared vocabulary becomes a tool for conversations that might otherwise be tense. In practice, naming can be done in meetings with a simple phrase: "Let's pause—I'm noticing a potential invisible sorting rule here. Are we favoring ideas that come from the loudest voices?"

Nudging: Small Design Changes That Shift Outcomes

Nudging is the action step. Once you've noticed and named a structure, what can you do to change it? The answer is almost always a small process change, not a grand cultural revolution. For example, if you've noticed that in your team meetings, certain people rarely speak (a precarious stack), a nudge could be to implement a 'round-robin' where everyone shares an update in turn, or to use a digital tool where ideas can be submitted anonymously before discussion. If you see a folded-over assumption in performance reviews, a nudge could be to require reviewers to list specific examples of both strengths and growth areas, rather than relying on a general impression. Nudges are cheap, low-risk experiments. They don't require overhauling the entire system; they just add a small check or a new step that makes the structure more visible. The Peanuto framework emphasizes that you don't need to be an expert to nudge; you just need to be willing to try one small change and observe the effect.

Step-by-Step: How to Audit Your Own Drawer and Redesign It

This section is a practical, repeatable process for applying the Peanuto framework to your own environment—whether that's your personal habits, your team's dynamics, or an entire organization. The process has five steps: Map, Question, Redesign, Test, and Iterate. You'll start by mapping the current 'drawer' (the system you're looking at), then question each part, then redesign a small element, test it, and repeat. This is not a one-time fix; it's a continuous practice. The goal is not a perfect drawer but a drawer that works better than it did before, with fewer hidden biases.

Step 1: Map Your Drawer—What Are the Visible and Invisible Elements?

Take a piece of paper or a digital whiteboard and draw a simple diagram of the system you want to examine. This could be a hiring process, a meeting structure, a project workflow, or even your own daily decision-making. On the left, list the visible elements: the steps you can see, the people involved, the criteria explicitly stated. On the right, list the invisible elements: the shortcuts you suspect, the unspoken rules, the patterns you've noticed from the noticing log. For example, in a hiring process, the visible elements might be the job description, the resume review, the interview questions, and the offer. The invisible elements might be the bias toward certain schools, the 'culture fit' (which often means 'like me'), and the time pressure that leads to quick rejections. By mapping both, you create a visual representation of the hidden structures. This map becomes the basis for the next steps. The act of mapping itself is powerful because it forces you to articulate what you usually take for granted.

Step 2: Question Each Element—Is This a Folded-Over Assumption?

For each element on your map, ask the Peanuto questions: Is this a folded-over assumption? (Are we seeing only part of the picture?) Is this an invisible sorting rule? (What criteria are we really using?) Is this a precarious stack? (Who has more stability, and who is at risk of toppling?) Is there a bottom-of-the-drawer effect? (Whose perspectives are we systematically missing?) For example, question the resume review step: Are we assuming that a gap in employment means lack of commitment? That's a folded-over assumption. Are we sorting by the prestige of the university? That's an invisible sorting rule. By questioning each element, you start to see where bias might be entering the system. The goal is not to eliminate all bias (impossible), but to identify the highest-impact points where a small change could make a big difference.

Step 3: Redesign One Small Element—The Nudge

Pick one element from your map that you suspect has a significant bias pattern. Design a small, concrete nudge to address it. For example, if you identified that the resume review relies too heavily on the 'prestigious university' sorting rule, your nudge could be to remove the university name from resumes for the first screening. This is a classic blind hiring technique. If you identified that meetings are dominated by a few voices, your nudge could be to adopt a 'first-thoughts' round where everyone writes down their ideas before the discussion starts. The nudge should be specific, low-effort, and reversible. You'll try it for a set period—say, one month—and then evaluate. The key is to start small. Big changes are hard to implement and even harder to sustain. Small nudges, on the other hand, can be tested, refined, and scaled if they work.

Step 4: Test and Observe—What Happens When You Nudge?

Implement your nudge and observe the results without jumping to conclusions. Use your noticing skills to pay attention to changes in dynamics. Did the nudge change who spoke in meetings? Did it surface different candidate profiles? Did it feel awkward or natural? It's important to collect both quantitative data (e.g., percentage of meeting airtime by person) and qualitative observations (e.g., comments like "I felt more comfortable sharing"). If the nudge seems to have a positive effect, consider expanding it to other parts of the system. If it has no effect or unintended consequences, that's also valuable data—it tells you that the structure might be more complex than you thought, and you need to try a different nudge. Remember, the goal is learning, not immediate perfection.

Step 5: Iterate—Repeat the Cycle

After testing, update your map with what you've learned. Then pick another element to question and redesign. Over time, you'll build a portfolio of nudges that continuously improve the system. This iterative approach is sustainable and respects the complexity of human behavior. It also builds a culture of curiosity and humility, where bias is seen as a solvable design problem rather than a moral failing. The Peanuto framework is not a one-time workshop; it's a ongoing practice. As you iterate, you'll notice that your 'drawer' becomes less chaotic, and the hidden structures become more visible to everyone involved.

Tools and Techniques to Keep Your Drawer Tidy: Practical Aids

Just as you might use drawer dividers, labels, or a specific folding method to keep your t-shirts organized, there are concrete tools and techniques that help you apply the Peanuto framework consistently. These tools range from individual practices (like journaling) to team processes (like structured decision-making protocols) to organizational policies (like anonymized reviews). The key is to choose tools that fit your context and to use them regularly until they become habits. Below, we explore three categories of tools: self-awareness tools, team collaboration tools, and system design tools. Each category addresses a different level of the 'drawer'—the individual mind, the group dynamic, and the organizational structure.

Self-Awareness Tools: The Bias Log and the Three-Second Pause

The simplest and most accessible tool is the bias log: a notebook or digital document where you record moments when you notice a potential bias pattern. For each entry, note the context, what you observed, and what Peanuto structure might be at play (folded-over assumption, etc.). Research from various behavioral science fields suggests that regular self-reflection can reduce automatic bias over time. The three-second pause is another micro-tool: before making a snap decision about someone, take three seconds to ask yourself what you might be missing. This pause can be integrated into high-stakes moments like evaluating a job candidate, responding to an email, or deciding who to assign to a project. Both tools are free, require no technology, and can be started immediately. They build the noticing muscle.

Team Collaboration Tools: Structured Participation Protocols

For teams, structured protocols can prevent invisible sorting rules and precarious stacks. One effective tool is the 'round-robin' format for meetings: instead of open discussion, go around the room and give each person a set time to share their thoughts before any cross-talk. Another is the 'anonymous idea submission' tool, where team members submit ideas via a shared digital board (like a shared document or a simple form) before the meeting, and then the team discusses them without knowing who submitted which idea. This prevents loud voices or hierarchical status from biasing the evaluation. A third tool is the 'decision criteria checklist': for any major decision, list the criteria you'll use in advance, and then check whether any hidden criteria crept in during the discussion. These tools are low-cost and can be adopted for a single meeting to test their effectiveness. Many teams find that they not only reduce bias but also improve the quality of ideas by surfacing diverse perspectives.

System Design Tools: Process Audits and Blind Reviews

At the organizational level, tools like process audits and blind reviews can systematically address hidden structures. A process audit involves mapping a key process (e.g., promotion, project allocation, customer service) and analyzing it for bias patterns using the Peanuto questions. This can be done annually by a cross-functional team. Blind reviews—where identifying information like name, gender, or department is removed from evaluations—are widely used in hiring and can be extended to other areas like award nominations or grant decisions. Many large organizations have adopted structured interviews with standardized questions, which reduce reliance on folding-over assumptions. For smaller teams, a simple peer-review system where feedback is anonymized can be a powerful nudge. These system design tools require more upfront effort but have a broader impact because they change the structure itself, rather than relying on individual vigilance.

Comparison Table: Self-Awareness vs. Team vs. System Tools

Choose the tool that matches your current capacity. If you're an individual, start with the bias log. If you lead a team, try a round-robin in your next meeting. If you influence organizational policy, propose a blind review. All tools are interconnected: using one often makes the others more effective.

Growth Through Persistence: How to Keep Your Drawer Tidy Over Time

Like maintaining an organized t-shirt drawer, reducing hidden bias is not a one-time project; it's an ongoing practice. The initial excitement of a new framework can fade, and old habits—like the folded-over assumption or the invisible sorting rule—can creep back. This section addresses the growth mechanics of the Peanuto approach: how to sustain momentum, deal with setbacks, and deepen your understanding over time. The key is to view bias reduction as a skill, not a destination. Skills require regular practice, feedback, and adaptation. We'll explore three growth strategies: building a habit loop, creating accountability structures, and expanding your circle of noticing.

Building a Habit Loop: Noticing, Naming, Nudging as a Daily Ritual

The Peanuto framework is most effective when it becomes a habit. Use the classic habit loop: cue, routine, reward. The cue could be a specific event (like starting a meeting, reading a resume, or making a quick decision). The routine is the three-second pause followed by noticing, naming, and nudging. The reward could be the satisfaction of catching a pattern or the positive feedback from a colleague who appreciates a more inclusive process. To make the loop stick, start small: commit to applying the framework in just one context per day. For example, for one week, focus on noticing folded-over assumptions during email communication. The next week, add naming them in team meetings. Over time, the practice becomes automatic. Many people find that after a few weeks, they start noticing patterns they never saw before, which itself becomes reinforcing. The habit loop is supported by environment design: keep a bias log on your desk, set a phone reminder, or share your commitment with a colleague who can check in with you.

Creating Accountability Structures: The Power of a Peanuto Partner

Accountability is crucial for long-term growth. Find a partner—a colleague, friend, or mentor—who is also interested in reducing bias. Meet weekly for 15 minutes to share one noticing, one naming, and one nudge from the past week. This simple structure accomplishes several things: it forces you to reflect, it provides a safe space to discuss mistakes without judgment, and it creates a shared vocabulary. Over time, your partner can help you see blind spots in your own noticing. If you're in a team, consider starting a monthly 'drawer check' where the team reviews one process element together using the Peanuto questions. This not only improves the process but also normalizes the practice of talking about bias openly. Many teams report that this regular check-in reduces the tension around diversity conversations because it frames bias as a structural issue we all contribute to, not a personal accusation.

Expanding Your Circle of Noticing: From Self to System

As you become more proficient, you'll naturally start noticing bias patterns beyond your immediate context. This is a sign of growth. The Peanuto framework encourages you to expand your circle of noticing: first, focus on yourself; then, on your team; then, on your organization; and ultimately, on broader societal patterns. Each level requires different tools and a deeper understanding of systems. For example, at the societal level, you might notice how invisible sorting rules affect access to education or healthcare. While you can't change entire systems alone, you can advocate for nudges in your sphere of influence. The growth mindset is about recognizing that bias is everywhere, but so is the potential for small, persistent improvements. Celebrate small wins—like a meeting where everyone spoke equally, or a hiring process that attracted a more diverse pool—and use them as fuel for continued effort.

Common Pitfalls and How to Avoid Them: When Your Drawer Gets Messy Again

Even with the best intentions, applying the Peanuto framework is not always smooth. People often encounter common pitfalls that can derail progress or cause frustration. Recognizing these pitfalls in advance helps you prepare for them and respond gracefully when they occur. Below, we identify five frequent mistakes: the 'just one more shirt' trap, the 'perfect drawer' fallacy, the 'blame the folder' reflex, the 'invisible rule denial', and the 'nudge fatigue' syndrome. For each, we offer concrete mitigation strategies based on the Peanuto principles of noticing, naming, and nudging.

The 'Just One More Shirt' Trap: Overloading Your System

The 'just one more shirt' trap occurs when you try to add too many nudges at once, overwhelming the system. For example, a team might decide to implement blind resume reviews, round-robin meetings, anonymous idea submissions, and a bias log for all members simultaneously. This overload leads to resistance, confusion, and abandonment of all changes. The mitigation is to start with exactly one nudge. Choose the highest-impact, lowest-effort change and implement it for at least one month before adding another. This creates a sustainable pace. Remember that the goal is not to fix everything at once but to build a habit of iterative improvement. Each nudge should be fully integrated into the routine before the next one begins. Think of it like organizing a drawer: you don't dump all the shirts out and try to reorganize in one go; you take out one stack, fold it neatly, and put it back.

The 'Perfect Drawer' Fallacy: Expecting Zero Bias

The 'perfect drawer' fallacy is the belief that if you apply the framework correctly, you will eliminate bias entirely. This is unrealistic and leads to disappointment when biases inevitably reappear. Bias is a feature of human cognition and social systems; it can be reduced but never eliminated. The mitigation is to reframe your goal from 'elimination' to 'reduction and awareness.' Celebrate when you catch a bias pattern, even if you didn't prevent it. The act of noticing is itself a win. The Peanuto framework is about progress, not perfection. In practice, this means setting a target like 'reduce the airtime imbalance in meetings by 20%' rather than 'ensure everyone speaks exactly equally.' Small, measurable improvements compound over time and are more motivating than an impossible ideal.

The 'Blame the Folder' Reflex: Personalizing Systemic Issues

The 'blame the folder' reflex happens when someone feels accused of being biased and becomes defensive. Because bias is often associated with moral failing, people may react strongly to being told they have a folded-over assumption. The mitigation is to frame all feedback in terms of structures and patterns, not individual character. Use phrases like 'our process seems to have an invisible sorting rule' rather than 'you are biased.' The Peanuto vocabulary helps with this depersonalization. Additionally, when you receive feedback about your own bias, practice curiosity instead of defensiveness. Ask, 'Can you help me see the pattern you're noticing?' This turns the conversation into a collaborative problem-solving effort rather than a confrontation.

The 'Invisible Rule Denial': Resisting the Idea That Rules Exist

Some people may deny that invisible sorting rules exist in their context, especially if they have benefited from the current system. They might say, 'We're purely meritocratic here; we just hire the best person.' The mitigation is to use data from your noticing log or from a simple process audit to show patterns. For example, you might track the demographics of candidates who advance in a hiring process and find a discrepancy. Data is harder to argue with than feelings. Another approach is to ask the person to imagine the opposite: 'If we had an invisible rule disadvantaging a certain group, what would we expect to see? Let's check if that matches reality.' This makes the abstract concept tangible. The Peanuto framework's concrete analogies (folded shirt, precarious stack) can help make the invisible visible. If someone is still resistant, it may be best to focus on the nudge that has the most empirical support (like blind reviews) and let the results speak for themselves.

The 'Nudge Fatigue' Syndrome: Losing Momentum After Initial Effort

Nudge fatigue sets in when the initial enthusiasm for a new tool wears off and people revert to old habits. This is common and natural. The mitigation is to embed nudges into existing routines so they don't require extra effort. For example, instead of adding a separate 'bias check' step, integrate it into a process you already do, like the agenda-setting for meetings. Another strategy is to rotate the responsibility for nudging among team members so it doesn't fall on one person. Finally, periodically revisit your 'why'—remind yourself and your team of the benefits you've already seen from the nudges. A simple check-in, like a quarterly 'drawer review' where you celebrate wins and discuss challenges, can reignite motivation. The Peanuto framework is a marathon, not a sprint; expect ups and downs, and keep going.

Frequently Asked Questions: Your Drawer Dilemmas Answered

In this section, we address common questions and concerns that arise when people first encounter the Peanuto analogy and try to apply it. These questions come from real-world conversations in workshops and online discussions. Each answer provides practical, nuanced guidance.

Q1: Isn't this just another way to make people feel guilty about their natural instincts?

This is a very common concern. The Peanuto framework explicitly avoids guilt or blame. It treats bias as a design problem, not a character flaw. The t-shirt drawer analogy is chosen precisely because it's neutral and relatable—everyone has a messy drawer. The goal is not to shame yourself for having biases but to understand the structure that creates them. Just as you wouldn't blame yourself for a poorly designed drawer, you don't need to blame yourself for hidden bias. Instead, you can feel empowered to redesign the structure. The framework encourages curiosity, not judgment. When you notice a folded-over assumption, simply note it and consider a small nudge. There's no guilt in noticing; there's only the opportunity to improve.

Q2: I'm in a leadership position. How do I introduce this to my team without sounding preachy?

Start with the t-shirt drawer analogy in a casual setting, like a team meeting or a one-on-one. Say something like, 'I've been thinking about how my own mental shortcuts might affect decisions, and I came across this analogy about a t-shirt drawer. It really clicked for me. Would you be open to trying a small experiment in our next meeting to see if we can surface more perspectives?' This frames the initiative as a personal exploration, not a top-down mandate. Then, suggest one small nudge, like a round-robin for sharing ideas. Let the team experience the benefit firsthand. Once they see that the nudge leads to better ideas or more inclusive conversation, they'll be more open to deeper exploration. The key is to lead by example and to emphasize that this is a learning process for everyone, including you.

Q3: What if the nudge doesn't work or makes things worse?

That is a valid risk, and the Peanuto framework accounts for it by being iterative. If a nudge doesn't work, it's not a failure; it's data. You can always revert to the old process and try a different nudge. For example, if you try a round-robin and find that people feel pressured to speak before they're ready, you might switch to anonymous written input followed by discussion. The key is to test your nudge for a set period (e.g., one month) and collect feedback before making a judgment. Avoid the impulse to abandon the entire approach if one nudge flops. Instead, use the experience to refine your understanding of the structure. The Peanuto method is about learning, not about being right.

Q4: How do I handle someone who says, 'This is just woke nonsense'?

This is a challenging situation. The best approach is to avoid political or ideological framing. Focus on the practical benefits: better decisions, more diverse ideas, reduced groupthink. Use the t-shirt drawer analogy to ground the conversation in a neutral, everyday experience. You might say, 'I'm not talking about politics at all. I'm talking about how our natural shortcuts can lead us to miss good ideas or good people. This is about effectiveness, not ideology. Would you be open to trying a small change in our next project review to see if it surfaces anything we might have missed?' By keeping the focus on outcomes and using concrete examples, you can often find common ground. If the person remains resistant, it may be best to proceed with the nudge on a small scale and let results speak for themselves.

Q5: I'm just one person. Can I really make a difference?

Absolutely. The Peanuto framework is designed to start with individual noticing and naming. One person's awareness can change a single interaction, which can then ripple outward. For example, if you notice a folded-over assumption in a hiring committee and name it, you might change the outcome for that candidate. Over time, as you share your practice with others, the impact grows. Many organizational changes start with one person who decided to try a small nudge. The bias log and three-second pause are tools that require only you. Even if you never change a policy, your own decision-making will become more aware and fair. And that matters.

Synthesis and Your Next Steps: From Messy Drawer to Clearer Vision

We've explored how the t-shirt drawer is a powerful metaphor for understanding hidden structures of everyday bias. The drawer isn't just messy—it's organized by invisible rules, folded-over assumptions, and precarious stacks that systematically hide certain shirts while making others easily accessible. The Peanuto framework gives you a practical way to notice, name, and nudge these structures, turning abstract bias concepts into concrete, manageable actions. The key takeaways are: bias is a design problem, not a character flaw; small, iterative nudges can create significant change over time; and the practice of noticing, naming, and nudging becomes easier with regular use. This is a skill you can build, just like learning to fold a shirt properly or organize your drawer with dividers.

Your Three Immediate Next Steps

1. Start a bias log today. Use a simple notebook or a note-taking app. For the next week, record at least one moment each day where you notice a potential folded-over assumption, invisible sorting rule, or precarious stack. Don't judge yourself; just observe. This builds the noticing muscle. 2. Pick one nudge for this week. Choose a context where you have influence—a meeting you attend, a decision you make, or a conversation you'll have. Implement the nudge and observe what happens. For example, in your next team meeting, suggest a round-robin for sharing updates. 3. Share the analogy with one other person. Tell them about the t-shirt drawer and the Peanuto framework. Ask if they'd be interested in trying a small nudge with you. This creates an accountability partner and spreads the practice. After a month, review your bias log and reflect on any changes you've noticed. Then, pick another nudge and continue the cycle.

The goal is not a perfect drawer but a more conscious one. Every time you notice a folded-over assumption, you've already made a difference. Every time you name a hidden structure, you give others permission to see it too. Every time you nudge a process, you create a small ripple of fairness. The Peanuto analogy reminds us that bias is not a mysterious force—it's something we can understand, talk about, and gently reshape, one t-shirt at a time. Start today.