On Mon, 18 Apr 2005 20:58:39 +0300, Miroslav Penchev <miroslavp@...>
wrote:

>
> P.S. In first few days of that discussion I have the idea that slogan
> must
> proof almost everything about the product, to tell at least 80% of
> features of Firebird. But now I am convinced that such slogan will be
> mistake. More important for product to gain market is to have a strong
> "10
> lines whitepapers" and useful 5 or 6 whitepaper each of 10-20 pages. That
> is not job for slogan. The right job to slogan is to have people to
> remember the product as name and to make them curious to read "10 lines
> whitepaper". If we say in slogan "Enterprise ready DBMS" or "Free
> Database" (or whatever else, heart from some different product) most of
> people will say "Oh, what. One more RDBMS, I have one, it is the same"
> and
> even they will not read "10 lines whitepaper" (which must be the
> strongest
> document of Firebird).
>

Another idea about the slogan.
What you say if we have a middle layer in "communication pyramid" - one
line between the true slogan and "10 lines whitepaper"? Something like
"sub-slogan".
When there is a capability to display text with different font sizes
(HTML, pictures) and there is enough room we will use both the slogan
(bigger font) and "sub-slogan" with much smaller font. In other places we
will use just the slogan (plain text messages, button captions an so on).
My idea is that the slogan should make people to remember our product and
to provoke them. The "sub-slogan" should tell them just a bit, and to
prevent them from confusing it about what is Firebird. If the sub-slogan
is 7-8 words it will be well placed under the slogan (which is 3 words for
example)

What do you think?

Cheers,
--
Miroslav Penchev