This month we open the blog with a practical look at Research department guidelines by my colleague, Michelle Guzman, who has had plenty of practice setting up workable systems. For example, even if you have a research request system in place, if it’s been a while since you’ve taken time to re-evaluate it, the steps Michelle outlines may help you come up with ideas for an even more efficient or helpful way to receive and deliver information. ~Helen
After sharing about imposter syndrome in a blog post last year, I’m excited to chat with you this time about setting up some guidelines for your research team and the larger development team at your organization.
Guidelines are essentially just formatted lists, right? And who doesn’t love making lists? So, let’s get our checkboxes ready to roll.
There are many guidelines you can establish around prospect development, and doing so can help you feel that you and your office have things under more control. For me, having a foundation and reference points that are agreed upon by leadership helps create better communication and a more useful end product.
Setting guidelines and timelines for what your team offers can be done at any point. Perhaps people in your organization kind of just know the “rules” or perhaps it is more of a free for all. Or maybe you just need to tweak your existing guidelines. I recommend that you follow a handful of steps to get through it.
First, write down – or type up – what deliverables/products/services you currently offer. This is a great time to also re-evaluate them. Are they still needed? Should you add another item that has not be officially offered but is needed?
Then, categorize them. For example, bios and ratings might go under the heading of “Deliverables”, and portfolio reviews might go under the heading of “Services”. Your office may focus purely on research or may add in areas of analytics and prospect management.
From there, you can consider the parameters you currently have set and then what you and/or leadership would like.
Next, think about product names. Are bios called profiles or overviews? Are these three names for different types of deliverables? If they are separate types of documents, make that clear and define them. Definitions can and should list what information is included in that deliverable.
For each deliverable or service, state how long it can take per prospect. This can be a range. I would recommend doing this per prospect so that it is not misinterpreted that a set of 6 bios would take 30 minutes to 1.5 hours. I mean, it could, but it is not likely. Instead, you would note:
Event Bio – 30 minutes to 2 hours per prospect
Giving yourself and your team a bit of padding on turnaround time will save some sanity in the end. This also allows you to schedule that 10 bios could take 5 hours to 3 business days – if you’re solely focused on just doing those, which is not always feasible. While considering how long the deliverable per prospect takes or could take, also consider how far out the deliverable should be requested and by whom.
Let’s walk through this a little bit using everyone’s favorite who, what, where, when, and why prompts, even if it is a little bit out of order.
Maybe right now, requestors can send an email requesting bios by the next morning. Maybe that works for you…. but probably it does not. So, let’s think about when it would be ideal to get the request.
For events, it might be ideal to have the guest list at least two weeks out from the event with the knowledge that there will always be last-minute additions. Now you have the time frame of two weeks out for event bios. Do you want that to be two weeks out from your deadline to get them to the requestor or two weeks out from the event? Whichever you choose, note that in your guidelines. Do you want to have a deadline for last-minute additions, such as having the cutoff be the end-of-business on the Thursday before a Saturday event? Or do you want it to be by noon on the Friday before? Or earlier?
You’re doing great. If you have gotten this far, you have thought through and written up at least one product name, the time frame it takes (or that you want the team to see it can take), and how far out the requestor should send the request/ticket. Now, it’s time to line out who should be requesting the items, which quickly tells us where it needs to go.
If, for example, the president’s office needs event bios, then who should be sending your office names for bios? My recommendation is that only staff members from that office should be sending you names. For example, it can become chaotic if many gift officers are sending you names they think the president should have bios on (but maybe they really don’t?). If the president’s office wants bios on people, they can let you know.
So, why would your office need to know the reason for the request? Well, as researchers it gives us a lot of context around how the product should be structured and can give us a place from which to consult with the requestor on what they need.
Are you now saying, “but Michelle, what does this actually look like?” Well, the format of this document can vary, of course. Your organization might have formatting standards. I would suggest you make it easy to read and understand for your office and the larger group. I have primarily done this using a table. The below is a very basic table you with an example:
Once you have completed the document – whether on your own or with your prospect development team – go over it with leadership. They can offer valuable edits like naming conventions or even what they want the gift officers to be doing. In the end, you will have their support. Having buy-in is very important and helpful when referencing the guidelines. These can be included with the policies of your office and the development policies, as well.
When you have the final version set, it will be up to you and the team on how you share the information. I have found that a great mantra to keep in mind for gift officers is “repeat, repeat, repeat”. We all have a thousand – or a million – things going on in our lives at work and at home. While we do this stuff every day, they do not. So, give handy guideline cheat sheets out at portfolio review meetings or consultation meetings that you have with gift officers. The guidelines are also great to include with training materials for new prospect development staff members joining your team.
Even if you don’t use these specific ideas, I hope they’ve helped give you some inspiration for creating guidelines that work for your organization!