• Home
  • BVSSH
  • C4E
  • Playbooks
  • Frameworks
  • Good Reads
Search

What are you looking for?

Policy : Eliminate Non-Value-Adding Activities

Commitment to Value-Focused Engineering
We believe that the most effective teams maximise time spent on high-impact work. Manual tasks, over-engineered solutions, and performative rituals dilute focus and distract from what matters. By eliminating non-value-adding activities, we create space for innovation, improvement, and real customer outcomes.

What This Means
We identify and remove friction that does not serve delivery or learning. We question habits, automate repetitive tasks, and simplify decision-making. Engineering time is precious—and should be protected from unnecessary ceremony, manual toil, and speculative complexity.

Our commitment to eliminating non-value-adding activities is built on:

  • Automation of Manual Tasks – Repetitive activities like deployments, testing, and reporting are automated wherever possible, reducing toil and improving consistency.
  • Focused Code Reviews – Reviews centre on meaningful improvements—clarity, correctness, maintainability, and alignment to architecture—not minor formatting or stylistic preferences.
  • Optimised Ceremonies – Standups, retros, and rituals are tuned for alignment and flow. We prioritise honest communication and coordination over performance or theatre.
  • Simplicity Over Abstraction – We avoid premature abstraction, generalisation, or framework-building that solves problems we don’t yet have. We build for clarity and current need.
  • Outcome-Oriented Data Pipelines – Data teams only build pipelines that lead to tangible decisions or improvements. Vanity metrics and pipelines without clear purpose are deprioritised.

Why This Matters
Time spent on low-value work is time not spent delivering outcomes. Overhead, bureaucracy, and speculative complexity slow teams down and reduce impact. By eliminating what doesn’t add value, we increase focus, accelerate learning, and improve team satisfaction.

Our Expectation
All teams must challenge the necessity and impact of how they work. This includes automating where feasible, simplifying where possible, and aligning work to clear outcomes. Leaders must support efforts to streamline rituals, reduce technical clutter, and cut unnecessary steps.

To support this policy, teams will be guided by standards for automation, ceremony effectiveness, pipeline justification, and review practices. By eliminating non-value-adding activities, we sharpen our focus on what really moves the needle—and maximise the return on engineering effort.

Associated Standards

Technical debt is like junk food - easy now, painful later.

Awesome Blogs
  • LinkedIn Engineering
  • Github Engineering
  • Uber Engineering
  • Code as Craft
  • Medium.engineering