Behavioral outcome graphConcept
Events to behaviors to patterns to outcomes.
The behavioral outcome graph would join every event, behavior, pattern and outcome Bylda sees into one map you can explore. It is direction, not product.
AnswersWhich behaviors travel with which outcomes, across everything?
Concept. Direction only. This is not in the product and has no release date. It is here so you can see where the system is going and tell us if it matters to you.
How it would work
- 01
Nodes
An event on a call, the behaviors it reveals, the pattern they belong to, and the outcomes that follow.
- 02
Edges
Each link would carry its sample size and confidence, under the same rules as today’s product.
- 03
Walk it backwards
Start from an outcome, like next step booked, and walk back to the behaviors that travel with it.
What you see
Read off the screen above. Every number is sample data from the app’s own prototypes, arranged in an illustrative layout.
- Event
- 18:42 pricing objection on the Acme Logistics call.
- Behaviors
- Answered in 0.4s. Offered 12% off.
- Pattern
- 4 of 6 price objections for Jordan in 30 days.
- Outcomes
- Next step booked 41% with an interruption against 72% without. The objection came back later.
Who it’s for
See the whole chain behind a number instead of one call at a time.
Understand why one habit matters more than another on your calls.
Where it fits
Bylda is one loop. Behavioral outcome graph is the outcomes step.
- EventsWhat happened on the call
- BehaviorsHow the rep acted
- PatternsWhat repeats, for whom
- OutcomesWhat it travels with
- ChangeOne focus, then measured
What it won’t claim
- Concept. Not in the product and no release date.
- Today’s product already builds the pieces: call review for events, analysis for behaviors, profiles for patterns, results for outcomes.
Also in Next
The whole product
What happened on the call, named as behavior.
Whether the behavior changed, with the confidence stated.
Where the system goes after V1. Not in the product yet.
