Summer 2016 — Sealing the collaborative deal
When Äventyret first met Chef they were looking for a digital partner rather than a new website. However, they also had a handful of bug fixes that had to be fixed for the interface of their site at the time, but the main ideas were around new functionality. We initially chose to address the needs of Chef in the following order:
- Fixing interface bugs in the website at the time
- Develop new strategies and concepts in collaboration with Chef
However, after loading/submitting the old site, we added plans. The project Website Bug Fix needed to grow in order to address the following needs:
- Greater editorial freedom for Chef to administer its own website
- Implementation of low-hanging fruit for conversion and user personalization
- A refresh of the design and style
- A module-based interface (to facilitate rapid iterations and implementations of future functions)
- Code releases and a well-thought out work flow for developers
- Better performance
No one wanted to divide the work into two phases any longer (bug fix and concept/strategy work) as we initially thought. Instead, it was reasonable to collaborate on development and concept work in a series of projects and iterations, where the launch of the new Chef.se website was the first in line.
Fall 2016 — Free range vision
Äventyret and Chef used the fall season to draw up and plan the Chef.se of the future. Chef had many clear ideas and questions about new features. Äventyret placed no restrictions on the work so that it would be able to build in a first launch. Instead, we placed value on understanding what would be reasonable in two-three iterations, irrespective of budget and initial aspects of time. There were several advantages to this:
- Some features were taking advantage of other features from the perspective of implementation. If several features required similar solutions, we may choose to add features earlier or postpone the addition of related features.
- This would make it possible to plan sub-projects, versions and iterations.
- The project gets a clear visionary direction, irrespective of whether all means are in place to implement all ideas at once. The first iterations of a product or service are the most important, as these form the foundations. Some extra time must be taken, while the smartest features can spice up the foundation work later. But keeping the buzz alive in the work group required the vision of the full product from the start.