Archlist

Work the improvements into the established direction rather than around it, and make every change one that could be argued for in the client's own terms.

This was the most constrained brief in this portfolio, and the constraint was the interesting part. The identity — the script wordmark, the navy, the topographic ground, the section titles set as watermarks — was not up for discussion, and neither was the overall shape of the product. Colour, typography and the general feel of the thing were the client's own work and they were closely attached to all of it. Proposing a different direction would have been the wrong instinct as well as an unwelcome one. So the case for each change was made in the client's language and against their own goals: legibility for their clients, fewer places to look, less repeated data entry. That case rarely landed the first time it was made. Most of it was put, reviewed, set aside, and brought back in the next meeting with the reasoning rewritten around something the client had already said they wanted — over a long run of those meetings. The phase timeline is where the method worked best. It keeps the ornament and the profession's own vocabulary, and adds a state model underneath it — a phase lights up when a document is filed against it, and the furthest lit phase is marked as where the project has reached. The architect gets their chronology; their client gets a progress indicator; nothing about the look had to change to get both. That last clause is why it was accepted. The same method runs through the rest. The object catalogue carries the fields a specification actually needs — type, sub-type, manufacturer — with the file thumbnails and their overflow count shown on the card, so a card answers a question rather than inviting a click. Inspirations sits next to an image generator, which is the client's idea, given a place in the flow where it supports the moodboard rather than interrupting it.