Edgar Allan is a decidedly anti-silo shop, and the way we approach system design is no different.
We involve everyone, from system architects to UX designers and developers, in discussing and devising solutions. Once we understand your needs and expectations, we hit the ground running and collaborate fiercely to deliver.
As far as our process is concerned, it looks like this:
- Identify
Before we start cooking, we take our time prepping. This stage is all about collecting insights and requirements to understand what the system needs to do, who will be using it, and what they expect from it before we start designing.
- Outline
Here’s where we start putting ideas down on paper and drawing a basic sketch of how the system could look. We consider various angles and consult multiple perspectives to ensure we hit the mark.
- Define
This is where the bulk of the work starts. We focus on all the key parts of your system and figure out how they’ll function and communicate with each other in practice.
- Consider
Teams often get bogged down by focusing only on a site’s functional requirements. We do expend lots of effort here, but also make time for the non-functional elements that add more to the overall experience. For example, elements like security and scalability are considerations we make at this stage of a project.
- Iterate
Testing and tweaking are ingrained into our process at EA. Here’s where we make changes based on your feedback and that of our team and consider anything we might have missed with the earlier versions of what we’re working on.
.jpg)
.png)
