When SpringLocker founder Dan Milligan came to us with the idea for the site, we all generally understood what he was going for. It would be a site showcasing outdoor gear and trips. There would be different types of users able to do different types of things. Gear from other sites would need to be easily added to SpringLocker. Dan would need statistical reporting and be able to track affiliate relationships. The site would allow users to add items and people to their accounts. Emails would be automatically sent out from the system to admins and users. Great concepts…but how to execute? That’s where we came in.
Our job was to get the concepts broken down into deliverable components and to get specific about requirements and logic. So we organized our work into three buckets:
- Front-end Site Features/Components
- Back-end (Admin Only) Features/Components
- Behind-the-Scenes Programming Tasks
Each bucket contained detailed descriptions for every required function or feature.
Following our tried-and-true process, through iterative launches (phased development), we brought the programmed reality of Dan’s concepts to him piece by piece. He was able to play with the search functionality and course-correct development by requesting more filters and improved logic. He was able to go through the registration process for each of his user types and introduce new steps in the approval and review process. He reviewed preliminary statistical reports and provided us with a wish list of statistical information he wanted. Where possible, we suggested the money-saving option of leveraging Google Analytics via custom integration. Where it wasn’t possible, we developed standalone custom reports available in the SpringLocker admin. Each launch provided Dan the ability to interact with his site in a real way. His valuable feedback allowed us to tweak development until the site was fully realized.