![]() ![]() If I get a customer who's confused, I simply rev up my ScreenSteps and in 10 minutes that customer has a clear idea of what to do next.” - Sean D'Souza, With Screensteps it was, and has always been a breeze. Then format them, and before I knew it 45 minutes had passed. Normally I'd have to take screenshots then put them in some word-based application. I was able to write documentation in a matter of 10 minutes or less. “I didn't think I needed "yet another screen capture" application.What surprised me was that ScreenSteps was completely different.But getting in the door $2500/yr for small business doesn't work. I don't even need to integrate it so much into web sites, just want to use it to make documentation that is simple, consistent, fast, concise and easy to update/modify. Pricing Could we get a $300 version with 5 contributors? I mean, I could probably sell it to a whole company based on using the software to make awesome, quick documentation and then have different departments ask me what I use and then teaching them to use screensteps. Screensteps put me on steroids and I was able to use just one program instead of three and maintain consistency throughout documentation and created documents that were clear to both end users or other IT people for the back end tasks that I had to learn for the first time on a daily basis - I had confidence that I could use my own screensteps instructions to give to others or re-read when I forgot the 20 steps it took to get adobe enterprise integrated into the active directory domain! CONS Just so you know, I'm super quick with screenshots (Windows shift + S), paste to mspaint, markup image, copy/paste to word doc. ![]() I could put together complicated documentation for processes complete with screenshots, consistent numbering of steps, easy to use inserts of images, text, number bubbles. Once set up, it works great, works fast, love it, wish I could afford it for my current company, I'd buy it in a heartbeat! Some parts are technical and difficult in initial setup, the support is good though, definitely need an IT person doing the set up. I'd never bother with the desktop application again. I wish there were an integration that would allow me to use SnagIt to capture screenshots and insert them directly into the web-based editor. It does have a built-in screen capture tool, but the capture options are limited compared to tools like SnagIt. ![]() ScreenSteps' desktop application is a little buggy and feels outdated, even if it's not. When major changes happen, such a big update to a software's UI, this can mean updating thousands of screenshots across hundreds of articles - with no easy/efficient means to do so. CONSīecause it's so easy to create ScreenSteps articles, and because articles are written in bite-sized pieces, you can quickly end up with hundreds of pages of content that need to be maintained. ScreenSteps works equally well in both situations, for both products. Two of these products require very different site settings (one is open to the public, the other is private and for customers only) and are developed by very different teams with very different communication styles. As my company's sole technical communicator, I run multiple ScreenSteps sites for different products. ScreenSteps is also loaded with useful features that can be flexibly incorporated into a team's documentation process. Other than the amazing customer support? ScreenSteps does exactly what it says it does - it enables teams to write beautiful, professional-looking online help documentation, FAST. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |