Ask HN: I've been promoted to Architect. What do I need to learn/do to excel?
Congrats!<p>1) learn to say no<p>2) learn to make simple enforcable short, medium and longterm goals (ie, everyone must be on platform x by november)<p>3) learn to listen<p>4) learn to love small incremental changes rather than big bang<p>why say no? because you'll be bombarded by brilliant solutions. On their own will be great, but in your environment will be tech debt. Or you'll be asked to allow team x to use a new widget, instead of the old one. But then team z will want to use a different new widget to do the same thing.<p>Clear goals that we widely communicated allow normal people to make design decisions autonomously. It can really remove the need for constant daily updates and information overload (for you)<p>Some of the best insight into a product or thing will come from a junior whos only just joined. Make sure you have regular contact with all the teams, if only to steal ideas.<p>Large changes almost always fail. smaller incremental changes always feel less thrilling, but when you look back over a year, they will accomplish a lot more. Plus its far easier to course correct.