While this process continually proves effective and efficient, we understand it may be adapted to fit the needs of each project, and in true agile fashion, we’re always open to improvements along the way.
Our design process is made up of three steps—workshop, site plan, and design.
The first step is a workshop, where the Amazee Labs team comes together with the client to discuss the project as a whole. This strategy session serves to identify and prioritize critical information for the design and development of the new site. This includes:
Requirements—what are the site’s basic needs, what are the must-haves?
Objectives, or goals—what will make the project a success?
Features—what specific functionalities are wanted or needed?
User stories—how the product can best serve the various users, or personas?
Stakeholders—specifically, who is our main point of contact, and who gives final approval?
Prioritizing what is most important to the success of the project is key to agile design and development. We will first deliver what is most important, and work down from there.
In this workshop, we also discuss administrative tasks like timelines, and the scrum process, that is, at what cadence work will be delivered and what stakeholders will be involved along the way.
We will also begin the visual design discussion to get a basic understanding of the desired look and feels of the website. Additional discussions may be needed later in the process.
2) Site Plan
In step two, Amazee Labs and the client agree to a general architecture for the site. Armed with the knowledge gained from the workshop, our team then develops a site plan. Typically, a designer, developer, and product owner will sit together and define information architecture, content types, and how the site works together as a whole.
We then present the site plan to the client, at which point it may go through a couple of rounds of revisions. Once we agree that we’ve satisfied requirements, objectives, features, user stories, and stakeholders, we move on to step three of the process—design.
We start with one piece of the puzzle, typically, the piece of highest priority. It goes through design first, and the others follow, in order of importance.
First, we wireframe. This defines what’s on the page, describes basic functionality, and order of importance. Just like with the site plan, we iterate with the client until approved.
Next, we user test. A prototype is built based on the wireframe. It’s as functional as we can make it so that users can actually click, scroll, and perform tasks. Based on the feedback we gather, changes will be made to the prototype until all parties are satisfied with its usability.
Finally, we design. This is where the site truly comes to life, complete with color, type, and fine-tuned layouts. We iterate with the client until approved, at which point this piece of the puzzle is handed to the development team.
We then grab the next piece and run it through the same process—wireframe, user test, design. We repeat this cycle until the site is designed in its entirety.
Our approach to design is significant for two reasons—
One, it keeps the design and the development team working on the project in tandem, which makes for a more considered end product. Secondly, it allows the client to be involved throughout the process, continuously reviewing and approving designs along the way.
An agile approach to design requires that all parties be involved in the process. At Amazee Labs, that’s how we like it. Everyone at the table equates to a better finished product.