Learning to tell the difference between preferences, traditions, and requirements (PTR) can help managers mitigate implicit bias, practice inclusive leadership, and get better outcomes.
This guide helps you learn the PTR framework, so you can delegate effectively, communicate organizational norms or expectations, and consider new perspectives.
Key Takeaways
- Addressing bias is essential for high-performing teams, a healthy team culture, and results.
- Bias in the workplace includes assumptions that influence decisions and outcomes (both conscious and unconscious). Bias can impact hiring, performance, retention, team culture, and progress toward goals.
- The PTR framework (preferences, traditions, requirements) helps managers reduce bias and delegate effectively. Start with the requirements for success, then pause to examine hidden assumptions or expectations.
- Reducing bias requires awareness, practice, structured decision-making, and diverse perspectives.
What is Bias in the Workplace?
Bias is conscious or unconscious assumptions that influence decisions and outcomes. We all have unconscious or implicit biases shaped by the world we live in, the cultures we come from, our lived experiences, and mental shortcuts we’ve learned along the way.
At work, bias can shape how we communicate and how we relate to others. Biases can affect:
- Hiring and promotions
- Task delegation and leadership opportunities
- Performance evaluations
- Equal pay or compensation
- Team dynamics, communication, and culture
A common example is “like me” bias or affinity bias: favoring employees who share similar backgrounds, interests, or communication styles.
Managers can reduce bias by using structured frameworks like PTR, choice points, hiring rubrics, performance evaluation rubrics, and fair process decision-making.
What is the Preferences, Traditions, and Requirements Framework?
PTR is a practical tool that helps managers separate what truly matters (the requirements) from habits or assumptions (preferences and traditions), so you can delegate effectively and empower staff to drive their work forward.
- Preferences: What you personally prefer
- Traditions: How things have always been done
- Requirements: What is actually necessary to get results
Bias often enters when preferences and traditions are treated as requirements.
From an equity and inclusion standpoint, using the PTR framework helps you to pause; get more explicit about organizational norms, culture, or expectations; and consider new perspectives.
We recommend that project leaders and managers start from the bottom: name the requirements.
Before delegating a task or project, ask yourself: What’s most important to achieve a good result? What does success look like? Then, delegate effectively with our guide and worksheet.
Example: Using PTR to Reduce Bias
Let’s say you’re onboarding a new manager and communicating expectations.
Instead of saying: “We send weekly written updates before meetings.”
Using PTR, you might communicate:
- Requirement: Team members have the information they need to make decisions and collaborate.
- Tradition: We send updates weekly via email.
- Preference: I prefer written updates but I’d love to discuss what works best for you.
This shift creates space for:
- New ideas (e.g., video updates, shared dashboards)
- More inclusive approaches
- Greater alignment around outcomes and expectations
By isolating the P, T, and R, you can manage with an eye toward the requirements, seek other perspectives, and be explicit when there’s a reason for requesting a particular approach.
Check out some additional examples of PTR in action.
Take your management skills further. Ready to build more equitable, high-performing teams? Explore our Managing to Change the World training to strengthen your skills in delegation, feedback, and decision-making, while learning how to reduce bias and lead more effectively.
How to Apply PTR in Your Work
Separating your PTRs takes practice. Here are some considerations as you get started.
1. Start with requirements
Define the outcome you need and the specific goal you’re trying to achieve. Then build the team’s sense of ownership and shared stake in success, by giving them room to shape the pathway to results.
Let’s say your organizational values include transparency and collaboration. With these values in mind, you might clarify that the requirement is for everyone to have timely access to the information they need to make decisions in their realm and spot opportunities to collaborate.
By distinguishing the requirement, you might realize you need to explore new paths to the same outcome, such as video updates with transcripts, which could be even more engaging and accessible.
Summary: Effective managers identify must-have outcomes or requirements, and rethink traditions.
2. Be flexible and seek other perspectives
Sometimes, you’ll need to let go of your preferences or work with staff to revise traditions (however beloved).
When we rely on preferences and traditions as shortcuts to outcomes, we risk short-circuiting our team’s ingenuity. We miss out on new approaches that emerge from diverse perspectives. So, seek other perspectives as you separate your R’s from your P’s and T’s.
Summary: Bias narrows thinking; diverse input expands it.
3. Watch out for sneaky P’s and T’s
Some P’s and T’s have been around so long they become autopilot requirements. This can impact the success, participation, and belonging of your team members who have different needs, experiences, or ideas. It can also obscure your goal.
If you find yourself dictating how you’d like something done instead of what outcome you’re aiming for, pause and ask yourself if the “how” is actually a requirement.
Summary: Traditions and norms can always be re-evaluated.
4. Avoid hidden expectations
When expectations and assumptions are unnamed (or unexamined), staff are less likely to succeed. Staff who are more like you (or know you better) may be more likely to pick up on those expectations. Staff who are less like you might not spot the clues. No one should be expected to read your mind. When you take the invisible expectations and assumptions you have in your head and articulate them, you get clarity and your staff member gets a compass. This helps you get better aligned for the good of the work and your team culture.
Summary: Unspoken preferences can disadvantage team members who don’t share your background or experiences.
5. Be explicit about why some preferences and traditions exist
There’s nothing inherently wrong with preferences or traditions, as long as you acknowledge them openly and distinguish them from requirements.
When a particular approach (mindset, behaviors, or values) is essential to getting great results, name it as a preference or tradition, share the “why” alongside the “how,” and indicate how open you are to other ideas.
- When you feel strongly about a preference or tradition, you might say: “For this project, I prefer we use the software we have, given the tight timeline and budget. Adopting new technology will take time we don’t have, but I’m happy to consider ideas for next time.”
- When your preference or tradition is a suggestion, but you’re open to other ideas, you might say: “We’ve been doing X because we’ve had good outcomes with X in the past, but I’m open to other ideas. What’s your experience been? Do you have another approach you think will get even better results?”
Summary: When a particular approach is essential to great results, explain why.
*Credit where credit is due: we got hooked on the idea of PTR because of this Fortune article.
Frequently Asked Questions about Bias and PTR
Implicit (or unconscious) bias refers to learned assumptions or judgments that affect a person’s decisions and behavior.
Understanding common types of bias can help managers spot them before they lead to unfair outcomes.
“Like Me” Bias: The tendency to think more highly of people who are similar to you. Also called affinity bias. Example: Giving more opportunities to team members with shared backgrounds or interests.
Confirmation Bias: Seeking information that confirms what you already believe, and discounting information that contradicts your belief. Example: Being quick to spot things that reinforce your initial impression of an employee.
Recency Bias: Relying on easily recalled (or recent) information instead of complete data. Example: Judging performance based on recent events rather than overall impact, progress, or goals.
These biases can show up in everyday decisions, especially under time pressure. The Management Center trains managers to spot choice points and address disparities, using tools like PTR, hiring rubrics, and fair process decision-making, and bias checks.
Unchecked bias can have real consequences for teams and organizations:
• Unfair treatment and discrimination for employees
• Lower retention and difficulty hiring, limiting perspectives and innovation
• Missed opportunities, harming employee advancement and careers
• Poor decision-making, driven by assumptions rather than evidence
• Reduced trust and team engagement
Addressing bias is essential for building effective management and high-performing teams.
Managers can reduce bias by using structured frameworks like PTR, choice points, hiring rubrics, and fair process decision-making.
Addressing bias improves fairness, strengthens team performance, and leads to better organizational outcomes.
PTR stands for preferences, traditions, and requirements, a framework that helps managers clarify expectations when delegating tasks or projects and reduce bias. Use TMC’s Effective Delegation Guide and Worksheet to put PTR into practice.
The Management Center is a 501c3 organization that helps leaders working for social change build equitable, sustainable, and results-driven organizations via trainings coaching, and online resources and tools.