That's too context-specific to answer without a whole lot more questions. Plus, if we're actually talking about code, physical metaphors break down anyhow. First-cut answer is "move bathrooms closer"/"make the hallway bigger" but one must also ask the question, "How did this mismatch arise in the first place?" Anything is possible, especially in software; the hallway may in fact be adequate and it's everything else that is grossly overspec'ed... or in fact, you might have ended up with a poorly-designed dining room for 100 people because that's all the previous guy knew how to build, when in fact you need a stadium for 100,000 people. (I've been there before.)
Ideally the architect is looking at a 'proposed' plan rather than what got implemented.
There is an entirely different (and very valuable) class of folks to can take an existing screw up and map out a series of steps to un-screw it up [1]. :-)
[1] I used to watch the New Yankee Workshop on PBS and see Norm cut lumber and then have it fit together so closely and smoothly that it practically didn't need glue. I suggested to my wife we could make a TV show which explored creative uses for a 2 x 4 that was 1/2" too short for its original purpose, or other parts that were made scrap by an imprecise execution of the 'cut to size' phase.
