<aside> 🤓 I’ve been a manager for over a year now, and been enjoying it every day.

</aside>

my team.jpg

Design core principles

**We are a thinking house,

not a factory**

We bring the most value by helping the wider business with strategic thinking in early stages of projects and streams of work.

We are enablers to help formulate and visualise ideas, but we also bring everybody together with other core decision makers to perform proper product thinking and shape solution in a smart manner.

We help reduce wasted code

We support insights and discovery stages by creating efficient prototypes to be tested in order to and get meaningful feedback and to iterate in an efficient way.

**We automate, reuse

and improve**

Ensure that design is contributing to max efficiency of broader squads through an ever evolving design system that is bridging the gap between development, product management and product design.

We know our customers,

their needs and background

Everything we do is centred on our customers and tailored to their needs and constraints. Once a problem is identified, we know how to best address it so it’s customer first.

We stand out and we look professional

Through our unique branding and design language, we stand out from our competitors and have a strong language that helps customers recognise Nurole when they see our content.

Discovery

Insights

We want to create a strong relationship with insights to make sure we are aware of our members and clients behaviours and trends on our platforms. We also should be able to work together in speaking with them on a regular basis for projects that we are working on as well as helping for business cases that we might want to advocate for with the rest of the business.

Ideation

We need to be involved early in any project process so we can make the most of our skillset. We are able to support the teams on various topics and types of delivery formats. That will also help us be in charge of a journey from beginning to end and make sure it makes sense and will be straight forward for our members and clients.

Keep colleagues in the loop

We have started to put feedback sessions in place with the rest of the business so that we could be able to share work in progress as well as get very useful feedback. That helps us share what we work on, how we work and what design entails. But that also helps us get incredibly valuable insights from our colleagues who are constantly speaking to our clients and our members and therefore will potentially have a much more focused way of seeing things through our user base eyes and way of thinking.

Another thing that is very valuable is that people come from vary different backgrounds, have a wide range of skills and different ways to see things. Often we have found that speaking to our colleagues in BD, CS, Marketing or Ops will raise questions that we don’t necessarily think about the first time, but also they will see things that we don’t really see anymore as we have potentially been working on the same prototypes for many hours and need fresh eyes on them.

Iterations & feedback

After having participated in the feedback analysis we are able to action prioritised feedback from any observation sessions that will happen. Feedback should never be seen as a painful point in our processes, it is always a way for us to progress and grow as a function.

Delivery

All work being done with engineers and PMs should involve discussions early on in the process. That will allow us to advise on where design can help: information architecture, strategy, user journeys, ideation session, screen flows, wireframes, prototyping, high fidelity design, etc.

The earlier design are involved, the more meaningful the work will be for our team because we will know all the context on the projects and will be able to help in the most efficient way.

In the past we have sometimes been involved too late in the decision making process which has led us to be disappointed with solutions that could have benefited from our help. (e.g. Auth user site map, hierarchy, journeys, and screen flows).

Design ops