|
|
|
|
|
|
by kneebonian
1097 days ago
|
|
|
I'm in this stage right now. I'm being moved from an engineering to being trained for an "architect" role, and it sucks. I look at my todo list and most of it involves emailing somebody about something, or preparing a presentation for some council. It feels like I can't actually do anything. Like when I was an engineer, boom move get things done produce actual results, something would be deployed and value would be delivered, now, if I want to get something done, engage with two or three other teams to do something, talk with their team leads, then the actual engineers, then have a meeting to actually discuss requirements, and what should be a simple program that takes 3 api calls, turns into a 3 month long project. |
|
|
Do all of the meetings/emails have to happen serially and in that order? If so, why?
Maybe look up what Amazon does with its 2-pagers and 6-pagers. See if you can do something similar where you are.
If it's really such a simple solution and that's obvious early, can you propose the obvious solution when you see it and get reactions?
If you're the only architect, you may have to define some of this stuff and make your changes part of the corporate culture.
If you have any PM buddies (whichever type of P), ask them for advice. A lot of this is their bread and butter, and if they already know your org, they'll have special insights.