We’re often asked about our methodology; we prefer to think of it as a way of thinking.
Customer happiness is putting the user first.
We approach our development in an agile fashion, focusing on customer and user feedback and involvement, user interfaces, and user interaction, captured in the form of user stories and workflows. Development follows definition of what the user wants. Simply stated, we put the user first, and we don't consider a project successful until you do, which we think is when your users do.
We're not trying to be simplistic about this. We've been there. We have team members who've done project management for Fortune 50 companies, led and operated initiatives under ISO X/CMMI/ITIL/more standards, managed and performed user-based contextual inquiry and uncovery/discovery, studied project management (PM) formally in college and via PMP (a candle's flame to the sun, considering the sun to be experience), and have used most PM tools out there, even having created some of our own, including a Kanban board and a "pure" PM, process-driven system.
What doesn't good communication and accurately-focused action solve?
We think a project's success is directly proportional to the amount of good communication and good action that take place. This means talking about money, the realities of the project, and what's working or not in an open, transparent manner. This means acting efficiently after asking good questions to define issues and next steps.