How, after all, to write these damn cases?

Eternal story about "show portfolio." Familiar, yes?

Well, if your company - designers and other generators of beauty, saving the world. Cut the screenshots - and your client.

And if you are harsh coders, analytic bores and waving managers? Yes, even if the UX-designers - and they have the result of the work is usually not decorated at all with rhinestones and half consists of "many letters."
')
It remains to write cases. Sparkling and inspirational, yeah. I do not want, but it is necessary.

We internally met for two years. Finally gathered. We took on the task - and realized that it was rather laborious. So, it requires a systematic approach.

Well, then we will work on ourselves as a customer.
How would we solve this problem for the client?
Yes, as usual - would make a model of information expectations of a potential reader. And then they would look for ways to satisfy these expectations.

We will not rassusolivat long - this is it, this model.
As we like, in the format of a list of questions grouped by sections of the future ideal case.
Together with checkboxes “Important / not important” (column “Priority”) and expectations of what means to search for an answer (texts, screenshots or searches of the layout such as callouts, dies and other lists with large icons).



Everything seems to be quite clear and typical, familiar to our other content projects - but specifically in the matter of case preparation, it has not yet been tested.

So please ask questions. And specify that it is unclear.

You can also use our information model, of course.

In the meantime, we have not begun to write and design cases according to this scheme - several hypotheses about their relevance by potential readers.

1. There is a feeling that the Meaning is the most interesting section for a potential customer. Some kind of it ... relevant to the business, or something.
2. But colleagues, on the contrary, will be interested in either the “Process” section (people from the production), or “At the start” (sales managers).
3. Pictures, unfortunately, will still have to cut. Even if it is even possible to suck screenshots of documents out of your finger. Well, no way without beauty unearthly.
4. Failure cases - it's not scary. And even it will be useful to write about them (well, just not being carried away).

Gone to write letters, design pages, cut screenshots and test hypotheses.
For now - what do you think, what do you say, what will you advise?