Project management has quickly become an issue at Digidop. Here is how we have learned to pilot, structure and manage our different Webflow projects with our customers. At the heart of this project management: define the stakes, centralize the data, manage the deadlines, communicate well.
Project management is a strategic aspect for any type of company. It is a means of ensuring a quality service, which respects the deadlines, the stakes, and all the constraints of the project. From scoping, design, management, closure and monitoring, each stage ensures that the project runs smoothly and achieves the set objectives.
At Digidop, we have put in place many processes allowing us to respond to each issue of the web projects we realize. Here is how we structure, manage and communicate with our customers, at each step of the Webflow projects.
Define the issues of the Webflow project
For all the web projects we carry out, we start by understanding and defining the issues. This phase is essential to start mapping the project, including the different actors, or defining the deadlines. A "web project" is a rather vague term, where many actors may be involved.
For example, if you need a website, you could simply come with a Figma or Sketch model, and Florian Webflow expert would simply have to take care of the Webflow development. But you could also need Digidop to integrate an SEO strategy to the project, and in that case we would call Thibaut Legrand SEO & Webflow expert. Without a mockup or with a need to redesign your graphic charter, Mérieux UX/UI expert designer would need to participate to the first calls to start the graphic audit. Finally if you want to connect tools like Hubspot, Zapier, or 360 Learining or any other no-code tools, it would be up to Thomas, automation expert, to look at your workflow.
In addition to defining the various players, this phase also allows us to establish precise specifications and a global and effective web strategy.
Centralise the project and the data
The data we need to share with each other for each project is as numerous as it is varied. To limit the back and forth and optimise the launch of the web project, we decided to centralise all this data on a Coda space. Via a "Pre-Project Checklist" that they find on this platform, our clients can share with us all the elements we need before starting:
- Graphic charter
- Visuals
- Competitors
- Partners
- SEO queries
- Identifiers
- etc.
A first phase methodologically designed for all future steps: graphic audit, wireframe and Figma model, Webflow development, SEO strategy, site automation, training.
Managing deadlines
Time management is an essential aspect of every project, and we feel it all the more so for web projects. Our priority is to ensure that our clients are satisfied, and the UX and UI phases sometimes require several round trips. The first thing we need to do to make sure we don't miss any deadlines is to have a clear timeline. This way, each party knows what role it has to play and within what timeframe. We set this timeline at the beginning of the project and make sure we stay as close as possible to the deadlines set at the start. We leave it visible from the Coda space, and make it evolve via a check-box system at each validated stage.
Provide visibility to all parties in real time
We work with our clients keyboard and mouse! No secret, transparency above all, to make sure we move forward together and in the right direction. Beyond the recurring points we make with our clients, we give them live access to all the stages of the project. At Digidop, we consider that customer autonomy is precious. Our customers can therefore access their site from the design phase, until the launch.
Access to the graphic charter
Our customers' graphic charts are accessible from their Coda space, via an access link or via a download button. Once created, we send it to you in PDF format, but you can also come and get it at any time on Coda.
Access to the Figma UX wireframe
As soon as the UX phase is launched, our customers have access to their Figma on their Coda space. They can either see a simple preview or go into the details of the Figma.
Access to the Figma UI model
Just like the wireframe, the Figma UI model is accessible at any time on our clients' Coda space. You can leave us comments on the Figma mockup or on the Coda at any time. The idea is to be able to give us feedback at any time during the service, in addition to our recurring points.
Access to the Webflow site under development
When we launch the Webflow development phase, we give you instant access to your site. Don't worry, the site will be published on your real domain name the day of the launch. In the meantime, you will have access to it from a link such as "domain.webflow.io". You will be able to follow the development progress and start filling in your site via the editor mode.
Communicating with our customers
Communication is a major issue in a web project, and we put it at the heart of our project management. To make communication with our clients, teams and other service providers effective, we pay attention to several things.
The frequency of exchanges
The frequency of the exchanges will vary according to the project and needs, but in all cases we define it before the project. The idea is to be able to give a coherent rhythm to the project, by setting recurring points. These points allow us to have the validation of our clients in order to progress step by step. This is what it could look like:
- Step 1 - first draft of UX model
- 3 days
- Point 1 - UX challenge
- 3 days
- Point 2 - UX validation revisited
- Step 2 - launch of the UI model
- etc.
Indirect communication
Indirect communication refers to all exchanges that do not take place simultaneously. For example, when a client wishes to send us feedback or a document at a time that was not planned. For this, there is of course email, but it is far from being the most suitable tool for web projects. We therefore use several levers, each of which depends on the message to be conveyed. For example, if a client wants to send us feedback on their web model. They will have the choice of leaving us a message on our Coda, to give us their general opinion on the design. But they can also enter the Figma to add a more targeted comment, on a page or a section for example.
The idea is therefore to choose the appropriate medium according to the message he wishes to convey. In addition, it is important to make this message accessible to everyone, and in a strategic place.
The communication tool
Everyone has their own habits and communication tools. At Digidop, we work with the most used tools to adapt to all our customers.
Main day-to-day communication channels :
- Slack
Main communication channels for meetings:
- Google Meet
- Teams
- Slack
- Zoom
The history of the exchanges
Every tool we use allows us to keep a history of our exchanges. This is an essential aspect, especially when we move from one phase of the project to another with different actors. For example, even if Florian recovers a Figma model for the Webflow development phase, he will be able to take into consideration the comments of this model to better understand the issues of each page and each section.
