How the Three-Point Shot Changes the Data Game

Jason Zanon

In tonight’s NCAA hoops final, there’s every chance that a three-point shot will determine a champion.

After all, 3 > 2 … and that makes the three-pointer, in the words of Citadel coach Duggar Baucom, a “game-changer”, the long-range bomb that can hasten a comeback or swing a result.

Yet only with the rise of sports analytics have teams truly committed themselves to changing their games around the three-pointer, embracing the power of 3 > 2.

The three-ball has taken over the professional game over the past couple of seasons, with the most progressive NBA clubs falling over each other to hoist more and more of the high-value shots. Last year, the Golden State Warriors became the first NBA team ever to hit 1,000 threes in an 82-game season. Last week, the Houston Rockets broke that mark … with 10% of their season yet to play.

And there’s every reason to expect that these are just the overtures to a future in triplicate — more threes, longer threes, the new basic currency of the hardwood.

3 > 2.

At Frakture we’re finding the same thing holds when it comes to nonprofit technology integrations: 3 > 2.

“Integration” is a word we shy away from, even though Frakture’s bots are great at supporting integrations. It’s true that we all want to join data from our donor database and our online CRM, but point-to-point integration is fast becoming the 18-foot jumper of technology: the play from yesteryear that turns out to pack more risk than a longer outside shot and none of the game-changing upside.

Instead of shooting for a two-point integration, Frakture suggests you go downtown for three: two systems, plus a warehouse.

Frakture 3 way Sync

By reorienting an “integration” towards a data warehouse — a central data repository that you control — you’ll join the forward-thinking nonprofits and agencies who are changing the data game.

With a data warehouse, Frakture bots give you the advantages of integration (and then some!) without the unwieldiness: your “integration” won’t break if one of the software systems involved releases an upgrade. Instead, Frakture is responsible for upgrading the Bot to be sure your data keeps flowing.

An integration sinks costs into specific platforms, multiplying code debt. But the warehouse sets you free. Want to drop Luminate for Engaging Networks? Want to add a new platform? Want to run two systems side by side during your migration? It’s a snap with a warehouse: we just unplug one FraktureBot from your warehouse, and plug in the new Bot instead.

Enjoy the big game tonight. But when it comes to placing your wager, whether on sport or on data, we suggest you bet 3 > 2.  We are.

Bender_Globetrotters

Keep Reading: Related Posts

The Bots Have Been Busy!
The Bots Have Been Busy!
Ahh, summertime! I’m looking forward to BBQs, berry picking and vacation. But somehow, my growing to do list didn’t get the memo that it’s summer. Apparently more daylight does not...
Missed it? Watch how to get a data-informed strategy.
Missed it? Watch how to get a data-informed strategy.
On April 23, 2015, the Frakture team presented a highly informative webinar on The Path to Having a Data Informed Communication and Engagement Strategy. Presenters: Chris Lundberg, CEO and Michael...
Why point-to-point integrations suck
Why point-to-point integrations suck
Our Bots do a lot of pulling and pushing data around, and there’s one rule we learned pretty quickly: Point-to-point (P2P) integrations suck. For a while we thought it was...

Want to take us for a spin?

Call us for a demo today and learn how Frakture can help your organization to get more done with robots