Project management is a strategic aspect for any type of business. It is a means to ensure a quality delivery that respects deadlines, challenges, and all project constraints. From framing and design to execution, closure, and follow-up, each step ensures the smooth progress of the project to meet the established objectives.
At Digidop, we have implemented numerous processes that allow us to address every challenge presented by the web projects we undertake. Here is how we structure, manage, and communicate with our clients at every stage of Webflow projects.
Defining the Challenges of the Webflow Project
For all the web projects we execute, we start by thoroughly understanding and defining the challenges. This phase is crucial to begin mapping the project, including various stakeholders, and defining deadlines. The term “web project” is quite vague and can involve many stakeholders.
For instance, if you need a website, you might simply come with a Figma or Sketch mockup, and Florian, a Webflow expert, would just take care of the Webflow development. However, you may also require Digidop to integrate an SEO strategy into the project, in which case we would call on Thibaut Legrand, SEO & Webflow expert. Without a mockup or if a redesign of your graphic charter is needed, Pierre, an UX/UI design expert, would need to participate in the initial calls to begin the graphic audit. Finally, if you wish to connect tools like Hubspot, Zapier, or 360 Learning, or any no-code tools, it would be up to Thomas, an automation expert, to look into your workflows.
Beyond defining the various stakeholders, this phase also allows us to establish a precise specifications document and an overall effective web strategy.
Centralize the Project and Data
The data we need to share for each project is numerous and varied. To limit back-and-forth and optimize the launch of the web project, we decided to centralize all this data on a Coda space. Through a "Pre-project Checklist" available on this platform, our clients can share all the elements we need before starting:
- Graphic charter
- Visuals
- Competitors
- Partners
- SEO queries
- Credentials
- etc.
This first phase is methodically designed for all future steps: graphic audit, wireframing, Figma mockup, Webflow development, SEO strategy, site automation, training.
Manage Deadlines
Time management is a vital aspect of every project, and we feel this even more with web projects. Our priority is to make sure our clients are satisfied, and the UX and UI phases sometimes require several back-and-forth discussions. To ensure we do not miss deadlines, the first requirement is an accurate timeline. As such, each party knows their role and the timeframes involved. We set this timeline at the beginning of the project and strive to stay as close to the initially set deadlines as possible. We keep it visible within the Coda space and update it through a checkbox system at each validated step.
Provide Real-Time Visibility to All Parties
We work hand in hand with our clients! No secrets, transparency is key to ensure we move forward together in the right direction. Beyond regular check-ins we have with our clients, we provide them with direct access to all stages of the project. At Digidop, we believe that client autonomy is invaluable. Therefore, our clients can access their site from the design phase all the way to the go-live.
Access to the Graphic Charter
Our clients' graphic charters are accessible from their Coda space via a direct link or a download button. Once completed, we send it to you in PDF format, but you can also retrieve it at any time from Coda.
Access to the UX Figma Wireframe
From the launch of the UX phase, our clients have access to their Figma on their Coda space. They can either see a simple overview or delve into the details of the Figma.
Access to the UI Figma Mockup
Just like the wireframe, the UI Figma mockup is accessible at any time on our clients' Coda space. You can leave us comments on the Figma mockup or on Coda at any time. The idea is to provide feedback at any stage of the service, in addition to our regular check-ins.
Access to the Developing Webflow Site
When we launch the Webflow development phase, we immediately grant you access to your site. Rest assured, the site will be published on your actual domain name on launch day. In the meantime, you can access it via a link formatted as "domain.webflow.io". This way, you can follow the development progress and start populating your site through the editor mode.
Communicating with Our Clients
Communication is a major challenge in a web project, and we place it at the heart of our project management. To make communication effective with our clients, teams, and other service providers, we pay attention to several factors.
Frequency of Exchanges
The frequency of exchanges will vary depending on the projects and needs, but in all cases, we define it before the project. The idea is to create a coherent rhythm for the project by setting recurring meetings. These meetings allow us to gain our clients' validation to move forward step by step. Here is what that could look like:
- Step 1 - first draft of UX mockup
- 3 days
- Point 1 - UX challenge
- 3 days
- Point 2 - revised UX approval
- Step 2 - launch of the UI mockup
- etc.
Indirect Communication
By indirect communication, we mean all exchanges that do not occur simultaneously. For example, when a client wishes to provide feedback or send a document at an unplanned moment. For this, of course, there are emails, but this is far from being the most suitable tool for web projects. Therefore, we use several channels that depend on the message to be conveyed. For instance, if a client wishes to give feedback on their web mockup, they can leave a general message on our Coda to share their overall opinion. But they can also dive into Figma to add a more targeted comment on a page or section.
The idea is to choose the appropriate medium based on the message they want to convey. Additionally, we ensure that this message is accessible by everyone and located in a strategic place.
Communication Tools
Everyone has their own habits regarding communication tools. At Digidop, we work with the most commonly used tools to adapt to all our clients.
Main channels of daily communication:
- Slack
Main channels of communication for meetings:
- Google Meet
- Teams
- Slack
- Zoom
History of Exchanges
Each tool we use allows us to keep a history of our exchanges. This is an essential aspect, especially when moving from one phase to another of the project with different stakeholders. For example, even if Florian is taking over a Figma mockup for the Webflow development phase, he will be able to consider the feedback on that mockup to better understand the challenges of each page and section.
