organizational change - cdn.ymaws.com · •building a migration plan to salesforce •bring in...

16

Upload: others

Post on 01-Aug-2020

0 views

Category:

Documents


0 download

TRANSCRIPT

Page 1: Organizational Change - cdn.ymaws.com · •Building a migration plan to Salesforce •Bring in diverse set of stakeholder perspectives: users, customers, donors, software experts,
Page 2: Organizational Change - cdn.ymaws.com · •Building a migration plan to Salesforce •Bring in diverse set of stakeholder perspectives: users, customers, donors, software experts,

• Organizational Change

• Department Collaboration

• Technology as a Tool

• Donor Centric Decisions

• Build on Successes

• Cross Pollinate Lessons Learned

Page 3: Organizational Change - cdn.ymaws.com · •Building a migration plan to Salesforce •Bring in diverse set of stakeholder perspectives: users, customers, donors, software experts,

• Silos of data on multiple platforms; no APIs or integrations

• Time intensive data collection for mailings and emails

• Lack of Information. No real data tracking

• Paper heavy recognition and manual workflows

Page 4: Organizational Change - cdn.ymaws.com · •Building a migration plan to Salesforce •Bring in diverse set of stakeholder perspectives: users, customers, donors, software experts,

• Single integrated platform

• Improved efficiency and productivity

• More effective tracking of data

• Customer/Donor friendly and customizable

Page 5: Organizational Change - cdn.ymaws.com · •Building a migration plan to Salesforce •Bring in diverse set of stakeholder perspectives: users, customers, donors, software experts,

• Experimented with different ways of reaching our audiences• Patrons of the Arts – older population with letters, email campaigns, phone

• Giving Tuesday – matching gifts with a video appeal via blog and social media

• Annual Appeal – paper campaign with and without letter, email campaigns

• Special stewardship recognitions

• Recognition societies

Page 6: Organizational Change - cdn.ymaws.com · •Building a migration plan to Salesforce •Bring in diverse set of stakeholder perspectives: users, customers, donors, software experts,

• Full inventory of campaigns and collateral: what, when and to whom

• Centralized marketing efforts to an annual marketing plan/calendar with all campaigns and initiatives planned out for the year • Project Management Platform

• Experiment with social media campaigns and strategies• Consolidated footprint and moved from pages to groups

• Launched blog and focus on SEO

• Analysis of technology platforms and strategic plan forward

Page 7: Organizational Change - cdn.ymaws.com · •Building a migration plan to Salesforce •Bring in diverse set of stakeholder perspectives: users, customers, donors, software experts,

• Segmented audiences based on interests and history

• Give members/donors ability to control the messages they receive

• Centralized schedule of all outgoing promotional messages

• Less paper mailings, more personal touches

• Come together on tech needs. What are our common goals?

• Technology as a tool for better engagement

• Automated Workflows to focus more on relationship building

Page 8: Organizational Change - cdn.ymaws.com · •Building a migration plan to Salesforce •Bring in diverse set of stakeholder perspectives: users, customers, donors, software experts,

• Keep your donors at the center of everything you’re doing

• How does what you're doing impact them?

• Constantly ask yourself “Why are we doing it like this?”

• Is this truly a best practice or is this just how we’ve always done it?• What’s the worst that can happen if we try something new? (risk analysis)

Page 9: Organizational Change - cdn.ymaws.com · •Building a migration plan to Salesforce •Bring in diverse set of stakeholder perspectives: users, customers, donors, software experts,

• Change our focus from being transactional to relationship building

• Less details, more outcomes and impacts

• Increase focus on content creation and storytelling

Page 10: Organizational Change - cdn.ymaws.com · •Building a migration plan to Salesforce •Bring in diverse set of stakeholder perspectives: users, customers, donors, software experts,

• Building a migration plan to Salesforce

• Bring in diverse set of stakeholder perspectives: users, customers, donors, software experts, senior leadership

• Network outside your agency: user groups, other non-profits, for-profits, local meet ups, conferences

• Make sure the timing is right (pro tip: the timing is never right)

• Clean data prior to migration

• If planning a data migration, take how much time you expect it to take and triple it.

Page 11: Organizational Change - cdn.ymaws.com · •Building a migration plan to Salesforce •Bring in diverse set of stakeholder perspectives: users, customers, donors, software experts,

• With clear expectations people will adapt• Patrons of the Arts, and older population that we worried would not be tech

savvy and adapt, by and large adopted the new system with few issues

• Produced a video explaining benefits of the new technology and how to best use it to their benefit

• For those who did have some struggles, we allotted time to walk them through it instead of doing it for them.

• Benchmark with other industry leaders

• Fear of the ticket fees and add a donation to your ticket purchase

• Trust between colleagues is paramount

Page 12: Organizational Change - cdn.ymaws.com · •Building a migration plan to Salesforce •Bring in diverse set of stakeholder perspectives: users, customers, donors, software experts,

• Integrated platform allows us to get a full picture of donors and constituents

• Leverage more SMS• Text to vote and Text to give (coming soon)

• Easy Patron of the Arts subscription renewals

• Automated workflows and recognition• Differentiated work flows based on giving levels and constituent VIPs

• Special recognition at events for VIPs – gifts and notes on seats

• Expand the platform to bring a full picture of all constituents

Page 13: Organizational Change - cdn.ymaws.com · •Building a migration plan to Salesforce •Bring in diverse set of stakeholder perspectives: users, customers, donors, software experts,

• Take a full inventory of your systems and processes

• Consistently ask “Why." Why are we doing things this way?• Trust between departments to allow us to ask why and challenge.

• Test some theories – don’t be afraid to try new things and break things, but measure your results and adjust quickly.

• Talk to people who support your ideas. More importantly talk to people who challenge them as well

• Push yourself to talk to your natural partners as well as the not so natural partners.• Not just YMCA and JCC, but what can we learn from Apple, Fandango, hotels, etc

Page 14: Organizational Change - cdn.ymaws.com · •Building a migration plan to Salesforce •Bring in diverse set of stakeholder perspectives: users, customers, donors, software experts,
Page 16: Organizational Change - cdn.ymaws.com · •Building a migration plan to Salesforce •Bring in diverse set of stakeholder perspectives: users, customers, donors, software experts,