Value Driven

As I think more on the subject, I think the picture can be simplified quite a bit. If we look at this minus some of the classification containers from the version 1 and version 2, the picture is a little simpler.

In a customer context or in a solution context (something we’ve implemented), we can basically define two entities: Condition and Goal.

Given these two entities, Value Proposition can be thought of as a general statement of how we will:

  • Address a condition (Fix a Problem)
  • Exploit an condition (Realize an Opportunity)
  • Satisfy a goal (Deliver a customer need)

It might be more appropriate to look at Goals descending from Conditions such that: Given Condition X, a Person will have Goal Y. From here we can say: Given Condition X or Goal Y (or both), we can add value by doing Z (or many other things). I think Goals always have to have some expressed parent Condition.

Incidentally, this is all a bit like BDD (Behavior Driven Development), but with a slightly difference angle of attack. I think it is most appropriate to call this a kind of Value-Driven process framework. It is less concerned with development and more concerned with how to define, organize, and relate Goals, Value Propositions, Strategies, and Implementations. We could quite easily flesh-out implementation into discrete tasks and milestones, and dependencies and all that. But, that's not the point at the present time.

Anyway, Implementation then becomes the specific action or actions one will take to realize the stated value proposition. Value, one can see in the diagram, is sort of mashed up against business objectives to make sure the value proposition lines up with business strategy. Thus, some Value Propositions, while valid, may not be implemented. It is important to note that while not every valuable thing is implemented, all value reasoning is captured and stored.

Further, Implementation creates new problems, new opportunities, and new goals. We must respond to these, which forms the basis for reflexive activities. Notice, however, that these are fed back through Value. Even reflexive Conditions and Goals are evaluated through the lens of Value (and ultimately Strategy).

That's the story at present. I'm developing a database model as well and will try to harden this all into something usable.