Continuously, the following decisions were driven by process optimisation, team scalability, cost-effectiveness and technology feasibility factors.
a) Hire a project manager
The amount of operational work was excessive enough to bring a new role in the team. Among other responsibilities, the primary duties for the new project manager were receiving and defining the brand and product design requests, assigning the job to a designer depending on the skills required and the workload. Consequently, designer's were able to focus directly on their design tasks.
b) Centralise requests to the Design Ops - Project Manager
The team director and project manager worked closely to plan the week by putting all the ongoing tasks, upcoming projects and follow-up tasks. This plan was then translated to the team members during the weekly sprint meeting. Designers were encouraged to give feedback about their proposed task plan for the sprint, so they could actively commit to the deadlines. Although stakeholders kept sending requests through several channels, they were all redirected to the project manager who could act as first filter on defining the briefing and, depending on urgency and estimated work time, place the request on the backlog to be reviewed in the planning meeting.
c) Move to Jira and scrum methodology
Although design activities have their particular needs different from other teams, an investigation into the best practices of using Jira for designers concluded that this platform has great potential — not just to be aligned with other members, but also to empower the team to be task-effective and scalable.
We adopt a mix of agile methodologies where we plan with one-week timeframes in mind, but at the same time, remain flexible enough to bring last-minute tasks to the schedule. Brand and product designers created their board with all team tasks. Product designers linked their tickets to their pertinent squad team. They could participate in the ongoing tickets through comments and sharing files, but also by keeping all the squad members up-to-date with the design status.
d) Reorganise Google Drive and set rules
The design team was gathered to discuss their needs and how they could organise the material in a clear and straightforward folder system. Once they collected everyone's ideas of best practices, inputs and comments were put into place through a system tree outline. They also defined a naming convention, to keep the system organised and speak the same language.
The team's commitment to developing this new procedure was so strong that even just one month after implementation, the team reviewed the usage of this system and they unanimously agreed they had seen a significant improvement in their jobs. Designers could now find their teamwork effectively without spending too much time maintaining it.
e) Automate design tasks tracking
We connected JIRA to our existing design tracking google sheet via JIRA API, to be able to have an updated detailed overview of the design tasks per designer and project (E.g. the stakeholders with the highest design demand, design requests received by the city, projects associated with OKR's, etc.)
Having real-time quantitative data in context was a massive step for the design team. It allowed to quickly prepare any kind of reports (e.g. risk assessment reports), enhance decision-making, prove that all the projects were aligned with business objectives and priorities and optimise processes continually.