From a developer to an architect, roles should be considered

Keep many different components in your mind.

Have a knowledge of how they work and communicate.

Focus on the big picture.

You now should focus on a wide-range interaction between multiple systems.

A high-level understanding of changes impacts:

• Will it impact the performance?
• Will it causes another component to behave differently?
• Will it expose new bugs?
• Will it impact multiple levels?
• Will part of the system need to change?

Teacher rather than director :

Work with developers, and help them to understand the facts that lead to a solution, Help them to come to the right decisions on their own.

Learn and experiment:

Step back and spend time learning and growing take time to write software that never going to be used in order to try new ideas, this valuable time gives you the knowledge and experience and new tools and techniques that may be helpful for the team in the future.

Help to make better decisions, procedures, and policies for the team.

sources