Early successes

Tech changes will demand organizational changes — like it or not.

But you don't have to do it all at once.

Often it's best to start by doing one thing very well -- get an early success -- to build early confidence, rather than insisting on wholesale change right out of the gate.

Case in point: I spoke recently with a CiviCRM site admin who wanted to start leveraging SearchKit for reporting, rather than just relying on the traditional (and more rigid) CiviReport framework.

But she knew it would make for a lot of questions for her team if she insisted on moving all their reports to SearchKit.

So took it a step at a time.
Picked one simple report.
Recreated it in SearchKit.
Told her team about it.
And even changed the criteria on the old report so it would always display zero rows (a kind of "this is not the data you're looking for" enforcement mechanism).

The result?

Her team have gotten used to the SearchKit interface,
and they're more open to using it in the future.
She's now in a position to start moving more reports to SearchKit,
and to start choosing SearchKit instead of CiviReports for new reporting needs.

Her staff are happy.
She's happy.

Because she moved slowly enough for her team to keep up, and focused on early success.

All the best,
A.