↘︎ On Leadership
↘︎ Building comprehensive systems comes with a lot of human interaction and errors. Amending, adjusting, and fixing is the way forward.
↘︎ In smaller teams, it's more obvious than in others when the errors are more visual. In a bigger team, the errors are more functional. Regardless of who discovers it, add the note to fix it. Two examples of the remote team we have a chance to serve.
↘︎ One where blame and backstabbing were a daily ritual—the toxic culture led to several people leaving depleted and almost hating the design overall. You know this presentation: Nothing is right after screen two. After six months, four designers left, and no one wanted to join the team.
↘︎ A very different team of 12 designers and 45 engineers created the proposition leading to Beta Release – every comment on Figma led to simplification and standardisation. Once agreed, it was added to the global Design System, and everyone was informed of the change and implications. Within less than six weeks, the team was able to build the E2E proposition, including the Design System and Knowledgebase reflecting 5 entry points, and two different colour modes on 3 different devices.
↘︎ Do not spend the time on blame.
↘︎ Spend time on creation.