Three specimen passages — when each value should lead
Privacy as primary
Use this priority when the tool processes personal or identifiable information and the main risk is misuse, mission creep, or erosion of trust.
- When appropriate
- If a scheduling plugin holds staff contact details, location logs, or links to health-adjacent notes and the user base expects limited visibility, prioritise privacy.
- Typical benefits
- Reduced surveillance, retained user trust, smaller data collection surface, and clearer limits on access. Policies and limited retention reduce future misuse vectors.
- Likely harms
- Higher friction for administrators, slower onboarding, and possible loss of helpful automation. Some legitimate convenience is sacrificed to reduce exposure.
Counterexamples: favoring privacy can backfire when it prevents necessary visibility for safety or when heavy redaction breaks essential workflows (see CASE-A and BOX-A style scenarios).
3-step tailored checklist (privacy)
- Confirm the minimal data needed to deliver the tool's core function and document omitted fields.
- Prefer local consent and role-limited access over broad defaults; record the rationale in the decision log.
- Define compensations: transparency notices and an appeal channel when access is limited.
Communicable rationale
We prioritise privacy because the tool will handle identifiable staff information and our primary risk is loss of trust and potential misuse. We will therefore minimise data collection, restrict access to named roles, and provide clear notices; where convenience is reduced, we will offer documented compensations such as a managed support channel and time-bound exceptions.
Convenience as primary
Make convenience primary when the tool addresses repetitive operational friction, the benefits are widely distributed, and small productivity gains compound across many users.
- When appropriate
- For a lightweight team dashboard that aggregates already-public schedule slots to reduce coordination time, convenience may be the dominant value.
- Typical benefits
- Faster workflows, reduced error from manual steps, higher adoption, and clearer productivity gains that free time for higher-value tasks.
- Likely harms
- Convenience-first designs can collect more telemetry, centralise control, and obscure who is affected; they can also entrench defaults that later become hard to unwind.
Counterexamples: convenience-centered features have backfired when automation masked bias in allocation or when data collection created unexpected exposure (SAMPLE-CODE like scenarios).
3-step tailored checklist (convenience)
- Identify the smallest automation that materially reduces user time and test on a pilot group.
- Document what data the automation reads and why it cannot operate on a less-detailed signal.
- Commit to rollback criteria and a monitoring channel if friction or harm emerges.
Communicable rationale
We prioritise convenience because this tool reduces repetitive coordination overhead across many teams; to balance privacy and fairness concerns, we will limit logging, run a constrained pilot, and publish clear rollback criteria and an owner for ongoing monitoring.
Fairness as primary
Choose fairness when the tool affects allocation, promotion, visibility, or evaluation in ways that could systematically advantage or disadvantage identifiable groups.
- When appropriate
- When a plugin influences who gets visible shift slots, promotional visibility, or workload assignment and those outputs determine opportunities, fairness must lead.
- Typical benefits
- Reduced systemic bias, clearer auditability, deliberate distribution rules, and increased legitimacy for decisions that affect careers or remuneration.
- Likely harms
- Stronger fairness safeguards can add process overhead, slow decision cycles, and sometimes reduce individual convenience; fairness work can also surface contested trade-offs requiring governance.
Counterexamples: fairness-first controls have sometimes created excessive bureaucracy or produced narrow rules that fail new edge cases, requiring rapid follow-up governance (see NEG-X sketches).
3-step tailored checklist (fairness)
- Map which outcomes the tool influences and identify groups exposed to distributional risk.
- Design simple, auditable rules that limit automated preferential treatment and record decision logic.
- Publish monitoring commitments and an escalation path if disparities appear in practice.
Communicable rationale
We prioritise fairness because the tool materially shapes access to opportunities; we will therefore enforce explicit allocation rules, require an audit log for critical decisions, and provide a governance owner to review outcomes at regular intervals.