nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Early Adopters?

Christine Robertson

While reading the Resilient Nonprofit report from the Blackbaud Institute, and there's a section on how Early Adopters fare. I like to think of myself as a somewhat early adopter. I want to be close to the front, but let others do the beta testing. Curious how others here see themselves in terms of early adoption!!

Find more posts tagged with

Comments

Lee Grisham

@Christine Robertson
I like trying new things out, especially if they solve an issue we are having. It needs to be constantly evaluated whether or not it is working and then reverted back if it causes too much work. Tributes on forms was like that for us. We added them, but then had many issues that were not foreseen, so we removed them.

Overall, I'm for progress and I believe our org could benefit from it, so I want to support it when we can.

Karen Diener

@Christine Robertson when I was working directly for a nonprofit I LOVED being part of discovery processes and early adopter programs. Now that I do consulting, it is more challenging.

Early on in my consulting career, we were told by Blackbaud that we weren't allowed to participate in these. No reason was given, but I felt like it was a big miss because I could easily represent the ideas of 15-20 different organizations. Not with EAP, since I cannot always work in their databases and test new functionality, but I could represent many perspectives in a discovery process.

I always encourage clients to take part in these but I don't believe they do. I have a lot of thoughts about that, but the TLDR version is that they are just too busy and/or the things they are asked to test would be disruptive to other departments / teams who are unwilling to participate.