A good friend once told me that she knew the exact day when she went from adolescence to young adulthood: it was the day that she realized that saying "no" to her mother was, at that time and in that place, the absolutionly postively right thing to do.
In a certain sense, the word 'architect' is not well understood or well defined. Different organizations are struggling with just how much power or control an architect should have. To be effective, an architect must have absolute decision rights over some aspects of systems design, but they must not have that right at all levels below that.
In other words, just because the architect decides that System X is composed of components A, B, and C, that doesn't mean that the architect can, or should, design the components. The component designer (or sometimes application designer) should design the components.
I'm not saying that the long list of people with architect next to their name doesn't contain folks who can do more. Not that at all. Every architect probably has some skill in application design.
What I am saying is that, for large projects, or in the case of enterprise architecture, there needs to be a clear understanding of where architecture ends and application design starts.
And then, for the folks who work inside the fantastic and sometimes naieve boundaries defined by their architecture, the snooping of the architect becomes meddlesome, irritating, and unwelcome.
Let your designers shine. Start by getting out of their way.