title: We made it reliable. What's next? Usability?
body: <p>I'm working in a small development group. We are building and improving our product.</p>
  
  <p>Half a year ago we couldn't think about higher characteristics, such as usability, because we had so many problems with our product. Many bugs, high technical debt, low performance and other problems kept us from being able to focus on usability.</p>
  
  <p>With time we've improved our process substantially. What we've done:</p>
  
  <ul>
  <li>Real Agile iterations</li>
  <li>Continuous integration</li>
  <li>Testing(unit-tests, functional Smoke tests, performance)</li>
  <li>Code quality is 'good'</li>
  <li>Painless deployment process</li>
  </ul>
  
  <p>So we are now producing stable, reliable releases. The following quote (paraphrased) describes our current situation:</p>
  
  <blockquote>
    <p>first - make it work; after that, make it reliable; after that, make it usable</p>
  </blockquote>
  
  <p>We are geeks, so we can't 'make' a great UI by ourselves.
  So what should we do? What direction can you recommend?
  Maybe we should hire Usability experts part-time or full-time?
  How can we explain the importance of Usability to our stakeholders?
  How do we convince them that this is useful?</p>