Skip to main content

Interpretation

as killer:

Successfully building anything requires a sequence.  Software particularly problematic in that coders can get wound around the math and interrelationships within the code.

"Look at this!"

And, that has nothing to do with with what's essential, the physics of user relationship.  Love of use.

"Where is it?"

There is a balance in software development that is absolutely essential.  The balance of connecting Engineering with Marketing.  Commits that are not kept doing a number of things to drag the  possibility of successful project down.

CHICKEN <> EGG: Devs like to develop, if they liked to talk, they'd be in marketing or sales.  This becomes a problem when what needs to be done is sell.  And, before selling we have to market.  It is very difficult to market that which you are unsure you'll ever see.


Application > Smart Contracts >> Building Agreements...


EXPLORATION: Where are we hesitant to have honest, open dialog?  Is it possible that by managing honest, open dialog with clear intention and care that we actually create relationship, not thwart it?


Case Example ~ Situation | Solution | Result:

Situation > n/a

Solution > n/a

Result > n/a


Distinctions: Assessments, Conversational Energy, Gifts, Stands, Intention, Care, Honesty, Openness, Culture, Development,  

Relation To Core: Acknowledgement, Observational Frameworks, Navigational Capacity, Bridging Realities, Human Interactivity's Ones & Zeros, The Language Of Coordination, Turning Business To Enterprise, Reciprocally Transactional Loops, Marketing's Continuum,