Discovery is often the most overlooked and under appreciated phase of any project. The desire to see and interact with something tempts many to try to rush past or, even worse, skip this phase. The mistakes of such impulsiveness may not be immediately obvious until later in the project, when such things endanger the budget or the timeline more significantly. We take discovery seriously, by starting to answer questions that guide the project to a natural and clear conclusion.
It's easy to think of design as simply a pretty picture or window dressing, but it's actually much more important than that. True, at the surface, it may be representing the technology behind it, such as in a button or a link, however, if we dig deeper and offer a more thoughtful design in our digital products it can be much more significant and impactful. Great design does not happen by accident and while the tangibility of its value may not be easily communicated, it is easily recognized as lacking when the uninitiated try to put something up that "just looks good".
Development is frequently quantified by how well things work. Like anything, if it works well, it should, in some sense, go unnoticed by the user. Bad development impedes ease of use and is easy to spot. We strive to develop simplistic and efficient code that anticipates your expectations and works with you, whatever the task may be. The technology itself is secondary and therefore has no place in the discussion of the digital project. We will never pitch a particular technology or platform. To do so is to serve technology, which is, not surprising, a horrible way to build something that is meant to serve us.
Deployment is the stage where all of the details get checked, rechecked then checked again, so it should come as no surprise that the tasks could seem to be a bit laborious and would therefore tempt some to skip past the process entirely. No thank you - we'd like to test and test again if we could please, thank you very much. We make sure all of our projects have the proper amount of time for testing and we reject the idea that testing has to come once and only at the end of a project. We engage testers early and often. There is a continual feedback loop between you our testing audience and us - and that begins on day one of the project lifecycle.