As I am starting an exciting project for a small business, I reflected on the steps I follow when initiating a project. One thing I observed is that this process gets more refined as I take on more tasks, and I also pay more attention to having a well-organised plan in place. This helps both me and the client to have a clear timeline and defined expectations.

1. Gathering requirements for the project

The first step I take is to understand the overall task and the client’s requirements. This is more of a discovery session where I attempt to find out some of the most important aspects of the desired website. For example, for my current project, I learnt that it's important for the client to manage the site and its content independently to some extent. Insights like this often guide my decision on the tech stack I might use.

After this session, I am able to create a functionality report that provides a clear overview of the project. I then like to reiterate this with the client and dive deeper into more details during a follow-up conversation. During this meeting, I also ask questions about the design or receive it in case it is available. In my situation, I am collaborating with the owner to help develop the design. Once the design is finalised I gather all the necessary resources for the website such as images, vectors, and copy.

2. Deciding on the tech stack

Once I gather all the necessary information about the website’s features and functionalities, I like to outline various tech stack options. I then give a short pros/cons presentation to the client, along with my advice for the best approach to take. Next comes the decision on the hosting platform and a conversation about any paid third-party libraries or tools that the front-end might be consuming. This varies depending on the website’s specific functionalities, and the client needs to be aware of any additional costs.

Since my current client wants to be able to manage the website, I also introduced my recommended content management system when I was presenting the tech stack options. This helps clarify the overall vision, including how it will be possible to manage orders, products, and pages.

3. Creating a timeline, setting goals, and developing a plan

The third step in my process is to create a detailed timeline, set goals for the project, and develop a plan. This involves breaking down the project into manageable parts. A well-organised plan keeps both me and the client on track and ensures efficient progress throughout the project.

4. Development, testing, and client review

My next step is development itself. By this phase, all the third-party tools, design choices, and assets have been decided on. During this stage, I set up the development environment, after which I implement back-end and front-end functionalities by focusing on modular, reusable elements. I also implement all the features discussed previously with the client.

Once the website is completed I conduct thorough testing including functionality, usability, and compatibility across browsers and devices. In case any bugs are identified during the testing phase I fix those, after which, I present the website to the client. Following the client review session, I make any necessary adjustments based on the feedback received.

5. Deployment and maintenance

The last step I take is to prepare for launch by finalising all content and settings and then deploying the website to the live server. I like to do a few more tests once the website is live. My final activities include training the client on how to manage the website and offering ongoing maintenance and support for post-launch issues.

I found that this approach helps lead to a successful outcome, and that communication is more effective throughout the process. What are some of the steps you follow when starting a project from scratch? I would love to find out and learn from a different perspective.