Perhaps the greatest challenge in a transformation project is balancing competing priorities between teams. While urgent, daily work needs to get done, teams are asked to re-imagine their business processes, and on top of that, to think strategically beyond their own group’s needs. Revenue teams should put aside their different goals and think together about a future vision and yet it is extremely challenging for teams to think as one, forward-looking team. At WBUR, this manifested in several ways:
- The organization’s current revenue-generating activities took precedence when defining system requirements, which meant that longer-term strategic plans were deprioritized in implementation.
- Each department had unique needs and requirements that sometimes conflicted with others’, leading to distinct implementations for teams, rather than holistic solutions.
- Merging data from legacy systems into one unified CRM required complex integration, and this meant time consuming negotiations for how to represent financial data.
These realities were not addressed at the beginning of the project, and in retrospect some teams express regret over that, but with limited time and resources, there were not easy opportunities.
After the platforms launched, it became easier to see how the legacy platforms had dictated how WBUR’s teams and their business processes functioned. With all departments merged into one platform, the opportunities for cross-team efficiencies were hard to ignore. WBUR made the organizational decision to merge the membership department and the major giving department (known as development at WBUR), to unify their approach to individual giving. Katie Stack, Director, Donor Relations & Operations for WBUR’s membership and development teams, observed that the new, unified individual giving department was fostering a seamless view of donor relationships, regardless of giving level.
“Before [membership and development] merged, we were kind of together, but we weren’t, and we were running in parallel,” explains Katie. “Now we’re trying to commingle together.”
The separate teams had often operated with distinct understandings of donor tools and interactions. Katie would hear from a development team member “‘Oh, Springboard… that’s just the pledge form.’” But Springboard, it turns out, can be used for a variety of financial processes for larger donors. After merging the departments, team members started to seek out new technology opportunities rather than dismissing a system as “not for them.”
Katie’s colleague Dixie Ledesma, Associate Director, Donor Strategy & Data, summarized it as, “Now we’re approaching everything not as development and membership, but as one full team. Donors move in and out: they’ll be in development, then they might move down into membership, and being aware of that movement and viewing it all as one pipeline is important.”