- Description
- Poteau indicateur à un carrefour de sentiers en forêt, avec plusieurs destinations
- Source
- Jacob W. Frank (National Park Service) · original page
- Licence
- PD Public domain
Where do biases show up?
Start from the situation you are in and find the biases lying in wait there.
In brief
- Entry by situation: each heading is a moment of the job (estimating, committee, hiring…).
- A bias appears everywhere it shows up: anchoring appears in estimating as in negotiation.
- The yellow bar on each line gives the bias's frequency in that line of work (a judgment, not a measurement).
On this page
- Recruitment 12 biases
- Annual evaluation 8 biases
- Architecture 7 biases
- Code review 7 biases
- Costing 5 biases
- Lessons learned 5 biases
- Committees 4 biases
- Contractor selection 4 biases
- Security 4 biases
- Code reviews 3 biases
- Feedback 3 biases
- Incidents 3 biases
- Meetings 3 biases
- Migrations 3 biases
- Onboarding 3 biases
- Post-mortems 3 biases
- Relations between teams 3 biases
- Technology choice 3 biases
- Tool choices 3 biases
- Annual reviews 2 biases
- Architecture choices 2 biases
- Budget 2 biases
- Bug diagnosis 2 biases
- Client communication 2 biases
- Client relationship 2 biases
- Crisis management 2 biases
- Delegation 2 biases
- Design 2 biases
- Estimation 2 biases
- Incident reviews 2 biases
- Innovation 2 biases
- Mentoring 2 biases
- Method choice 2 biases
- Negotiation 2 biases
- Overhauls 2 biases
- Performance evaluation 2 biases
- Promotions 2 biases
- Relations with contractors 2 biases
- Release planning 2 biases
- Requirements gathering 2 biases
- Risk management 2 biases
- Specifications 2 biases
- Sprint commitment 2 biases
- Supplier contracts 2 biases
- Team organization 2 biases
- Technical debt 2 biases
- Acceptance testing 1 bias
- Alerts 1 bias
- Analogy-based costing 1 bias
- Application screening 1 bias
- Architecture evolution 1 bias
- Assignments 1 bias
- Attachment to the status quo 1 bias
- Audits 1 bias
- Backups 1 bias
- Benchmarks 1 bias
- Bonuses 1 bias
- Budgets and resources 1 bias
- Business continuity 1 bias
- Career and assignments 1 bias
- Career management 1 bias
- Case studies 1 bias
- Change management 1 bias
- Choice of methods or technologies 1 bias
- Choosing a supplier 1 bias
- Choosing a technology 1 bias
- Choosing “best practices” 1 bias
- Client negotiation 1 bias
- Client relations 1 bias
- Collective evaluation 1 bias
- Communication 1 bias
- Comparing offers 1 bias
- Component choices 1 bias
- Component reuse 1 bias
- Conflict management 1 bias
- Consulting 1 bias
- Content negotiation 1 bias
- Contract renewal 1 bias
- Cross-functional projects 1 bias
- Dashboards 1 bias
- Data analysis 1 bias
- Decision meetings 1 bias
- Default settings 1 bias
- Delegated tasks 1 bias
- Delivery flow 1 bias
- Demos 1 bias
- Deployments 1 bias
- Design and ergonomics 1 bias
- Design review 1 bias
- Design reviews 1 bias
- DevOps 1 bias
- Digital transformation 1 bias
- Documentation 1 bias
- Dropping a feature 1 bias
- End-of-project review 1 bias
- Evaluating a person 1 bias
- Evaluating past decisions 1 bias
- Expert committees 1 bias
- Forecast 1 bias
- Forecasts 1 bias
- Gathering preferences 1 bias
- Go / no-go decisions 1 bias
- Go / no-go trade-off 1 bias
- Handover 1 bias
- Hierarchy 1 bias
- Hosting 1 bias
- Ideation 1 bias
- Internal recruitment 1 bias
- Investment 1 bias
- Investment decisions 1 bias
- IT 1 bias
- Juries and auditions 1 bias
- Leadership teams 1 bias
- Maintenance 1 bias
- Management 1 bias
- Management tools 1 bias
- Managerial feedback 1 bias
- Managing experts 1 bias
- Market research 1 bias
- Maturity reviews 1 bias
- Method change 1 bias
- Metrics 1 bias
- Metrics by department 1 bias
- Migration to a new product 1 bias
- Mockups and prototypes 1 bias
- Monitoring 1 bias
- Motivation 1 bias
- Objectives 1 bias
- Open source 1 bias
- Operations 1 bias
- Planning poker 1 bias
- Prioritization 1 bias
- Problem solving 1 bias
- Progress reports 1 bias
- Project communication 1 bias
- Project management 1 bias
- Project planning 1 bias
- Project review 1 bias
- Project reviews 1 bias
- Project scoping 1 bias
- Project steering 1 bias
- Projects going off track 1 bias
- Promises to the client 1 bias
- Promoting an expert into a manager 1 bias
- Promotion 1 bias
- Proof of concept 1 bias
- Quality 1 bias
- Quick decisions 1 bias
- Recovery plans 1 bias
- Recruitment and salaries 1 bias
- Relationship with a contractor 1 bias
- Release decisions 1 bias
- Remote visibility 1 bias
- Replacing an existing system 1 bias
- Reporting 1 bias
- Resource trade-offs 1 bias
- Reuse 1 bias
- Reviews 1 bias
- Rewards and bonuses 1 bias
- Risk decisions 1 bias
- Sales forecasts 1 bias
- Schedule 1 bias
- Scope management 1 bias
- Security patches 1 bias
- Self-assessment 1 bias
- Shared objectives 1 bias
- Software quality 1 bias
- Solution acceptance 1 bias
- Splitting into work packages 1 bias
- Sponsors 1 bias
- Spreadsheets and office tools 1 bias
- Steering 1 bias
- Steering committees 1 bias
- Subcontracting 1 bias
- Successive interviews 1 bias
- Supplier choice 1 bias
- Supplier evaluation 1 bias
- Support 1 bias
- Talent spotting 1 bias
- Task assignment 1 bias
- Team building 1 bias
- Team climate 1 bias
- Team communication 1 bias
- Team management 1 bias
- Team mergers 1 bias
- Team rating 1 bias
- Team reorganization 1 bias
- Team velocity 1 bias
- Teamwork 1 bias
- Technical choices 1 bias
- Technical conferences 1 bias
- Technical debt management 1 bias
- Technical decisions 1 bias
- Technical trade-offs 1 bias
- Tool change 1 bias
- Tool misuse 1 bias
- Tool selection 1 bias
- Training 1 bias
- Trends 1 bias
- Upskilling 1 bias
- Use of AI assistants 1 bias
- User interviews 1 bias
- Version upgrades 1 bias
- Workload assessment 1 bias
- Workshops 1 bias
- Writing 1 bias
Each bias entry states “where it occurs”. This page turns that information around: for a given situation, which biases should you watch for? The richest situations (those that accumulate the most biases) come first. Type a word (“estimating”, “committee”, “hiring”) to filter.
An entry point, not an inventory
The headings reuse the terms chosen in each entry: the same situation may appear under several similar names. For an overview, see also the map of links and the toolbox.
