gdevore
Software Documentation Without Screenshots Stinks [video]
Video - What if your GPS was as chatty as most software documentation?
3 Steps to Killing It as an Exhibitor at Dreamforce
Clarify Expands Screenshots Into Tutorials
Why You Shouldn’t Put Software Documentation In Your User Forums
3 Reasons HubSpot Users Should Be Excited About the Performable Acquisition
Screencasts vs. ScreenSteps vs. Single Image Capture
Are You Communicating or Just Writing?
Technically, they had the feature but the feature didn't help the doctors be better doctors. Features don't automatically translate to outcomes.
It’s Not What Your Software Does, It’s What People Do With Your Software
“Build It and They Will Come” Is Not a Software Documentation Strategy
Creating Screencasts: 2 Minutes is too Long
Moving Beyond Customer Support: Focusing on Customer Success
Chargify isn't blaming their customers for incorrect assumptions, but their customers are feeling the effects of their incorrect assumptions.
With the way things are now at Chargify it costs more to maintain/support a current customer than that customer generates in revenue. You can afford to grandfather old accounts if you can still at least break even on those accounts. If you can't then you have to do something like what Chargify did or your business will cease to exist. The key is to do all that you can to not put yourself in the position that your support costs are so high that you can't be profitable on existing customers.
I blogged more about it here:
http://www.bluemangolearning.com/blog/2010/10/building-scala...
Building Scalable Support – Lessons Learned From the Chargify Price Increase
Regardless though, this was a bad way to handle the price increase.
Or, here is another example site we set up:
Very simple to use and very effective. You can read a case study here:
http://www.bluemangolearning.com/screensteps/case_studies/se...