Skip to main content

About Value Driven Engineering

The philosophy, history, and evolution of VDE

Who's Behind This?

I was that engineer. The one shipping features nobody used. Chasing velocity metrics. Working weekends to hit arbitrary deadlines. Getting praised for "hustle" but frustrated that my work didn't feel impactful.

I'd built a dozen features in six months. Only two got meaningful adoption. The rest? Wasted effort. Technical debt. Code someone would eventually delete.

The breaking point came during a sprint retro when the PM said, "Great velocity this quarter!" while I sat there thinking: "But did any of it matter?"

That question changed everything.

The Shift

I started asking uncomfortable questions:

  • "Why are we building this?"
  • "What metric does this move?"
  • "How will we know if it worked?"
  • "Is this the best use of our time?"

At first, it felt like I was slowing things down. Questioning too much. Stepping outside my lane.

But something interesting happened: My work started mattering.

Features I built got used. Projects I advocated for moved business metrics. Stakeholders started pulling me into strategy discussions. I got promoted—not because I shipped more code, but because I delivered more value.

That shift—from output-obsessed to outcome-focused—transformed my career. And I realized most engineers never make it because they don't know it's an option.

Why This Site Exists

Too many talented engineers are stuck in feature factories.

They're smart, hardworking, and capable—but they're optimizing for the wrong things. They're measured on velocity, not value. On output, not outcomes. On activity, not impact.

This site exists to change that. To give engineers the mindset, frameworks, and tools to deliver real business value—not just ship code.

Because the world doesn't need more engineers who blindly follow instructions. It needs engineers who ask hard questions, challenge assumptions, prioritize ruthlessly, and deliver measurable value.

It needs value-driven engineers. And you're already on the path to becoming one.

What is Value Driven Engineering?

Value Driven Engineering (VDE) is a mindset and methodology that transforms how we approach software development. Instead of measuring success by lines of code, velocity, or features shipped, VDE focuses on the measurable business and user value delivered.

The Pattern I Kept Seeing

After my own transformation, I started noticing this pattern everywhere: teams building features that nobody uses, shipping code that doesn't move business metrics, and engineers disconnected from the impact of their work.

This disconnect creates several problems:

  • Wasted effort – Building features that don't get used
  • Slow feedback – Waiting months to learn if something worked
  • Low morale – Engineers don't see the impact of their work
  • Misaligned priorities – Engineering and business speak different languages

The Philosophy

"The goal of software engineering is not to write code—it's to deliver value."

Core tenet of Value Driven Engineering

VDE starts with a simple question: "Why are we building this?"

This question leads to a fundamental shift in how engineering teams operate:

  • From output (features shipped) to outcomes (problems solved)
  • From velocity (story points) to impact (business metrics)
  • From building (coding) to learning (validating)
  • From individual work to business partnership

Key Influences

Value Driven Engineering draws inspiration from several movements and methodologies:

Lean Startup

Build-Measure-Learn cycles, MVP thinking, and validated learning

Agile Manifesto

Customer collaboration, responding to change, and working software

Outcome-Driven Innovation

Focus on jobs-to-be-done and desired outcomes rather than features

Product Management Best Practices

Discovery, experimentation, and continuous delivery

How VDE Differs

While VDE shares DNA with these approaches, it specifically focuses on the engineering perspective:

  • Engineering accountability – Engineers own outcomes, not just outputs
  • Technical-business bridge – Translating between technical and business domains
  • Measurement culture – Data-driven decision making at all levels
  • Sustainable value – Balancing short-term delivery with long-term health

The Impact

Organizations that embrace Value Driven Engineering typically see:

  • Higher user adoption of new features
  • Better alignment between engineering and business
  • Increased engineer engagement and satisfaction
  • Faster feedback loops and learning
  • More efficient use of engineering resources
  • Clearer prioritization and decision-making

Getting Started

The journey to Value Driven Engineering doesn't require a complete organizational transformation. It starts with individuals and teams adopting the mindset:

  1. Start asking "why?" – Understand the business context
  2. Define success metrics – Know what "done" looks like
  3. Ship small, learn fast – Embrace iterative delivery
  4. Measure outcomes – Track business impact, not just activity
  5. Speak business language – Translate technical work to value

How I Can Help You

I've distilled everything I learned into three resources:

1. Free Newsletter

Monthly insights on delivering value, avoiding waste, and accelerating your engineering career. No fluff, just tactics you can apply this week.

2. Engineering Impact Starter Kit

5 battle-tested templates and frameworks that helped me (and hundreds of other engineers) shift from feature factory to value-driven. Free when you subscribe to the newsletter.

3. This Site

Principles, frameworks, and guides you can use immediately. Everything I wish someone had told me when I was stuck in the feature factory.

My promise: No hype. No BS. Just practical tactics that work in real engineering organizations.

Ready to Escape the Feature Factory?

Get the Engineering Impact Starter Kit—5 templates and frameworks that transform how you work. Free when you join the newsletter.