I've proceeded with my career keeping those on mind:
- listen to what people say, you can't and won't be an expert on everything
- when you listen to them - verify and deepen your knowledge on topic, it's good to be able to connect dots
- be a practitioner - there's nothing worse than an architect that doesn't know how to code/configure server etc ;)
- attend both developer teams' demos, plannings and product teams' meetings - context is king and as an architect you have to see things both broad and narrow connecting technology with business needs
- be realistic - most businesses don't need super-high-tech-microservices-based-kubernetes-mesh-powered architectures ;)
- remember that architecture is about structure, guidelines, policies and order that aligns with business needs (so this is the starting point - understanding what business tries to achieve). Technologies really don't matter - they are just a tool
- always assume that you don't know everything - challenge your own assumptions
- be authentic and polite - people don't like super-star-asshole-know-it-all-architects (been one, don't recommend that :))
Good luck!