This is the requirements-gathering phase, where we identify what the client organization wants to achieve, which leads naturally to understanding your users and their needs. These key elements of requirements are then fleshed out with technical analyses of integrations with legacy systems, support capabilities, and many other boundary-condition parameters. The efforts in discovery lie in the “problem space,” where we are focused on the problems that need to be solved, we do not yet look at solutions. Researchers and user experience experts lead the effort in discovery.
This is the phase where we enter the “solution space,” where we look at how we can meet the organizational objectives and user needs that are defined in the discovery phase. Designers and system architects take the lead in design. This is when we finalize the features and functionality needed, the technical architecture of the solution. This is also where we provide a visual design concept and user workflows that will define the user experience on the website.
This is the phase where the developers take over and start building the underlying infrastructure, the platform on which all else rests. They build the features and functionality as specified in the technical specifications from discovery. Front-end developers implement the design concepts and user interface created in the design phase. Our software development life cycle is mature, hardened, and secure. We use industry-standard continuous integration, static code analysis, and modern DevOps principles to build and secure code.
Once all the code is complete, the IT group takes the fore and leads the deployment process. Our expertise in DevOps and Infrastructure-as-Code enables us to make the challenging task of deploying a complex website manageable and eliminates downtime for users. The automation we leverage to deploy code also follows the best practice of planning for failure and creating environments that scale, self-heal, and are secure. We limit human interaction with production environments to simply lessen the errors that can be introduced.
While the name may sound a bit frivolous at first, the delight phase is extremely important for any website that is interested in attracting, engaging and retaining customers who exist in a continuously evolving web-enabled world. This is the phase where the KPIs identified back in the discovery phase, incorporated into the design, and developed into the code should be monitored. Whether it is monitoring page views to determine user interest, performing A/B tests to optimize interfaces, or tracking conversion funnels, monitoring is the best way to ensure you are keeping your users happy. Of course, monitoring is only as effective as the insights gained from monitoring are put into practice.