BigBadCollab

Process

I’m sure you already know this, but process is king. One of the first conversations we had as a company was around process creation. It is what makes or breaks a company. It is what makes a client love or hate the project. There is power in process.

That said, we believe that the process we follow has been crucial to the success of the projects we have been a privileged to be a part of. We have spent time in conversation and collaboration around how to successfully manage a project and have even been given the opportunity to speak on the subject.

How we manage and run projects is outlined below. We have even created a few other pages for the vision/discovery step and the process path to further explain how a successful collaborative project works.

1. Vision Discovery and Planning – This is by far the most important part of the process. This is where we sit down and soak in your vision like a sponge. No, like a ShamWow. We’re like a ShamWow with how much we absorb. We share our hearts, listen and find out the path for the project. After everyone has shared and we have done a significant amount of white boarding, we talk about next steps and build a defined project path.

2. Architecture and Design – In this step we build out the architecture of the project. Without a plan you can’t build anything around it, kinda like building a house. After the architecture has been built and approved we move into the design step. This is where we flex our User Interface and Typography muscles on top of the developed site architecture.

3. Experience and Development – This phase is where we get down to the nitty gritty of how your business processes integrate into the application that will be built based on the architecture and design. Once everyone has a clear picture of the final product it is built with love.

4. Testing and Launch – In this step we work on private and public testing of the product and all of the processes that go with ensuring that the final product aligns with the vision. Once the project is completed we work to market the product through many public and grassroots efforts. We then finally define the new brand or translate the impact on the brand that the new product has.

5. On-going Support – This can apply to multiple facets of support. Things like little bugs/issues all the way to new functionality development based on user response. The point is that once we finish the work we hang around. We don’t launch anything that we are not proud to be a part of.