This site uses cookies to improve your experience. To help us insure we adhere to various privacy regulations, please select your country/region of residence. If you do not select a country, we will assume you are from the United States. Select your Cookie Settings or view our Privacy Policy and Terms of Use.
Cookie Settings
Cookies and similar technologies are used on this website for proper function of the website, for tracking performance analytics and for marketing purposes. We and some of our third-party providers may use cookie data for various purposes. Please review the cookie settings below and choose your preference.
Used for the proper function of the website
Used for monitoring website traffic and interactions
Cookie Settings
Cookies and similar technologies are used on this website for proper function of the website, for tracking performance analytics and for marketing purposes. We and some of our third-party providers may use cookie data for various purposes. Please review the cookie settings below and choose your preference.
Strictly Necessary: Used for the proper function of the website
Performance/Analytics: Used for monitoring website traffic and interactions
The first step is to understand how your organization is structured, and how it views technology. Ask on listservs ( ProgEx , NTEN Affinity Groups , ISF Yahoo group , etc.) This is not the time for jargon -- save that for talking to your developers (or your NTEN listserv buds). to get success stories. is going end-of-life!"
I started my research on a listserv of practitioners for SalesForce Nonprofit version asking for case studies and examples. I got enough information to put together an outline and rough storyboard So, I had the overall structure for the 15 minute screencast. I grabbed these from the mp3 file from Ready/Talk recordings.
You can think of it as having 24/7 access to another users filing cabinet, but each user's collection of bookmarks helps to build an rich knowledge network. Think of wikis of a good tool to collect information or knowledge. In most cases simple syntax structure is used. Resource Collection off a listserv: [link].
And my mission is really to educate and empower nonprofit leaders and their teams with the knowledge and tools to scale their revenue and amplify their impact. And the way that I’m going to talk about these case studies is the purpose, the structure, and the outcome of each. So the first case study is about parlor meetings.
And I think another important component is knowledge. Those tend to be a lot more structured and there has to be more concept refinement before submitting an application and cultivation with the program officer. And so do you have that sort of squared away on the roles and responsibilities and the processes? .
The artifacts are reaccessioned, the labels (hopefully) recycled, but what happens to the knowledge? I spoke to them on different days, so I've taken some liberty with structure here, but their words are maintained intact. NSF requires grant applicants to build on prior knowledge--where do you get it?
We organize all of the trending information in your field so you don't have to. Join 12,000+ users and stay up to date on the latest articles your peers are reading.
You know about us, now we want to get to know you!
Let's personalize your content
Let's get even more personalized
We recognize your account from another site in our network, please click 'Send Email' below to continue with verifying your account and setting a password.
Let's personalize your content