Here at Atomic Object we have a strong culture of sharing the benefits of our success with each other – in many ways far more generously than is common in our industry. Of course, coupled to these rewards is an equally emphasized sense of responsibilities – not the least of these is our commitment to the value and success of our blog.
A lot of what sets Atomic Object apart is our people – we work very hard to ensure we hire the best. But hiring great people isn’t enough. The best people need to be set up in an environment where they can use their skills effectively and translate their excellence into business value. Atomic’s strategy of deploying poly-skilled, co-located teams of generalists puts us in a position of delivering quality to every customer every time.
At Atomic Object we want to build products people love to use. To that end we have integrated design into our practice in a holistic way. In this article I will present our understanding of design as a concept and a discipline and give some practical insight into how design works on projects here at Atomic Object.
Atomic grew from a rich computer science culture that focused on coding and project management practices. Before we hired and integrated designers directly into our agile teams, we used to work with outside design partners.