Comments for EDM Blog

Comment on The rule of 100 and 1000 by Wes Trochlil

Wes Trochlil — Wed, 10 Mar 2010 13:45:54 +0000

Thanks Garry. People often need rules to guide them, so here’s a rule!

Comment on The rule of 100 and 1000 by Garry Polmateer

Garry Polmateer — Wed, 10 Mar 2010 13:29:10 +0000

I have never heard anyone formalize the rule of 100-1000, that’s excellent! I subconciously ask about dataset sizes, but never thought there was a rule about it.

Garry

Comment on Two New Articles Posted by Wes Trochlil

Wes Trochlil — Thu, 18 Feb 2010 22:22:11 +0000

Thanks for the note, Garry.

Comment on Two New Articles Posted by Garry Polmateer

Garry Polmateer — Wed, 17 Feb 2010 15:06:11 +0000

Thanks for the great articles! We have seen a need for a while to figure out how to better use the current systems in place, and sometimes it just takes some imagination. Jeff G, one of our consultants posted this blog which dovetails nicely with your article here:

http://www.nimbleuser.com/blogs/Nimble_News/Nimble_News/Who_are_your_most_valuable_members__Do_you_know_.aspx

Have a great day!

Garry

Comment on What everyone should know about “percentages” by Wes Trochlil

Wes Trochlil — Tue, 09 Feb 2010 13:55:55 +0000

Scott, you’re right, this IS a great post!

Good point about board books. We have to be careful about how represent (or misrepresent) our data.

Comment on What everyone should know about “percentages” by Scott Oser

Scott Oser — Mon, 08 Feb 2010 23:03:21 +0000

Wes,

This is a great post. I hope that BOD members and EDs read your blog so they realize the importance of understanding the numbers behind a percentage. Many Board books and regular reports include a large number of stats which at face value look very impressive. It is only when we look behind the percentages do we really find out what is happening. All leaders need to understand that so thanks for pointing it out.

Scott

Comment on Oh, the changes I’ve seen… by Garry Polmateer

Garry Polmateer — Fri, 29 Jan 2010 14:36:34 +0000

I think you hit the nail on the head - the biggest changes we’ve seen are around the “Cloud based” Saas solutions, and outsourcing.

It all started when we switched to Google Apps for our internal email and collaboration. We ditched our Exchange box, spam applicance, needed less backup space, less antivirus, less power…. It was a cascading effect. Now we’re using Google Apps for all of our internal collaboration, hosting project sites, we have a web based ERP (Netsuite), and our Sales teams are all using Salesforce.com.

It’s a night and day difference between 10 years ago, when everyone was constantly adding more servers, more infrastructure and getting more complicated. Now, we let other people handle that, pay the fixed cost and use our mental bandwidth for other things.

Thanks for a great blog.

Garry

Comment on Don’t miss ASAE’s Technology Conference in February by Garry Polmateer

Garry Polmateer — Thu, 28 Jan 2010 13:34:18 +0000

I will be there and try like the dickens to get to your sessions! Have a great day.

Gary

Comment on Another great idea from an AMS vendor by Wes Trochlil

Wes Trochlil — Mon, 25 Jan 2010 22:07:09 +0000

Good points, Ray and Michael. Thanks for sharing.

Comment on Another great idea from an AMS vendor by Michael

Michael — Fri, 15 Jan 2010 18:31:44 +0000

A few aspects to consider for ANY/ALL idea portals:

1 - Make suggestion area easy to access & updated. (i.e. Post date of most recent sugggestion). Without knowing if/when a new suggestion has been posted puts a burden on the client to check regularly to see if /when new items have been posted.

2 - Make clients aware of the criteria (i.e. a certain # of votes) for when an idea gets green lighted to development.

3 - Be fair with your pre-screening of posted suggestions. (Albert Enstein: “if at first the idea is not absurd, then there is no hope for it”)

4 - Be very clear on what you are asking users to vote on — (i.e. “good idea”, “good idea AND can use right away”, “good idea AND will use someday”, “good idea BUT won’t use”) — to help determine development urgency.

5 - Be open & post ideas that are rejected.

[Disclosure: I'm an i4a client]