outcome role model 002/ a lot of enterprise software is built around objects. customers. tickets. documents. assets. we’ve been interested in modeling outcomes instead. every company has different processes, but most work still comes down to a few recurring questions: who requested this? who is responsible for moving it forward? who receives the outcome? one simple pattern we've found useful is: customer → actor → user the customer initiates the need. the actor performs the work. the user receives the outcome. what's interesting is how often that pattern appears once you start looking for it. the domain changes. the participants change. the tools change. but some version of that structure keeps showing up. that feels like a useful foundation for helping ai understand how work moves across very different environments.
- 1 reply
- 0 recasts
- 0 reactions
Both teams need to score and win.
- 0 replies
- 0 recasts
- 0 reactions
Love the way the world comes together for the game of it.
- 0 replies
- 0 recasts
- 1 reaction