Re: "use-case based documentation"

Subject: Re: "use-case based documentation"
From: Keith Hood <klhra -at- yahoo -dot- com>
To: Margaret Cekis <Margaret -dot- Cekis -at- comcast -dot- net>, 'Julie Stickler' <jstickler -at- gmail -dot- com>, 'Technical Writing' <techwr-l -at- lists -dot- techwr-l -dot- com>
Date: Thu, 5 Feb 2015 18:33:22 +0000 (UTC)

Since we don't have use cases, design documents, or even what I'd call
proper user stories..."
Ye gods and devils, how the bleep do the developers work? Post-it notes on top of a whiteboard diagram? (I've actually seen that. The entire design guidance was a flow chart drawn on the wall, and whenever someone thought of some nuance, they'd either write something under a node or they'd stick written notes to the diagram. As you can probably guess, documentation was not a high priority with that bunch.)

On Thursday, February 5, 2015 12:10 PM, Margaret Cekis <Margaret -dot- Cekis -at- comcast -dot- net> wrote:

Use cases alone are not sufficient to necessarily build a robust product. I
worked for a tech startup that was building an internet platform for a TV
commercial marketplace. After two years work based on very detailed use
cases and personas for advertisers, and network, and TV station salespeople,
they had a product that looked great and impressed everyone. However, it
broke down whenever a low transaction threshold (about a dozen simultaneous
transactions) was exceeded. They then went back to the drawing board and
created the specifications to handle a much higher volume (like thousands)
of simultaneous transactions, and rebuilt a much more robust system.
Margaret Cekis, Johns Creek GA

Doc-To-Help: The Quickest Way to Author and Publish Online Help, Policy & Procedure Guides, eBooks, and more using Microsoft Word |


You are currently subscribed to TECHWR-L as archive -at- web -dot- techwr-l -dot- com -dot-

To unsubscribe send a blank email to
techwr-l-leave -at- lists -dot- techwr-l -dot- com

Send administrative questions to admin -at- techwr-l -dot- com -dot- Visit for more resources and info.

Looking for articles on Technical Communications? Head over to our online magazine at

Looking for the archived Techwr-l email discussions? Search our public email archives @


RE: "use-case based documentation": From: Margaret Cekis

Previous by Author: Re: "use-case based documentation"
Next by Author: Re: "turn on" vs. "power on" vs. "power up", and their opposites ?
Previous by Thread: RE: "use-case based documentation"
Next by Thread: Re: "use-case based documentation"

What this post helpful? Share it with friends and colleagues:

Sponsored Ads