#NoMeetings for Frontend Specialists

by | Nov 14, 2023 | AIDA, team | 0 comments

By Jose María Santos, Front-end Tech Lead at AIDA.


The article presents the implementation of the #NoMeetings initiative in the front-end specialist area of AIDA. To avoid silos, they have a front-end guild where they hold various ceremonies such as discussions on UI/UX standards, code review and retro. With the global initiative #NoMeetings they aim to optimise communication and reduce face-to-face meetings. They have migrated the minutes to Confluence to create customised templates per meeting, including types such as “Code review” and “UIUX minutes”. This management has facilitated the search for information and allowed colleagues to review what happened during their absence.

In today’s article, I would like to present how we have applied the #NoMeetings initiative within the front-end specialist area of AIDA.


The AIDA team is composed of back-end, front-end and full-stack developers. Within our organisation, a few of us specialise in front-end and the vast majority of our colleagues are C# developers.

To avoid silos, we have a front-end guild in which we have several ceremonies:

  • Guild
  • Standards
  • UI/UX discussion
  • Code review
  • Retro

In all of them, notes were taken in Google Docs and tasks came up that most of the time were forgotten until the next meeting or had to be followed up with third-party tools.

AIDA was committed to improving and getting more out of our meetings, so we started working on the “We can work better” initiative (at a global level) with the help of Javier Rubio. With this initiative, we aim to optimise the flow of communication and reduce the number of face-to-face meetings.

Due to its recent creation, we must clarify that our Front team joined the initiative once it had already started, so our experience was different from the rest of the AIDA teams but no less enriching for that.

How do we improve the flow?

The first thing we did was to sort through all the minutes we had from our meetings and migrate from Google Docs to Atlassian’s Confluence. This allowed us to create customised document templates per meeting.

We have several types of minutes:

  • Code review” is a simple template type in which little data is recorded, but the table allows us to visualise, in its corresponding section, a status report.
  • Acta UIUX” is arguably the queen of templates. It is so comprehensive that we have added a table of contents for easy navigation. It includes excerpts from the previous meeting, a section to summarise the current meeting, which the next meeting will be linked to as the previous one, Jira boards, a Miro and a decisions section.

All our templates usually have a decision section, this is very useful, as we have a section in our space, where we list all the meetings of the month and all the decisions taken at the meeting.

All this management is not time-consuming in general terms. The investment is made at the beginning to analyse the type of meetings and generate the templates. But the great benefits that it has brought us is to facilitate the search for information and even, in a period when a colleague has been on holiday, it has been really easy to check what has happened in his absence by consulting the different reports that we have.

In short, the #NoMeetings initiative has strengthened collaboration and transparency in our team, paving the way for more productive and focused work.

Selección de consentimientos