blob: 60c87e4e96c16c5c3fb71617f5a061f7b4432952 [file] [log] [blame]
<html>
<head>
<meta HTTP-EQUIV=CONTENT-TYPE CONTENT="text/html; charset=utf-8">
<title>Features &amp; Benefits</title>
</head>
<body text=#000000 bgcolor=#FFFFFF link=#0000CC vlink=#000080 alink=#0000CC>
<center>
<a href="index.html"><img src="first1.gif" border=0 alt="First page"></a> <a href="img4.html"><img src="prev1.gif" border=0 alt="Back"></a> <a href="img6.html"><img src="next1.gif" border=0 alt="Continue"></a> <a href="img25.html"><img src="last1.gif" border=0 alt="Last page"></a> <a href="text5.html"><img src="text.gif" border=0 alt="Text"></a></center><br>
<center><img src="img5.gif"></center>
<p><h3>Notes:</h3><br>
Features and Benefits is a key marketing concept. <br>
<br>
In the Community we are often pre-occupied with product features - will this particular 'feature' make its way into the next release.<br>
<br>
From a user's perspective, a 'feature' has to pass the 'so what' test before it brings them any benefit:<br>
<br>
Feature: OpenOffice.org has an open-source licence<br>
<i>So What?</i><br>
Benefit: you can give it away to other people<br>
<br>
<br>
</body>
</html>