When and how do the different stakeholders of a digital project get involved?
I work on the creation and redesign of web and mobile applications, as well as software. I always work as part of a team. I collaborate with various stakeholders, and each one gets involved at a key moment in the project and in a specific order.
On some projects, I take on the role of project manager, while on others, I join already established teams.
To illustrate my point, I’ll use the example of creating a software application.
The different stakeholders
On each project, there are various stakeholders — at least six of them.
They are:
- The project manager
- The designer
- The front-end developer
- The back-end developer
- The client
- The target user
The project manager is like a conductor. They set the pace and ensure everything resonates correctly for the client and the users. They prevent chaos and make sure everyone plays their part perfectly.
The designer is responsible for identifying the users, their needs, and expectations. They work with the client to define the user journey and the software’s structure. They design the different screens (wireframes and mockups) and create the graphic universe, respecting the company’s branding when it exists.
The front-end developer handles the integration of the mockups. They take care of the visible part of the site.
The back-end developer manages the technical and functional aspects of the site. They handle database management. Their work is invisible to users navigating the website.
The client comes with a problem or a need, and the project team addresses it. They bring their industry expertise and validate the various project deliverables.
The user is the central figure of any project. After all, we are creating a product to meet their needs. It is therefore crucial to know, identify, and involve them in the project as early as possible. They will also participate in testing phases to provide feedback on inconsistencies, missing features, or even suggest functionalities that hadn’t been considered.
The order of involvement
Each project starts with a scoping phase.
This phase takes place between the client and the project manager. It helps define the project’s boundaries, the client’s needs, and their expectations. It also allows for the creation of a timeline, the estimation of the workload, and the identification of the people who will be involved in the project.
The designer comes into play during the scoping phase and remains involved until the end of the project. They gather the client’s needs, identify the user, their expectations, and their requirements. They design the user journey and the product’s structure in collaboration with the client and the project manager.
It’s beneficial to involve the developers during this phase as well. Thanks to their technical perspective, they can spot complex features that may require significant development time, potentially causing delays, or suggest postponing them to a V2 of the product.
Next, the designer creates the different screens, starting with wireframes (functional black-and-white mockups), followed by detailed visual mockups.
This two-step approach serves several purposes, notably allowing the client to first focus on the structure (the « what ») and then on the design (the « how »).
Once the wireframes are validated by the client, user testing is organized to ensure that the interface design truly meets the users’ needs.
Finally, development can begin.
The creation of the mockups happens in parallel with the development phase. This helps optimize the workflow and project timeline.
During the wireframing phase, it’s important to share and collaborate with other stakeholders.
For example, developers’ feedback is crucial to validate the technical feasibility of the proposed interfaces. Developers integrate all the mockups once they are validated by the client.
They are responsible for ensuring the software functions correctly, fixing any bugs that arise, and maintaining the software afterward.
Working method: agility and iteration
The work is divided into time blocks called sprints.
Typically, a sprint lasts about two weeks. During this period, each member of the project team has specific tasks to complete.
The project manager ensures that everyone stays on track.
If a team member encounters difficulties or starts falling behind, the project manager is responsible for finding a solution to keep the project moving forward.
At the end of each sprint, deliverables are presented to the client, such as the software’s site map, the user journey, or a demo of the software.
During these presentations, the client can validate all or part of the work done.
If any changes are needed — for example, on the wireframes — the designer processes the client’s feedback and presents the updated work during a new meeting.
This way of working is called iteration:
- Design
- Feedback
- AdjustmentValidation
This cycle repeats until the final product perfectly meets the user and client needs.
You might also be interested in: What are the impacts of implementing a UI kit?
Conclusion
A digital project brings together a diverse set of skills and profiles.
The project manager ensures the smooth running of the project. They rely on their team to meet the client’s needs. Both the client and the target user are key players.
Working in an agile and iterative way involves all stakeholders in the project and helps keep the timeline on track. It allows potential issues to be identified quickly, preventing delays or other setbacks.
Are you looking to redesign your website, create an application, or develop software? I can guide you through this project. Discover my services in detail by clicking here.