association comments-o-matic » Effective Database

Comment on ASAE 2010 Annual Meeting Recap by Wes Trochlil

comments-o-matic — Fri, 27 Aug 2010 13:50:05 +0000

Garry, good meeting you in LA, too. Reply at Effective Database - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Comments-o-matic is brought to you by Scott Oser [...]

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Comments-o-matic is brought to you by Scott Oser Associates. Upcoming: more marketing education from Scott Oser and Kevin Whorton.

Comment on ASAE 2010 Annual Meeting Recap by Garry Polmateer

comments-o-matic — Thu, 26 Aug 2010 23:50:05 +0000

I had a great time at the meeting as well, just wanted to say it was great to meet you and look forward to more great blog posts!

-Garry

Reply at Effective Database

Comment on Working in a homegrown system is malpractice by Leslie Ems-Walker

comments-o-matic — Sun, 08 Aug 2010 15:00:08 +0000

Our association is currently using an homegrown AMS system. And I have found that after the upgrade and reorganization I did this past winter, and getting through the bugs this spring, I am receiving less and less errors and we are getting more and more stuff done. We are transitioning to a SaaS for our knowledge center but not sure if we will for the AMS portion. Just wanted to leave a positive about a homegrown.

Reply at Effective Database

Comment on The Best Blog You’re Not Reading by David Gammel

comments-o-matic — Tue, 20 Jul 2010 14:20:07 +0000

Thanks Wes!

“Assumes the risk for it.” That is a tremendously powerful phrase right there that gets to the heart of it. Orgpreneurs assume the risk. It can be terrifying to some but not taking on the risk is the more risky approach these days.

Reply at Effective Database

Comment on The Best Blog You’re Not Reading by Wes Trochlil

comments-o-matic — Tue, 20 Jul 2010 14:20:07 +0000

Good point. It’s riskier NOT to take the risk!

Reply at Effective Database

Comment on New Article Posted – Three Steps to Ensure Switching Systems Doesn’t Slow You Down by Garry Polmateer

comments-o-matic — Fri, 18 Jun 2010 13:00:09 +0000

Wes, awesome article! I have been using a documentation tool called Screensteps, it’s very fast and very easy to update, also synchs with Google Sites for intranet distribution.

(I have no affiliation with Screensteps, just think their stuff works great)

Garry

Reply at Effective Database

Comment on New Article Posted – Three Steps to Ensure Switching Systems Doesn’t Slow You Down by Wes Trochlil

comments-o-matic — Fri, 18 Jun 2010 13:00:09 +0000

Thanks for the post, Gary. I’m unfamiliar with Screensteps but just took a quick tour and it looks like a pretty slick tool. Anything that encourages documentation is a good thing!

Reply at Effective Database

Comment on Simplifying Your Processes Means Limiting Your Inputs – New Article Posted by Garry Polmateer

comments-o-matic — Sat, 22 May 2010 12:55:03 +0000

Great article! Another thought – if you limit the inputs, you’re limiting the variables and leaving yourself a bigger choice of event management systems. If you only have 3 requirements vs 12, there are many more options that would meet those 3.

Thanks!

Garry

Reply at Effective Database

Comment on Your Processes Means Limiting Your Inputs – New Article Posted by Garry Polmateer

comments-o-matic — Fri, 21 May 2010 13:35:03 +0000

Thanks!

Garry

Reply at Effective Database

Comment on Three Reasons Why You Need a Formal Tracking System – New Article Posted by Wes Trochlil

comments-o-matic — Tue, 20 Apr 2010 18:20:05 +0000

Sam, you raise a great point, which is that user adoption is the key to success for any data management system (which, after all, is what an issues tracking system is).

I would emphasize that “slickness” of the system is secondary to user adoption, so if Google Docs is working for you, stick with it. What is key is to ensure that users have access to it so that they know if their concerns are being heard and addressed!

What you’ve described in terms of reviewing the doc on calls is exactly what we’re shooting for; a single source for everyone to refer to. It sounds like you’re actually being fairly successful, even if it doesn’t look pretty.

Reply at Effective Database