Collaboration & Feedback ยท Lesson 1 of 3
Disagreeing well
Study notesAbout 3 minutes. A full lesson with quick checks is on its way.
In short
Disagreeing is a normal part of engineering. Argue with evidence and trade-offs, not opinions, and let the agreed decision-maker settle it if you can't agree.
In your work
You and a colleague disagree about a form builder or custom code for a charity's referral form. You each list the costs, data protection and upkeep, and ask the tech lead to decide when you're still split.
What the UK rules say
- The BCS Code of Conduct asks IT professionals to respect and value other viewpoints, and to seek, accept and offer honest criticism of work.
What to do
- Write down the options and trade-offs, not just your preference.
- Use evidence: requirements, data, prototypes or past incidents.
- Agree who decides if you can't agree, and accept the decision.
Watch out for
- Turning a technical point into a personal one.
- Re-arguing a decision instead of bringing new evidence.
In your organisation
Who has the final say on technical decisions in your team, and where are decisions recorded?
Your employer's own policies come first.
Sources
- BCS, BCS Code of Conduct (opens in a new tab), checked 6 October 2026.
UK law and guidance, explained for learning. Not legal advice.
