Eight Steps in the Design ProcessFeasibility Study, Programming, Schematic Design, Design Development, Construction Documentation, Bidding and Negotiation, Construction Management, Post-Occupancy Training. Organizations have a need to communicate to stakeholders their positions on issues and make their products and services known to the public. Often, the need for communication, such as a website, is triggered by a change in strategic direction or a new offering. Identifying the reasons for the existence of the site and what it is supposed to achieve is the first step in the process.
The goals and objectives that are set at the start of the project inform all future decisions, from the structure of the site and the naming conventions used in navigation to the visual design of the site. The first step in the definition process is to interview the organization's stakeholders to identify the strategic objectives of the site, understand the key needs of the audience, and identify key competitors. The goal of the definition step is to identify three measurable key outcomes that are directly related to the organization's strategic objectives. The challenge in this step is to limit the number of goals.
Most organizations will have more goals than they know what to do, and each department believes that the goals of their individual unit are the most important. Being able to focus attention on the objectives of the organization will facilitate the development of the site and make the final product more effective. Before launching the site, it will be placed on a production server where only internal audiences and anyone you share the link with can see it. Site testing is critical, as there will inevitably be issues that need to be addressed before the site goes live.
There is nothing that erodes a brand more than a site that is not working properly or that has spelling errors or broken design elements. At this stage, it will be necessary to check the site on various browsers (Firefox, Safari, Internet Explorer) and on various devices (laptops, tablets and mobile devices) to see if and where interruptions occur. You've tested the site, the project stakeholders have reviewed and approved it, and you're ready to launch it. But once the site is launched, the project is not finished, you should be prepared to respond to comments from users who are adapting to the new site.
Expect to make some immediate changes to the site, such as fixing broken links, editing text, and making adjustments. The Web is a fluid medium that changes daily, if not every hour, change is inevitable. At this point, discussions on risks, issues and change management are likely to be brief. Risks and problems will be further developed during the exploration and design phases of the project.
However, it must be analyzed in detail how risks and problems will be handled, as well as how change and change orders will be managed and executed in the project, and will be of great interest to the paying customer. The primary delivery of the exploration phase is the Business Requirements Document (BRD) and must require formal customer approval. Without that approval, the project manager could be pursuing scope issues for the duration of the engagement. In my opinion, and generally, as a general practice for external client projects, each unique delivery of each project must receive formal approval from the customer.
The BRD release of this phase is the document that lays the foundation for the creation of the Functional Design Document (FDD) or the Functional Requirements Document (FRD), depending on what you want to call it, which is the main delivery for the next phase of the project, the design phase. It is worth noting here that in projects that are smaller or with very tight deadlines, the exploration phase and the design phase can be compacted into a combined phase. I usually refer to this combined phase as the design phase. I don't recommend it if you can avoid it, as separating the phases allows you to dig deeper into your business requirements and gives you a better opportunity to devote yourself to design with a common understanding of what requirements your system will meet.
However, it's not always possible, so it's a good opportunity to make up some time for critical development and testing phases if the deadline is tight. Once the exploration phase, marked by the customer's official approval of the Business Requirements Document (BRD), is complete, the design phase is ready to begin. If your project has the luxury of dividing Exploration and Design into two separate phases, do so of course. Few projects suffer from additional planning and requirements analysis in advance.
However, as I mentioned in my post on the exploration phase, these two phases can be combined by compacting the project timeline or budget, and this combination of phases can allow the delivery team more time available for the development and testing phases. At the close of the design phase, the team members who will support the development effort in the next phase should be identified and incorporated. The FDD will serve as a basis for catching up with the project requirements and what they will be working on during their development effort. A technical design document (TDD) is a documented outcome of the development phase.
May or may not be an actual delivery to the customer. If it is, it's actually for documentation purposes only; it should NOT require formal approval, as it is actually a documented representation of the “as-built” solution. This can facilitate future changes to the system by the original vendor, the customer or an external vendor, or it can be a document that assists the customer during future upgrades. Either way, it's good to have it and it's up to you or whoever you tell if you give it to the customer.
22.7% of respondents mention that not having enough time is their biggest problem with the design thinking process. Ideally, the customer has performed some process analysis and requirement analysis on their own prior to the start of this phase of the project. Several stages of the design process (and even earlier) can involve a significant amount of time spent locating information and research. The goal of the design phase is to successfully complete and sign its only core product: the Functional Design Document (FDD).
However, this is where you can tell the customer how you, as a PM, will carry out the project, how each phase will happen, and what the expectations and deliverables are for each phase when it comes to this specific project. I will apply this to a situation that happened to my car this weekend and show how I used the Engineering Design Process to fix my car. With the approved designs, it's time to develop the layout of the pages, develop new content and refine the old content, create videos, slideshows, podcasts and other media that will appear on the site, as well as start building the HTML and CSS of the site. But expert designers know that the success of a web design is not determined by code, social media integration, or cool images.
This process allows the designer to move from identifying a design opportunity to testing and evaluating a solution. The facts and insights you gain during the research phase inform each subsequent part of the design process. The key difference between the engineering process and the scientific process is that the engineering process focuses on design, creativity and innovation, while the scientific process emphasizes discovery (observation). Design requirements control the design of the product or process being developed, throughout the engineering design process.
The design phase still consists mainly of the project manager and the business analyst on the delivery team side. . .