There are two parts to a web project: doing the work, and determining what the work is going to be in the first place. We take both parts very seriously, which is why we dedicate the beginning of our projects to a detailed discovery process that helps us iteratively scope a technical plan — both so we have a great idea of what we might be building, and our clients have a good understanding of how much each part might cost.
Recently, we worked with a nationwide healthcare members organization and their design partner to translate wireframes and site design into a technical plan — and did so in a way that kept surprises to a minimum. Each week, another section of the site would be scoped, providing an updated technical budget, a better understanding of how parts of the content model might interact with each other, and a healthy ongoing dialogue between all three main parties.
What this has resulted in is a smooth, no-nonsense project plan that moves from strategy to design to technical development without a hitch. Iterative scoping, detailed content modeling, and solid QA work have helped both Blend and its partners forge a strong relationship.
- A progressively scoped technical plan that outlined connections between content types
- A sprint-by-sprint look at current budget vs. future phases
- Product ownership to ensure that QA ran as a part of the process, rather than tacked on at the end
Creating a New Product: From User Flows to Prototypes
User flows helped us determine the best way to move users from one point to another, and prototypes helped confirm we were going in the right direction.
- Client: Obvious Foods
- Industry: Events and Commerce