So, how do the refs decide whether to award possession? This is the grey area. Certainly the amount of elapsed time between catching and dropping the ball plays a role in deciding. How much the receiver may have juggled the ball is also taken into account. But a generally accepted guideline is, for possession to occur, the receiver must catch the ball and then make something called a "football move" -- which is still somewhat nebulous but at a more granular level. Sometimes, a football move occurs when the receiver has the ball and takes two steps; sometimes, it's when he tucks the ball under his arm and shifts his feet. Whatever the specifics, the idea is that the receiver must exhibit some palpable sign of controlling the ball.
It is similar, in other words, to the concept I will designate as the "managerial move".
This phenomenon is most often observable at the lower managerial rungs, with junior or rookie managers. It happens a lot when command and control within an organization are ill-defined regardless of what hierarchy chart might say -- at least for the purposes of a given project. Most junior managers are unsure of themselves (which is understandable) and greet each and every opportunity to appear managerial as if every meeting is the Super Bowl and they are Tom Brady. If you tell them to manage a fire hydrant, you will soon spot one standing over the hydrant with a clipboard and a pencil, wearing an intent look. Eventually, the hydrant will gain a reputation for having a bad attitude.
Like the football move, the managerial move is designed to make the player look like he's in control. And like the football move, it is hard to specify exactly what it is. However, like Supreme Court Justice Stewart said about pornography: it can't be easily defined, but we know it when we see it.
Example? A junior manager has emailed the big boss with a proposal to proceed directly with a technical solution, recommended by a vendor, involving massive and expensive changes to the server configuration. You were not copied on the email -- perhaps because you, as a high-level techie, have raised unwelcome questions about other solutions the vendor has proposed. But the big boss performs due diligence and forwards you the proposal, asking for your opinion. So, you work two hours late and respond by raising some questions, which prompts the boss to direct you to arrange a phone conference with the vendor. Only then do you get an email from Junior (your boss is cc'ed), stipulating that you need to invite "all of the players" to the phone conference -- because he doesn't "want a breakdown in communication on such an important issue". Never mind that the communication had already broken down in the first place when Junior bypassed you on the original email. You busted his play, and his reaction was to deny that a play had been attempted -- and not incidentally to hint ever so gently that you are the rogue and require some level of adult supervision. In short, this is a classic managerial move.
To provide assistance to a certain species of junior manager is to discover that the harder you work, the more bullets find their way onto his resume. This is probably why most of the senior techies you know are grumpy, terse, and matter of fact. Ronald Reagan once said you'd be surprised at what you can accomplish, if you don't care who gets the credit. And maybe the President of the United States can afford such a magnanimous attitude. The rest of us may occasionally need to point to an accomplishment or two without someone else hogging all the credit.
I'm not completely without compassion. The life of a junior manager can be unpleasant and uncertain, or so it appears to this techie. And many junior managers eventually get promoted and become good bosses, and what would we do without them? But just keep all this in mind the next time a junior manager for whom you don't work starts following you around with a clipboard.