Issue 43 March 2014

By Martha Tuff, Development Information Officer, IWK Foundation

No prospect researcher works alone.  We all work for, and with teams of development officers, administrators, volunteers and other researchers (sometimes!)

In the not-for-profit world, we are all driven by the same goal and that is to raise more money for a worthwhile cause, even though we may do so in different ways.   The strength of the team lies in how well they work together and a big part of this strength lies in knowing what each member brings to the team.

At IWK Foundation, I have been the sole prospect researcher within my team since starting here in Oct. 2011.  However, I believe my “tips and tricks” would also work for a larger group. 

 

Getting To Know One Another

One-on-ones: When I first started in my position, I booked one-on-one meetings with my team members. This was a great way to get introduced and learn more about what they do. I aim for one-on-ones a few times a year to maintain our relationship. It only take a few minutes, but really supports ongoing collegiality.

Team huddle: Once a week, the team gets together for 15 minutes to discuss strategy and needs for upcoming meetings and requests.  It’s great way for me to keep up with team activity and see if I can provide resources for support.

Research “contests”: To encourage team members to be a part of the prospect research process, research “contests” – an initiative which stared this March - are open to colleagues who submit a prospect, update prospect information or share some “insider” knowledge over a week long period.  Their names are dropped in a hat and the lucky winner receives a coffee card!

Lunch & Learn: Many different members of the team have used this avenue to gain awareness of new programs or initiatives and it has proven to be a great, informal way to present new ideas to the team.

Weekly updates: All team members submit weekly updates to ensure everyone is aware of current and future asks.  I can also include new prospects for the team to review.

Information sharing: I share articles and information tidbits with colleagues once I know their areas of interest and priorities.  It has helped show the team I’m thinking of them and their needs.

At the end of the day, in order for me to provide the best resources to my team, I not only need to know and understand them well, but vice versa - only then are we best able to support, acknowledge and anticipate future projects.

Share this with your networks!