Architectural Design Fundamentals Case Studies
Creative5 Case StudiesUpdated Sep 2026
These five case studies come from fictional practices working on libraries, schools, community halls, and mixed-use buildings. Each one follows a project through a point where the brief, the people who would use the building, the production limits, and the feedback from reviewers stopped agreeing with each other. The cases are not models to copy. Read them as a colleague would describe a hard job: what was known, what was assumed, which signals were trusted, and what changed once the evidence arrived. Figures are internal to the fictional firms and show scale only.
Case Study 1
A library brief that asked for everything at once
Corliss and Marr Architects, a nine-person practice in a river town that designs libraries, schools, and small civic buildings.
The situation
The Tallow Creek branch library had been operating out of a converted bank for many years, and the board wanted a renovation that would serve three groups. Teenagers, many of them after-school regulars, wanted a space that felt like theirs, with saturated color and loud furniture. Older patrons asked for quiet reading rooms with acoustic control. The county historic review board wanted the street facade to read as civic and restrained. The brief arrived as a list of twenty-two requirements with no ranking, and the board wanted a visualization for a public meeting in three weeks. Danielle, the project lead, had a budget that covered two-thirds of the interior scope they were describing.
The challenge
The requirements did not just compete on the surface. Loud color and acoustic quiet work against each other in a single reading room, and the historic review board would likely reject any facade that used the teen palette. Danielle had to decide which requirements defined the concept and which would be translated into evaluation criteria the board could score. Without that step, the visualization would show a building that tried to be everything and satisfied no one at the meeting.
Analysis
Teams grounded in Architectural Design Fundamentals usually start by separating the creative brief into a concept statement and a set of tests. Here the concept came from the audience overlap rather than from a style. Danielle grouped the twenty-two requirements by the people they served and found that most of the teen and older-patron items shared one need: a place with clear zones and a visible threshold between them. That reframed the concept as a building that makes its own sound zones legible, with the street facade carrying the restraint the historic board needed. Ranking the groups by actual use then decided which requirements the concept carried.
The production side pushed back as well. The construction documents were already scheduled, and the structural grid could not carry the open ceiling the teen zone wanted without a steel upgrade the budget did not cover. Ravi, who ran documentation, proposed holding the ceiling height and using a lowered acoustic soffit over the reading room instead. The review feedback came in two rounds. The board's first comments focused on the color palette, which made the concept look like a compromise. The second round asked for the criteria to be scored in the room instead of by the architect alone. Each round tightened the criteria rather than the design.
- Group requirements Sort the twenty-two items by the people each one serves.
- Rank by use Weight each group by how often it used the branch.
- Define the concept Keep five requirements that the concept must carry.
- Score the rest Turn remaining items into weighted criteria for review.
Actions taken
- Rank the twenty-two requirements by which group they served and how often that group used the branch, then mark the five that define the concept. The remaining items become scored criteria with a weight.
- Write the concept as one paragraph that a board member could repeat at a meeting, and attach the scoring criteria beneath it so the visualization is judged against the test the team used.
- Test the zone separation with a physical study: foam or cardboard massing of the reading room and teen area, checked with two staff members and three regular patrons before the drawings were revised.
- Hold the scoring session with the historic review board's staff present, and record each comment against a criterion so later changes trace back to a stated reason rather than a preference.
Results
The visualization went to the public meeting in the third week, with the concept in one paragraph and the criteria printed beneath it. The board scored the design against the five defining requirements and approved the schematic on one condition: the teen zone had to be visible from the circulation desk. The lowered soffit met the reading room acoustic target, and the steel upgrade came out of the budget. Documents were issued by the end of the quarter. The palette stayed bolder than the historic board first wanted, but the facade stayed restrained, as predicted.
Questions for discussion
- Which requirement in your own brief would you have ranked first, and what evidence would have changed that ranking?
- How should a team decide when a client's stated preference and the audience's actual use point in different directions?
- What would you need to see in a scoring matrix before you trusted it to judge a design?
Case Study 2
Revision loops stalled a mixed-use drawing set
Harrow Lind Studio, a twelve-person practice that produces drawing sets for mid-sized residential and mixed-use projects.
The situation
The Maple Row project was a six-story building with retail at street level and forty-eight apartments above, and the documentation set was due to the permit office in six weeks. Harrow Lind had a documentation team of five, two external consultants for structure and mechanical systems, and a shared file server that nobody fully trusted. In the first month the team logged 214 revision markups across the set, and about a third of them came from working on superseded sheets. Ines, the production manager, noticed that the level three plan existed in three versions with different wall types. The lender's reviewers had marked up the older version, so the feedback was already stale.
The challenge
The problem was not the number of revisions. A set that changes is normal in a building this size. The problem was that nobody could say which sheet was current, so the consultants were redlining drawings that the documentation team had already replaced. Each handoff added a day, and the permit date did not move. Ines needed a way to slow the loop down enough to control versions without slowing the people who had to make the changes.
Analysis
A drawing set is a creative brief in its own right, since it carries intent to readers who were not in the design meetings. The audience here was the permit reviewer, the lender's technical staff, and the contractor who would price from the set. Each group needed a different thing from the same sheets: the reviewer needed code detail, the lender needed the unit mix to match the financing, and the contractor needed wall types that were unambiguous. Treating the set as one deliverable hid that. Once each reader's first check was listed, the version problem became a matter of which sheet was authoritative for whom.
The production constraints were tighter than the schedule suggested. The consultants worked in their own model files and exported PDFs on Fridays, so a change made on Tuesday could sit unseen for four days. Review feedback arrived as markups on prints, which the documentation team then had to transcribe into the model by hand. Tomas, the BIM coordinator, found that about one comment in five referred to a sheet that had already been superseded. The feedback was accurate in intent but stale in location, which is the most expensive kind of review comment because it looks valid until someone checks the sheet number.
Actions taken
- Give every sheet a version code in the title block that combines the issue date and a revision letter, and lock the superseded set in a read-only folder the day a new issue goes out.
- Set a single Friday cutoff for consultant model exports, and require each export to carry a transmittal sheet listing the sheet numbers and version codes it replaces.
- Move markups onto a shared review log keyed to sheet and version code, so each comment is checked against the current issue before anyone edits the model.
- Run a short triage each Monday with the production manager, the BIM coordinator, and one consultant lead, clearing stale comments first and assigning the remaining changes by discipline.
Results
Stale comments fell from about one in five to a handful each week within the first month, and superseded sheets stopped circulating once the log was live. The level three plan now has one authoritative version, and the wall types were reconciled with the structural and mechanical consultants. Revision markups for the rest of the set fell by about a third. The permit package went in on the due date with a transmittal sheet listing every version, and the lender's reviewers returned only two comments. Ines kept the Monday triage because it cost almost nothing.
Questions for discussion
- Which of your recent drawing or document sets had a version problem, and how would you have recognized it earlier?
- Where in your own workflow does a handoff add time without adding any check?
- How much version control is enough for a team of five, and at what size would you add a formal change log?
Case Study 3
Two facade directions split the riverside neighbors
Penrose Mill Studio, a seven-person practice in a river town that designs community sports, arts, and civic buildings.
The situation
Penrose Mill was asked to design a combined sports hall and arts studio on a vacant riverside lot. The city parks department wanted a building that would draw young families and teenagers, and the steering group wanted it to belong to the surrounding streets. Two directions came out of the early sessions. Direction A used warm timber and brick, echoing the older houses across the road. Direction B used pale glazing and perforated metal, drawn from a nearby pump house. Both were shown at two open houses, which drew 186 and 240 residents, and an online survey returned 312 responses. Mira led the design team, and Hal handled the parks liaison.
The challenge
The open houses gave the team strong reactions in both directions, which was the hard part. Older residents, many of them near the lot for most of their lives, read Direction B as a warehouse and said so. Younger attendees liked it in person, but the youngest survey respondents leaned toward timber by a narrow margin. Mira had to decide whether the reactions reflected the building or the way the two boards had been presented, and whether the survey could be trusted at all.
Analysis
The brief described a building that belonged to the street, and that phrase carried two meanings that the team had not separated. One was resemblance: the building should look like it came from here. The other was use: the building should be used by the people who lived here. Direction A answered the first meaning and Direction B answered a version of the second, since its glazing was meant to show activity from the road. Testing the directions against both meanings made it clear that the brief had been written as one requirement when it was really two.
The production constraints favored the metal option on cost and lead time, and the team could not ignore that. The timber build needed a specialist installer and a longer procurement window, which put it at risk for the grant deadline. Review feedback from the steering group was unusually useful because it separated the two complaints. The older residents objected to the look of Direction B, while the parks staff objected to its maintenance profile. Hal pointed out that the perforated metal would need cleaning every season near the river, which the department had not budgeted. Both objections were specific, and both could be tested before a decision.
Actions taken
- Split the survey results by age band and by distance from the lot, and report each cut separately so the youngest respondents and the nearest neighbors are not averaged away.
- Run a short A/B walk-through with a dozen residents, showing each direction at street scale on the same board layout, and ask them to describe the building in their own words before rating it.
- Price the metal option with the cleaning cycle included and ask the parks department to confirm the maintenance budget in writing before the steering group votes on material.
- Propose a hybrid for the second round, with timber at street level where residents meet the building and perforated metal higher up, where it reads as a distant screen and needs less frequent washing.
Results
The second round went to the steering group with the hybrid as a costed option beside the two originals. The survey, cut by age and distance, showed the nearest neighbors objected most strongly to Direction B, while the youngest respondents were split. The walk-through residents described Direction A as familiar and Direction B as unfinished. The steering group chose the hybrid with timber at street level, and the parks department accepted a maintenance schedule for the upper screen. The decision added about two weeks, which the team absorbed by starting timber procurement earlier.
Questions for discussion
- When two directions draw opposite reactions, what would make you trust one reaction over another?
- How would you word an open house board so that residents compare the buildings rather than the presentation?
- At what point should a steering group stop testing and commit to a direction, and who should decide that?
Case Study 4
A school extension grew past its original brief
Alder Point Design, a fourteen-person practice that does school additions, clinic fit-outs, and small civic work.
The situation
Alder Point took on a two-classroom extension for a primary school under a fixed fee of 146,000 for design and construction administration. The agreed scope covered two classrooms, a toilet block, an external play canopy, and a refreshed entrance. Early in the design phase, Ayesha, the principal, asked for an art room, a serving kitchen for a breakfast program, and a staff room moved to the new wing. Teodor, the district facilities officer, then asked for a larger accessible toilet to meet the district's own standard. By the end of the first design review, the floor area had grown by about a third, and requests kept arriving by email.
The challenge
The fee had not moved, and neither had the completion date. Every addition was reasonable on its own, and each one made the building better for the school. The difficulty was that the contract defined scope in a short list, and the list did not say how to price a change or when a change had to be approved. Gwen needed to protect the quality of the classrooms, which were the reason for the project, without turning every request into a fight with a principal who had a point.
Analysis
Scope creep usually begins as a good idea from the people who will use the building. The original brief described the classrooms by pupil numbers, but the principal was describing the school day: where breakfast happened, where art could be messy, where staff could take a break. Those are audience needs, and they are not wrong. The mistake was treating each one as a separate addition rather than as evidence that the brief had underdescribed the building. Naming the activities as well as the rooms gives a team a basis for sorting requests into those that fit the design intent and those that need a new decision.
Both the fixed fee and the fixed term start made each request expensive in its own way. The toilet upgrade changed the drainage run and the structural opening in the wall the team had already detailed, so the redesign touched two consultants. The kitchen servery needed a grease trap and a separate ventilation route that the budget did not include. Review feedback from the district was precise: the accessible toilet had to meet the district standard, but the review comments came back as a list of items with no costs attached. Gwen treated that list as the first draft of a change register, not as a set of instructions.
- 1Request loggedWritten down with the requester and the reason given.
- 2Effect pricedCost, schedule, and affected consultants estimated.
- 3Options offeredTwo or three packages presented within the fee.
- 4Decision recordedApproved, deferred, or declined, with the reason stated.
- 5Quality checkedCore rooms confirmed against the original specification.
Actions taken
- Write a change register with one line per request, showing the cost, the schedule effect, the design owner, and the decision date, and send it with each design review agenda.
- Price each request as a separate option, and present the principal with a choice of two or three packages that fit inside the fee, rather than a single yes or no.
- Ask the district to confirm in writing whether its accessible toilet standard was a requirement or a preference, and whether a funding line could cover the added drainage work.
- Protect the two core classrooms by holding their size, daylight, and finishes at the original specification, and state that protection in the next approval so the extras cannot draw from them.
Results
Ayesha chose one of two packages: the art room and staff room move went ahead, and the servery moved to a later phase with its own budget. The accessible toilet was built to the district standard, funded through a separate allocation the facilities office found in the second week. The classrooms kept their original size and daylight. The change register closed with 14 approved items and 3 deferred, and no request was approved without a stated schedule effect. Gwen noted that the principal valued the written options more than the final layout, which she counted as a useful result.
Questions for discussion
- At what point in a project does a series of small requests become a change of scope that needs a new fee?
- How would you explain a deferred item to a client without suggesting the original design was incomplete?
- Which parts of a brief should be treated as fixed, and who on your team should be allowed to say so?
Case Study 5
A community hall motif raised consent questions
Sable Ridge Collaborative, a six-person practice that designs community and cultural buildings alongside local partner groups.
The situation
Sable Ridge was commissioned to design a community hall for a river town, with a main room for markets and classes and a sheltered entrance court. The town council wanted a feature screen at the entrance that would express local identity. Nia, the project designer, proposed a screen based on a band pattern that a local weaving cooperative had used in its cloth for generations. An access review was also due, since the wayfinding relied on color-coded panels with small type that the seniors' group said they could not read from the door. The hall was expected to receive about 380 visitors each week, and some would arrive by wheelchair or with low vision.
The challenge
The screen raised two questions the team had not planned for. The pattern belonged to a cooperative whose members had never been asked whether a council building could use it, and the cloth itself carried meaning for specific families. At the same time, a screen placed at the entrance would be the first thing visitors met and the thing most likely to make the wayfinding harder to read. Nia needed a decision that respected the cooperative, served the access requirement, and did not quietly drop either.
Analysis
The creative brief asked for local identity, a phrase that hides a question about whose identity it is. A band pattern that appears in a community's cloth is not a neutral motif, and the people who made it may hold rights of attribution and of refusal that a design team cannot assume. The audience here was broader than the council: the cooperative members and the visitors who would walk under the screen every week. Nia made their needs the first constraint, not a consultation scheduled after the concept was fixed. That changed the question from whether the pattern could be used to how its use would be agreed, credited, and limited.
The production constraints were modest but real. The entrance court had a fixed footprint, and any screen would sit on the route that wheelchair users were expected to take, so its depth and clear width mattered as much as its pattern. The access consultant, Desmond, reviewed the mockup and found that the screen's openings would cast a rhythmic shadow across the threshold, which could confuse low-vision visitors judging the step. Review feedback from the cooperative was the most direct: members wanted the pattern shown at reduced scale on a panel that credited the source, not placed as the hall's main image. Two concerns were met by one change.
- First weekCouncil asked for an entrance screen expressing local identity.
- Second weekCooperative consulted, with terms and a credit line drafted.
- Fourth weekFull-scale access test exposed the threshold shadow problem.
- Sixth weekRevised screen and credit panel accepted by all parties.
Actions taken
- Hold a working session with the cooperative before any further drawing, with the terms of use, credit line, and any refusal conditions written down and signed by the coordinator.
- Commission the access consultant to test the screen at full scale, including the shadow pattern on the threshold, and record the result as a design condition rather than a note.
- Replace the color-coded wayfinding with high-contrast panels, larger type, and tactile markers at the entrance, and check the sign heights against the accessibility standard the council already applies.
- Put a credit panel beside the screen that names the cooperative, describes the source pattern, and states the terms of use, and list the same credit in the hall's published materials.
Results
The cooperative agreed to a scaled version of the pattern on the screen and a full credit panel, with a clause letting members withdraw use if terms were breached. The access test showed that the original screen density cast a shadow strip that low-vision users could mistake for a step, so the openings were widened. The sign system was redrawn with high-contrast panels and tactile markers, and the council accepted the revised standard for its other buildings. The hall opened with a credit panel that visitors read more often than expected, and the cooperative asked to join the next project.
Questions for discussion
- What obligations does a design team take on when it uses a pattern that belongs to a living community?
- How should an access review be scheduled so that it changes the concept rather than only the signage?
- When a community group sets terms that limit the design, how do you decide whether the limit improves the work?
Learning Resources
Creative CASE STUDIES
China, India, United States, Indonesia, Pakistan, Nigeria, Brazil, Bangladesh, Russia, Japan, Mexico, Philippines, Vietnam, Egypt, Turkey, Germany, United Kingdom, France, Italy, Canada, South Korea, Australia, Spain.