One of the responsibilities for an architect is to provide a space that is usable and enhances the possibilities for what you do. But mostly, museums are just the opposite; they're horrible spaces, anti-art, they can't be used. They can't function, they overwhelm it. So in a way, they become objects in themselves many times, almost sculptures, and they get a lot of aggrandizement out of it...In terms of Bilbao, the one difference there is that they did not really want a museum, they wanted a monument. They wanted a thing that would bring people to the Bilbao.
The traditional process of delivering design, vs. delivering design just in time.
Designers are often working at least one sprint ahead of engineers. While one sprint might not seem like much of a lag, a typical product team learns a lot after the design hand-off. ...Instead of working ahead, we should finish designing as close to the end of a sprint as possible: just-in-time design.
Get embedded in the team. Designers should use sprint planning, grooming, standup, and retro as opportunities to provide design to — and receive feedback from — the rest of the team. Designs can take the form of written or verbal descriptions, not just wireframes and high-fidelity mockups.
Only design what’s needed. Use constant communication between engineering and product partners to understand what your collaborators will need next. Then, plan on delivering only what is needed, and nothing more. Use the agile process — grooming, planning, and retro — to find any shortfalls or excesses.
Avoid creating a backlog of designs. Designs don’t age well. In the time between finishing design and shipping code, it’s likely that you’ll learn something new that changes your understanding. If you’re producing more design than can be implemented, focus more on the quality of each design.