What is a good software manual?

I wanted to tell so much, write so much, that you lose sight of the horizons, thoughts, and considerations.

It would probably be worthwhile to talk about the company and its projects, but this can quickly introduce the reader into sadness and longing. Therefore, the first thing we decided to start, ask for advice.

With the growth of the WELLtime project, our development team faced several questions. The developing software gave the ground for reorganizing the range of proposals, changing priorities between its modules and gave a lot of interesting ideas.
')
But it was one of the main expected activities.

We did not think we didn’t guess, and we didn’t expect that the product would expect a coordinated update of reference material from us.

Making a product is not easy, but writing a competent manual to it is no easier.
There were a lot of interesting ideas and rational proposals, but I would like to ask the habroles that for them is an indicator of a good software manual?