Our Process in 3 Words: Explore » Plan » Deliver
It sounds simple because it should be simple. Here’s the longer version:
You communicate your goals, we listen, ask questions, propose solutions, and plan the execution. We then develop, test and deploy a working product. But wait, great software is never done... After a celebration, the solution is reviewed and assessed, and together we propose and plan the next phase – an improvement, a new feature, or just anything that will consistently improve the outcome.
Still fuzzy on the details? Here’s a little more:
1 Explore
We start with an introduction to your company, your people, your methods and the problems that need to be solved. We research, listen, learn, and ask questions along the way. We become a part of your team, learning as much as we can about your business, your competition, and the way you work. We propose solutions to your current problem, but help frame solutions to problems you haven’t thought of yet. We identify other ways in which our expertise can increase efficiency, communication, and promote the core values of your brand.
2 Plan
Our solution is mapped out with proposal documents, user stories, wireframes, and design samples. We integrate the design with your existing brand or propose ways in which we might expand or refine the brand’s look and feel for the web. We determine the technical requirements and create user stories to go along with them. We ensure that all parties understand what we are building and delivering, and set the stage for development.
3 Deliver
The client and the developers are part of the process. Real people are part of the pool of users that test the product before delivery is accepted. Even after delivery, planning for the next phase of the solution may have already begun. The process is cyclical, with improvements and new features constantly under planning and development. This is how software avoids stasis, and how your workforce can stay ahead of the curve.
and Improve…
An initial project should consist of Minimal Marketable Features, or MMFs – that way, the project can have a launch date and a milestone. But that doesn’t mean we are done. Phase 1 should lead to Phase 2, and then Phase 3, etc… as new ideas surface and new procedures evolve. The work landscape is constantly changing, and the technology landscape changes as well. Why should your software stand still?
That’s a bit about what we do. Here are some of the folks we do it for:
Selected Clients
- Regis Corporation
- Westport CT Public Schools
- The Providence Plan
- First Data Corporation
- Odell Associates
- Bristol-Myers Squibb
- Firestone
- Hewlett Packard
- Johnson & Johnson
- PGAL Architects
- Ready 2 Learn Providence
- APC / Schneider Electric
- Choppahead
- Stackbin Corporation