ball is the game (enterprise software pondering)

There are two ways to follow a game - go to the football stadium, or have the progress virtually represented and delivered by modern technologies; i.e. watch the game on the telly.

At work the game would be called business process where you either could be looking over shoulders as things happens, or read a report.

As we cannot be at all games nor be everywhere in the company we need some virtual representation of the progress. The legacy method is to document events with reporting thereof.

But there is an alternative representation method, keep the focus on the ball so to say. Let me expand:

Imagine watching the football (soccer) game on the telly - you do not see the ball but suddenly a pop-up appears above Beckham on the screen saying "Time: 10:23:32, Player: Beckham, Report number: Yu299, Action: Kicked ball, Where: Towards right hand corner".
Then quiet for a few seconds while the players move a bit around until another pop-up over some player on the right saying "Time: 20:23:35, Player:...".

That would be today's enterprise software documenting events and transactions. Nice pop-ups though.

Now sit down again, but this time you see the ball as it moves around on the field. Push a button and pop-ups over chosen players comes up with statistics and history as well as vectors poking out of the ball showing it's speed and direction.
But you keep such information suppressed until post-game analysis, now just sit back and enjoy the game as it follows the ball.

That would be the thingamy sticking to the football data object letting it drive the process and capture all.

Methinks that the ball should be the game.

[Note: Legacy systems are event/transaction driven business process models while thingamy is object driven.]